The Third Document, on Record
Matching an order against a receipt against the supplier's invoice is the standard control over paying for goods. In many systems the third document is one the buyer generated itself, which makes the match two-way under a longer name. Here the supplier’s bill is a record of its own, and the third leg reads it.
The control everybody names when asked how they stop paying for goods they did not get is a comparison between three documents: what you ordered, what arrived, and what you were billed. Agreement on all three, within tolerance, and the payment is safe to release.
All three are compared here. Which document fills the third slot is the question to put to any system — because in many of them it is not the supplier’s.
What the third document actually is in our system
When goods are received, a record is created that the system calls an invoice. It carries line items, a total and a currency, and it is attached to the receipt. It looks like the third leg of the match and it is positioned where the third leg would be.
It carries no supplier. It carries no invoice number. And its prices are our own purchase prices, taken from our item records — not from anything the supplier sent us. It is a valuation of the goods we received, priced by us, generated by us, at the moment we received them. That makes it a useful valuation and the wrong third leg.
Comparing that against the receipt is comparing the receipt with a copy of itself.
A three-way match where you wrote the third document yourself is a two-way match with a longer name.
So the supplier’s real invoice is captured as a record of its own rather than only as a file a person can open and nothing can compare. It is a supplier bill: the supplier, their invoice number, the bill date and lines against the order’s own lines, with the file attached — typed by your team, or submitted by the supplier through the portal for your team to approve. Once a bill is approved its lines are the third leg, and an order with no bill yet falls back to our own valuation, with the match saying which one it used.
What that means for the control itself
It is worth being precise about the machinery underneath the third leg. The order-to-receipt match is careful: it compares per line, applies tolerances you set for quantity and price, sums partial deliveries rather than reading one of them, treats an order with nothing received as open rather than short, and keeps an exception queue. A discrepancy blocks payment by default, and overriding it needs a specific permission plus a written reason that is pinned to the discrepancy it authorised.
What that machinery catches depends on which documents it compares — and the bill is what adds the second group below.
What each comparison can and cannot catch
Everything in the first group is a discrepancy between what you asked for and what turned up. Everything in the second is a discrepancy between what turned up and what you were billed — which is the entire reason the third document exists. That group is invisible to any match whose third document the buyer generated; with an approved supplier bill on the order it is caught, and an order with no bill captured matches on two legs only.
Why this is a Latin American post
Because of an irony that is specific to this region and getting sharper every year.
In much of the world the supplier's invoice arrives as a PDF or on paper, and the reason systems struggle to use it as data is that it genuinely is not data. Extracting it means scanning, reading and guessing, which is why invoice capture is a whole product category.
That is not the situation here. Across this region the supplier invoice is increasingly a structured electronic document by default — issued, validated and delivered in a machine-readable form, with a number and an issuer identity that are meaningful outside your organization. The hard problem that stops three-way matching elsewhere has largely already been solved for you, by regulation, at the supplier's end.
Here the bill is the place it lands — keyed in by your team, submitted by the supplier in the portal, or read from its PDF or photo by the bills inbox and confirmed by a person, rather than read from the structured document the supplier already issued. In a region where the third document arrives as data, that is the step worth taking next.
What a match needs recorded before it has a real third leg
- A supplier invoice as a record, not a file — with the issuing supplier on it.
- The invoice number the supplier used, so the same bill cannot be received twice under two references.
- The invoice date, which is what payment terms actually run from.
- Its lines, resolved to the items they refer to, so a per-line comparison is possible at all.
- Its own totals and tax, so the document can be checked against itself before it is checked against anything else.
- A link to the order it bills, so each line lands against the order line it charges for.
That list is deliberately short and deliberately unglamorous. None of it is difficult, its absence is what stops most matches at two legs, and all six are on the supplier bill here.
The next step, on top of the bill
The supplier bill is the record everything else depends on, and it ships. What remains is filling it without typing.
Ingesting the electronic invoice directly
Populating the bill from the structured document the supplier already issued is the natural next step, and in this region it is a far smaller problem than optical capture would be elsewhere. This is the part where the regional situation works in our favour rather than against it.
Reading the attached file into the bill
Where the invoice arrives as a PDF or a photo, proposing its lines from the attachment for a person to confirm, rather than typing them from it.
Either one feeds a record that already exists, which is why both are worth building: the value is in what the bill makes checkable, and that part is live.
Talk to us about invoice matchingFour questions that find out whether a match is really three-way
Where does the supplier invoice live — a record, or a file?
What a straight answer sounds like
One word. Ours is a record, with the file attached.
Why it matters
This single question settles it. A file cannot be compared to anything.
What stops the same invoice being paid twice?
What a straight answer sounds like
A number, uniquely constrained. Ours is refused when it repeats for the same supplier.
Why it matters
Duplicate payment is the most common loss in accounts payable and it needs exactly one field to prevent.
Bill me for 100 when 60 arrived. What happens?
What a straight answer sounds like
A block, or nothing. Ours is a discrepancy on the order, which the payment gate reads.
Why it matters
This is the scenario the third document exists for. If it passes silently, the control is two-way whatever it is called.
Can you ingest an electronic invoice as data?
What a straight answer sounds like
Yes with a format named, or no.
Why it matters
In this region the answer should increasingly be yes, and a vendor who has not noticed the invoice is already structured is not paying attention to your market.
What AWRA OpsHub does today
- A per-line comparison of what was ordered against what was received, with quantity and price tolerances you set.
- Partial deliveries summed, so a split delivery cannot creep past the comparison one receipt at a time.
- An exception queue and a match status kept on the order, rather than a check that runs and is forgotten.
- A payment gate — a discrepancy blocks payment by default across every payment route, and an override needs a specific permission, a written reason, and is pinned to the discrepancy it authorised so it self-withdraws if the problem changes.
- The supplier's invoice retained as a document, attached to the order and served securely.
- A supplier invoice as a record — the supplier bill: a vendor, their invoice number, a bill date and lines against the order, typed by your team or submitted by the supplier in the portal.
- Duplicate-invoice detection: the same invoice number from the same supplier is refused at capture.
- A three-way match once a bill is approved: billed quantity against received, and billed price against agreed, within your tolerances.
- A bills inbox that reads the invoice file into a draft bill. A PDF or photo 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 confirmed by a person before the bill enters approval.
More we can add to your workspace
- Structured electronic invoice ingestion — reading the machine-readable invoice itself, in the format a market prescribes, rather than its PDF. Commission it
Where we point you to a specialist
- We cite no country's electronic invoicing rules in this post. Where our copy discusses a specific regime it does so with a date and a source, and this argument needs neither.
- We call the match three-way only where an approved supplier bill is on the order. An order with no bill captured is matched on two legs, and the match says so rather than borrowing the longer name.
The verdict
Our controls over receiving are good, and our control over paying reaches the bill as well: what you ordered, what arrived and what you were billed are compared line by line. What is left is how the bill gets in — typed today, where in this region the supplier has usually already issued it as data. If your accounts payable exposure is the invoice rather than the delivery, ask the file-or-record question first, of everyone you are considering — it takes one sentence to answer and it settles the whole conversation.
Send us a supplier invoice as you receive it
In whatever form it arrives. We will show you it captured as a bill and matched against its order, and what reading it in directly would save.
Talk to us about accounts payable