Complete guide to SEPA direct debit order

In essence, a SEPA direct debit order is the document that lets you charge your customers directly to their bank account. It is the formal authorisation you need to initiate collections—whether one‑off or recurring—throughout the SEPA area.

What a SEPA direct debit mandate is and why it matters for your business

Think of the SEPA mandate as a formal handshake between your business and your customer. This agreement is not just a formality; it is the cornerstone that supports your entire direct debit system. Without a valid, properly signed mandate, any collection you issue can be returned by your customer’s bank—leading to unexpected costs and cash‑flow problems.

The creation of the Single Euro Payments Area (SEPA) was a major step in unifying collection rules across Europe, replacing the old, fragmented national systems. It brought far more security and efficiency for both businesses (creditors) and customers (debtors).

A valid SEPA mandate is your best defence. It is the irrefutable proof of your customer’s consent, protecting you against returns and giving you a far more stable, predictable cash flow.

The backbone of automated collections

The main advantage of a direct debit order is that it completely automates the collection process. Once your customer signs the document, your company has the green light to initiate charges on the agreed dates, without the customer having to do anything else for each payment.

This system is perfect for business models such as:

• Subscriptions and memberships: Gyms, SaaS products or any membership‑based service.
• Recurring payments: Rent, utilities (electricity, water, internet) or ongoing professional services.
• Regular invoicing: Any company that bills customers on a recurring basis.

Understanding in detail how SEPA direct debit works is the first step to getting your finances under control. While mandates are ideal for recurring payments, it is also useful to understand how to manage other one‑off collections through a payment request so you can fully control your income.

Poorly managed mandates are a risk you cannot afford. A document with incorrect data, incomplete fields or that is not stored securely can invalidate the whole process and trigger returns. Understanding this is the foundation for mastering the full collection cycle we will look at next.

The key players in the SEPA direct debit process

To really understand how a direct debit works, you first need to know its main players. Think of the SEPA direct debit order as the script of a play in which each participant has a very clear role.

The first actor on stage is the debtor, your customer. Their role is to trigger the whole process by signing the mandate, which is nothing more than the authorisation for you to charge their account. Without their signature, there is no show.

Next comes you: the creditor. Your role as a business is to initiate the collection. Once you have the debtor’s “yes”, it is your turn to prepare the move by generating a direct debit batch—the file that contains all the payment instructions.

Each actor has a defined role: the debtor authorises, the creditor charges and the banks execute. Understanding this dynamic is key to resolving any issues that may arise.

Finally, we have the banks, both your customer’s bank and your own. They act like the referees of the game, making sure money moves from one account to another according to SEPA rules. They check that everything is in order and process the transactions.

Roles and responsibilities in the process

If we break down each player’s responsibilities, the flow becomes much clearer and it is easier to see where problems might appear.

• The debtor (your customer)
  • Signs the direct debit order to give you permission.
  • Must check that their account details are correct.
  • Retains the right to return a charge, under conditions that vary between CORE and B2B mandates.
• The creditor (your business)
  • Is responsible for creating the mandate and storing it securely once it is signed.
  • Creates and sends the collection batch with accurate data and within the correct deadlines.
  • Needs a unique SEPA Creditor Identifier. If you do not yet have one, here is how to obtain your SEPA creditor identifier.
• The banks
  • The debtor’s bank ensures there are sufficient funds and that the mandate is valid (this last point is critical for B2B).
  • Your bank receives the funds and credits them to your business account.

Understanding this choreography gives you a huge advantage, as it allows you to anticipate issues and know exactly who to contact if a payment goes wrong.

How to choose between the SEPA CORE and B2B schemes

When you prepare a SEPA direct debit order, it is not just about filling in fields. One of the most critical decisions you will have to make is whether to use the SEPA CORE or SEPA B2B (Business‑to‑Business) scheme. Believe me, a poor choice here can directly impact the security of your collections and your cash flow.

Think of it this way: the CORE scheme is like a universal fishing net. It is incredibly versatile and lets you collect from any type of customer, whether consumers (B2C) or companies (B2B). In fact, it is the standard scheme that all banks in the SEPA area are required to offer.

But, as always, that flexibility has a downside. The CORE scheme gives the debtor a fairly generous right to return collections, which can create uncertainty.

• Refunds without questions: Your customer has 8 weeks from the collection date to return a direct debit. They do not need to justify it.
• Unauthorised collections: If the debtor claims the charge was not authorised (for example, because the mandate is not valid or they never signed it), the refund period jumps to 13 months.

This level of protection is mainly designed for the end consumer. A typical example would be a monthly gym fee or a streaming subscription.

The B2B scheme: a shield for your cash flow

On the other hand, the SEPA B2B scheme is more like a safe. It is designed exclusively for operations between businesses and/or self‑employed professionals, and its main attraction is the firmness of the collection.

With a B2B mandate, uncertainty around business‑to‑business collections disappears. Once the debtor’s bank validates the order, the payment is final and irrevocable. This protects your cash flow far more robustly.

