SEPA Direct Debit (SDD) instructions to the bank can only be done in one format: ISO 20022 XML Pain 008 format: All banks supporting the delivery of instructions for direct debits support this format. It includes basic payment information such as the payer's and payee's bank details, transaction amount, and payment date.
ISO 20022 XML Pain 007 format: this format allows a reversal of a pain 008 batch. With this exchange it is possible to quickly undo the collection. This format needs to be handled with extreme care as it is not guaranteed that all banks can execute this correctly.
Some banks very exceptionally accept the delivery of old legacy formats such as DOM80, Clieop, CFONB, etc... and offer a conversion module. Additionally it is sometimes possible to use also a CSV format for the delivery of the instructions.
It's important to note that different banks may support different file formats/versions for SEPA Direct Debit instructions, so it's always a good idea to check with your bank to see which formats they support and what requirements they may have for submitting payment instructions. Or you can use an intermediate party such as Twikey that supports API (www.twikey.com/api) delivery and translates the instructions in the correct banking format.
SEPA Direct Debit (SDD) supports several file formats that can be used for reconciliation and reporting purposes. Here are some of the most common formats that can be used with reporting feedback:
ISO 20022 Pain.002: is used for delivery of immediate feedback. This could be a first stage of feedback although the feedback is in most cases limited to a (non)-delivery notification.
CAMT.053 XML format: This is a format that is commonly used for bank statements and reconciliation purposes. It allows for the exchange of detailed information on SEPA Direct Debit transactions, including information on rejected or failed transactions.
CAMT.054 and CAMT.052: These formats can also be used to retrieve partial information. This is however an overlap with the 053 format and most parties only use the latter as it gives the full final view.
MT940 format: This is a legacy format that is still used by some banks and payment service providers for reporting and reconciliation purposes. It includes basic information on SEPA Direct Debit transactions, such as the transaction amount, payment date, and reference information. It is the default reporting format in a lot of countries although every country and bank have a different "flavor" of this format which makes it sup optimal to work with.
CSV format: This is a simple file format that can be used for reporting and reconciliation purposes. It typically includes basic information on SEPA Direct Debit transactions, such as the transaction amount, payment date, and reference information. However there is no standardization in this and every bank has defined it's own formatting. It is more ideal for usage in combination with Excel, Google Sheets...
CODA format (Belgium only): This is the Belgium format used as default format in Belgium by all banks for reporting and reconciliation purposes. It includes all reporting information from the bank (end-of-day) information. It is besides CAMT.053 the most advanced and structured reporting available in Europe and was created decennia before CAMT.053 was created. It continues to be used and there is no end-date foreseen.
It's important to note that different banks and payment service providers may support different file formats and reporting tools for SEPA Direct Debit transactions, so it's always a good idea to check with your bank or payment provider to see which options they offer and what requirements they may have for reconciliation and reporting.