Three Way Match: How to Automate the AP 3-Way Match in SAP and NetSuite
A three way match checks an invoice against its purchase order and goods receipt before payment. How SAP and NetSuite run it, and how to automate it.

A three way match is an accounts payable control that compares a supplier invoice with the purchase order and the goods receipt behind it, and releases the invoice for payment only when quantities and prices agree within set tolerances. The purchase order says what you agreed to buy, the goods receipt says what arrived, and the invoice says what the supplier is billing.
SAP S/4HANA and NetSuite both run the match themselves: SAP blocks an invoice for payment when a variance exceeds its tolerance limit, and NetSuite routes a vendor bill with discrepancies to a supervisor. What usually stays manual is the work around the match: getting invoices in, finding a missing receipt or purchase order number, and working each exception until someone can release the invoice.
Where engini fits: engini automates the work around the ERP's own three way match, not the match itself. A workflow reads each incoming invoice with a ready-made Analyze Invoice action, looks up the purchase order and receipt in SAP S/4HANA, SAP Business One or NetSuite, creates the invoice in the ERP with its purchase order reference, and gathers the facts behind each exception for the person who resolves it. See the Analyze Invoice docs.
Key Takeaways
- A three way match compares the purchase order, the goods receipt and the supplier invoice. A two way match skips the receipt.
- In SAP S/4HANA, tolerance keys such as PP (price) and DQ (quantity) set limits per company code, and an invoice over an upper limit is posted but blocked for payment.
- In NetSuite, the 3 Way Match Vendor Bill Approval workflow comes with the NetSuite Approvals Workflow SuiteApp, needs Advanced Receiving, and does not support partially received item receipts.
- While an invoice is blocked, the supplier's cash discount period may expire, so clearing exceptions fast matters as much as the match.
- Let the ERP do the comparison and keep release and approval there. Automate intake, missing references and exception follow-up.
What Is a Three Way Match?
A three way match is the check that an invoice bills only for goods that were ordered and received, at the agreed price. Accounts payable compares three documents, line by line:
| Document | What it proves | Where it comes from |
|---|---|---|
| Purchase order | What you agreed to buy, how many, at what price and terms | Purchasing, in the ERP |
| Goods receipt (item receipt in NetSuite) | What actually arrived | The warehouse or receiving team |
| Supplier invoice (vendor bill in NetSuite) | What the supplier wants paid | The supplier, by email, portal, EDI or upload |
A two way match compares only the invoice and the purchase order, which suits services and non-stock items. A three way match adds the goods receipt, so you do not pay for goods that never arrived. A four way match adds an inspection or acceptance record for goods that must pass a quality check first.
How Does the Three Way Match Work, Step by Step?
The three way match works the same way in most ERPs: the purchase order sets the expectation, the receipt confirms delivery, and the invoice is checked against both.
- Purchasing creates and approves the purchase order.
- Receiving posts the goods receipt against the order lines when goods arrive.
- Accounts payable enters or imports the invoice with its purchase order reference.
- The ERP compares each invoice line with the order price and the received quantity, within your tolerances.
- Within tolerance, the invoice is posted and can be paid. Outside tolerance, it is blocked or routed for approval.
- The owner resolves the exception (the buyer for price, receiving for quantity, the supplier for a credit memo), and the invoice is released.
Tip: Most delay sits in step 6, not in the comparison. Measure blocked invoices by reason and age before you automate.
How Does the 3-Way Match Work in SAP?
In SAP S/4HANA, the 3-way match happens in invoice verification, where the system checks each invoice item for variances against the purchase order or the goods receipt. Each type of variance has a tolerance key, with limits set per company code (SAP Help: Tolerance Limits for Invoice Postings, SAP S/4HANA 2025 FPS02).
| Tolerance key | What SAP checks |
|---|---|
| PP: price variance | Each invoice item against quantity invoiced times order price, with absolute and percentage limits |
| DQ: quantity variance | Order price times the quantity billed beyond what was delivered and not yet invoiced |
| DW: no goods receipt yet | An invoice for an item that requires a goods receipt when none has been posted |
| BD: small differences | Whether the invoice balance is small enough to post automatically |
| AN, AP, ST, VP | Item amounts without or with an order reference, date variance, and moving average price variance |
If an upper limit is exceeded, except for BD and VP, the invoice is blocked for payment when you post it and must be released in a separate step. If the BD limit is breached, the invoice cannot be posted. If key DW is not maintained for a company code, SAP blocks any invoice whose goods receipt has not been posted. Because DQ multiplies the quantity difference by the order price, it tolerates larger quantity differences on low-value items and only small ones on high-value items.
What a block does. SAP enters an R in the Payment block field of the vendor line, so Financial Accounting cannot pay the invoice. The block applies to the whole invoice even if only one item has a variance, and while it lasts, the supplier's cash discount period may run out. SAP can also block for an item's amount, by a stochastic (random) block, or manually (SAP Help: Blocking Invoices).
Goods-receipt-based invoice verification. With GR-based invoice verification, the invoice refers to individual deliveries rather than the whole purchase order. The GR-based IV indicator must be set on the order item, and the goods receipt must be posted before the invoice is entered. The purchase order history shows which receipt each invoice was assigned to (SAP Help: Goods-Receipt-Based Invoice Verification).
Releasing blocked invoices. The Release Blocked Invoices app (app ID MRBR) releases invoices manually or automatically; for automatic release, the system checks whether each blocking reason still applies and deletes the ones that no longer do (SAP Help: Release Blocked Invoices, SAP S/4HANA Cloud Public Edition 2608). For integrations, the Supplier Invoice OData V2 API can create, park, release, reverse and read supplier invoices (SAP Help: Supplier Invoice OData V2).
How Does the Three Way Match Work in NetSuite?
NetSuite runs the three way match with the 3 Way Match Vendor Bill Approval workflow, which checks a vendor bill against its purchase order and item receipt and routes bills with discrepancies to the assigned supervisor (NetSuite Help: 3 Way Match Vendor Bill Approval Workflow). It checks the bill against the purchase order for terms, location, quantity and amount, and against the item receipt for its existence and quantity.
Limits can be set at the vendor, item or subsidiary level: a tolerance limit is a percentage, and a difference limit is an absolute quantity (NetSuite Help: Exception Criteria). In Oracle's example, a purchase order for 100 units and 1,000 is billed as 97 units and 970. With a quantity difference limit of 2, the bill goes to the supervisor; with only an amount tolerance of 0.10, it is approved automatically.
Setup. The workflow comes in the NetSuite Approvals Workflow SuiteApp and needs the A/P, Purchase Orders, Advanced Receiving, Approval Routing and SuiteFlow features, with approval routing on for vendor bills (NetSuite Help: Setting Up 3 Way Match Vendor Bill Approval). It is a template you can customize, and "Item receipts that have been partially received are not supported."
Variances. With Advanced Receiving, NetSuite posts bill quantity, bill price and bill exchange rate variances to variance accounts. An order line marked Match Bill to Receipt compares bill lines with the related receipts; you post the variances at Transactions > Payables > Post Vendor Bill Variances (NetSuite Help: Vendor Bill Variances).
Invoice intake. Bill Capture creates vendor bills from emailed or uploaded PDF, JPEG and PNG files, matched to vendors, items and purchase orders. The three way match and approval workflows in your account still apply to the bills it creates (NetSuite Help: Bill Capture).
SAP and NetSuite Three Way Match Side by Side
SAP blocks an invoice that fails the match; NetSuite routes the bill to an approver. The other differences follow from that.
| SAP S/4HANA | NetSuite | |
|---|---|---|
| Where the match runs | Invoice verification, when the invoice is posted | 3 Way Match Vendor Bill Approval workflow (SuiteApp) |
| How limits are set | Tolerance keys per company code, absolute and percentage; supplier-specific limits as a separate setting | Tolerance (percentage) and difference (absolute) limits per vendor, item or subsidiary |
| Outside tolerance | Posted with payment block R | Routed to the assigned supervisor |
| Invoice before receipt | Blocked unless key DW allows it | The workflow checks that an item receipt exists; partial receipts are not supported |
| Release | Release Blocked Invoices app, manual or automatic | Approval in the workflow |
| Invoice intake | Supplier Invoice API, EDI and upload apps | Bill Capture, by email or upload |
What Are the Most Common Three Way Match Exceptions?
Most three way match exceptions fall into a few types, each with a different owner. Routing each type to its owner, with the facts attached, is where most time is saved.
| Exception | What it means | Who resolves it | What they need to see |
|---|---|---|---|
| Price variance | Invoice price above the order price beyond tolerance | The buyer | Order price, contract or price list |
| Quantity variance | More billed than received | Receiving | Goods receipt, delivery note |
| No receipt yet | Invoice arrived before the receipt was posted | Receiving | Expected delivery date, open order lines |
| Partial receipt | Only part of the order has arrived | Receiving | Receipts so far, remaining quantity |
| Missing purchase order number | The invoice cannot be tied to an order | Accounts payable, with the supplier | The supplier's open orders and amounts |
| Duplicate invoice | Same supplier and invoice number already entered | Accounts payable | The earlier invoice and its status |
| Terms or location mismatch | Terms or location differ from the order | The buyer | The purchase order header |
How Do You Automate the Three Way Match?
You automate the three way match by letting the ERP do the comparison and automating the work before and after it. The ERP already holds the tolerances, the block and the approval, and those are the controls your auditors test.
| Task | Best handled by | Example |
|---|---|---|
| Comparing invoice, order and receipt | The ERP's own rules | SAP tolerance keys, NetSuite exception criteria |
| Reading invoices from email or a folder | Invoice extraction | Supplier, invoice number, totals, line items |
| Finding the order for an invoice with no number | An AI agent, with rules checking its proposal | Matching supplier, items and amounts to open orders |
| Catching duplicates before posting | Rules | Same supplier, invoice number and amount |
| Explaining an exception to its owner | A workflow, with an AI agent writing the summary | Order price, receipt and invoice line in one message |
| Releasing or approving the invoice | People, in the ERP | SAP's Release Blocked Invoices app, NetSuite's approval workflow |
Start by cleaning the setup: tolerance limits, order line settings (GR-based IV in SAP, Match Bill to Receipt in NetSuite) and supplier records, because automation on loose tolerances only pays wrong invoices faster. Then automate intake and duplicate checks, create each invoice in the ERP with its purchase order reference, route exceptions by type, and track blocked invoices by reason, age and cash discount date.
Tip: If an integration creates your invoices or vendor bills, confirm in a sandbox that your match and approval workflow runs on invoices created that way before you switch over.
The match gets harder when the receipt is not in the ERP: receiving runs in a separate warehouse system or database, a legacy system behind the firewall holds part of the data, or SAP and NetSuite run side by side after an acquisition. Then the job is to bring the receipt or order into the ERP before the invoice needs it.
How engini Automates the Three Way Match Around SAP and NetSuite
engini runs the steps around the three way match as a workflow you can read, and leaves the match, the block and the approval to the ERP. Finance and operations teams build it in Workflow Studio without code; developers can run the same actions from code.
- Invoice intake. A workflow starts when an email arrives in Gmail or Outlook or a file is added to Google Drive, or runs on a schedule to collect files from SFTP or a folder on your own servers. The Analyze Invoice action "reads an invoice and returns the supplier, the invoice number and date, the totals and currency, the tax registration number, and every line item," and custom properties pull details such as the purchase order number (engini docs: AI tools).
- SAP S/4HANA. Through the OData services your SAP administrator exposes: get, create, update and delete records on any object a selected service exposes, plus a custom request to any endpoint, on a cloud tenant or an on-premises or private-cloud system (engini docs: SAP S/4HANA).
- SAP Business One. Get, create, update and delete records, also in batch, and upload or download attachments; on-premises databases connect through the On-Prem Agent.
- NetSuite. Create, update, upsert, delete and get records, with triggers on created or updated records checked as often as every 15 minutes. A NetSuite administrator sets up the integration record, role and tokens first (engini docs: NetSuite).
- Receipts that live elsewhere. Database connectors and the On-Prem Agent reach a warehouse system or legacy database behind your firewall, with no inbound ports opened. Every integration runs both ways, and custom fields and custom objects are read live.
- Exceptions. Conditions, loops and data transformation check each invoice and route each exception type. Tables hold the exception list, and a message goes to the owner by email, Slack or Teams with the facts attached. An AI agent step proposes the order for an invoice with no number and summarizes each exception; the workflow's rules check the proposal before anything is written.
- Approvals stay in the ERP. engini does not add its own approval step before an action. Release and approval stay in SAP and NetSuite, where your controls already are.
- Record and controls. Run history, an audit log with export and streaming to a SIEM, roles, and separate development, staging and production environments. engini holds SOC 2 Type II and ISO 27001.
- From code. The same actions run through the SDKs, the CLI, the REST API or MCP, and a toolset can limit an agent to reading orders and receipts and creating invoices, with no delete.
When you do not need engini: if suppliers send invoices straight into SAP or NetSuite, most invoices carry a purchase order number, receipts are posted on time in the same ERP, and few invoices sit blocked, the ERP's own features are enough. engini fits when intake is manual, receipts or orders live in another system, you run more than one ERP, or exceptions sit for days. See also accounts payable automation on SAP and NetSuite, finance, NetSuite integration for AI agents, all integrations, and the guide to financial workflow automation.
Agent gateway
Ship agents into systems you can’t afford to break
Connect AI agents to your ERP, CRM, financial and legacy systems through MCP, SDK, API or canvas, with secure auth, tool permissions and an audit trail built in.
Frequently Asked Questions
What is a three way match in accounts payable?
A three way match checks that a supplier invoice agrees with its purchase order and goods receipt, within set tolerances, before the invoice is paid. It stops payment for goods that were not ordered, not received, or billed at the wrong price.
What is the difference between a two way and three way match?
A two way match compares the invoice with the purchase order only; a three way match also checks the goods receipt.
How does the 3-way match work in SAP?
SAP S/4HANA checks each invoice item against the purchase order and goods receipt during invoice verification, using tolerance keys set per company code. An invoice over an upper limit is posted with payment block R and released later in the Release Blocked Invoices app.
Does NetSuite support three way matching?
Yes, through the 3 Way Match Vendor Bill Approval workflow in the NetSuite Approvals Workflow SuiteApp. It needs Advanced Receiving and routes bills with discrepancies to a supervisor.
What tools automate three-way matching in SAP?
SAP itself automates the comparison, the payment block and the release of blocked invoices. Other tools automate what surrounds it: reading invoices, finding missing purchase order numbers, catching duplicates and following up exceptions.
Can AI agents do a three way match?
They can, but the ERP should keep the matching rules, because those are the controls auditors test. AI agents help most by reading invoices, proposing the right purchase order and explaining exceptions, with rules checking each proposal.
Sources
- SAP Help: Tolerance Limits for Invoice Postings (SAP S/4HANA 2025 FPS02)
- SAP Help: Blocking Invoices
- SAP Help: Goods-Receipt-Based Invoice Verification
- SAP Help: Release Blocked Invoices (SAP S/4HANA Cloud Public Edition 2608)
- SAP Help: Supplier Invoice OData V2
- NetSuite Help: 3 Way Match Vendor Bill Approval Workflow
- NetSuite Help: 3 Way Match Vendor Bill Approval Exception Criteria
- NetSuite Help: Setting Up 3 Way Match Vendor Bill Approval
- NetSuite Help: Vendor Bill Variances
- NetSuite Help: Bill Capture
- engini docs: AI tools (Analyze Invoice)
- engini docs: SAP S/4HANA
- engini docs: NetSuite