The Third Document That Is Our Own
Three-way matching compares what you ordered, what arrived, and what you were billed. We do the first two properly, with tolerances and a payment gate behind them. The third is the supplier’s bill, captured as a record of its own — and on an order without one, the third document is a valuation we generate from our own prices, so we call that a two-way match.
Almost every procurement system in this bracket advertises three-way matching. Very few of them have anywhere to put a supplier's invoice. It is worth understanding why those two facts coexist so comfortably.
The first two documents
The purchase order, with its lines, quantities and prices. And the receipt, recorded at check-in, with what actually arrived.
The comparison between them is careful, and several of the details are the ones that separate a working match from a demonstration.
- Tolerances on quantity and price are set per organisation, so a small variance is not an exception.
- An order with nothing received yet is treated as open, not as a shortage. Getting this wrong makes every new order an exception and the queue unusable within a week.
- Partial deliveries are summed. A split delivery is compared against the order in total rather than one row at a time.
- Receipts are resolved through the order's own adjustment, so a check-out can never be mistaken for a receipt.
- The result is persisted on the order — a status, a discrepancy count, and when it was last checked — and discrepant orders collect in an exception queue.
And it has teeth. A single gate decides whether an order may be paid, and every payment path in the product calls it: the web order payment, the API, manual vendor payments, two mobile-money paths and the card processor. A discrepancy blocks by default. Paying before receipt only warns, because prepayments are legitimate, and that warning can be turned into a block per organisation.
Overriding needs a dedicated permission — deliberately not the one that approves purchase orders — plus a written reason, stamped with who and when. And the override is pinned to the discrepancy count it authorised, so if the documents change into a different problem the authorisation withdraws itself rather than continuing to release money.
Two documents, compared carefully, with a gate on the money. That part stands on its own, and we would put it against anybody’s.
The third document, and where it comes from
There is an invoice record in the matching path that we create ourselves. It is made at check-in, valued from our own item prices. It carries no vendor and no supplier invoice number, because it is not a supplier's invoice — it is a valuation of what was received.
Your supplier’s actual invoice is captured as a supplier bill — the supplier, their invoice number, the bill date and lines against the order — typed by your team or submitted by the supplier through the portal, and refused if the same number from the same supplier arrives twice. Once a bill is approved, its lines replace our valuation as the third leg. The lines are typed rather than read from the file.
So on an order with no bill captured, the match compares our valuation of the receipt against our own order. It is a real check and it can find real things — a price on the order that does not match the item master, for instance — but it is not the control that three-way matching exists to provide. That control is the one that catches a supplier billing you for something other than what they delivered, it requires the supplier’s numbers, and an approved bill is where it gets them.
Why this is the wrong thing to be relaxed about in Thai manufacturing supply
Because the invoice discrepancies that matter in a components and contract-manufacturing supply chain are rarely dramatic. They are a unit price a fraction above the agreed one, a quantity billed against an order that was partially delivered, a surcharge added at invoice stage, a currency applied differently from the quote.
Every one of those is invisible to a match that does not read the invoice — which is why capturing the bill, rather than only attaching it, is the habit worth building. And every one of them recurs, monthly, across a supplier relationship that lasts years — which is what makes the aggregate large even though each instance is small enough to wave through.
Four questions that test a three-way-matching claim in ten minutes
Where do I enter my supplier's invoice number?
A good answer sounds like
A field, on a record, that the match reads.
What it actually means
This one question settles it. If the answer is an attachment or a note, the third document is not in the comparison.
Whose price is on the third document?
A good answer sounds like
The supplier's, from their invoice.
What it actually means
Ours is the supplier’s once their bill is captured, and our own valuation before that. A match against your own prices cannot catch a supplier billing differently from the order.
Show me an order where the invoice disagrees with the order but the receipt agrees.
A good answer sounds like
An exception.
What it actually means
The scenario three-way matching exists for. Ask for it specifically rather than for a demonstration of the feature.
What stops payment when there is a discrepancy?
A good answer sounds like
A single gate, named, called by every payment path.
What it actually means
Ours is exactly that, across six separate payment doors. Ask how many doors theirs has.
Our position
Buy this for the match and the payment gate, which stop the largest category of loss — paying for goods that did not arrive — and, once the supplier’s bill is captured against the order, the second: being billed for something other than what was delivered. The match is three-way only where a bill is on the order, so make capturing every supplier invoice as a bill the rule, and make sure your finance team knows an order without one is matched on two legs.
What AWRA OpsHub does today
- A two-way match comparing ordered against received, per line, with per-organisation quantity and price tolerances.
- Partial deliveries summed, an unreceived order treated as open rather than short, and receipts resolved so an issue cannot be read as a receipt.
- Match status, discrepancy count and last-checked time persisted on the order, plus an exception queue.
- A single payment gate called by all six payment entry points, blocking a discrepant order by default.
- Payment before receipt warning rather than blocking, switchable to a block per organisation.
- Overrides requiring a dedicated permission and a written reason, pinned to the discrepancy count they authorised so they self-withdraw when the problem changes.
- Capture of a supplier invoice as a supplier bill — vendor, invoice number, date and lines — typed by your team or submitted from the supplier portal, with a repeated invoice number refused.
- A bills inbox that reads the invoice into a draft bill. A bill emailed to the workspace’s own bills address, or uploaded, is read — by AI where the workspace allows it, from the PDF’s text layer otherwise — matched to its supplier and order, and offered as a draft bill that a person confirms before it enters approval.
- A three-way match on any order with an approved bill: billed quantity against received and billed price against agreed, within the same tolerances.
- Payment runs: bills batched, approved by somebody other than the person who built the run, and paid, with a bank file for transfers.
More we can add to your workspace
- An inspection or quality gate at receipt, which is what makes four-way matching achievable. Commission it
Where we point you to a specialist
- The invoice-shaped record created at check-in is our own valuation of the receipt, used only where no supplier bill is captured. Calling it an invoice in the schema is a naming legacy and we would rather explain it than rename it quietly.
- The two-way match catches the largest single loss in procurement — paying for what did not arrive. What the middle column adds is the second-largest, not the first.
- This is market-neutral. It is what a match without a supplier invoice can and cannot see; Thailand is where the long-running components relationship makes the small recurring discrepancy worth the most.
What we can build for your market on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for your market, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a tax authority pipeline, a local-language interface, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Tax authority pipelines and reporting
Electronic invoicing against your authority's published interface or its accredited network, with retries, a failure queue and a daily report of sales that never reached it. The regimes here range from a live clearance model to a purely voluntary scheme, so this is one build per country and we will say which country rather than sell an ASEAN integration that does not exist.
Local-language interface, banks and wallets
Interface text and document templates in the language your finance floor and your statutory documents actually require, plus real-time payment collection, e-wallet settlement and bank statement feeds wired into the Payments Register.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
Social security, provident fund and withholding computed on live records, with the contribution files produced in the layout each agency expects and any statutory bonus accrued through the year rather than found at the end of it.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedCheck the boundary before your finance team assumes it
The most expensive misunderstanding here is a finance team believing every invoice is being checked automatically, when only a captured bill is. Ten minutes with us and your accounts-payable process will know exactly where the machine stops.
Walk the boundaryFrequently asked questions
Can I attach the supplier invoice at all?
Yes — and better, capture it. Attached to a supplier bill, the file sits beside the lines typed from it, and those lines enter the comparison once the bill is approved. A file attached to a bill you typed is kept as evidence rather than parsed; send it through the bills inbox instead, by email or upload, and it is read into a draft bill for you to confirm. Either way, the lines are what the match reads.
What does the two-way match actually catch, then?
Short delivery, over-delivery beyond your tolerance, and a price on the order that disagrees with the item master beyond your tolerance. In cost terms that is the largest category — paying for goods that never arrived — and it is the one worth having automated.
Would you build invoice capture?
It ships. The record half is the supplier bill, with its own number, vendor and lines, and the bills inbox gets those lines in without typing: an invoice emailed to the workspace’s bills address or uploaded is read from its PDF or photo and offered as a draft bill a person confirms. Reading the structured invoice the supplier’s own system issued is the part we can add. Describe the volume you process and we will scope it properly rather than guessing.