Live General Ledger & Controlling demo — journals, trial balance, budget-vs-actual variance and financial statements.
Talk close & controllingAccounts Payable
Finance-owned invoice-to-pay slice of Procure-to-Pay
Mette Holm
Group Controller
AP Workspace - invoice capture, match, post, accrue, pay
Built from the Finance AP handbook: AP is inside Finance, but depends on Procurement, Warehouse, Treasury, Controlling, and GL/R2R.
Open AP
DKK 5.7M
unpaid supplier liability
Touchless rate
50%
posted or paid without exception
Exceptions
3
match, coding, or bank-control work
Next payment run
DKK 4.7M
eligible posted invoices
Create an AP invoice
This is the missing practical part: capture invoice, code it, then post it into GL.
Posting impact preview
Select an invoice below. Demo-created invoices can be posted and then appear in GL Journals.
AP document
AP-4472
Cost object
CC-200 Warehouse
GL entry
JE-4472
| Account | Debit | Credit |
|---|---|---|
| 5000COGS | DKK 3,280,000 | - |
| 2200VAT payable | DKK 820,000 | - |
| 2000Accounts payable (AP) | - | DKK 4,100,000 |
Effect: debit expense or inventory + debit VAT, credit Accounts Payable. The AP open item then moves into the payment run and GL/R2R close evidence.
End-to-end ownership map
The same P2P record moves across departments; AP owns invoice-to-pay, not the whole chain.
Need -> PR -> PO
Approved request becomes a controlled PO with supplier, price, tax, terms, and cost object.
System: SAP ME51N/ME21N - D365 Purchase requisition/PO
Control: Approval matrix, release strategy, PO compliance
Goods / service receipt
Warehouse posts GR or service entry so AP can prove the supplier delivered before payment.
System: SAP MIGO/ML81N - D365 product receipt
Control: Receiver separated from requester and payer
Invoice capture
Supplier invoice arrives by PEPPOL, EDI, portal, OCR, or AP mailbox and becomes an AP document.
System: OCR/e-invoice inbox - SAP MIRO/FB60 - D365 vendor invoice
Control: Duplicate check, supplier identity, PO lookup
Match and exceptions
3-way match PO vs GR vs invoice within tolerance; non-PO invoices need coding and approval.
System: SAP MRBR - D365 invoice matching
Control: No-PO-No-Pay, tolerance keys, exception reason codes
Post liability
Matched invoice posts AP liability, VAT, expense/inventory, and cost object into the GL.
System: FI-AP reconciliation account -> GL
Control: Preparer not approver, balanced debit/credit posting
GR/IR and accrual
Goods received not invoiced and unbilled services are accrued so liabilities are complete at close.
System: SAP MR11/F.13 - close cockpit
Control: Period-end completeness review, auto-reversal next period
Payment proposal and run
Treasury funds the run, AP proposes, approvers release, bank file is sent, remittance issued.
System: SAP F110 - D365 payment proposal/journal
Control: Four-eyes payment release, bank-detail callback, positive pay
Vendor statement recon
Supplier statement is reconciled to AP ledger to find missing invoices, unapplied credits, stale items.
System: Vendor open items FBL1N - AP aging
Control: Open-item clearing, aged-item ownership
Finance umbrella
Accounts Payable
Invoice capture, matching, GL coding, payment run, GR/IR, vendor statement recon
Accounts Receivable
Billing, open AR, aging, dunning, collections, cash application
General Ledger
Chart of accounts, journals, trial balance, reconciliations, statements
Controlling
Cost centers, budget vs actual, allocations, internal orders, profitability
Treasury / Cash
Cash position, payment factory, bank security, working-capital timing
Record-to-Report
Sub-ledger close, accruals, recs, consolidation, reporting, sign-off
The AP fraud point
Vendor bank detail is the attacked field. Any change blocks the payment run until callback verification on a known number. That is why AP, Vendor Master, and Treasury cannot be one unchecked click.
Invoice worklist
PO invoices inherit coding; non-PO invoices need GL + cost-object approval before posting.
| Invoice | Vendor | Lineage | Match | Amount | Status |
|---|---|---|---|---|---|
AP-4472 PEPPOL - due 28 Jun 2026 | Atea Denmark | S2PPO-3310GR-1186 | 3-way | DKK 4,100,000 | Posted |
AP-4475 EDI - due 24 Jun 2026 | Nordic Freight Lines | S2PPO-3361GR-1190 | 3-way | DKK 612,000 | Posted |
AP-4480 Supplier portal - due 02 Jul 2026 | Lyreco Office | S2PPO-3374GR-1192 | 3-way | DKK 186,000 | Exception Quantity variance over 5% tolerance |
AP-4482 OCR - due 26 Jun 2026 | Falck Service | No PO | non-PO | DKK 94,000 | Pending AI coding confidence 91%; awaiting cost-center owner |
AP-4486 Email - due 30 Jun 2026 | Baltic Components | S2PPO-3402GR-1204 | 3-way | DKK 740,000 | Blocked Vendor bank detail changed - callback required before payment |
AP-4468 PEPPOL - due 18 Jun 2026 | Copenhagen Facility | No PO | 2-way | DKK 128,000 | Paid |
Procurement handoff - what belongs where
This is why P2P is shown under Procurement but AP also exists under Finance.
Source-to-Contract
Procurement
category strategy, RFx, supplier qualification, contracts, price lists
Requisition-to-Order
Procurement
catalog/free-text PR, budget check, approval matrix, PO release, supplier transmission
Receiving
Warehouse / Operations
goods receipt, service entry sheet, over/under-delivery tolerance
Invoice-to-Pay
Finance AP
invoice capture, 2-way/3-way match, exceptions, posting, payment proposal
Cash execution
Treasury
payment-run funding, bank file release, fraud controls, cash timing
Close handoff
GL/R2R
GR/IR clearing, accrual completeness, AP ledger reconciliation, period lock
Controls and automation
World-class AP is exception-based: capture once, match/post by rules, route only risk.
No-PO-No-Pay
Non-PO invoices route to approval and coding before posting.
3-way match tolerance
Price +/-2%, quantity +/-5%, DKK 500 absolute floor.
Duplicate invoice check
Vendor + invoice number + amount + date before posting.
Bank-detail callback
Changed bank data blocks payment until verified on known phone.
Payment-run four-eyes
AP proposes; Treasury funds; CFO/Controller releases.
GR/IR close review
Goods received not invoiced accrual reviewed before period lock.