Many companies still use payment files generated by older software. This will only work as long as the bank accepts these file formats. This is precisely where action will be needed in 2026: Banks and payment service providers are transitioning to the new ISO 20022 and SEPA format standards.

The German Banking Industry Committee (Deutsche Kreditwirtschaft) is making the data format specification—Annex 3, Version 26.11—valid as of November 15, 2026, available via EBICS. Commerzbank notes that SEPA format versions 2.9 and lower will no longer be accepted as of March 2026, and that starting in November 2026, only SEPA formats version 3.7 and higher are expected to be accepted.

For corporate customers, this means: Anyone generating SEPA files from legacy systems should check now whether the PAIN versions they are using are still accepted.

A rejection can occur, for example, if your software still generates old SEPA or PAIN versions, such as older variants of:

•    pain.001 for SEPA credit transfers 
•    pain.008 for SEPA direct debits 
•    older SEPA XML files from association, ERP, or accounting software 

The actual payment data is often correct. The problem then lies in the format, in required fields, or in the version of the SEPA XML file.

SEPA-Transfer helps exactly in this situation: It imports the existing file, checks the transactions, and outputs them in a suitable format or transfers them via online banking.

1. Import an old SEPA XML file
Import existing SEPA XML files from older versions of PAIN. SEPA-Transfer can also process payment data from Excel, CSV, text, and database sources.

2. Review and consolidate transactions
After importing, you’ll see a clear overview of the included transactions in SEPA-Transfer. Invalid records can be flagged and corrected before execution. Multiple files can be combined if necessary.

3. Export to a current SEPA format
Create a new SEPA XML file from the imported transactions. This allows you to reuse old payment data without having to immediately adapt your source system.

4. Alternatively, send directly via online banking
Instead of exporting a new file, you can also transmit the transactions directly from SEPA-Transfer to your bank via online banking. SEPA-Transfer supports FinTS/HBCI-compliant batch transfers. 

Companies with older ERP or accounting systems
Does your system still generate SEPA files, but your bank requires newer formats? SEPA-Transfer can serve as a bridge: import the old file, verify the transactions, generate the current SEPA-XML, or send it directly.

Clubs with direct debit runs
Membership dues are often exported from club management software. If this software generates old PAIN versions, direct debit files may fail at the bank. With SEPA-Transfer, you can import the file and continue processing the transactions.

Tax Firms and Accounting Firms
When clients provide SEPA files from different programs, you need a flexible solution for importing, verifying, converting, and forwarding them.

Organizations with Bulk Payments
SEPA-Transfer is suitable for recurring payments such as payroll, membership dues, supplier payments, or bulk direct debits.
 

Old SEPA files often contain dozens, hundreds, or thousands of transactions. Manually re-entering this data is prone to errors and time-consuming.

With SEPA Transfer, you can retain your existing payment data and continue processing it in a structured manner:

•    less manual data entry 
•    fewer sources of error 
•    continued use of existing systems 
•    quick response to bank requirements 
•    practical interim solution for SEPA 3.7 migrations 
•    suitable for credit transfers and direct debits 
 

SEPA 3.7 introduces updated formats and stricter requirements for certain data fields. Businesses, in particular, should therefore check whether their payment software still generates compatible SEPA files. According to its current product page, SEPA-Transfer supports the new SEPA 3.7 standard and can import payment data from existing sources. 

Practical tip: Before your next batch transfer or direct debit, test whether your bank still accepts the generated SEPA file. If not, import the old file into SEPA-Transfer and create a new file that meets the requirements.

1.    Import a file
Open your existing SEPA XML, Excel, or CSV file in SEPA-Transfer.
2.    Review transactions
Check the payee, IBAN, amount, payment description, and execution date. 
3.    Export or send
Create a new SEPA file or transfer the transactions directly to your bank via online banking.