Master SEPA direct debit for your SME

For any SME, managing collections can be a real headache. You’re constantly chasing invoices, sending reminders and crossing your fingers that payments arrive on time. This is where SEPA direct debit comes in—a tool that completely changes the game.

In essence, it’s the Europe-wide standard that lets you collect directly from your customers’ accounts, always with their prior consent. Think of it as the engine that automates the collection of fees, subscriptions and regular services. For a business, that means much more predictable cash flow and far less admin.

What is SEPA direct debit and how does it work?

Imagine that instead of issuing an invoice every month and waiting for your customer to remember to pay it, you could schedule the collection so the money lands in your account on the exact date you need. That’s exactly what a SEPA direct debit does (from the Single Euro Payments Area).

The whole system is built on an agreement between three key players: your company (the creditor), your customer (the debtor) and the banks that process the transaction.

The foundation of everything is the SEPA mandate. This document, which can be physical or digital, is the signed authorisation from your customer that gives you the green light to initiate collections on their account. Once you have it, you can generate and send collection orders to your bank in an automated way.

The concepts you need to master

For everything to run like clockwork, it’s important to be clear on the components of the system. It’s not just a case of “passing a charge”; it’s a regulated process with well-defined parts that keep things secure and efficient.

Here’s a summary table of the terms you’ll use day to day:

Key concepts in SEPA direct debit This table summarises the main elements of a SEPA direct debit for easy reference.

Element	Brief description
Creditor	The company or professional that issues the collection. In this case, you.
Debtor	The customer (individual or business) who authorises the payment from their account.
SEPA mandate	The contract or authorisation signed by the debtor to allow the charges.
SEPA remittance	The digital file (in XML format) you send to the bank with one or more collections.
IBAN	Your customer’s bank account number, essential for executing the charge.

As you can see, each part has its role so the whole mechanism works smoothly, from the initial authorisation to the execution of the collection.

Important: a direct debit is not the same as a transfer. When someone makes a transfer to you, that person (the debtor) initiates the payment. With direct debit, you (the creditor) initiate the collection, which gives you full control over the process.

The real impact on your collections

Implementing SEPA direct debit is a before-and-after moment for any SME’s cash flow. The key word is automation. You stop chasing unpaid invoices and processing payments one by one, because income starts arriving on time and predictably. To dig deeper into the benefits, you can read what is direct debit on our blog.

It’s no coincidence that this method has become the preferred option for any business with recurring payments. In fact, SEPA direct debit is the go-to for subscriptions and services in Spain, thanks to its reliability, low cost and predictability.

By automating collections, your admin team is freed from a repetitive, low-value task. That time is valuable, and they can now use it for financial analysis, customer support or any other activity that actually drives the business. For gyms, consultancies, SaaS companies or any subscription model, it’s simply an essential tool for growth.

The journey of a SEPA collection: from mandate to your account

To understand how SEPA direct debit works, it helps to follow the money step by step. Think of it as a clear process that starts with an agreement with your customer and ends with funds in your account.

It all starts with the SEPA mandate. It’s not just a piece of paper; it’s the legal authorisation your customer (the debtor) gives you to initiate collections on their account. Without a valid, properly stored mandate, any collection is at risk of being returned. To get to grips with this document, here’s our complete guide to the SEPA mandate.

With that authorisation in place, the next step is practical: group all the collections you want to make into a single file. This file, known as a remittance, has a very specific technical format (XML) and acts as a bulk instruction you send to your bank.

This diagram gives you a clear view of the full journey: from the customer’s signature and automated submission to the money arriving in your account.

As you can see, it’s a logical sequence where each part fits with the last. It’s a system designed so that collections are carried out securely and in line with the rules.

From submission to settlement: the deadlines you must respect

Once you upload the remittance file to your online banking, the interbank machinery kicks in. Your bank receives and validates the file, then sends the direct debit instructions to your customers’ banks.

This is where deadlines become your main ally—or enemy—for managing cash flow well. The key is to submit the remittance with enough lead time before the date you want the collection to be executed.

Minimum lead times depend on the type of collection: * First collection or one-off collection (FRST/OOFF): you need to send the remittance at least 5 banking business days before the charge date. * Recurring collections (RCUR): the window is more comfortable, at 2 banking business days before the charge date.

Pay close attention: we’re talking about interbank business days, which excludes weekends and public holidays. A slip in planning can delay your collections by a full week.

On the collection date you specified, the customer’s bank charges the amount and transfers the funds to yours. The money is settled and appears on your statement, closing the loop. Understanding this journey gives you control to anticipate cash flows and avoid nasty surprises.

