Written and maintained by CASRAI Editorial Board
Last updated
General procurement information for buyers and accounts-payable staff. It is not legal, accounting or medical advice.
Short answer
A two-way match compares a supplier invoice with the purchase order (PO) it should belong to. Per Oracle’s Payables documentation (legacy release), it checks that the quantity billed is no more than the quantity ordered and that the invoice price is no more than the PO price, within tolerances you set. It does not look at what was received, so on its own it cannot show that medical supplies arrived.
Definition and scope
“Two-way match” is an accounts-payable control term, not a regulatory term. Oracle’s Payables documentation (legacy release, checked 2026-11-01) says that “2-way matching verifies that purchase order and invoice information match within your tolerances.” Two documents are compared: the PO and the invoice. This page uses medical and laboratory supplies as the setting, but the match rules come from general payables software documentation and apply to any purchased goods.
The guide on three-way match covers the version that adds a receiving record. This page stays with the two-document version and with what it leaves out.
How the match works
Oracle’s documentation describes two tests for a two-way match:
- Quantity: quantity billed is less than or equal to quantity ordered.
- Price: the invoice price is less than or equal to the purchase order price.
If the invoice and PO do not match within the tolerances you define for quantity and price, the system places a matching hold on the invoice, and the hold must be released before the invoice can be paid. The tolerances are set by the organisation that buys; this page does not recommend a percentage. A PO number on the invoice is what lets the two documents be paired in the first place.
One AP-software vendor’s blog (AvidXchange) illustrates tolerance with a 5% example: 102 units billed against 100 ordered would pass, while 115 would be flagged. Treat that as one vendor’s worked example, not a standard.
Two-, three- and four-way matching compared
The levels differ in which extra document the invoice is tested against. The first three columns below follow Oracle’s Payables documentation (legacy release); the last follows Oracle PeopleSoft Payables, “Matching Types” (release 9.2, checked 2026-11-01).
| Level | Compares | Extra test beyond the PO | When PeopleSoft applies it |
|---|---|---|---|
| Two-way | Invoice and purchase order | None (quantity billed ≤ ordered; price ≤ PO price) | Receiving Required option on the PO is Do Not Receive or Optional |
| Three-way | Invoice, PO and receipt | Quantity billed ≤ quantity received | Receiving is Required and inspection is not selected for the receiver |
| Four-way | Invoice, PO, receipt and inspection | Quantity billed ≤ quantity accepted | Receiving is required and inspection is required |
The practical reading is that the level is decided by whether the buyer’s system requires a receiving record. A related record, the goods receipt note, is the kind of document the third leg relies on.
Where it matters for medical supply buying
This section is reasoning from the definitions above, not a finding about how often errors occur.
- A two-way pass is not proof of delivery. Because the test uses only the PO and the invoice, an invoice that matches its PO can be approved whether or not the goods were received. Only the three-way level adds a received-quantity test.
- Quantity accepted is a separate question. Only the four-way level adds an accepted-quantity test, which is the level that brings inspection into the match.
- Records the match does not hold. Lot numbers, expiry dates and device identifiers live on the product label and receiving records, not in a price-and-quantity comparison. See the guides on UDI labels and medical device recalls for the records a buyer may need to trace a product, and supplier risk assessment and procurement KPIs for supplier-level controls.
Document checklist tied to a federal example
In US federal contracting, FAR 32.905 (checked 2026-11-01) sets out payment documentation. It says payment “will be based on receipt of a proper invoice and satisfactory contract performance.” A proper invoice includes the “description, quantity, unit of measure, unit price, and extended price of supplies delivered or services performed.” Payment must be supported by a receiving report or other government documentation authorizing payment, and the receiving report lists the “quantities of supplies received and accepted.”
For a buyer that wants its own checklist, those elements map onto what an invoice-versus-PO comparison needs on the page: description, quantity, unit of measure, unit price and extended price. The receiving report is the separate document that a two-way match does not use. This applies to US federal contracts; other buyers set their own rules.
Common misunderstandings
- “FAR requires a three-way match.” FAR 32.905 does not use the word “matching.” It requires a proper invoice and a receiving report or equivalent documentation, which is a document requirement rather than a named matching method.
- “Two-way match confirms receipt.” It does not; it compares invoice with PO only.
- “A match hold means fraud.” A hold means the invoice fell outside the tolerances set for quantity or price; it needs review before release.
FAQ
What is a two-way match?
It is a payables check that compares an invoice with its purchase order on quantity and price, within tolerances, before payment is released.
What is the difference between two-way and three-way match?
Three-way adds a third criterion: quantity billed must not exceed quantity received. Two-way tests only the PO and the invoice.
When does a system apply a two-way match?
In Oracle PeopleSoft Payables, two-way matching applies when the Receiving Required option on the purchase order is Do Not Receive or Optional.
What happens when an invoice fails the match?
Per Oracle’s documentation, a matching hold is placed on the invoice and must be released before it can be paid.
Sources
All sources checked 2026-11-01.
- Oracle E-Business Suite Payables, “Two-, Three-, and Four-way Matching” (legacy release): https://docs.oracle.com/cd/A60725_05/html/comnls/us/ap/point04.htm
- Oracle PeopleSoft Payables, “Matching Types” (release 9.2.056): https://docs.oracle.com/en/applications/peoplesoft/financials-and-supply-chain-management/9.2.056/peoplesoft-payables/matching-types.html
- Federal Acquisition Regulation 32.905, “Payment documentation and process”: https://www.acquisition.gov/far/32.905
- AvidXchange, “2-way vs 3-way matching FAQs” (vendor blog, used only for the tolerance example): https://www.avidxchange.com/blog/2-way-vs-3-way-matching-faqs-pros-cons/
