SAP Three-Way Match Diagnostics

Core idea

Three-way match in SAP compares purchase order (PO) quantities and prices against goods receipt (GR) and supplier invoice. When any leg differs, the invoice blocks or posts with a variance. The goal is to find which leg is wrong, not just clear the block.

Common symptoms

• Invoice blocked in MIRO with quantity or price variance.
• GR/IR clearing account shows open items that do not net to zero.
• Missing goods receipt for a PO line even though the invoice arrived.
• Duplicate invoice warning (message type F5, F6, or custom check).
• Partial delivery creates confusion: one PO line has multiple GRs and invoices that do not sum cleanly.
• Invoice posted but PO history does not show the expected reference.

Likely causes

• GR quantity differs from invoice quantity due to over-delivery, under-delivery, or unit-of-measure conversion.
• Invoice price differs from PO net price because of price changes, scales, or conditions not copied correctly.
• Tax code or tax amount mismatch between PO, GR, and invoice.
• Currency exchange rate differences for foreign-currency POs.
• GR was reversed or cancelled after invoice posting, leaving an unmatched invoice.
• Invoice was posted against wrong PO or wrong PO line.
• Delivery costs or unplanned delivery costs were added in MIRO but not reflected in PO conditions.

Where to check in SAP

• ME23N — PO history tab shows GR and invoice references per line item. Check quantities, dates, and document flow.
• MIGO — review GR document, movement type, and whether it references the correct PO and line.
• MIRO / MIR4 — invoice document, blocked reason, and variance details. Check the Messages tab for block reasons.
• MR11 — GR/IR maintenance: lists open GR/IR items and allows write-off of small differences.
• FBL3N — line items on the GR/IR clearing account to see open debits and credits.
• ME2N / ME2L — PO list to confirm delivery status and invoice status per PO.

Key tables / transactions / objects

• EKPO — PO item data (quantity, price, delivery status, invoice status).
• EKET — PO delivery schedule lines; useful for partial delivery scenarios.
• MKPF — GR document header.
• MSEG — GR document items; links to PO via LFBNR, LFPOS, LFBJA.
• RBKP — invoice document header.
• RSEG — invoice document items; links to PO and GR.
• EKBE — PO history (aggregated view of GR and invoice per PO item).
• BSEG / BSIS — accounting line items for GR/IR account.

Diagnostic workflow

Start with the blocked invoice in MIRO or the open GR/IR item in FBL3N. Identify the PO number and line item. In ME23N, compare PO quantity, GR quantity, and invoice quantity. If GR is missing, check MIGO for unprocessed inbound deliveries or warehouse delays. If quantities differ, check whether the tolerance limits in the vendor master or company code allow the difference. If price differs, compare PO conditions (ME23N Conditions tab) with invoice conditions in MIRO. For duplicates, check RBKP for existing invoices with the same reference, amount, and vendor. Use MR11 only after confirming the mismatch is not a real business issue.

Typical fixes or next actions

• Release the invoice block if the variance is within tolerance and approved.
• Post a missing GR in MIGO if goods were physically received but not recorded.
• Request a credit memo from the vendor if the invoice overstates quantity or price.
• Reverse and repost the invoice against the correct PO line if it was posted incorrectly.
• Use MR11 to write off small, approved GR/IR differences that will not be cleared by future documents.
• Update PO price or conditions if the vendor price changed and the business agrees.
• Escalate to procurement or warehouse if the mismatch indicates a process failure (wrong goods received, theft, or system bypass).

Support takeaway

Three-way match failures are rarely a single-document problem. The operator should trace PO → GR → Invoice in that order, confirm which document is the outlier, and decide whether the fix is data correction or process change. Never clear GR/IR blindly without understanding why the mismatch occurred.

Escalation signals

• The PO, GR, and invoice quantities or prices diverge by more than the business tolerance and root cause is unclear.
• The mismatch points to a recurring supplier issue or possible fraud (duplicate invoices, altered PO prices).
• Clearing the GR/IR account requires a manual adjustment that affects financial reporting or audit trails.
• The case involves subcontracting, consignment, or pipeline materials where standard three-way matching does not apply.

Boundaries and non-goals

This guide does not cover vendor master data issues, tax jurisdiction configuration, or custom invoice validation enhancements. It also does not replace SAP standard help or company-specific approval workflows.

This is not official SAP documentation and not a replacement for system-specific analysis.