Fully autonomous project. The Procurement Codex is built, verified, and published end-to-end without manual authoring. Its core logic — the spine, the layer model, and the platform comparison rubric — is rebuilt and improved on every iteration for continuous method validation. Content is generated programmatically and refined each cycle: treat it as a directional learning aid, verify against primary sources, and send corrections — accuracy and fairness compound with each pass.
Episode 10 · Where the promise meets reality
The purchase order was a promise. Receipt is the first moment anyone checks whether the promise was kept. It is also the step most organisations treat as clerical — and then spend the rest of the cycle paying for, because an invoice cannot be matched against a receipt that nobody recorded.
Below: the plain concept → how every major platform handles it → best practice → process mining, AI, orchestration and ownership, stacked until standalone is never enough.
Receipt is the confirmation that goods arrived or a service was performed, recorded against the purchase order line that committed to them. For goods it is a goods receipt with a quantity, a date and usually a location. For services it is a service entry or milestone confirmation against a rate card or schedule. Either way it creates the second of the three documents that matching in Ep11 depends on.
Because without it the organisation is asked to pay on the supplier word alone. Receipt is what converts a commitment into a liability at the moment value is actually delivered, what makes accruals real rather than estimated, and what gives you a defensible answer when a supplier says the shipment went out and the requester says it never came.
Receipts are entered within hours, not weeks. Warehouse staff scan rather than type. Requesters confirm desktop deliveries from a phone. Service milestones are confirmed by the person who consumed the service, on the schedule the contract defined. Quantity and quality exceptions are recorded as exceptions rather than quietly rounded to make the invoice clear.
Same rubric for every vendor, 1–5. We state explicitly what each is best and worst at. Toggle platforms to compare.
| Platform | Best at | Watch-out | |
|---|---|---|---|
Scores are directional teaching aids based on typical deployments, not vendor benchmarks. Your mileage varies by configuration, module licensing, scope, and integration maturity.
Stack layers onto a paper delivery note and watch the architecture — and the outcome metrics — change. This is the whole thesis of the Codex in one control.
A real best-of-breed receipt architecture is never one product. Here is the composite, and where the value actually lives — in the seams.
flowchart LR PO[Ep09 purchase order
lines, quantities and dates] --> EXPECT[L2 Expected receipt
from confirmed delivery date] ASN[L5 Advance ship notice
SAP Business Network / EDI] -.what is arriving.-> EXPECT EXPECT --> GOODS[L1 Goods receipt
S4HANA MM / Oracle / D365] EXPECT --> SVC[L1 Service entry
milestone or rate card] MOB[L4 Mobile and scan capture
barcode, photo, desktop confirm] -.who received it.-> GOODS REQ[L6 Requester confirms
desktop and service delivery] -.consumption evidence.-> SVC GOODS --> QC{L2 Quality and tolerance
accept, reject or return} SVC --> QC PM[L3 Process mining
Celonis / Signavio / Apromore] -.receipt lag and rework.-> QC QC --> ACC[L1 Accrual and inventory
posted at the moment of delivery] QC --> INV[Ep11 · Invoice and 3-way Match] ACC -.matching basis.-> INV
Standalone, a receipt module records a number. Wired to Ep09 for the expected quantity, a supplier network for advance ship notices, mobile capture for the people who actually touch the goods, mining for where receipt lag really comes from, and a service-entry construct for everything that has no box, it produces the evidence the rest of the cycle runs on. No single vendor is strongest at warehouse capture, service confirmation and network reach at once — which is why the leverage sits in the seams.
Pick one from each column. The Codex assembles the composite and calls out where the seams need engineering. Shown here for goods and service receipt; the same engine powers every episode.
Record that what was ordered actually arrived or was performed, against the PO line that ordered it, at the moment it happens and by the person who saw it.
Receipt lag · touchless receipt rate · invoices blocked for missing receipt · service entry timeliness · rejection and return rate.
If accounts payable is posting your receipts, you do not have three-way match — you have a formality.
ERP-native engines win on inventory, service entry and accrual accounting; S2P suites win on requester-side desktop confirmation; supplier networks win on advance ship notices.
L0 paper delivery note → L1 receipt engine → L2 discipline and tolerances → L3 mining → L4 mobile and vision capture → L5 network orchestration → L6 named receipt owners → L7 composite.
Standalone is never enough. Receipt only becomes evidence when expectation, capture, exception handling and ownership are wired into it.