SEPA File Checker
Menu

SL01 reason code: direct debit not paid because of a block or limit

Last updated: 28 October 2026

SL01 stands for a specific service of the payer's bank: the bank did not pay the SEPA direct debit because the payer has set up a block or a limit, for example for your creditor identifier or for amounts above a certain level.

Code
SL01
Meaning in the rulebook
Due to specific service offered by the Debtor PSP
ISO name
Specific Service Offered By Debtor Agent
Type of R-transaction
Reject before or return after the debit
Schemes
SEPA Core and SEPA B2B
Collect again?
Only once the payer has lifted the block

What SL01 means

Payers can instruct their bank to limit direct debits: to a maximum amount or frequency, to allow only certain creditors, or to block certain creditors. Banks must offer these options; the basis is Article 5 of the SEPA Regulation.

If such a setting applies, the bank returns the direct debit with SL01. The European Payments Council lists creditor blocking and limits on amount and frequency as use cases; the code can also cover other services of the bank.

What the payer and the creditor see

As the payer

The direct debit does not appear on your statement, or only with a reversal. Your bank can tell you which blocks and limits apply to your account.

As the creditor

Your bank debits the amount back and shows SL01. Which setting applied, you do not learn.

Creditor's bank statementAssociation current account
DateTransactionAmount EUR
3 NovSEPA direct debit collection, 214 itemsMembership fees 11/2026+8,560.00
5 NovSEPA direct debit returnMandate M-0412, membership fee 11/2026Return reason SL01 Specific service of payer's bank−40.00
5 NovReturn fee−3.00
Example: how a return with SL01 can appear on the creditor's bank statement. Layout and fees differ from bank to bank.

Typical causes

  • The payer has blocked your creditor identifier at their bank.
  • The amount is above the maximum the payer set for direct debits.
  • The payer limited the frequency, and the limit has been reached.
  • The payer only allows direct debits from certain creditors, and you are not one of them.

What you can do as the payer

  1. Ask your bank which block or limit applied.
  2. If you want to keep paying by direct debit, lift the block for this creditor or adjust the limit. You recognise the creditor by their creditor identifier.
  3. Let the creditor know and pay the open amount or agree on a new direct debit.

What you can do as the creditor

  1. Contact the payer; only they can change the setting at their bank.
  2. Resubmit only once they have confirmed that the block was lifted or the limit adjusted, or the direct debit will come back again.
  3. Announce the new collection with amount and due date (pre-notification), at least 14 calendar days in advance unless agreed otherwise.

Deadlines

SL01 arrives before the debit or shortly afterwards: under SEPA Core no later than five, under SEPA B2B no later than three bank business days after the due date. Under SEPA B2B, too, the payer can instruct their bank not to allow any direct debits on the account.

Related reason codes

Frequently asked questions

What is a direct debit block?

An instruction from the account holder to their bank not to pay direct debits at all or from certain creditors. There are also maximum amounts and limits on frequency. Banks must offer these options.

Can I as the creditor see which block applies?

No. You only see the code SL01. Ask the payer.

What is the difference between SL01 and MS02?

With MS02 the payer refused one direct debit. With SL01 a setting applies that the payer has stored with their bank, such as a block or a limit.

Sources