PO, GRN and Supplier Bill Controls: Designing a Reliable Three-Way Match

Three-way matching is not a single yes-or-no test. A useful design compares the same item, unit, quantity, price, tax treatment, legal entity and location across the approved purchase order, goods receipt and supplier bill. Differences should create visible exceptions, not disappear through manual edits.

Build the control from line-level identifiers Give every approved request and purchase order a stable external reference. Map supplier items to controlled internal items and units. When a supplier sends the same request again after a timeout, the integration should find the existing transaction rather than create a duplicate.

Treat receipt as operational evidence The goods receipt should record what was accepted, where, when and by whom. Partial deliveries must use remaining open quantities from the source system. Untouched lines should not be received automatically. Rejected, damaged or substituted goods need separate evidence and approval.

Compare the supplier bill without rewriting history Match billed quantity and price to the approved order and accepted receipt. Route freight, discounts, tax and other charges according to documented policy. A tolerance should identify low-risk differences for review, not silently change the purchase order or receipt.

Create an exception queue Classify price, quantity, duplicate, missing receipt, wrong entity, wrong location and tax-code exceptions. Each item needs an owner, status, evidence, decision and timestamp. Resolutions should be immutable or versioned so an auditor can reconstruct the path.

Connect approval to posting and payment Approval should occur before the bill is posted or released for payment, based on defined authority levels. Segregate request, receipt, bill review and payment where practical. Urgent overrides need a reason, approver and retrospective review.

Professional boundary This article describes finance and system controls. Exact accounting, VAT and contractual treatment depends on the transaction, entity configuration, evidence and current requirements.