SEPA CORE and B2B schemes: which one do you actually need?

When automating collections, the first question to ask is: who am I collecting from? And it’s not a minor one. The SEPA system clearly distinguishes between collecting from an individual and collecting from another business, and that choice determines everything else.

This is where the two main direct debit schemes come in: CORE and B2B. Mixing them up isn’t just an admin slip; it can mean returned collections, loss of trust and a hit to your cash flow. So let’s look at them clearly so you know which is yours.

The CORE scheme: the all-rounder for almost everyone

Think of the SEPA CORE scheme as the default option—the most common and flexible. It’s designed to work with any type of customer: individuals, the self-employed and businesses.

You’d use it for gym membership fees, monthly software subscriptions or service invoices to end customers. Its main advantage is that versatility.

That flexibility comes with a trade-off, though: protection for the debtor is maximum. Your customer has up to 8 weeks (56 days) to return a direct debit, with no need to give you any explanation. And note: if the collection was not authorised (for example, you don’t have a valid signed SEPA mandate), that window extends to 13 months.

The B2B scheme: for businesses only

As the name suggests, the SEPA B2B (Business-to-Business) scheme is only for business-to-business or self-employed transactions. Burn this into your mind: never, under any circumstances, use it to collect from an individual.

Its aim is to give maximum certainty and finality to professional collections.

So where’s the big difference? In the refund. With the B2B scheme, the business you’re collecting from expressly waives its right to refund the collection once it has been executed. The only option they have is to reject it before the charge date, and their bank must verify that the mandate exists and is correct before processing each collection.

That rigidity is a major guarantee for whoever issues the collection. You know that once collected, that money is safe in your account.

To see the differences at a glance, we’ve put together this table. It’s essential to have it clear before you prepare your first remittance.

SEPA CORE vs B2B direct debit scheme comparison

Feature	CORE scheme	B2B scheme (Business-to-Business)
Type of debtor	Individuals, self-employed and businesses. It’s universal.	Businesses and self-employed only.
Refund period (with mandate)	8 weeks (56 calendar days) with no justification.	Not possible once the charge has been made. The debtor must tell their bank to reject the payment before the charge date.
Mandate verification	The debtor’s bank is not required to verify it.	The debtor’s bank must verify the mandate before each charge.
Main use case	Fees, subscriptions, services to end consumers (gyms, software, rent).	Payments between suppliers, fees to business associations, B2B services.

In short, the choice is simple: if you have individual customers, the CORE scheme is your only option. If you only work with other businesses or the self-employed and want maximum certainty on collections, B2B will give you peace of mind that CORE can’t, but it requires stricter handling by everyone.

How to create SEPA XML remittances without errors

For many SMEs and accountancy firms, the moment of generating the file for the bank is where the problems with SEPA direct debit begin. This file, with a technical name like XML, is simply a document containing all the collection instructions. The catch is that the bank is very strict: one error and it rejects the whole file.

The frustration is understandable. An XML file is basically code. It has a rigid structure where every field must be in the right place and in the correct format. Doing this by hand is a sure source of headaches and calls to your bank’s support desk.

The critical fields your bank will scrutinise

Although building a remittance from scratch without help is a huge task, it’s still important to know which data causes most rejections. If you have this under control, you’re most of the way there.

Pay close attention to these fields, because this is where mistakes are often made:

• Valid IBAN and BIC: It sounds obvious, but one wrong digit in the IBAN is the most common error. Rejection is immediate.
• Mandate reference: It must be identical, character for character, to the one on the document your customer signed.
• Date format: Both the collection date and the mandate signature date must follow the format YYYY-MM-DD. No slashes or other formats.
• Correct amounts: The format must be numeric, with a dot as the decimal separator. For example, 123.45.
• Watch out for special characters: XML is very fussy. It doesn’t accept accents, the letter “ñ” or symbols like “&” or “€” in text fields such as name or collection description.

Think of the XML file like the assembly instructions for a precision piece of furniture. If you skip a step, use the wrong screw or tighten something in the wrong order, the whole thing falls apart. Same here—except the result is that your collections don’t get processed.

How to avoid the most common errors

The list of possible mistakes is almost endless. It could be a wrong country code in the IBAN, a flaw in the overall file structure… the smallest detail can invalidate the file. Imagine having to review a remittance of 50 collections because the bank rejected it for a single misspelt IBAN.

And that’s not all. SEPA regulation itself keeps evolving. For example, from November 2025, Regulation (EU) 2024/886 will bring important changes to strengthen security. This will require banks to verify that the IBAN and the account holder’s name match before processing the payment, making data accuracy even more critical.

