What’s inside: connections to your systems · step-by-step flow
The question this file answersHow many supplier credits are sitting unapplied because nobody found the invoice they belong to?
Fits: finance teams processing 500–5,000+ invoices a month.
Typical pattern, unmeasured — the finance playbook counts invoices (500–5,000+ a month for a mid-size firm), not credit notes, so we give no figure for them. Credits arrive in the AP mailbox beside invoices. Someone types vendor, amount and a reference into the ERP and hopes it finds the pair.
Before month-end close, the AP clerk’s list holds the orphans — a credit against an invoice you never received, a partial amount, a returns credit for goods still in stock — and nothing else. The paired credits are posted as drafts, and the close stops waiting for someone to find the pair.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
credit note matched to its original invoice before posting — same build as our supplier-invoice capture file; no published figure for credit notes
Before: someone types each credit note and hopes the ERP finds the pair. After: paired credits are posted as drafts; the orphans go to the AP clerk with the candidates shown. Percentage: none here — the AP range is the parent file’s.
No published benchmark isolates credit-note processing. The Ardent Partners and IOFM (2023) AP figures are about invoices and remain on the parent file — credits are not invoices, so the number does not move. Not a cash or DPO claim.
Your ERP stays — SAP, Oracle, Dynamics or the one that runs AP. This is the same capture build as our supplier-invoice file, with pairing added:
Unmatched credits. Commercial disputes. Returns that never reached stock. Tax coding arguments.
Not a cash or DPO claim.
Suppliers often omit or mistype the invoice reference — those credits are matched on vendor and amount only, and shown to a person rather than posted, which is why the orphan list will not be empty. Tax coding on a credit follows the original invoice; if that was coded wrongly, the credit inherits it and a person must catch both.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.