AUTOMATION
Three-way matching works best when exceptions have owners
Matching the purchase order, receipt and invoice is the beginning. The operating model determines whether an exception is resolved correctly or simply pushed through.
By CA Tony Thomas · Chartered Accountant · 4 minute read
Prepared
PRACTICAL PERSPECTIVES / FINANCE · AUTOMATION · AI
Define what the match is meant to establish
An accounts payable team receives a supplier invoice that looks familiar. The purchase order exists and the amount is within budget. That is not yet enough to establish that the goods were received, the price is correct or the invoice has not been processed already.
Three-way matching compares the approved order, evidence of receipt and the supplier invoice. Its effectiveness depends on reliable underlying records and a clear route for resolving differences. The workflow should distinguish a missing document from an unsupported charge and a genuine commercial change.
Define the scope before automating. Goods with quantity receipts, milestone-based services and recurring subscriptions may need different evidence. Do not force every expense through a goods-receipt model that does not reflect the transaction.
Work at line level where it matters
Consider a fictional order for 100 units at AED 500 each. The receipt confirms 80 units, while the supplier invoices 100 units at AED 510. The order value is AED 50,000 and the invoice value is AED 51,000 before any applicable tax.
There are at least two questions: why were 20 units invoiced before the recorded receipt, and why is the unit price AED 10 higher? The comparison should expose both. Comparing only total invoice and order values could hide a quantity shortfall behind a price concession on another line.
On the stated inputs, 80 received units at the ordered rate correspond to AED 40,000. That does not automatically authorise a partial payment or an accounting adjustment. The team needs the contract, delivery evidence and applicable approval requirements to decide the treatment.
Check for additional receipts, approved order amendments and prior invoices against the same order before reaching a conclusion.
Design tolerances as policy decisions
A small rounding difference may be acceptable under an approved policy. A bank-detail change, unsupported receipt or unusual supplier identity should not be accepted merely because the amount is low.
Define separate tolerances for quantity, unit price, rounding and other relevant differences. Specify whether limits apply per line, per invoice or cumulatively against the order. Otherwise several small invoices may pass controls that a single equivalent invoice would fail.
Record the rationale and approving owner for each rule. Make the rule visible to reviewers and version it. The system must not widen tolerances automatically because too many exceptions are appearing.
Tax validation, supplier-master controls and payment authorisation remain separate requirements. A successful three-way match does not establish a tax deduction, confirm an invoice's authenticity or validate a change to the beneficiary bank account.
Route the problem to the person who can resolve it
Send a missing receipt to the receiving owner, a price dispute to procurement and a contractual acceptance question to the service owner. Accounts payable should coordinate the process without being expected to manufacture evidence on behalf of other teams.
Each exception needs a reason, amount affected, owner, next action, due date and evidence reference. Allow a reviewer to reject a proposed match with a reason. Keep evidence of overrides, including who approved them and whether the action was permitted under the authority framework.
Use distinct statuses for invoice received, match proposed, exception under review, approved for posting and approved for payment. Collapsing these into one green indicator makes it difficult to tell which control actually happened.
Supplier communications should use confirmed information and established channels. An internally suspected overcharge should not become an accusatory automated email.
Prevent duplicates across the whole workflow
Check the invoice against existing invoices, credit notes and previous imports using supplier identity, invoice reference, currency, amount and transaction context. Normalise references carefully; removing meaningful characters can create false duplicates.
Link order consumption to prior receipts and invoices so a partial delivery cannot be matched repeatedly. Preserve credit-note relationships and reversal histories. Reprocessing a file should update the run record rather than create another payable.
If AI extracts the invoice fields, validate key identifiers and amounts against the document. A confident extraction can still confuse a purchase-order number with an invoice number. Document text must not be allowed to instruct the workflow to bypass approval or change payment details.
Pilot a complete decision path
Test clean matches, partial receipts, revised prices, credit notes, duplicates, multiple currencies and service milestones. Include a legitimate exception so the pilot proves that reviewers can resolve the unusual case rather than only process the easy one.
Measure incorrect passes, unnecessary holds, resolution time and repeated exception causes. A low exception count can indicate strong data quality or an overly permissive rule; sampling is needed to distinguish them.
Start with one purchase category and a limited supplier population. The aim is a controlled route from invoice to supported decision, with fewer avoidable delays and no loss of accountability.
Personal educational perspective, independent of my employer. All business examples and figures are fictional and illustrative. Proposed workflows do not claim completed deployments or measured productivity gains. This is not entity-specific accounting, tax, legal or investment advice. Apply professional judgment, the applicable reporting framework and your organisation’s approval and data-protection policies.