What’s inside: output checking · connections to your systems
The question this file answersHow many vendor invoices are we holding because receiving and the ASN never agreed?
Fits: multi-vendor retailers matching hundreds to thousands of invoices a month.
Typical, from the e-commerce playbook (vendor invoices): multi-vendor retailers see hundreds to thousands of supplier invoices a month, each resting on a receipt that must match. DC count, vendor ASN and PO sit in three systems; a clerk rebuilds the story by email before payment, worst before a season launch.
When the invoices arrive at month-end, AP finds the receipts already confirmed and a short list of open shorts and overs, each with the ASN and PO beside it. The receiving lead's argument with the vendor still happens — on a screen, not from an email chain.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
ASN, count and PO on one screen — the AP three-way build at the dock; no published figure for DC receiving
Before: the count, the ASN and the PO disagree and payment waits on a reconstruction. After: the three numbers meet on one screen and only the shorts and overs wait for the receiving lead. The percentage stays on the AP file.
Distribution-centre receiving has no benchmark of its own. Ardent Partners (2023) and RetailWire (2023) measure invoice processing, not receipts, so their figures remain on the AP file. Not a shrink or vendor-compliance claim.
The OMS or ERP — NetSuite, SAP, Brightpearl, whatever runs purchasing — and the warehouse system are untouched. Our AP three-way check is moved to the dock:
Vendor disputes. New vendors. Chargebacks that are really a conversation.
Not a shrink or vendor-compliance claim.
Vendors who do not send ASNs leave two documents, not three; those receipts are matched to the PO only and stay noisier. Case-pack and unit-of-measure differences between the vendor's file and your PO generate false shorts until they are mapped. RetailWire's 60–70% and the Ardent Partners figure are about invoice processing cost and live on the AP file; no published number covers DC receiving itself.
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 · Ops.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.