Every collection in a SEPA Direct Debit (SDD) file carries a sequence type. Get it wrong and some banks reject the whole pain.008 upload, or the payer's bank returns the debit. This page is only about that field — for the full file recipe see how to create a pain.008 from Excel.
The four values
| Code | Meaning | When to use it |
|---|---|---|
| OOFF | One-off | The mandate itself is for a single collection. After that debit, the mandate is finished. |
| FRST | First | Historically: the first collection under a recurring mandate. Some banks still want this on the first run. |
| RCUR | Recurring | A collection under a recurring mandate that is not (or no longer) flagged as first/final. Most creditors use RCUR for every recurring collection today. |
| FNAL | Final | Optional last collection under a recurring mandate you are closing. Not every bank requires it; check their guide. |
What changed in November 2016
Under the original SDD Core and B2B schemes, the first collection on a recurring mandate had to be marked FRST, and later ones RCUR. From 20 November 2016 the European Payments Council amended the schemes so that RCUR may also be used for the first collection of a recurring mandate. Creditors no longer need a separate "first" run in the scheme rules.
That is why modern tooling (including ours) defaults to RCUR. FRST remains a valid code for banks or processes that still ask for it.
Practical decision tree
- Is the mandate one-off? → use OOFF only.
- Is it a recurring mandate?
- Does your bank's file-upload guide still say "FRST for the first collection"? → send FRST once, then RCUR.
- Otherwise → send RCUR for every collection, including the first.
- Closing the mandate and the bank asks for a final indicator? → last run as FNAL.
When in doubt, follow the PDF your bank gave you when they issued the Creditor Identifier — not a generic blog post (including this one).
How sequence types appear in the XML
In pain.008 the sequence type sits in the payment information block (PmtInf / PmtTpInf / SeqTp), not on each individual debit. That means one block per combination of sequence type and collection date. If your spreadsheet mixes FRST and RCUR rows for the same day, a correct generator splits them into two PmtInf blocks, each with its own transaction count and control sum.
<PmtTpInf>
<SvcLvl><Cd>SEPA</Cd></SvcLvl>
<LclInstrm><Cd>CORE</Cd></LclInstrm>
<SeqTp>RCUR</SeqTp>
</PmtTpInf>Common mistakes
- Sending FRST every month. After the first successful collection (or when your bank does not require FRST at all), further FRST tags can cause returns.
- Using OOFF on a recurring mandate (or RCUR on a one-off mandate). The code must match the mandate type you hold.
- Mixing sequence types in one PmtInf. The schema allows one
SeqTpper block; mixed rows must be split. - Ignoring pre-notification timing. Sequence type does not replace the need to notify the payer before the collection date (commonly 14 days unless you agreed otherwise).
CORE vs B2B (not the same as FRST/RCUR)
CORE and B2B are local instrument / scheme choices. Sequence types apply inside both. B2B is only for business payers who have registered the mandate with their own bank; it has no eight-week "no-questions" refund right. Do not switch to B2B just to avoid FRST/RCUR questions.
In PayBatchKit
The free SEPA direct debit generator lets you set a default sequence type in the header and override it per row with a Sequence column. Rows are grouped into separate PmtInf blocks automatically. Download a ready-made sheet from our free templates page. Output is checked against the official ISO 20022 schemas in our tests; your data is not uploaded.
This is general information about publicly documented scheme rules, not advice for your specific bank contract. Scheme rulebooks are updated over time — verify against the current EPC documents and your bank.
Sources
- European Payments Council – SEPA Direct Debit Core rulebook
- EPC – SEPA Direct Debit scheme documents (sequence type rules)
- ISO 20022 pain.008 message definitions
Related guides
- How to create a SEPA direct debit file (pain.008) from Excel
- How to create a SEPA XML payment file from Excel
- How IBAN validation works
Published 2026-10-02 by Karuna Labs. Our tools check file structure and checksums; always review outputs (and payment files in your bank's preview) before relying on them. This is general information, not financial, tax or legal advice.