Produce a credit transfer or direct debit file from a CSV
Not every organisation has a tool that can produce a bank file. When the batch is prepared in a spreadsheet, the question is not theoretical: how do these lines become a file the bank accepts?
Two uses
- A real file — from your CSV export: creditors, IBANs, amounts, references, execution date. The result is a compliant credit transfer or direct debit, ready to be submitted.
- A fictitious test batch — credible but entirely invented batches, to exercise your own controls, a test phase or a bank setup without handling real data.
Checked as it is produced
The generated file goes through the same rules as the validation module: it does not leave the tool with a known format error. CSV lines that cannot be converted are listed with their reason rather than silently dropped.
- IBAN format and check digits.
- Banking character set and field lengths on labels and references.
- Consistency of amounts, currencies and batch totals.
- Mandatory fields of the message and the applicable rulebook.
What is produced
Credit transfer batches (pain.001) and direct debit batches (pain.008), in the versions in force, with address blocks in the structured format where the information is available.
Frequently asked questions
Which columns must my CSV contain?
The expected columns are listed in the tool and a template is provided: creditor, IBAN, amount, reference, execution date, and the address if you pass it. Column order does not matter.
Can the generated file be used in production?
Yes, that is what it is for. As with any first batch on a new channel, a test with your bank is still advisable before switching a recurring flow.
What about direct debit mandates?
Mandate references and sequence data are taken from your CSV: the tool produces the file and checks consistency, it does not keep the mandate register for you.