Why is AP still rebuilding PO, delivery and invoice?

The question this file answersOut of hundreds of vendor invoices a month, how many does anyone actually check line by line?

Fits: multi-vendor retailers matching hundreds to thousands of invoices a month.

Typical day

What the desk looks like today

Typical, from the retail and e-commerce playbook. A multi-vendor retailer receives hundreds to thousands of supplier invoices a month. A clerk pulls the PO, the delivery record and the invoice, compares them, chases the vendor, approves payment. It hurts after peak season, when the peak-season invoices arrive together.

What changes

What Monday looks like after

Two weeks after peak, the AP clerk is working a list of genuine breaks with the vendor e-mail half-written, rather than re-keying the purchase order to find out whether there is one. Finance can see, per vendor, what matched, what did not and how long each break has been open.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~50–70%

less invoice-processing effort where the three documents match — RetailWire (2023); disputes stay a conversation

Before: a clerk rebuilds PO, delivery and invoice, then chases the vendor. After: RetailWire (2023) puts the processing-cost saving from automated matching at 60–70% — disputes and new vendors stay a conversation.

Where this number comes from

Ardent Partners “AP Automation” (2023) reports best-in-class AP at 80%+ touchless; RetailWire (2023) puts the cost reduction from automated vendor-invoice matching at 60–70%; the retail playbook uses 50–70%. Industry figures, not ours.

What we install

What we put in front of the systems you already run

Your OMS and ERP stay — NetSuite, SAP, Brightpearl or the ones you run. It reuses our AP invoice-matching build, wired to retail systems:

vendor invoices come in from the AP mailbox and the vendor portal
every line is matched against the PO and the goods-received record through the platform’s API — retail stacks usually have one
lines inside your tolerance are approved for the payment run as drafts; the rest reach the AP clerk with the break named — price, quantity, missing delivery — and the vendor’s contact already on the note.

What stays human — and what this will not do

Vendor disputes. New vendors. Contract terms. Pricing disagreements that are really negotiations.

What can go wrong — and what we do about it

If deliveries are booked in the OMS after the invoice arrives, nothing matches and the list is long until the receiving habit changes. Vendors on marketplace or drop-ship arrangements invoice differently — those flows need their own rule, and until they have one they go to a person. RetailWire’s 60–70% is processing cost on matched invoices; disputes and new-vendor set-up are not in it.

What it costs to get there

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.

This is about you if…

Do vendor invoices still get compared with the PO and the delivery record by hand?
Is the goods-received quantity recorded in the OMS or ERP, not only on the packing slip?

What does this mean in euros?

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.

Get your free savings estimate 60 seconds · no sales call Or write first → Map an ops process like this one — free, 60 seconds →

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.

All process files