Direct debits CSV columns

What data should your SEPA direct debits CSV contain

A SEPA direct debit isn’t just about collecting: it must be backed by a mandate. The CSV for direct debits therefore needs extra fields compared with transfers.

Mandatory

Column	Notes
Debtor name	Exactly as in the mandate
Debtor IBAN	No spaces
Amount	Two decimals
Concept	What the debtor will see
Unique Mandate Reference (UMR)	Unique within your organisation
Mandate signature date	DD/MM/YYYY

Optional

Sequence type: no need to fill it in. GenerateSEPA marks every debit in the file as RCUR, including the first one on a mandate, which EPC rules have allowed since November 2016. A FRST/RCUR column in your file does not change the generated XML.
Debtor BIC: derived from the IBAN.
End-to-end reference: for internal reconciliation.
Payment category: optional (SUPP, SALA, etc.).

Template

Download a ready-to-use direct debits CSV template.

Conclusion

Six columns is all you need. The key is to keep the mandates and use a consistent UMR per debtor across collections.

Frequently Asked Questions

What if I get the mandate reference wrong?

The debtor's bank will return the collection (typically MD01 'no mandate') and your bank will charge you a return fee.

Do I need to mark the first collection as FRST?

No. Since November 2016, EPC rules no longer require FRST: the first collection on a mandate can be sent as RCUR. GenerateSEPA marks every debit in the file as RCUR.

Can the signature date be earlier than the first collection?

Yes. It is the actual date when the debtor signed, not the date of the collection.