Doxis Blog  P2P & O2C

3-Way Matching in SAP: How to Run It End to End

| Fabian Rückels

A woman smiling while working on a laptop, showcasing 3-way matching in SAP with documents.

 

A supplier ships 800 of the 1,000 parts on your purchase order and invoices all 1,000. SAP blocks the invoice, and now three teams have to agree on who fixes it.

That moment is where the three-way match in SAP earns its keep, and where most of its cost sits. The comparison itself is instant. The days go into exceptions like this one.

This guide shows how 3-way matching works in SAP, how to set tolerances your finance team can defend, and how to route each discrepancy to the person who can resolve it. Scenarios from three industries show where those exceptions come from.

Key Takeways

  • 3-way matching in SAP compares each invoice line with its purchase order and goods receipt, and blocks payment when a difference exceeds the tolerance set in SAP
  • A worked example shows how one invoice with a partial delivery and a price increase would overpay a supplier by $2,700 without the match
  • Tolerance limits are a business decision owned by finance and procurement, reviewed against exception rate, touchless rate, cycle time and first pass yield
  • Each discrepancy type has a natural owner: price goes to procurement, quantity to the warehouse, a missing PO number to the requester
  • Automation adds most value around the match: capturing invoice data before it, and routing exceptions with the full document context after it

What is 3-way matching in SAP?

3-way matching in SAP is an invoice control that compares three documents before payment: the purchase order, the goods receipt and the supplier invoice. SAP checks quantities and prices line by line. If all three agree within the tolerance limits, the invoice can post and be paid. If they don't, SAP blocks it and an exception has to be resolved.

Each document comes from its own step in the purchase-to-pay process. The purchase order records what you ordered and at what price, created in ME21N. The goods receipt, posted in MIGO, records what actually arrived. The invoice is entered and checked in MIRO.

The match is one part of invoice verification, which also covers tax and legal checks before approval. The logic works the same way in SAP ECC and SAP S/4HANA.

When to use 2-way, 3-way or 4-way matching

The right method depends on whether there is something physical to receive. 3-way matching is the standard for goods. 2-way matching, which compares only the invoice and the purchase order, fits purchases where no goods receipt exists.

Procurement scenario Recommended matching method
Physical goods and inventory 3-way matching
Capital equipment with a goods receipt 3-way matching
Services 2-way matching or a service entry sheet
Software subscriptions and recurring invoices 2-way matching
Goods that need inspection before acceptance 4-way matching

Most enterprises run both 2-way and 3-way matching side by side, set per purchase order type. The table covers the common cases. Edge cases deserve a written rule so buyers and AP apply them the same way.

Service invoices and service entry sheets

Services have no goods receipt, so SAP uses a service entry sheet (SES) to confirm that the work was done. The business department approves the SES, and SAP treats it as the equivalent of a goods receipt in the three-way match.

The alternative is a 2-way match against the purchase order, with a separate approval workflow for the service confirmation. The SES route automates more of the check and leaves a cleaner audit trail. It only works when departments create entry sheets consistently and on time.

4-way matching for inspected goods

4-way matching adds a fourth document to the comparison: an inspection or quality acceptance record. The invoice is only paid for goods that arrived and passed inspection.

This makes sense for components with quality requirements, where a delivery can arrive in full and still be partly rejected. In those cases the accepted quantity is what the invoice should match.

A worked example: one invoice, two variances

Back to the 800 parts. The numbers show what the match catches and what the company actually owes.

Your purchase order covers 1,000 parts at $12.00 each, a total of $12,000. The warehouse posts a goods receipt for 800 parts, because the rest are on backorder. The supplier then invoices 1,000 parts at $12.30 each, a total of $12,300.

When the goods receipt posts, SAP debits inventory and credits the GR/IR clearing account at the purchase order price, $9,600 in this case. When an invoice posts, it debits GR/IR and credits the supplier. Once quantities and prices agree, GR/IR clears to zero. That clearing account is what makes the match visible in your books.

Here the match finds two variances at once. The quantity variance is 200 parts invoiced but never received. The price variance is $0.30 per part, 2.5% above the agreed price. With a price tolerance of 2% and no tolerance on quantity, SAP blocks the invoice for payment.

What you actually owe is 800 parts at $12.00, or $9,600. Paying the invoice as submitted would have cost $12,300, an overpayment of $2,700. The open questions are who confirms the backorder and who challenges the price. The next sections cover both.

Set tolerance limits your finance team can defend

Tolerance limits decide which small differences SAP accepts without an exception. Rounding differences and small price movements are normal, and blocking every one of them floods the AP queue. Tolerances are configured centrally in SAP customizing and applied to every invoice.

Absolute and percentage tolerances

An absolute tolerance sets a fixed amount, such as a maximum price variance of $20 per invoice. A percentage tolerance sets a relative limit, such as 2% per line item. Most companies combine both, so a small percentage on a large order can't add up to a large sum.

