← Back to Work
Process file · Manufacturing
Manufacturing
What’s inside: output checking · connections to your systems
Subcontract invoices matched to what left and came back
The question this file answersParts go out for plating and come back with an invoice — who checks that quantity and price match what we sent?
Fits: plants where receipts, counts and invoices are reconciled by hand.
Typical day
What the desk looks like today
Typical pattern, not a measured desk; the manufacturing playbook publishes no subcontract volume. Parts leave on a subcontract PO, return on a delivery note, and the invoice disagrees on quantity or price; purchasing, stores and AP each reconstruct their part of the trip. It hurts when payment is due first.
What changes
What Monday looks like after
When the invoice arrives, AP sees a draft posting for the lines that agree; the few that do not sit in a short list, each with the three documents already side by side. The conversation with the subcontractor is about scrap, rework and price — not about who has the delivery note.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
PO
Return
Match
Invoice
Break
How this file is built
Ardent Partners (2023) and Deloitte (2022) measure invoice and PO processing in general; neither isolates outside processing, so their ranges stay on the AP and PO files and this one carries no percentage. Not a rework or scrap claim.
What we install
What we put in front of the systems you already run
Your ERP stays — SAP S/4HANA, Oracle, Dynamics, Infor or the one you run. This is the same three-way checking build as our AP invoice matching, applied to outside processing:
- the subcontractor's invoice is read from the mailbox or supplier portal and its lines extracted
- each line is matched to the subcontract PO and the goods receipt of the returned parts in the ERP, inside your tolerance
- matching lines become a draft posting that goes through approval as it does today, and quantity or price breaks appear on one screen with PO, receipt and invoice together.
What stays human — and what this will not do
Rework. Scrap. Price disagreements. New subcontractors.
Not a rework or scrap claim.
What can go wrong — and what we do about it
If returns are not receipted in the ERP — parts booked straight to the line — there is no third document to match and the build has nothing to check; receipting discipline comes first. Rework, scrap and price disagreements are excluded by design; a break stays a break until a person settles 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 subcontract invoices still get reconciled against the PO and the return delivery by three different people?
- Is the return of subcontracted parts recorded as a goods receipt in the ERP, not only on a paper note?
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.
Not a named Aperanda client. Process file · Manufacturing.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.
All process files