SEPA Direct Debit for small businesses: mandates and batches

To collect by SEPA Direct Debit, a business needs a Creditor Identifier, a signed mandate from each payer, and a bank that accepts collection files. Each run is sent as a pain.008 batch, and under the Core scheme payers can ask for a refund for eight weeks.

Direct debit suits regular, predictable amounts: subscriptions, retainers, maintenance plans. Instead of waiting for each customer to pay, you collect on the agreed date. This guide covers the pieces you need in the SEPA area and how a collection run works from mandate to bank statement.

Core or B2B: two schemes

Scheme	Who pays	Refund right	Mandate check
Core	Consumers and businesses	Eight weeks after the debit, no questions asked	Kept by you, the creditor
B2B	Business payers	None for an authorized debit	The payer's bank checks the mandate before paying

Many small businesses start with Core: across the EU, a payer's bank that handles direct debits generally has to accept euro collections, while banks can choose whether to offer B2B. B2B gives more certainty but needs the payer to register the mandate with their own bank, so check that your customers are willing.

The Creditor Identifier

The Creditor Identifier (often shortened to CI) names you as the collecting business in every collection. It starts with your country code and two check digits, followed by a national part. In many countries you get it through your bank or a national body; your bank's direct debit pages explain the route. You usually also sign a direct debit agreement with your bank before it accepts collections from you.

The mandate

A mandate is the payer's signed permission to collect. Under the rulebooks it generally carries:

• A mandate reference (the UMR) of up to 35 characters, which you choose and never reuse for another mandate.
• Your name and Creditor Identifier.
• The payer's name and IBAN.
• Recurrent or one-off, the date and place of signing, and the payer's signature.

Keep every mandate on file for as long as you collect on it, and longer: if a payer disputes a debit, their bank can ask you for a copy of the mandate. A mandate with no collection for 36 months generally expires, so a customer who comes back after a long pause signs a new one. If details change, such as the payer's account, record the change as an amendment under the same reference.

Pre-notification

Before each collection, tell the payer the amount and the date. Under the Core rulebook the notice generally goes out at least 14 calendar days ahead unless you agree a shorter period, for example in your terms. An invoice that states "will be collected by direct debit on" a date, with your Creditor Identifier and the mandate reference, often serves as the notice. Clear notices are also one of the habits in the guide to getting paid faster.

The collection batch: pain.008

You don't send collections one by one. You send your bank a file, an ISO 20022 pain.008 message, that holds a batch of them:

1. Group the collections by scheme, sequence type and collection date. Each group becomes a block in the file.
2. Set the sequence type. FRST marks the opening collection on a mandate, RCUR the following ones, OOFF a one-off and FNAL the last. Since the 2016 rulebook FRST is optional, but some banks still ask for it.
3. Add each collection: the amount, the mandate reference and signing date, the payer's name and IBAN, an end-to-end reference such as the invoice number, and the remittance text.
4. Upload the file in time. Under the Core scheme a file can generally be sent up to 14 days before the due date and must reach the payer's bank by the day before. Your bank sets its own cut-off, so check it.
5. Read the status report. Many banks answer with a pain.002 message that accepts or rejects the file and its collections.

Supplier payments run the same way in reverse, with a pain.001 credit transfer file; the explainer on paying suppliers in one batch covers it.

After the collection: returns, refunds and matching

Not every collection succeeds. A rejected or returned collection, for example when the account is closed or has no funds, comes back with a reason code. A Core payer can also ask for a refund within eight weeks, and generally within 13 months when there was no valid mandate. These come back as R-transactions on your bank statement.

Your bank statement is where the collections land. Because each one carries your mandate reference and end-to-end reference, a statement file makes matching straightforward; what a camt.053 bank statement is explains how those references tie money to invoices. Then mark each invoice as paid, as in matching payments to invoices. For one-off payers, a payment QR code on the invoice is often the simpler choice.

Frequently asked questions

How do I get a SEPA Creditor Identifier?

In many countries you apply through your bank, which requests it from the national body; in some you apply to that body yourself. Your bank's direct debit pages say which applies to you.

Can a customer reverse a SEPA direct debit?

Under the Core scheme, yes: the payer can ask their bank for a refund within eight weeks of the debit, without giving a reason, and generally within 13 months if there was no valid mandate. Under B2B there is no refund for an authorized debit.

What is a pain.008 file?

It is the ISO 20022 XML message a business sends its bank to request a batch of direct debit collections. It holds the collection dates, amounts, mandate references and payer accounts.

Does a mandate need a handwritten signature?

Not always. The rulebooks allow paper mandates and electronic mandates, and many banks accept a mandate signed online. Check what your bank accepts before you switch.