Take an invoice of $10,000 that differs from the purchase order by $15. With an absolute tolerance of $20, SAP accepts it automatically. Without one, the same $15 creates an exception that someone has to review. Tolerances can be set per line item or per vendor.

Who owns the rules, and how to review them

Tolerance limits are a business decision, owned by finance and procurement. Limits that are too generous let price drift through unnoticed. Limits that are too tight create exceptions that cost more to process than the variance is worth.

Document every rule and every change with its reason, so auditors can follow the history. Restrict who can change tolerance settings in SAP, and require a second approval for each change. Then review the rules regularly against four KPIs:

  • Touchless processing rate: the share of invoices that go from receipt to posting with no manual step, your main measure of automation
  • Exception rate: the share of invoices that need manual review, where a high value points to master data or purchasing gaps
  • Cycle time: the average time from invoice receipt to approval for payment, which decides whether you capture early payment discounts
  • First pass yield: the share of invoices that pass the match on the first attempt, where a low value points to supplier data quality

Read the four together. A rising touchless rate with a rising cycle time, for example, means the exceptions that remain are taking longer to resolve.

Route each discrepancy to the person who can fix it

An exception is resolved fastest by the person who owns its cause. When every blocked invoice lands with accounts payable first, AP becomes a switchboard, chasing buyers and the warehouse by email. Routing by discrepancy type sends each case straight to its owner.

Discrepancy Usual cause Who resolves it
Price variance Price change missing from the PO, or a wrong price on the invoice Procurement
Quantity variance Partial delivery, a wrong goods receipt or a wrong invoice quantity Warehouse or goods receipt
Missing PO number Supplier left it off, or the purchase bypassed the PO process (maverick buying) Requester or buyer
Wrong line item Wrong item delivered or invoiced Procurement and requester

The pattern behind the table matters as much as the individual cases. If one supplier causes most price variances, the fix is a contract or master data update. If one plant causes most quantity variances, the fix is in its goods receipt routine.

When the invoice arrives before the goods receipt

Invoices regularly arrive before the warehouse has posted the goods receipt. SAP then finds nothing to match against, and an invoice that may be entirely correct gets blocked.

The fastest resolution sits with the person who placed the order. They see the blocked invoice in their task list, check whether the goods have arrived, and trigger the goods receipt check again once the receipt is posted. A digital delivery note process shortens this gap, because the receipt is recorded when the goods arrive.

Deadlines, escalation and stand-ins

Decide which discrepancies block payment entirely, such as a large price variance, and which only need additional information while the invoice moves on. Then give each exception type a resolution deadline, for example two business days.

Clear deadlines only help if something happens when they pass. Route unresolved cases to a manager or a named backup approver after the deadline. Set up stand-ins for every approval step, so a vacation never stops an invoice.

Automate Work. Accelerate Business.

Bring together AI, ECM, and workflow automation in one powerful enterprise platform.

How 3-way matching plays out in your industry

The match works the same in every industry. The exceptions it produces don't. Each scenario below shows where they typically come from and what helps.

Manufacturing: partial deliveries and surcharges

Manufacturers buy high volumes of production material, often from suppliers who ship in batches. Partial deliveries invoiced in full are the classic quantity variance. Raw-material surcharges that suppliers add to the invoice, but nobody added to the purchase order, are the classic price variance.

Both are easier to resolve when the buyer sees the invoice, the order and the delivery note side by side. They can confirm the backorder or approve the surcharge in one step.

Automotive supplier Eissmann Group Automotive automated inbound invoice capture with SAP integration and workflow-based invoice verification for up to 3,800 participants. Volume grew from around 80 to 100 to 120 invoices a day.

The company gained full transparency at every processing stage and now meets its discount deadlines. It rolled the process out to its sites in the US, the Czech Republic and Mexico.

Krone, the commercial vehicle and agricultural machinery group, automated its entire inbound invoice process. Invoices arrive by email, on paper or as IDocs. Each one is captured automatically and checked in SAP before accounting validates and releases it. Krone extended the process to its subsidiaries in France and the Netherlands.

Energy and utilities: maintenance and project invoices

Illustrative scenario. A utility runs maintenance contracts across dozens of sites. Many invoices are for services, so they have no goods receipt and depend on service entry sheets. When a site manager approves the entry sheet late, a correct invoice waits in the queue.

Large network projects add invoices against framework orders, where quantities are confirmed in stages. The useful rules here are clear deadlines for entry sheet approval, and routing to the site that ordered the work.

Energy and utilities companies are already among the most automated document processors. In the Market Momentum Index: IDP Survey 2025 by AIIM and Deep Analysis, which surveyed more than 600 US and European organizations, the sector reported 67% of document processing automated, tied for the highest share.

Transport and logistics: freight and subcontractor invoices

Illustrative scenario. A logistics provider receives thousands of carrier and subcontractor invoices a month. Fuel surcharges and accessorial charges often differ from the agreed rate. Volumes billed can also differ from what was actually moved.

