3619848 - Bank Charges Categorization in SAP S/4HANA Cloud Public

Business requirement to categorize the Bank Charges for payment in the system.

SAP S/4HANA Cloud Public Edition 

The categorization of bank charges for outgoing payments, particularly how it's communicated in the outgoing payment file (e.g., XML format), is primarily controlled by the "Charge Bearer" (ChrgBr) instruction. This instruction determines who bears the bank charges:

SHAR (Shared): Charges are shared, meaning both the debtor (your company) and the creditor (recipient) bear their own bank charges. This is often the default.
DEBT (Debtor): All transaction charges are to be borne by the debtor (your company).
CRED (Creditor): All transaction charges are to be borne by the creditor (the recipient of the payment).

The definition of different instruction keys in your system using the configuration activity "Define Instruction Keys" (SSCUI ID 101046). These instruction keys can then be assigned to specific suppliers.

The actual mapping of instruction key (or other payment data) to the ChrgBr field in the payment XML file (e.g., pain.001.001.03 for SEPA) is done in the "Map Format Data for Payments" (SSCUI ID 100558) configuration activity.

Here, it's possible to define the rules for how the system fills the payment data in the payment format. Also it's possible to define conditions that translate the instruction key or other relevant data into the appropriate SHAR, DEBT, or CRED values in the XML.

It's important to note that for SEPA payments, the ChrgBr value is often SLEV (Shared - unless agreed otherwise), and specific rules apply. However, for non-SEPA payments, the 00, 01, 02 codes (corresponding to SHAR, DEBT, CRED) are commonly used internally and then mapped to the XML standard.

Automatic Payment Different Bank Charge Depen... - SAP Community

Bank Charge, XML File, ChrgBr, Instruction Keys , KBA , FI-BL-PT-BA-2CL , bank statement (Public Cloud) , How To