Tags: Payroll FI-AP DMEE SEPA BAdI CGI

The Problem

A recurring question in SAP communities and support channels: how do you make SAP generate INST in the payment XML so the bank processes the payment as an instant transfer?

Many customers configure the payment method in transaction FBZP and find no option to mark a transfer as “instant payment.” After searching through notes and community threads, the instructions seem scattered and contradictory. This post consolidates the answer.

What needs to happen in the XML

For the bank to process a transfer as a SEPA Instant Credit Transfer (SCT Inst), the generated XML file (pain.001 format) must carry the INST indicator. The standard requires adding a  (Service Level) block inside the payment information () or within each individual credit transfer (). This value tells the bank to route the order through the SCT Inst scheme rather than the standard SEPA Credit Transfer.

Option A — Service Level at payment batch level

  
    
      SEPA
    
    
      INST
    
  
  

Option B — Local Instrument at transaction level

  
    
      INST
    
  
  

The INST node is the key signal. Banks supporting SCT Inst will detect it and apply the instant processing rules (funds available within 10 seconds, 24/7/365).

This node appears at two levels in the pain.001 structure: – Batch level () — for SEPA payments – Transaction level () — for non-SEPA payments

Why it doesn't work out of the box

The CGI DMEE trees control this node through the exit function FI_CGI_DMEE_EXIT_W_BADI. If you look at the standard implementation, you'll find this code:

WHEN ''.
*   This node defines the Local instrument for the payment
    CLEAR c_value.

WHEN ''.
*   This node defines the Local instrument for the payment
    CLEAR c_value.

SAP explicitly clears this node in standard for countries including ES and DE. There is no customizing switch to change this behavior — it requires a BAdI implementation.

Solution: BAdI FI_CGI_DMEE_COUNTRIES_CUST

The exit function calls two BAdIs in sequence:

BAdI Who can implement Purpose

The recommended approach is to keep the standard implementation intact and use the customer BAdI to override only the nodes that need modification.

Step-by-step

1. Apply the latest CGI tree notes Implement all notes listed in the overview of SAP Note 2253571 (collective information note for CGI_XML_CT and CGI_XML_DD). The DMEE tree references exit function modules delivered by these notes — having an outdated implementation causes unexpected behavior.

2. Create a BAdI implementation In transaction SE19 (or via SPRO), create an implementation for BAdI FI_CGI_DMEE_COUNTRIES_CUST in Enhancement Spot ES_IDFI_CGI_DMEE.

3. Implement the method In the BAdI method, check the node path and assign the value INST when appropriate:

abap " Pseudocode — adapt to your business logic WHEN ''. c_value="INST".

You can add conditions here to apply INST only to specific payment methods, house banks, or company codes — giving you full control over which payments are sent as instant transfers.

1. Follow the official guide SAP Note 2253571 includes an attachment: ‘Customer Enhancement in CGI with BAdI_150416.docx'. This document provides a full worked example of how to implement the customer BAdI correctly.

Alternative: PMW user exits (OBPM3 / OBPM1)

If the information needed by the bank is not available in the standard payment structures (FPAYH, FPAYP, FAPYHX), you can use Payment Medium Workbench exits to enrich the data before it reaches DMEE:

• Event 05 (transaction OBPM1) → populates FPAYH-REFxx fields
• Event 06 (transaction OBPM3) → populates FPAYHX-ZREFxx fields via a custom function module with the same interface as FI_PAYMEDIUM_SAMPLE_06. The ZREF fields are then mapped in the DMEEX tree.

Note: ZREF fields cannot be populated via Event 05 — use Event 06 for those.

Reference: SAP Note 965723 — PMW: use of exits (transaction OBPM3)

ECC vs S/4HANA / SAP SuccessFactors Employee Central Payroll

System CGI Tree Notes

Reference Notes

Note Content

Summary

There is no standard customizing option to activate SEPA Instant Transfers in SAP payment files. The path is:

1. Ensure CGI tree notes are up to date (note 2253571 overview)
2. Implement BAdI FI_CGI_DMEE_COUNTRIES_CUST to set c_value="INST" for the  node
3. Add business logic conditions as needed (payment method, company code, etc.)
4. Consult the example document in note 2253571 for implementation details

This is a consulting activity, not a software error — SAP does not plan to deliver INST as a standard default for any country. The BAdI is specifically provided for this kind of bank- and country-specific customization.

Have you implemented SEPA Instant Transfers in your system? Share your experience in the comments.