MM / P2Pintermediate

MM Invoice Verification Part 2: Configuration Essentials

Key takeaway

Set up LIV: company code defaults, tax handling, tolerance keys per company code, number ranges, automatic payment blocks, unplanned delivery costs, GR/IR clearing account determination, duplicate invoice check and default values for MIRO.

Explanation

📌 KEY POINTS
✅ Tolerance limits are defined per company code and tolerance key (OMR6).
✅ Tax: default tax codes, jurisdiction, calculate tax automatically.
✅ Unplanned delivery costs can be distributed to items or posted to a separate G/L account.
✅ Duplicate invoice check compares supplier, reference, date, amount (configurable).
⚠️ Loose duplicate-check settings allow duplicate payments.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered the process. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TOLERANCES

OMR6 per company code; keys PP, DQ, BD, etc. (Part 3).\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 2. TAX\n• Tax codes, defaults, automatic calculation.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DELIVERY COSTS

Planned (in PO conditions) vs unplanned (distribution or G/L).

━━━━━━━━━━━━━━━━━━━━
▶ 4. DUPLICATE CHECK

Criteria: company code, reference, invoice date, currency/amount.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GR/IR AND DEFAULTS

WRX account determination; MIRO default transaction and layouts.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Configure tolerances for company code.
Set duplicate check criteria.
Define unplanned delivery cost handling.

✅ CHECKPOINT: a duplicate invoice triggers a warning/error and unplanned freight posts as defined.

Code example

ABAP Code

===== STEP 1: SPRO > MM > Logistics Invoice Verification =====Invoice block > set tolerance limits (OMR6) per company codeIncoming invoice > set check for duplicate invoices (reference, invoice date, company code)Incoming invoice > configure unplanned delivery costs (distribute or separate G/L) ===== STEP 2: account determination =====OBYC WRX (GR/IR) | UPF unplanned delivery costs (if separate account)

Real project scenario

A client's duplicate check only compared reference numbers; suppliers resent invoices with slightly different references and were paid twice. Enabling reference + invoice date + amount criteria and training AP on warnings stopped the duplicates.

Common mistakes

Weak duplicate check.
Unplanned costs distributed to stock unintentionally.
Wrong tax defaults.
No tolerances per company code.
Missing WRX entries.

Best practices

Configure strict duplicate checks.
Decide delivery cost treatment.
Maintain tax defaults.
Review tolerances with finance.
Test all postings.

Interview angle

Questions: "Where are LIV tolerances configured?", "How are unplanned delivery costs handled?", "How does the duplicate invoice check work?"
Strong answer: OMR6 tolerances, tax, delivery costs, duplicate check, GR/IR account and defaults.

Practice this lesson

Quick check

1. During invoice verification, the system performs a duplicate invoice check. Which combination of fields is typically used by this check?

2. How are unplanned delivery costs typically handled during invoice entry in MIRO when they were not anticipated in the purchase order?

3. A purchasing document is flagged for 'GR-Based Invoice Verification'. What is the direct consequence for the invoice posting process?

Interview questions

1. An invoice-to-pay workflow integrated through BTP Integration Suite is intermittently posting invoices with incorrect withholding tax amounts, but only for vendors subject to a specific country's withholding tax scheme. How would you isolate whether the defect is in SAP tax configuration, the middleware mapping, or the source invoice data?

Answer it in your own words first, then compare.

2. An AP team is parking invoices with incomplete tax data pending clarification from a third-party tax engine interface (e.g., Vertex or similar), but a batch of parked invoices failed to complete when the tax interface timed out, leaving them stuck in park status without error indication until month-end close, when they were discovered unposted. How would you troubleshoot and prevent recurrence?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.