Before the first B2B collection is processed, your customer’s bank must verify with them that the mandate is correct. Once they give the green light, the right to a refund disappears. The collection becomes final and you can relax.

This model is perfect for high‑value or strategically important business‑to‑business payments, such as office rent, key supplier invoices or professional service retainers.

SEPA CORE vs B2B scheme comparison

To make things clearer, here is a summary table of the key differences between the two schemes. It will help you decide which best fits your business model and the level of security you need.

Feature	CORE scheme	B2B scheme (Business‑to‑Business)
Type of debtor	Consumers, companies and self‑employed.	Companies and self‑employed only.
Refund period	8 weeks without giving a reason.	No right to refund after validation.
Unauthorised operation period	13 months.	The debtor’s bank validates the mandate before the first collection.
Collection security	Lower. The debtor has broad refund rights.	Maximum. Once processed, the collection is effectively irrevocable.
Agility	Faster to implement, no prior bank validation required.	Requires explicit validation by the debtor’s bank.

As you can see, the choice is far from trivial. Each scheme has its purpose and its place.

A strategic decision

The move to SEPA has been a major step forward for SMEs, which already manage 60% of direct debit batches in Spain. The use of SEPA direct debits has reduced collection errors by around 40%. If you want to see how these rules affect the self‑employed, you can consult information on Social Security contributions.

In the end, the decision is purely strategic: if most of your customers are consumers, the CORE scheme is your path. But if your operations are business‑to‑business and you want the strongest possible guarantees for your collections, B2B is, without a doubt, your best ally.

What information a SEPA mandate must contain to be valid

A SEPA mandate is, in practice, the contract that lets you charge your customers. Think of it as the foundations of a building: if a single piece is missing or poorly placed, everything collapses. For the bank to accept a collection and not return it, the mandate has to be flawless.

And when we say flawless, we mean it must contain a list of mandatory data with no exceptions. Forgetting one field or mistyping another is the fastest way to a bank rejection—which means delays, more admin and, let us be honest, a serious headache.

It is like entering coordinates into a GPS. One wrong number and you end up anywhere but your destination. The same goes for SEPA direct debits: one digit out of place in the IBAN or a duplicated mandate reference and your collection gets lost along the way.

Identification data: who charges and who is charged

For the system to work, each mandate needs to clearly identify all the parties involved. These are the fields that must always be present:

• Unique Mandate Reference (UMR): This is the ID of each authorisation. It is a code of up to 35 characters that you create yourself and that must be unique for each customer and agreement. Using the same UMR for two different mandates is a serious error that will invalidate the collections.
• Creditor Identifier: Your identification code within the SEPA system. It is a unique code provided by your bank that accredits you as a business authorised to issue direct debits.
• Full debtor details: A first name is not enough. You need the customer’s full name (if an individual) or legal name (if a company), as well as their full postal address.
• Debtor’s bank account: The critical piece here is the IBAN. A single incorrect digit is enough for the bank to automatically reject the collection. Double‑checking it is essential.

Agreement details: what is paid and how

Beyond identifying who pays whom, the mandate must set out the terms of the agreement in writing. This gives security and transparency for both your company and your customer.

The key information here is:

• Payment type: You must specify whether the collection will be recurring (like a monthly subscription) or a one‑off payment. This tells the system how to handle future charges associated with that mandate.
• Place and date of signature: The document must record where and, above all, when it was signed. The date is a legal requirement that proves when consent was given.
• Debtor’s signature: This is the final, crucial step. Without the account holder’s signature—whether handwritten on paper or via a valid electronic signature—the mandate has no legal validity. It is the definitive proof that your customer has given you permission to charge them.

Filling in all these fields by hand, one by one, is an invitation to disaster. A tiny human error can undermine the whole process. That is why the smartest approach is to use standardised templates or, better still, tools that generate mandates automatically. This way, every SEPA direct debit order starts off complete and ready to be processed without surprises.

The journey of the collection: from signed mandate to XML file

Once your customer signs a SEPA direct debit order, it is not enough to file the document away. That piece of paper (or PDF) is the key that sets in motion the entire process that turns their authorisation into real money in your account.

First—and this is absolutely crucial—comes mandate storage. You must keep it in a secure place, whether physical or digital. This document is your legal lifeline: if any dispute arises or a customer returns a collection, the bank will ask you for it as proof of consent.

With the mandate safely stored, the next step is to group outstanding invoices for one or several customers into what we call a direct debit batch. Here is where the technical side starts: all that data needs to be translated into a language banks can understand.

From raw data to the bank’s language: the XML file

That universal language is SEPA XML. Imagine it as an extremely strict digital form where every piece of data (debtor’s IBAN, amount, collection date, mandate reference) has its specific box. If anything is out of place or in the wrong format, the bank’s system will reject it outright.

This diagram helps you visualise how mandate data becomes the backbone of each collection you include in the file.

As you can see, the mandate reference, debtor details and their IBAN are the pillars of every collection order within the XML file.