Price variances dominate here, and many sit just above the tolerance limit. A vendor-specific tolerance for carriers with known surcharge rules keeps the queue manageable. Capturing proof of delivery digitally helps the quantity side, because the receipt exists before the invoice arrives.

Keep an audit trail your auditors can follow

For US companies, the three-way match is one of the most common internal controls over purchasing, and external auditors commonly test it as part of SOX audits. They want to see who cleared each exception, and on what basis.

Three controls make that possible. Log every action with user and timestamp, from the first match attempt to final release. Enforce segregation of duties through roles, so the person who posts an invoice can't also approve it.

Link the invoice, purchase order, delivery note and approval record together and keep them in a tamper-proof archive. SAP records every posting with the user and a timestamp. Audit-proof retention of the documents themselves needs an enterprise content management layer next to SAP.

Where automation fits around the SAP match

The match itself is rule-based and fast. The manual work sits before it, when invoice data has to be captured, and after it, when exceptions have to be resolved. That is where automation pays off.

Before the match, AI classifies each incoming document, for example as an invoice or a credit note. OCR and content understanding then extract the header and line items, including the purchase order and delivery note numbers that the match depends on.

With Doxis, the match then runs inside SAP. Each invoice line is assigned to its purchase order item and goods receipt, and checked against the tolerance limits you set in SAP customizing. Invoices within tolerance post in SAP without a manual step. Your tolerance rules stay in one place.

When a line fails, the person responsible gets the case with the invoice, purchase order and delivery note in one view. They can resolve it without deep SAP knowledge, and every step lands in the audit trail.

Start with a pilot covering a small group of suppliers and simple rules. Measure the four KPIs, then widen the scope. You get quick results and learn where your exceptions really come from.

Clear your exception queue in SAP with Doxis

Blocked invoices cost you early payment discounts and AP time. With Doxis, invoices that match post in SAP on their own, and the ones that don't reach the right person with everything needed to decide.

Doxis P2P for SAP covers the full process from invoice intake to audit-proof archiving. The same platform also covers contract management, so the supplier agreements behind your purchase orders sit next to the invoices they govern.

  • Invoices from every channel captured and extracted automatically
  • Line-level matching inside SAP against your own tolerance limits
  • Exceptions routed by discrepancy type, with deadlines and escalation
  • Invoice, purchase order and delivery note in one view
  • A complete audit trail of every match, exception and approval
  • Tamper-proof archiving linked to the SAP posting

Doxis Purchase-to-Pay Automation for SAP S/4HANA is SAP-certified for Clean Core with RISE with SAP on SAP S/4HANA Cloud Private Edition. Request a free demo.

Automate Work. Accelerate Business.

Bring together AI, ECM, and workflow automation in one powerful enterprise platform.

Frequently Asked Questions About 3 Way Matching in SAP

What happens when an invoice exceeds the tolerance in SAP?

SAP blocks the invoice for payment and it becomes an exception. Someone has to resolve the variance, for example with a corrected purchase order or a credit note, before the invoice can be released.

What if the supplier invoice arrives before the goods receipt?

The invoice is blocked until the goods receipt is available. The person who placed the order can trigger the check again once the receipt is posted.

Which SAP transactions are involved in 3-way matching?

The purchase order is created in ME21N, the goods receipt is posted in MIGO, and the invoice is entered and verified in MIRO. Blocked invoices are released in MRBR.

Does 3-way matching apply to service invoices?

Yes, when you use service entry sheets. SAP treats the approved service entry sheet as the equivalent of a goods receipt and matches the invoice against it and the purchase order.

Is 3-way matching required for SOX compliance?

SOX doesn't prescribe 3-way matching. It requires internal controls over financial reporting, and the three-way match is one of the most common controls auditors test for purchases of goods.

Does Doxis work with both SAP ECC and SAP S/4HANA?

Yes. Doxis posts invoices in SAP ERP (ECC) and SAP S/4HANA. Doxis Purchase-to-Pay Automation for SAP S/4HANA is SAP-certified for Clean Core with RISE with SAP on SAP S/4HANA Cloud Private Edition.

Is Doxis ISO 27001 certified?

Yes. The Doxis information security management system (ISMS) is certified to ISO 27001.

Fabian Rückels

Fabian is an experienced software evangelist, solution engineer, and sales leader with a passion for high-quality software and outstanding customer service. His mission is to revolutionize how companies tackle purchase-to-pay (P2P) and order-to-cash (O2C) natively embedded in SAP through Doxis's leading Intelligent Content Automation (ICA) solution. Fabian has deep technical knowledge (e.g. SAP ecosystem, eInvoicing, databases, APIs, mobile development environments and user experience) and extensive market experience with the SAP client base.

You might also be interested in

How can we help you?

+49 (0) 30 498582-0
Please add 3 and 1.

Your message has reached us!

We appreciate your interest and will get back to you shortly.

Contact us

Table of contents