Notice says twelve, dock counts eleven, pallet still unbooked

The question this file answersHow does one disputed carton keep a whole pallet unbooked while the emails go round?

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 lacks a goods-receipt section, hence no volume. The ASN says one quantity, the dock counts another, the PO a third; the GRN stays open while emails go round and material sits unbooked. It hurts when the line needs that pallet.

What changes

What Monday looks like after

As the truck is unloaded, the lines that agree are receipted and released to put-away, and the receiving lead's screen shows only the cartons in dispute, with the three quantities side by side. The argument with the supplier still happens; it starts the same day, with the evidence.

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

GRN posted

the same three-way build as AP invoice matching — no published figure for inbound receipts

Before: the notice says one number, the dock another, and goods receipt stays open for three emails. After: matching lines post the GRN and the disputed cartons wait on a person, evidence attached. No percentage — the AP figure lives on the parent file.

No published figure for this desk. The range lives on the parent file: Invoices hand-matched to POs already in the ERP →

How this file is built

Ardent Partners (2023) measures invoice processing and Deloitte (2022) purchase orders; goods receipt on the dock is neither, so both ranges stay where they were measured and this desk shows none. Not an inventory-accuracy claim.

What we install

What we put in front of the systems you already run

Your ERP and any WMS stay — SAP S/4HANA, Dynamics, Infor or the ones you run. This is the same three-way checking build as our AP invoice matching, moved to the dock:

the ASN is read from EDI or the supplier's email, and the dock count from the scanner or the receiving sheet
each line is matched to the PO and the ASN inside your receiving tolerance
matching lines post the goods receipt note in the ERP, and short or over lines appear on one screen with notice, count and PO together — before put-away, not after.

What stays human — and what this will not do

Short shipments. Quality holds. New packing units.

Not an inventory-accuracy claim.

What can go wrong — and what we do about it

Suppliers who send no ASN leave only two documents to match — the build still checks count against PO, but the early warning is gone. Long-tail suppliers send notices as PDF or free text, where extraction is weaker; quality holds and new packing units stay a person's decision.

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…

Does goods receipt still wait while emails settle a difference between the notice, the count and the PO?
Do you receive ASNs — by EDI or email — from the suppliers that matter most?

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 a manufacturing process like this one — free, 60 seconds →

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