3769147 - Supplier invoice blocked or in error due to missing goods receipt in 3-way match in SAP S/4 HANA Cloud Public Edition

When a supplier invoice is integrated from 'SAP Business Network (Ariba Network)' into SAP S/4HANA Cloud Public Edition before a 'Goods Receipt (GR)' has been posted against the corresponding purchase order, you may observe one or more of the following:

• The invoice is saved with status "With Errors" or blocked for payment due to quantity variance.
• Tolerance Key DW (Quantity Variance - GR quantity = 0) is triggered during invoice posting.
• 3-way match (Purchase Order / Goods Receipt / Invoice) reconciliation fails because no GR document exists at the time of invoice posting.
• After the GR is posted, the invoice does not automatically reconcile or re-attempt posting - manual reprocessing by the Accounts Payable team is required.
• High volumes of invoices in error state accumulate, causing operational overhead and potential payment delays.

SAP S/4HANA Cloud Public Edition

1. Create a Purchase Requisition (PR) in SAP S/4HANA Cloud Public Edition and obtain approval.
2. Allow the system to generate a Purchase Order (PO) from the approved PR.
3. Confirm that the PO is transmitted to SAP Business Network (Ariba Network).
4. Do NOT post a Goods Receipt against the PO at this stage.
5. Using a supplier account on SAP Business Network, create and submit an invoice referencing the PO before any GR is posted.
6. Allow the invoice integration to run — the invoice is transferred into SAP S/4HANA Cloud.
7. Observe that the invoice is saved with status "With Errors" or blocked for payment due to missing GR.
8. Post the Goods Receipt against the PO in SAP S/4HANA Cloud.
9. Observe that the previously errored invoice does NOT automatically re-attempt posting or release — manual AP reprocessing is required.

When an invoice arrives before a Goods Receipt is posted, the delivered quantity on the Purchase Order item is zero. During invoice posting, the system evaluates the quantity difference between the invoiced quantity and the delivered quantity and applies Tolerance Key DW (Quantity Variance when GR Quantity = 0). Depending on the configured tolerance limit for DW, the system either blocks the invoice for payment or saves it with status "With Errors". This is standard, designed system behavior. Once the invoice is in error or blocked state, there is no automatic mechanism to re-attempt posting unless the appropriate background jobs and configuration are in place.

The following standard SAP S/4HANA Cloud Public Edition features and SSCUI-based configurations eliminate or significantly reduce the need for manual Accounts Payable reprocessing in this scenario. No custom development, BAdI implementation, or custom code is required.

Note : Apply all configuration changes in a test or quality system first and validate end-to-end before transporting to production.

1. Configure Tolerance Key DW — Quantity Variance (no GR posted)
   1. Navigate to: Manage Your Solution → Configure Your Solution → Procurement → Logistics Invoice Verification → Set Tolerance Limits (SSCUI for Tolerance Keys).
      • Locate Tolerance Key DW and set it to Check Limit (block rather than reject). When configured this way, invoices received without a GR are placed in a payment block state instead of an irrecoverable error state. This block is automatically lifted once the GR is posted and the blocking reason is resolved by the Release Blocked Invoices background job (see step 3).
2. Enable GR-Based Invoice Verification (WEBRE flag).
   • Activate the GR-Based Invoice Verification (WEBRE) indicator on the vendor master record or at the Purchase Order item level. This ensures that invoice matching is performed against delivered quantities only. Invoices received before a GR are placed in a controlled block state that is automatically releasable once the corresponding GR is posted.
3. Schedule background jobs via the Schedule Supplier Invoice Jobs — Advanced app
   • Use the Fiori app Schedule Supplier Invoice Jobs — Advanced (app ID F1683) to schedule the following standard background programs:
     1. Verification in Background (RMBABG00): Automatically re-attempts posting of invoices that were saved in "Defined for Background Verification" status because no GR existed at the time of the initial posting attempt. This is the standard SAP retry mechanism for invoice-before-GR scenarios.
     2. Release Blocked Invoices (MRBR): Automatically releases payment blocks where the blocking reason (e.g., Tolerance Key DW) is no longer valid following GR posting.
   • Recommended scheduling interval: every 2–4 hours. This ensures that invoices are automatically posted or released in the next job cycle after GR posting, eliminating the need for manual AP intervention.
4. Configure GR/IR automatic clearing (SSCUI 101971)
   • Configure automatic clearing criteria for the GR/IR clearing account via SSCUI 101971. Schedule the Maintain GR/IR Clearing Account job via app F1683 to run periodically. This ensures that matched GR and invoice line items are cleared automatically without manual journal entry.
5. Enable invoice parking for invoices received without a goods receipt (SAP Business Network integration parameter).

In SAP Business Network / Cloud Integration Gateway (CIG) configuration, consider enabling the invoice parking parameter INV_HDR_PRK_NOSES_POGRX_ENBLD. When active, invoices received via Ariba Commerce Automation without an existing GR are parked in SAP S/4HANA Cloud rather than saved with errors. Parked invoices can subsequently be posted cleanly by the RMBABG00 background job once the GR is available.

Recommended configuration combination: Configure Tolerance Key DW to Check Limit, enable the WEBRE flag on vendor master or PO items, and schedule both RMBABG00 and MRBR background jobs via app F1683. This combination covers the complete invoice lifecycle from initial receipt through automatic release following GR posting, without any manual AP intervention.

supplier invoice, goods receipt, GR, 3-way match, three-way match, invoice blocked, invoice error, missing GR, Tolerance Key DW, WEBRE, GR-based invoice verification, MRBR, release blocked invoices, RMBABG00, verification in background, F1683, invoice reconciliation, Ariba Network, Ariba Commerce Automation, J82, 42K, INV_HDR_PRK_NOSES_POGRX_ENBLD, invoice parking, SSCUI 101971, GR/IR clearing, MM-FIO-IV-2CL, SAP S/4HANA Cloud Public Edition, 2CL, automatic reposting, invoice reprocessing, quantity variance, DW tolerance, 3759600, 1375425 , KBA , MM-FIO-IV-2CL , Fiori UI for Invoice Verification (Public Cloud) , Known Error