3791713 - Intercompany Supplier Invoices via New EDI/Background Framework Are Blocked (R) And Start Workflow Due To Tolerance Key AN In SAP S/4Hana Cloud Public Edition

• After switching to the new EDI/background framework channel for classic intercompany, supplier invoices are created on the MM side.
• The amount check with tolerance key AN applies to invoices without a purchase order reference.
• Invoices receive payment block R and the approval workflow for supplier invoices starts.
• No specific error messages or error codes were reported.

• Product: SAP S/4HANA Cloud Public Edition
• Intercompany processes (Public Cloud)

1. Use the new EDI/background framework channel for classic intercompany payable postings.
2. Post an intercompany payable; the system creates a supplier invoice (MM) without a purchase order reference via MIRO/MM BAPI.
3. The company-code-level amount check (tolerance key AN) applies and the invoice is set to payment block R.
4. The approval workflow for supplier invoices starts.

• The legacy channel posted directly to Finance, bypassing invoice verification, so no block or workflow occurred.
• The new channel posts as a purchasing-style supplier invoice without a purchase order reference; the company-code-level amount check (tolerance key AN) applies.
• When the invoice amount exceeds the limit, the system sets a payment block and starts the approval workflow.
• Tolerance key AN is defined per company code only; it cannot be selectively deactivated for only intercompany invoices.
• The payment block is system-set at posting time and cannot be auto-released for this tolerance scenario.

1. Preferably adopt a purchase-order-based flow (Advanced Intercompany) so the “no PO reference” amount check does not apply, removing both the block and the workflow at source.
2. If a purchase-order reference is not feasible, configure the Manage Workflows for Supplier Invoices app to exclude intercompany invoices (for example, by supplier) so approval does not start.
3. Release remaining blocked intercompany invoices using the Release Blocked Invoices app, filtered to the intercompany supplier only, and perform releases under controlled review. Do not mass-release all blocked invoices.
4. Where organizationally possible, segregate intercompany postings into a dedicated company code and adjust the amount check there without impacting other invoices.
5. If selective exemption is required as a standard feature, submit a request via the Customer Influence program.

• Refer to: 3737906 - Switch to the new background-framework channel for classic intercompany payables
• Refer to: Intercompany payables posting: mandatory transition from IDoc to successor channel
• Refer to: 2334433 - IDoc invoice not blocked on tolerance violation (context difference)
• Refer to: 3089121 - Workflow start scope for Logistics Invoice Verification invoices
• Refer to: 3748502 - Amount block behavior and release considerations
• Refer to: 3072643 - Support channels and best practices

intercompany, edi, background framework, bgpf, supplier invoice, invoice verification, block R, tolerance key AN, workflow, liv, miro, mm bapi, no po reference, release blocked invoices, manage workflows , KBA , MM-IV-LIV-IC-2CL , Intercompany processes (Public Cloud) , Problem