Instead of wrestling with code and becoming an XML expert, the practical approach is to use tools that do the heavy lifting. Platforms like ConversorSEPA are built for exactly this. A good SEPA converter doesn’t just generate the file; it validates every field for you, ensuring your remittance is 100% compatible with what your bank expects. It saves hours of checking and gives you the confidence that collections will go through first time.

How to handle SEPA collection returns

Having a collection returned is a setback, for sure, but it’s just an incident along the way. When a SEPA direct debit is rejected, your bank will notify you with an “R code” that explains the reason. Understanding what that code means is the first step to fixing it.

Managing these returns in an organised way is essential. It’s not only about recovering the outstanding amount, but also about looking after the relationship with the customer and, above all, understanding why the collection failed. A good follow-up process will help you minimise the impact on your cash flow.

Decoding return codes: what is the bank telling you?

Each R code tells a different story. It’s not the same when a customer has insufficient funds as when the account is closed. Each reason needs a different response, and acting without knowing the cause often leads to more returns.

Here are some of the most common codes you’ll come across day to day:

• MS02 (Insufficient funds): The customer’s account doesn’t have enough balance. The simplest approach is to contact them, agree a new date for the charge and represent the collection later.
• AC04 (Account closed): Here the problem is more serious: the account no longer exists. You need to ask the customer for a new IBAN and, of course, update the SEPA mandate so it’s valid.
• MD01 (Incorrect or missing mandate): Be careful with this one. It means the mandate you have is not valid or doesn’t even exist in the bank’s records. It’s a serious error that you must fix before any new collection attempt.
• AG02 (Incorrect transaction code): This is usually a technical fault. The most likely cause is an error in the XML file you sent to the bank. You need to review how you’re generating those remittances.

A return is not a definitive non-payment. It’s an incident that in the vast majority of cases can be resolved. The key is to classify the reason and apply the right procedure, and avoid representing a collection without fixing the root cause first.

Your action plan when a return arrives

Once you know why the collection failed, it’s time to act. For that you need a simple procedure that tells you exactly what to do in each case.

For example, if the return is for insufficient funds (MS02), there’s no point representing the collection the next day. The smart move is to call the customer, confirm they can now cover the payment and agree a date. If the error is an invalid mandate (MD01), any new collection attempt is doomed to fail and will only create distrust. Here, the absolute priority is to obtain and record a new signed mandate.

The importance of efficient handling is clear when you look at the figures. In 2025, the Spanish national payment system (SNCE) processed a staggering 3.424 billion transactions, with an average of 13.8 million transactions per day. With that volume, making sure remittances are processed without errors from the start isn’t optional—it’s a must. Tools like ConversorSEPA are key to validating data before submission and minimising returns. For more, you can read the news on the Spanish payment system’s record operations.

Let’s get straight to the most common questions about SEPA direct debit. After all the theory, practical questions always come up in day-to-day work. Clearing them up is essential so you can manage your collections with full confidence and no surprises.

How long do I have to keep a SEPA mandate?

The rule here is clear: you must keep the SEPA mandate (the original document, physical or electronic) while the direct debit is active. But it doesn’t end there. Once you’ve made the last collection, you’re required to keep it for at least 14 more months.

Why so long? Think of it as your lifeline. If a customer claims a refund for a past charge, that mandate is the evidence you’ll present to the bank to show the transaction was legitimate. Don’t underestimate it.

Can I change the amount or date of a recurring collection?

Yes, of course. SEPA direct debit is quite flexible and lets you adjust both the amount and the date of collections in each remittance you send.

One golden rule: your customer’s trust is sacred. Always notify them of any change in advance. It’s good practice and is usually set out in the mandate terms. That way you avoid unexpected returns and misunderstandings.

What if an IBAN in my remittance is wrong?

This is one of the most common cases. If you use a wrong IBAN, the customer’s bank will simply reject that specific collection. The good news is that the rest of the remittance will continue and be processed without issue.

The problem is that most banks only validate the IBAN format when they receive the file; they don’t check whether the account actually exists until the charge date. So validating data before sending the file to the bank isn’t optional—it’s essential. It saves you time, the return fee and the hassle of dealing with the failed collection.

---

If you want to stop fighting with Excel files and avoid these errors costing you money, ConversorSEPA is your best ally. It converts your remittances to SEPA XML format in seconds and, just as importantly, validates the data so your collections and transfers are processed first time, without failures. Start your free trial at ConversorSEPA.

---

Related posts