Three-way match is a procurement control that compares the purchase order, invoice, and receipt before payment is approved. It helps prevent overpayment, fraud, and unauthorized spending by requiring all three records to align. In ERP systems, it is a standard control for purchase-to-pay governance and audit assurance.
What a three-way match does
A three-way match is a purchase-to-pay control that compares the purchase order, invoice, and goods receipt before payment is released. Its job is to confirm that the buyer ordered the item, received what was ordered, and is being billed for the same transaction, reducing the chance of duplicate, inflated, or unsupported payments.
Why the control matters in procurement and ERP
The control is useful because payment workflows can fail when documents drift apart across procurement, receiving, and accounts payable. A valid match gives organisations a practical check that the transaction exists end to end, that quantities and prices are consistent, and that payment approval is tied to evidence rather than a single document.
In ERP environments, three-way match is often part of the control layer that supports auditability, segregation of duties, and spend discipline. It is especially important where large supplier volumes, decentralized buying, partial shipments, or manual invoice entry create room for error.
How the match works in practice
The purchase order establishes what was authorised, the receipt shows what actually arrived, and the invoice states what the supplier wants to be paid. The control succeeds when these records align on core fields such as supplier, item or service, quantity, and value, though organisations may set tolerances for partial delivery or minor price variance.
- When the invoice exceeds the purchase order or receipt, the mismatch should block or route payment for review.
- When the receipt is missing, the organisation lacks evidence that goods or services were actually delivered.
- When the purchase order is missing or altered after the fact, the control no longer protects the approval chain effectively.
Common failure modes and control limits
Three-way match is strongest for tangible goods with measurable receipt evidence. It is less straightforward for services, subscriptions, milestone-based work, and emergency purchases, where receipts may be ambiguous and invoice validation depends more on contract terms, acceptance records, or service confirmation.
The control can also be weakened by poor master data, rushed exceptions, weak threshold settings, or users who override mismatches without independent review. A three-way match is only as reliable as the records feeding it, so inconsistencies in supplier data, item setup, or receiving discipline can create false confidence.
Risk and Threat Considerations
Three-way match reduces payment fraud and overbilling risk, but it is still vulnerable to document manipulation, collusion, and exception abuse. If one part of the record chain is controlled by the same people who can approve payment, the control can become a formality rather than a real barrier.
Failure mechanism: An attacker, dishonest employee, or colluding supplier exploits weak receiving, false invoicing, or manual override paths to make unsupported payment look legitimate.
Impact: The organisation can suffer direct financial loss, repeated overpayment, unauthorized spend, and weaker audit assurance over purchase-to-pay activity.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Supports limiting who can approve or override purchase-to-pay exceptions. |
| AU-2 — Audit Events | Three-way match depends on auditable approval, receipt, and invoice events. | |
| AU-6 — Audit Record Review, Analysis, and Reporting | Exception handling in three-way match needs review of mismatches and overrides. | |
| Recommendation — Restrict approval and override authority to the minimum roles required. Record purchase, receipt, and payment events with enough detail to reconstruct each transaction. Review invoice mismatches and manual overrides for abnormal payment activity. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Payment approval workflows require controlled access to financial and procurement systems. |
| A.5.18 — Access rights | Role-based approval and override rights are central to preventing payment abuse. | |
| Recommendation — Limit who can create, receive, approve, and pay supplier transactions. Review and revoke excessive approval and override rights on a regular basis. | ||
Practitioner Guidance
Why practitioners should care: Three-way match is not just an accounting control, it is a governance checkpoint that depends on clean upstream purchasing and receiving data. Treat exceptions, tolerance bands, and manual overrides as control decisions, not clerical conveniences.
Common misunderstanding: A matching invoice is not proof of legitimacy on its own. The control only works when the receipt is credible and the purchase order reflects an authorised commitment before delivery or invoicing.
Practitioner takeaway: If a business process regularly cannot complete a true three-way match, the issue is usually with the procurement design or receiving discipline, not with the matching rule itself.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org