SEPA / Learning brief
SEPA Direct Debit: B2B versus Core
Your notes
In simple terms / 01
What this means in plain language
The SEPA (Single Euro Payments Area) Direct Debit Business-to-Business scheme differs from the Core scheme: no no-questions refund right for authorised collections, a mandatory mandate check by the debtor's bank, and eligibility limited to non-consumer payers.
SEPA Direct Debit (SDD) lets a creditor pull money from a debtor's account under a signed mandate, and it comes in two schemes that share the same machinery but protect the debtor very differently. SDD Core is the everyday scheme, open to consumers: its safety valve is a generous refund right, so a debtor can ask for an authorised collection back within eight weeks with no reason required, and can challenge an unauthorised one for thirteen months. SDD Business-to-Business (B2B) is for payers that are not consumers. It makes the opposite trade. There is no no-questions refund right for a collection the debtor authorised — once taken, the money is final — which gives the creditor certainty it does not have under Core. In exchange, protection moves earlier: the debtor's own bank must hold and check a confirmation of the mandate before it will debit the account. Fewer payers qualify, and both the debtor's and creditor's banks must offer the scheme for it to work.
Complete lesson / 02
Understand the full idea, step by step
Two doors can lead into the same building. SEPA Direct Debit has two — Core and B2B — and they run on almost the same machinery. Yet a payment that is perfectly ordinary through one door would be wrong through the other. The difference is not how the money moves. It is where the safety net is hung.
SDD B2B — SEPA Direct Debit Business-to-Business — the non-consumer direct-debit scheme
SDD B2B is a separate SEPA scheme that shares Core's mechanics — a signed mandate, a creditor collection, a due-date debit — but is open only where the debtor is not a consumer. An individual paying a household bill cannot use it. It exists because businesses value settlement certainty differently from consumers, and the scheme is built around that preference.
Same mechanism, relocated protection
Both schemes look alike at collection time: a mandate carrying a unique reference and the creditor identifier, a collection sent to the creditor's bank, an interbank exchange aiming at a due date. What differs is the balance of protection and certainty. Core protects the debtor after the fact and asks nothing of the debtor's bank at collection time. B2B protects the debtor before the fact and gives the creditor finality afterwards. Choosing a scheme is really choosing where the protection sits.
| SDD Core | SDD B2B | |
|---|---|---|
| Who may be the debtor | Consumers and businesses | Non-consumers only |
| Debtor-bank mandate check | None — debits on presented data | Mandatory — must hold and check the mandate before debiting |
| Refund right for an authorised collection | Yes — a no-questions right within the scheme window | None — authorised collections are final |
| Where protection sits | After the fact, via the refund right | Before the fact, via the mandate check |
| Reachability across banks | Effectively universal in SEPA | Narrower — both banks must support B2B |
The refund right, present and absent
The defining difference is the refund right. Under Core, a debtor may ask its bank to reverse an authorised collection within the scheme's no-questions window, needing no reason and no argument with the creditor first — so a Core creditor must treat collected money as provisional through that window. B2B removes that no-questions refund for authorised collections entirely: once a business debtor's authorised collection is taken, it is final, and the creditor can recognise the funds with confidence rather than waiting out a reversal window. This is not a gap in protection — it is a deliberate relocation of it.
The mandate check, and who does the work
B2B's certainty for the creditor is paid for by an obligation Core never imposes. Under Core the debtor's bank debits on the strength of presented data. Under B2B the burden flips: the debtor's bank must obtain, store, and check a confirmation of the mandate before it may debit a business account, matching each incoming collection against the mandate details it holds. So in Asha Traders' case, Bank Alfa will already hold the mandate for the logistics supplier and will refuse any collection that does not match it. The protection is performed up front, by the bank, instead of afterwards, by a refund.
COMMON CONFUSION
“B2B has no refund protection at all, so an unauthorised pull on a business account is simply final.”
The right that disappears in B2B is only the one attached to collections the debtor actually authorised. A collection with no valid mandate behind it is a different matter — an unauthorised pull is exactly what the scheme's controls exist to catch and unwind, and it remains challengeable. B2B trades away the convenience refund for authorised collections, not the defence against unauthorised ones.
STRICTLY SPEAKING
Strictly speaking, the exact refund windows, presentation timings, mandate-confirmation mechanics, and the list of banks reachable for B2B are defined in the European Payments Council's current SDD Core and SDD B2B rulebooks and change between versions. The summary here is the stable shape of the two schemes, not a substitute for the edition in force.
FOR NOW, REMEMBER
- Core and B2B share the direct-debit mechanism but relocate the protection: Core after the fact, B2B before it.
- Core gives the debtor a no-questions refund right for authorised collections; B2B makes authorised collections final.
- B2B requires the debtor's bank to hold and check the mandate before debiting; Core requires no such check.
- B2B is for non-consumer debtors only and needs both banks to support it; Core reachability is effectively universal.
- The defence against an unauthorised pull survives in both schemes — only the convenience refund for authorised collections is traded away in B2B.
TRY IT YOURSELF
Asha Traders' logistics supplier collects EUR 12,400.00 under a B2B mandate. Three weeks later Asha Traders decides the service was poor and asks Bank Alfa for a no-questions refund of that authorised collection. What is the right answer?
Refunds are one way a collection can unwind — but only one. Rejects, refusals, returns, and reversals each undo a collection at a different moment. The next lesson sorts the whole family.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SDD Core gives the debtor a no-questions refund right for eight weeks; SDD B2B removes that right for authorised collections, making them final.
- 02
Under B2B, the debtor's bank must hold and check a confirmation of the mandate before it may debit the account, shifting protection to before settlement.
- 03
B2B is available only where the payer is not a consumer, and only when both the debtor's and creditor's banks offer the scheme.
Practical use cases / 04
Where you would use this
A biller with business customers chooses B2B for the certainty that collected funds will not be reversed weeks later, and Core for consumer customers who need the refund right.
A debtor bank operations team validates and stores each B2B mandate confirmation so it can check an incoming collection against it before debiting a business account.
A collections team monitors R-transactions differently per scheme, since B2B residual risk sits in pre-settlement rejects and refusals rather than after-the-fact refunds.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional supplier, Castellan Components, collects EUR 42,750.00 a month from a fictional business customer, Nordvale Manufacturing, for parts. Under SDD Core, Nordvale could ask its bank to reverse an authorised collection within eight weeks with no reason given, so Castellan would have to treat each EUR 42,750.00 as provisional for 56 days. The two firms instead sign a SEPA Direct Debit Business-to-Business (B2B) mandate. Nordvale gives its own bank a confirmation of that mandate; the bank stores it and, when Castellan's EUR 42,750.00 collection arrives, checks it against the stored mandate before debiting the account. Because Nordvale is a business and the collection is authorised, there is no eight-week refund right — once the EUR 42,750.00 is taken, Castellan can treat it as final. Nordvale gained certainty over what its bank will honour; Castellan gained certainty that the money will not walk back. A genuinely unauthorised collection, one with no valid mandate, is still challengeable.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01ProcessingThe debtor signs a B2B mandateBusiness debtor → Asha Traders (creditor)
The business debtor signs a B2B direct debit mandate authorising Asha Traders to collect from its account. Unlike Core, this authorisation is business-only and carries no consumer refund right.
- 02ProcessingThe debtor registers the mandate with Bank AlfaBusiness debtor → Bank Alfa (debtor bank)
The B2B scheme requires the debtor to lodge the mandate details with its own bank. Bank Alfa stores this so it can later check every collection against a mandate it already knows about.
- 03MessageAsha Traders submits the collectionAsha Traders (creditor) → Nordbank (creditor bank) · pain.008
Asha Traders instructs Nordbank to collect the invoice. A corporate creditor sends a pain.008 collection request naming the debtor and referencing the signed mandate.
- 04MessageNordbank sends the interbank collectionNordbank (creditor bank) → Clearing & settlement mechanism · pacs.003
The creditor bank converts the instruction into an interbank pacs.003 collection and submits it to the clearing and settlement mechanism for routing to Bank Alfa.
- 05ProcessingBank Alfa verifies the mandateBank Alfa (debtor bank)
This is the defining B2B step: the debtor bank must check the incoming collection against the mandate it registered before it debits. Core has no such mandatory pre-debit mandate check.
- 06Clearing obligationThe CSM calculates positionsClearing & settlement mechanism
The CSM validates the collection and includes it in a clearing cycle. Each participant's obligations are calculated — this creates who-owes-whom, not yet a movement of money.
Clearing produces obligations. No money has moved yet — that only happens at settlement.
- 07SettlementPositions settle in central bank moneyBank Alfa (debtor bank) → Nordbank (creditor bank)
The calculated positions settle across the banks' settlement accounts at the central bank. Only now has money finally moved from Bank Alfa to Nordbank for the collection.
- DR Bank Alfa settlement account — EUR 9,600.00
- CR Nordbank settlement account — EUR 9,600.00
- 08PostingThe debtor's account is debitedBank Alfa (debtor bank)
Having verified the mandate, Bank Alfa books the debit on the business debtor's account. The pull has now taken money from the debtor to fund the settled collection.
- DR Business debtor's account at Bank Alfa — EUR 9,600.00
- 09PostingAsha Traders is creditedNordbank (creditor bank)
Nordbank credits Asha Traders for the collected invoice. The collection is complete end to end: mandate verified, banks settled, debtor debited, creditor credited.
- CR Asha Traders' account at Nordbank — EUR 9,600.00
Read the steps as text
- 01ProcessingAsha Traders confirms the mandateAsha Traders (creditor / biller)
Before pulling any money, the biller checks it holds a valid mandate that Riya signed authorising these collections. The mandate — not the invoice — is what permits the pull; no mandate means no right to debit.
- 02MessageAsha Traders pre-notifies Riya of the collectionAsha Traders (creditor / biller) → Riya (debtor / customer)
The creditor tells the debtor the amount and the due date in advance, so Riya can expect the debit and keep the account funded. This is a courtesy notice ahead of the pull, not the money movement itself.
- 03MessageAsha Traders submits the collection to NordbankAsha Traders (creditor / biller) → Nordbank (creditor bank) · pain.008
Here is the mirror image of a credit transfer: the instruction starts at the payee. Asha Traders sends a pain.008 collection request to its own bank, Nordbank, to go and pull the funds from Riya's account.
- 04MessageNordbank submits the interbank collectionNordbank (creditor bank) → STEP2-T (CSM) · pacs.003
Nordbank converts the customer collection into an interbank pacs.003 and submits it to the clearing and settlement mechanism, which will route it toward the debtor's bank to be collected on the due date.
- 05Clearing obligationThe CSM calculates obligationsSTEP2-T (CSM)
On the due date the CSM validates the collection and includes it in a clearing cycle, calculating who owes whom. In a pull this obligation runs from the debtor's bank to the creditor's bank — the reverse of a credit transfer.
Clearing produces obligations only. Nordbank does not have Asha Traders' money yet — that waits for settlement.
- 06SettlementPositions settle in central bank moneyBank Alfa (debtor bank) → Nordbank (creditor bank)
The calculated positions settle across the banks' accounts at the central bank. Money moves from Bank Alfa (debtor side) to Nordbank (creditor side) — funds flowing debtor to creditor even though the instruction came from the creditor.
- DR Bank Alfa settlement account — EUR 480.00
- CR Nordbank settlement account — EUR 480.00
- 07PostingBank Alfa debits RiyaBank Alfa (debtor bank)
Bank Alfa books the debit against Riya's account for the collected amount. This is the customer-facing side of the pull: money leaves the debtor's account because the mandate authorised it.
- DR Riya's current account at Bank Alfa — EUR 480.00
- 08PostingNordbank credits Asha TradersNordbank (creditor bank)
Nordbank credits the biller's account. The collection is complete end to end: debtor debited, banks settled, creditor credited — with the funds having travelled from Riya to Asha Traders.
- CR Asha Traders' account at Nordbank — EUR 480.00
Evidence & review / 07
Evidence & review
SEPA Direct Debit Core and B2B schemes, euro area.
What this brief simplifies: Refund windows and reachability are described rather than pinned to numbers; the comparison captures the stable shape of the two schemes, not version-specific parameters.
Sources for this brief3
- Scheme-specific rule2025 v1.1 (EPC222-07)
2025 SEPA Direct Debit Business-to-Business rulebook version 1.1 (EPC222-07) ↗ — European Payments Council · Eligibility; mandate confirmation; finality
- Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · Refund right; reachability
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.