
More automation in payment transactions
TYRIOS now supports various SEPA formats for direct debits and credit transfers
Imagine you have everything ready: The customer invoice has been written, the payment run started - and then you get a response from your bank: "SEPA file not readable - format error." Now the annoying troubleshooting begins: Which format was meant? Where can you even change it? Who actually decided that there have to be so many SEPA variants?
Unfortunately, this happens more often than you might think. Some banks have made a joke of regularly changing the supported formats on their portals. To make this problem a thing of the past in future, we will simply support all common SEPA formats for direct debits and credit transfers in TYRIOS. You simply set the appropriate format - and the rest runs automatically.
Why this is an issue at all
SEPA is not just SEPA. Although there is a standardised payment area, each bank does its own thing when it comes to the actual technical implementation. Some banks expect a PAIN.001.001.03 file for credit transfers, others rely on PAIN.001.001.09 or even on special variants for certain countries or providers. The same applies to direct debits.
In practice, this leads to a real problem: if you use the wrong format, the payments are rejected - and you have to rework them manually.
This costs time, nerves and, in the worst case, even money. What's particularly annoying is that you usually only find out about the error when you upload the file - and your entire payment process comes to a standstill.
The solution: Automatically the right format
With the new function in TYRIOS, you can now store the correct SEPA format once throughout the system. As soon as this is done, the system takes care of everything else:
-
The correct direct debit format is automatically used for direct debits (e.g. customer payments, membership fees, recurring invoices).
-
For credit transfers (e.g. supplier invoices, credit notes, rents or recurring payments), TYRIOS uses the appropriate transfer format.
You no longer have to manually export, reformat or use special tools. You select the format once - and TYRIOS ensures that it is always converted correctly.
What are the specific benefits?
This small change has a big impact:
✅ Fewer returns for payment files
✅ No more format chaos - no matter which bank you work with
✅ Automated payment processes without manual post-processing
✅ Secure processing of invoices, credit notes and regular payments
✅ Less effort in accounting
Typical use cases
The new SEPA format feature is used wherever payment files are created in TYRIOS:
-
Customer invoices with direct debit
-
Refunds and credit notes
-
Payments to suppliers
-
Processing of regular fees or rental payments
-
Integration with DATEV or other accounting systems
In short: Wherever money flows, TYRIOS now ensures the right data flow.
Conclusion: A small adjustment with a big effect
With the new support for various SEPA formats, we are taking a further step towards fully automated, efficient financial processes. No more format stress, no more manual post-processing - instead a system that adapts to your reality.
This makes TYRIOS even more of a central platform for your entire business - from the quote to the final booking.
Click here for the corresponding KnowledgeBase on how to set up the SEPA formats.
What does "PAIN" actually mean?
The term PAIN stands for "Payments Initiation" and refers to a group of XML formats that are used to digitally transmit payments in the SEPA area.
There are different PAIN formats depending on the type of payment:
- PAIN.001: Credit transfers
- PAIN.008: Direct debits (Direct Debit)
The additional numbers (e.g. 001.001.03) indicate the version of the format - similar to software versions. Some banks insist on certain versions, others are more flexible. This is exactly why it is so important that TYRIOS now supports different PAIN formats - so that you can always use the right one.