Skip to content
J
← Insights
Operations · Procurement6 min readBy Junmarvi Tampac

Why 3-Way Matching Is Still Hard in Construction Procurement

Ask any ERP vendor and 3-way matching is a solved problem: the purchase order, the goods receipt, and the invoice meet in the system, quantities and prices agree, and payment releases. Ask anyone who has actually closed a month on a construction project and you will hear a different story — one involving exports, spreadsheets, and a very long weekend.

The theory meets the site

Construction breaks the clean model in predictable ways. Deliveries arrive partial, early, or consolidated across POs. Delivery notes reference supplier part numbers that do not match the PO line description. Site urgency means material is issued before the GRN is posted. Unit-of-measure conversions — tons ordered, pieces received, meters issued — quietly corrupt automatic comparison.

None of these are exceptions in the statistical sense. On a live project they are the normal texture of the data. An ERP configured for the happy path routes many real transactions into a manual review queue — which is a polite way of saying the matching is manual after all.

Where the real logic lives

The matching logic that actually works lives in the heads of experienced material controllers: which suppliers habitually short-ship, which tolerance is commercial noise versus a genuine claim, which mismatch means a typo and which means a missing delivery. That judgement is real, and almost nowhere is it written down.

The tools I build start by trying to write that judgement down as explicit rules — tolerance bands per material class, alias tables for supplier references, sequencing logic that tolerates issue-before-receipt and reconciles it later. The tool executes the rules; the controller owns the exceptions. That division of labour is the whole point.

What good looks like

A working 3-way match in construction is continuous, not monthly. It matches on tolerances a procurement professional would defend in an audit, not on exact equality. It produces exception lists with owners and context, not variance dumps. And it treats the delivery note — the ugliest, most manual document in the chain — as a first-class citizen, because that is where the truth usually is.

The technology to do this is not exotic. What is rarer is the combination: someone who has argued with a supplier over a short shipment and can also build the tool. That intersection is where the broken parts of procurement actually start to get fixed.