Three-Way Matching and Living POs: Reconcile Earlier
Use earlier buyer, supplier and receiver review to improve final invoice controls while preserving the original PO and financial approval responsibility.
Jainul Vaghasia/Published /Updated /9 min read
LineNow workflow
Take the next step inside the product workflow.
This page is closest to product evaluation. If the workflow matches your business, the useful next step is pricing or a demo with your current supplier process.
Traditional three-way matching is an accounts-payable control. It waits until the supplier invoice arrives, then asks AP to compare three documents: the purchase order, the receiving record, and the invoice.
A living purchase order can add earlier review to that control.
Instead of waiting for AP to reconstruct what happened, the PO stays current as the supplier confirms the order, the buyer accepts or rejects changes, the receiver checks what arrived, and supplier AR sends the bill. Earlier review can resolve commercial differences before the payable reaches AP, while preserving any unresolved exceptions.
That is the difference: three-way matching is a downstream document check. A living PO is an upstream reconciliation system.
Quick answer
Three-way matching compares the purchase order, goods receipt, and vendor invoice before payment. It is useful, but it usually happens late, after the invoice has already reached AP.
Living PO reconciliation starts earlier. The purchase order remains live as supplier replies, buyer approvals, receiving events, and supplier AR updates change the order. The system runs smaller two-party reconciliations along the way: supplier vs. PO creator, PO creator vs. receiver, and supplier AR vs. PO creator. AP still reviews policy, coding, tolerances, and payment timing, but AP is no longer the first team trying to discover what happened.
Read before ordering
A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.
LineNow's aim is to give AP the order and receipt evidence needed for its review. AP must still investigate unresolved or suspicious differences.
Why traditional three-way matching happens too late
Three-way matching assumes three documents are clean enough to compare:
The purchase order says what the buyer authorized.
The goods receipt says what physically arrived.
The vendor invoice says what the supplier wants to be paid.
That control works when each document reflects the same reality. A problem arises when the order record omits later buyer-approved changes.
The supplier may confirm a different quantity, propose a substitution, change a price, split the shipment, move the ETA, or attach a different invoice number. If those changes stay in an email thread, the original PO is no longer the real order. The receipt may reflect what arrived. The invoice may reflect what the supplier shipped. The PO may still reflect what the buyer hoped would happen two weeks earlier.
At that point AP is not just matching documents. AP is doing operational archaeology.
A living purchase order is not a PDF frozen at the moment it was sent. It is the shared state of the order.
When the supplier replies, the PO can update. When the buyer approves a supplier change, the PO can update. When the receiver records a short shipment, the PO can update. When supplier AR sends the invoice, the invoice can be checked against the supplier-confirmed and received state instead of the stale original.
The core object is still the PO. The difference is that the PO keeps absorbing reality.
That supports AP matching with earlier checks closer to the event; it does not replace the final comparison of authorization, receipt and invoice.
The four reconciliation moments
Living PO reconciliation has four control moments.
Moment
Parties being reconciled
What is checked
What AP receives
1. Supplier confirmation
Supplier and PO creator
Quantity, price, availability, ETA, substitutions, pack sizes, MOQ, partial-fill notes
A supplier-confirmed PO, not just the original request
2. Receiving
PO creator and receiver
What arrived vs. the supplier-confirmed order
A receipt tied to the current PO state
3. Supplier AR
Supplier AR and PO creator
Invoice lines vs. confirmed PO, receiving state, approved changes, credits, freight, and fees
A bill ready to approve or pay, with exceptions isolated
This is still a control system. It is not blind automation. The difference is where the control is applied.
Old three-way matching compresses the control into AP. Living PO reconciliation spreads the control across the workflow, where the people closest to each event can resolve it while the context is fresh.
The three upstream two-way reconciliations
The phrase "two-way reconciliation" can sound weaker than three-way matching. In a living PO workflow, it is not weaker. It is earlier and more targeted.
Supplier vs. PO creator
The first reconciliation is between what the buyer requested and what the supplier confirmed.
Example:
Buyer sends 10 cases at $42/case.
Supplier confirms 8 cases at $44/case, with the remaining 2 cases backordered.
The PO creator approves the changed quantity, price, and backorder note.
The PO now reflects the commercial agreement. AP should not discover that price change for the first time when the invoice arrives.
PO creator vs. receiver
The second reconciliation is between the supplier-confirmed PO and what the receiver actually counts.
Example:
Supplier confirmed 8 cases.
Receiver counts 7 cases and marks 1 case short.
The PO moves to a received-with-variance state.
The receiving event becomes the digital goods receipt. Inventory updates from what arrived, and the short shipment is visible before the bill is approved.
Supplier AR vs. PO creator
The third reconciliation is between the supplier's invoice and the already-confirmed order state.
Example:
Supplier AR invoices 8 cases.
The received state says 7 cases arrived.
The PO creator sees the variance and can request a credit, approve a tolerance exception, or hold the invoice line.
This should happen before AP is handed a bill with no context.
How the controls work together
Three-way matching does not require a permanently frozen PO or disconnected supplier emails. A controlled revision process can preserve the original authorization and later approved changes. A living-order workflow is one way to make that history usable during purchasing and receiving.
The important distinction is timing and ownership. The buyer reviews supplier proposals; the receiver records the physical result; AP checks the invoice, authorization, evidence and policy. Each check still needs the other records. A sequence of informal two-party agreements is not automatically equivalent to a complete financial control.
What AP should do at the end
Living PO reconciliation does not remove AP. It changes AP's job.
AP should still verify:
the payable is tied to an approved supplier and PO
line-item variances are within tolerance or have review approval
received quantities support the payable quantity
freight, handling, credits, landed costs, tax, and fees are coded correctly
GL accounts, departments, locations, and classes are correct
payment terms, due date, discount date, and cash timing are appropriate
duplicate invoice risk has been checked
the final bill is ready for QuickBooks Online, Xero, or the accounting workflow
The point is not "AP does nothing." The point is that AP should not be forced to become the detective for every supplier reply, dock count, substitution, and invoice discrepancy.
Why this matters for SMBs
Small teams may combine purchasing, receiving and accounting responsibilities. Document the necessary review and approval controls even when one person performs several steps.
In a small business, the PO creator may also receive goods, talk to the supplier, and answer the bookkeeper. A control that waits until AP has three disconnected documents is too late because there may not be a dedicated AP team with time to investigate.
That is why the living PO matters. It gives small teams a way to preserve control without hiring a separate department for every step. The system keeps the order state current, and humans review the moments where judgment is needed.
This is also why closed-loop procurement is the broader category. Closed-loop procurement connects demand, purchase orders, supplier replies, receiving, inventory, accounting, and the next reorder in one operating loop. The living PO is the object inside that loop. Upstream reconciliation is the control model that makes the loop trustworthy.
Example: the same order in both systems
Imagine a cafe sends a produce PO:
10 cases strawberries at $40/case
6 cases blueberries at $55/case
Delivery expected Wednesday
The supplier replies:
only 8 strawberry cases available
blueberries are unavailable
substitute raspberries at $58/case
delivery moves to Thursday
In a static PO workflow, that reply lives in email. The receiver may count what arrived. The invoice may bill the substituted order. AP later sees a PO that does not match and has to ask what happened.
In a living PO workflow:
AI reads the supplier reply and proposes changes to quantity, item, price, and ETA.
The PO creator approves or rejects those changes.
The receiver checks Thursday's delivery against the supplier-confirmed state.
Supplier AR invoices against the confirmed and received state.
AP receives a bill with the approved substitution, price change, received quantity, and source thread attached.
The commercial truth did not wait until invoice time. It was captured as the order evolved.
Verify the handoff in LineNow
Test a supplier proposal, buyer approval, short receipt and invoice difference in the same order. Confirm supported channels, permissions, account mappings and the records created by the accounting connector. Retain the source documents and verify that neither a receipt nor a bill is created twice.
FAQ
Does a living PO replace three-way matching?
No. A living PO does not remove the need to check PO, receipt, and invoice before payment. It makes that check cleaner because the PO and receipt are already closer to the final supplier-confirmed state.
Is upstream reconciliation the same as invoice automation?
No. Invoice automation usually starts when the invoice arrives. Upstream reconciliation starts when the supplier replies to the PO and continues through receiving. The invoice is the final checkpoint, not the first place the mismatch appears.
Why not just update the PO manually?
Manual PO updates work only when the operator has time to retype every supplier change. In real SMB workflows, supplier changes arrive through email, WhatsApp, portals, PDFs, and phone follow-ups. A living PO workflow turns those messages into reviewable updates so the record can stay current without duplicate entry.
What should AP see when the bill arrives?
AP should see the supplier-confirmed PO, receiving state, approved variances, source messages, invoice lines, coding context, and payment terms in one place. AP should approve, hold, or pay from that record instead of searching email threads to understand the bill.
