Invoice Verification

Lessons in this topic

• Tolerance Keys, Variance Types and Invoice Blocking LogicExplains how SAP tolerance keys drive automatic price and quantity variance checks during invoice entry, and how blocked invoices are released for payment.
• Architecting Invoice Verification for Scale, Compliance and S/4HANA TransformationArchitectural decisions, governance, and migration strategy for enterprise-scale Logistics Invoice Verification across ECC, S/4HANA on-premise, private cloud, and public cloud landscapes.
• Understanding Invoice Verification and the Three-Way MatchIntroduces the business purpose of Invoice Verification, the three-way match concept, and how MIRO fits into the Procure-to-Pay cycle.
• Configuring Tolerance Keys and GR/IR Clearing for Invoice VerificationExplains how tolerance key configuration controls automatic blocking of invoices and how the GR/IR clearing account mechanics work across the invoice lifecycle.
• GR/IR Reconciliation, Invoice Reduction and Subsequent Debit/Credit HandlingCovers advanced invoice verification scenarios: GR/IR clearing account behavior and reconciliation, invoice reduction for disputed amounts, and subsequent debit/credit corrections.

Interview questions covered

• An automated invoice interface from a third-party billing system is creating invoices that consistently trigger price variance blocks against sales order related purchase orders. What integration and configuration areas would you investigate to resolve the recurring blocking pattern?
• Describe the configuration prerequisites and workflow implications for enabling Evaluated Receipt Settlement (ERS) for a vendor in an external services procurement scenario.
• During month-end GR/IR reconciliation, you find an invoice was blocked as a duplicate, but the vendor insists it's a legitimate separate delivery tied to an SD-driven return-and-replace scenario. How do you investigate and resolve this?
• A client wants to implement Evaluated Receipt Settlement (ERS) for a set of vendors providing recurring maintenance services, but is concerned about output management for self-billing notifications. What must be configured and communicated to make ERS viable for this scenario?
• An integrated procurement solution using SAP BTP Integration Suite is forwarding vendor invoices from an external OCR platform into SAP for MIRO posting via workflow, but duplicate invoices are slipping through because the duplicate check compares only invoice number and vendor, missing scanned invoices with slightly different reference numbers due to OCR misreads. How would you architect a fix spanning the integration and SAP layers?
• An EWM-managed warehouse posts goods receipts with quantities that differ slightly from what the PO specifies due to batch splitting at putaway confirmation. This is causing a spike in quantity-blocked invoices in LIV. How would you architect a resolution?
• During month-end close, a large number of GR/IR line items for invoices ingested through BTP Integration Suite from a cloud supplier portal remain open, despite goods receipts and invoices both being posted. How would you troubleshoot this using LIV tolerance settings and reconciliation tools?
• A vendor is enabled for Evaluated Receipt Settlement (ERS) on recurring maintenance service POs, but the scheduled ERS run (via MRRL) is not generating settlement documents for several service entry sheets that show as accepted. How would you diagnose why ERS is not picking up these entries?
• What architectural controls and performance techniques would you apply to keep GR/IR reconciliation manageable in a high-volume production environment where PP backflush postings generate large numbers of goods movements daily?
• An EWM-integrated warehouse posts goods receipts that trigger automatic invoice blocks due to quantity mismatches between EWM-confirmed quantities and PO order quantities, and the MRBR release queue has grown to thousands of items with no clear audit trail of who released what and why. How would you architect an audit-compliant MRBR release process for this scale?
• During a tax audit, it's discovered that several vendor invoices were blocked for tax code mismatches but were subsequently released and posted with the original incorrect tax code rather than being corrected, creating a compliance exposure. What audit control and process fix would you implement?
• During a three-way match audit you find that a batch of vendors migrated through MDG show consistent GR/IR price matches but recurring quantity mismatches, traced to an incorrect purchasing unit-of-measure conversion applied during the MDG vendor and material data migration. How would you investigate and remediate this while satisfying audit requirements?
• An Ariba-sourced invoice is parked in SAP for month-end GR/IR reconciliation but the corresponding purchase order was created directly in SAP rather than sourced through Ariba, causing a mismatch in PO reference during the parking process. How would you resolve this and prevent recurrence?
• During month-end close, GR/IR reconciliation shows large unexplained variances. Goods receipts are posted in an external warehouse system and pushed into SAP via BTP Integration Suite, and invoices arrive separately through a supplier portal. How would you diagnose and resolve the discrepancy across the landscape?
• An SAP BTP Integration Suite iFlow that pushes invoice data from a third-party e-invoicing platform into SAP via API has started silently dropping line items on invoices with more than 20 lines, causing MIRO postings to be incomplete and GR/IR tolerances to be breached. How would you diagnose and architect a fix?
• Your Ariba-integrated procurement process posts subsequent debit and subsequent credit documents for price corrections, but a batch of subsequent debits is passing LIV tolerance checks with amounts far exceeding what the original invoice compliance policy allows, apparently because the tolerance keys applied to subsequent debits differ from those applied to standard invoices. How would you investigate and correct this at scale?
• A vendor sends an invoice for 1,000 units at $10/unit, but the PO price was $9.50/unit and quantity delivered per GR was only 950 units. AP wants to pay the vendor only for what is correct and notify them of the discrepancy rather than simply blocking the invoice for manual correction. How would you configure and process this using invoice reduction, and what happens in FI as a result?
• Post go-live of an Ariba integration, invoices routed through Ariba are landing in MRBR with a price variance block even though the PO price matches Ariba's catalog price exactly. How do you troubleshoot this cross-system discrepancy?
• Invoices submitted through Ariba are being posted into SAP LIV, but a pattern of price and quantity tolerance blocks (keys PP and BR) is emerging that did not exist before Ariba go-live. As the lead architect, how would you investigate and redesign the integration to reduce false blocks?
• Walk through the standard sequence of GR/IR clearing and period-end review activities required to close inventory periods cleanly when significant GR/IR balances remain open.

Related topics