Adapting SAP to KSeF identifiers and ISO 20022

We help combine these requirements into a single project for adapting SAP to KSeF payment identifiers and ISO 20022: from analysis of current processes, through system configuration and development, to testing with banks and preparing finance users. Our approach is to align the systems with the new banking and tax requirements while taking into account the KSeF solution already in use. We support scenarios for organizations using:

• All for One KSeF,
• SAP DRC (Document and Reporting Compliance),
• other KSeF solutions integrated with SAP,
• external financial and accounting systems, as long as the data required for payments is available in standard or usable locations in SAP.

For customers using All for One KSeF, we can design the process within a cohesive All for One ecosystem that supports invoice handling, payments, JPK reporting, and other local compliance obligations. Based on years of experience, we have identified the areas that may pose the greatest challenges when adapting the payment process to the upcoming changes.

Check the project scope for your system and get started today.

Since February 2026, issuing and receiving structured invoices via the National System of e-Invoices (KSeF) has been mandatory in Poland, and since April 1, 2026, the obligation to issue structured invoices has covered almost all active VAT taxpayers. As of January 1, 2027, payments for KSeF invoices will have to include either the KSeF invoice number or the collective payment identifier. The obligation will apply to payments between active VAT taxpayers and payments made under the split payment mechanism.

For companies using SAP ECC and SAP S/4HANA, this means the need to adapt the payment process so that the system can:

• store the KSeF number and link it to the invoice,
• use the KSeF number when preparing the bank transfer,
• handle payments for multiple invoices with a single transfer,
• send the correct identifier to the bank,
• check the completeness of the data before generating the payment file.

Proper preparation of the system is both a legal obligation and the basis for maintaining operational continuity, especially for organizations that handle large payment volumes, use the split payment mechanism, work with an extensive supplier base, or process payments centrally for several companies within a group.

For many organizations, this will be more than just adding a new field. The review may need to cover payment medium formats, vendor master data, bank accounts, custom enhancements, electronic banking integrations, collective payment handling, and data completeness checks before file generation. The challenge is greatest for companies that work with multiple banks, manage multiple company codes, process bulk payments, use split payment, or run highly customized payment processes in SAP.

ISO 20022 is an international standard for financial communication that changes the way payments are prepared and sent between a company and a bank. For organizations using SAP ECC or SAP S/4HANA, this means verifying whether the current payment process will comply with the banks’ new requirements. The entire process can be verified: from invoice and counterparty data, through the payment proposal, to transferring the file to electronic banking and subsequent settlement.

SAP alignment with ISO 20022 may primarily cover:

• payment file formats, including the transition to XML messages, such as pain.001.001.09 for outgoing transfers,
• mapping data from SAP to ISO 20022 structures so that the bank receives complete and accurate information,
• counterparty data in SAP, especially addresses, bank accounts and other data required by banks,
• integration between SAP and electronic banking, including file testing for individual banks,
• handling settlements and bank statements, e.g., in camt.052 and camt.053 formats if used in the organization.

This is especially important for companies using multiple banks, multiple companies, foreign payments, bulk payments or custom extensions in SAP.