Summarise the article with your AI
Here you can read:
SEPA B2B Direct Debit is a euro-only payment scheme built for business-to-business transactions across the Single Euro Payments Area. Unlike SEPA Core (which most consumers use), the B2B version doesn't give payers an automatic refund right once they've authorised a payment. This single difference is significant, particularly when collecting recurring payments from other businesses across about 40 European countries.
If you're running B2B payments across Europe, you already know the headaches: cash flow forecasts that don’t materialise, lengthy settlement times, and disputes that appear weeks after you thought a payment was settled. SEPA B2B Direct Debit was designed because enough businesses got frustrated with these problems.
The Single Euro Payments Area (SEPA) covers about 40 countries and creates one system for euro payments. Within this framework, two main direct debit schemes exist: SEPA Core (works for consumers and businesses, comes with refund rights) and SEPA B2B (exclusively for business-to-business transactions).
Which one you choose actually affects how your treasury function manages working capital.
SEPA B2B vs SEPA Core
SEPA B2B Direct Debit is an optional scheme, and it's only available to businesses. The idea is straightforward: automate payment processing and let bills get paid when they're due, which should help both sides manage liquidity better.
Who can use it? Only registered businesses. Consumers can't participate, and in many jurisdictions, neither can sole traders.
Every transaction runs in euros (EUR), regardless of whether the source account is in London, Berlin, Stockholm, or Paris.
Where it works: The SEPA area includes about 40 countries: all 27 EU member states plus Iceland, Liechtenstein, Norway, Switzerland, Monaco, San Marino, Andorra, Vatican City, the United Kingdom, and several EU accession countries like Albania, Montenegro, Moldova, and North Macedonia.
The real difference: no refund rights
Under SEPA B2B scheme rules, once a payment has been authorised and collected, the payer can't request a refund. This is a fundamental difference from SEPA Core, where payers get 8 weeks to reverse any payment, no explanation required.
The only exception: unauthorised transactions (fraud)
Payers can claim refunds for truly unauthorised or fraudulent transactions within 13 months. But ‘unauthorised’ means exactly that: no valid mandate existed, or the debtor never gave permission. Buyer's remorse doesn't count. Neither do disputes about invoice quality or service delivery.
What this means in practice: If you're collecting authorised B2B direct debits, your cash flow forecasting gets more reliable.
Key features of the SEPA B2B scheme
Bank registration of mandates: This is the big operational difference from SEPA Core. With Core, you just keep the signed mandate on file. With B2B, the debtor has to register it with their bank before you can collect anything. More paperwork upfront, but it tends to mean fewer failed collections later.
Shorter submission windows: You can submit B2B collections just one interbank business day before payment's due. SEPA Core needs two to five days, depending on whether it's a first or recurring collection.
Lower chargeback risk: Combine no refund rights with mandatory bank validation and business-only participation, and you generally end up with fewer reversals than SEPA Core would give you.
Automation: The scheme uses ISO 20022 XML message formats, so if you're already running automated straight-through processing, it should slot in. Less manual intervention, fewer errors.
SEPA Core vs SEPA B2B: comparison table
What is SEPA B2B vs. SEPA core, in comparison:
| Feature | SEPA Core Direct Debit | SEPA B2B Direct Debit |
| Who pays | Consumers and businesses | Businesses only |
| Refund right | 8 weeks, no questions asked | None once authorised |
| Fraud window | 13 months | 13 months |
| Mandate handling | Creditor stores it | Debtor registers with their bank |
| Submission lead time | 2-5 interbank business days | 1 interbank business day |
| Chargeback risk | Higher | Lower |
| Currency | EUR only | EUR only |
| Coverage | Approximately 40 SEPA countries | Approximately 40 SEPA countries |
| Payment certainty | Variable | Generally high |
How to set up a SEPA B2B mandate (step-by-step)
Step 1: Verify business payer status
Confirm that your customer is a registered business entity. The scheme is not available for consumers.
Step 2: Create the SEPA B2B mandate
You'll need your unique creditor identifier, the debtor's IBAN and BIC, a unique mandate reference, clear authorisation language, and whether it's for recurring or one-off collections.
Step 3: Debtor registers the mandate with their bank
This is where B2B differs from Core, and where most delays happen. The debtor submits the signed mandate to their bank. Until that registration goes through, you can't collect.
Step 4: Wait for confirmation
The debtor's bank should validate the mandate information and confirm registration. Don't try to collect before this comes back as the transaction will bounce.
Step 5: Submit collection requests
Once the mandate is registered, submit collection requests per the rulebook. For SEPA B2B, collections can typically be submitted one business day before the due date.
Step 6: Monitor settlement and exceptions
Collections usually settle within one to two business days. Modern treasury management platforms can help automate this monitoring. They can flag exceptions and help with reconciliation of successful settlements.
Common pitfalls: why B2B payments fail (and how to avoid it)
Most SEPA B2B failures come down to a handful of preventable mistakes:
Unregistered mandates: the most common error
The most common problem, by far. You try to collect before the debtor's bank has the mandate on file. The bank has no record of authorisation. Rejected. Always confirm registration before your first collection attempt.
Wrong mandate reference or creditor ID
Every collection must reference the exact mandate reference and creditor identifier registered with the debtor's bank. Even minor discrepancies may trigger rejection.
Non-EUR collections
SEPA Direct Debit only does euros. Attempting to initiate a collection in GBP, USD, or any other currency will result in rejection.
Using the scheme with consumer accounts
Some businesses accidentally try B2B collections against sole traders or small businesses using consumer-type accounts. These fail. If you're not sure what kind of account your customer has, SEPA Core might be the safer choice since it handles both.
Is SEPA B2B right for your treasury?
It depends. The scheme offers real advantages for businesses with recurring B2B payments in euros. Payment certainty improves. Chargeback risk drops. Cash flow forecasts become more reliable. However you should:
Stick with Core if you:
- Serve consumers or mixed B2C/B2B customer bases
- Need simpler mandate setup processes without bank registration requirements
- Process primarily one-off or irregular payments
- Your customers prefer the safety net of refund rights
SEPA B2B may be more suitable if you:
- Process recurring euro payments to other businesses across Europe
- Want reduced chargeback exposure
- Have customers willing to register mandates with their banks
- Operate across multiple SEPA countries and want consistent processing
- Care about faster submission timelines
For treasury teams seeking efficiency and payment certainty in B2B relationships, SEPA B2B Direct Debit can serve as a useful tool in the modern payments landscape. Consider starting with a pilot programme, refine your operational procedures, and expand as you gain confidence.