Trying to build this XML file by hand is a monumental task and almost guaranteed to produce errors. A single extra space or incorrect character can invalidate the entire batch and delay your collections. That is why tools such as SEPA Generator are so useful: they turn a simple Excel or CSV into a valid XML file ready to send to the bank, without you having to fight with code.

The SEPA XML file is not just any file. It is the digital messenger that carries your collection orders into the banking system. If the message is not written and structured correctly, it will never reach its destination.

For businesses still using old formats, this transition can be a real headache. Fortunately, there are ways to make it easier. If, for example, you still work with the old Spanish “Norma 34” format, you will find this example of converting a Norma 34 file to SEPA XML particularly useful.

The final step: sending the batch and meeting the deadlines

Once your XML file has been validated and is ready, there is only one stage left: uploading it to your online banking. But watch the deadlines: SEPA rules are strict here.

• CORE scheme (recurring or one‑off collections): You must submit the file at least 2 banking business days before the collection date.
• B2B scheme (business‑to‑business collections): The minimum lead time is 1 banking business day.

Missing these deadlines is not an option. If you do, the bank simply will not process the collection on the planned date, which can throw your cash‑flow forecast completely off track. Sticking to this calendar is just as important as having filled in the original mandate correctly.

How to fix the most common errors in SEPA direct debit management

Managing a SEPA direct debit order can be a bump‑strewn road if you are not careful. Bank rejections or returned collections are not just a line item in your accounts; they are leaks of time and money that directly affect your business’s cash flow.

Let us be honest: mistakes happen. A mistyped piece of data, a file in the wrong format or simply missing a submission deadline can easily turn a collection you took for granted into a problem. The good news is that most of these errors can be anticipated and, more importantly, fixed.

Errors in mandate data

The most common—and almost the most frustrating—errors originate right at the source: the mandate itself. An IBAN with a wandering digit, a misspelt name or an incomplete address are more than enough reason for a bank to automatically reject the collection.

The key is to get ahead of the problem, acting before the error reaches the bank. Tools like SEPA Generator act as an initial quality filter thanks to their IBAN validation engine. This system checks that the bank account has a valid structure before a batch is even created, avoiding up to 90% of rejections for this reason.

• The problem: Incorrect or incomplete mandate data (IBAN, name, address).
• The solution: Use a tool that validates data automatically. That way you only process correct information from minute one, saving time and avoiding return fees.

Defective XML files and duplicated references

Here is where things get a bit more technical. Another critical area is creating the SEPA XML file. This file is, essentially, the language banks speak, and its structure is extremely strict. A small mistake when converting your Excel to XML can invalidate the entire batch.

A malformed XML file is like sending a letter with a blurred address. The postman (the bank) will not know what to do with it and sends it back. Here, precision is not optional; it is mandatory.

Equally serious is using a Unique Mandate Reference (UMR) that you have already used before. This is an error that invalidates collections instantly. To avoid these failures, which are almost always human, the smartest solution is to automate the process.

SEPA Generator, for example, uses an intelligent mapping system. You simply tell it which column in your Excel corresponds to each SEPA field (amount, IBAN, reference, etc.). The platform places each data point in its exact position within the XML file, ensuring it complies with the standard. In other words, it turns a manual, error‑prone process into a reliable, frictionless collection flow.

Frequently asked questions about SEPA direct debit orders

Theory is all well and good, but it is in practice where real doubts arise. Let us answer some of the most common questions we hear day to day so you can manage your collections without surprises.

How long must I keep a signed SEPA mandate?

The golden rule is to keep the original mandate (paper or digital) for as long as it is in force. But once you make the final collection, the rules require you to keep it for at least 13 months.

Why so long? Because that is the window in which a customer can dispute a collection as “unauthorised”. Think of the mandate as your legal insurance policy; it is the irrefutable proof that you had their permission.

What if a customer changes their bank account?

This happens more often than you might think. If a customer tells you they have a new account, it is very important that you do not just edit the existing mandate. That is not valid.

The correct procedure is clear: the customer must give you their new IBAN so you can generate a new SEPA direct debit order. This new document needs their signature to authorise collections on the new account. The old mandate, for the previous account, becomes automatically invalid.

Can I use the same mandate for both one‑off and recurring collections?

Yes, a single mandate can cover both situations—but you must state this from the beginning. When you create it, you have to specify whether the payment type is “Recurring” (for instalments or subscriptions) or “One‑Off” (for a single charge).

If you marked a mandate as “Recurring”, you can use it for all periodic collections without worry. However, if you created it as “One‑Off”, the safest and most transparent option is to generate a new mandate before starting a series of recurring collections. This protects you legally and maintains your customer’s trust.

Paying attention to this detail is crucial to making sure each collection matches what was agreed and preventing misunderstandings.

---

Tired of wrestling with SEPA files and having your bank send them back? SEPA Generator converts your Excel or CSV files into valid XML SEPA batches in seconds. Forget manual errors and bank rejections. Simplify your batches and get paid first time with our online tool. Take a look at https://www.generatesepa.com.

---

Related posts