Is SEPA a file format?

No. SEPA is a set of payment schemes, and the files are ISO 20022 messages: pain.001 for a credit transfer, pain.008 for a direct debit collection. The scheme decides which elements are mandatory and what may go in them — service level SEPA, accounts identified by IBAN, amounts in euro, each side paying its own bank. A system can parse a pain.001 perfectly and still produce a file no bank in the area will execute.

What is a SEPA direct debit mandate?

The debtor’s written authorization for one named creditor to collect from their account, and for their bank to pay it. It carries its own reference and the date it was signed, and both travel inside the collection file that uses it. A collection with no valid mandate behind it is not a scheme collection, whatever the file says, and the mandate is the first thing a debtor’s bank asks about when the money is disputed.

What is the difference between SEPA and SEPA Instant?

The deadline and the calendar. A standard credit transfer settles on a business day, on the timetable the two banks keep. An instant one has to reach the payee’s bank and be made available to them within ten seconds, at any hour, on any day of the year. Same rulebook family, same file, same IBANs — a different service level, and a different set of banks able to receive it.

Which countries are in SEPA?

The euro area, the rest of the European Union, and a group of neighboring countries and territories that joined the schemes. The list moves, so it is not something to write into code: what matters operationally is whether the beneficiary’s account is reachable for the scheme you are sending under, and that is a property of the account rather than of the country.

Does a SEPA payment carry a reference the beneficiary sees?

Two of them, and they are not the same. The remittance information is what you write to the beneficiary — an invoice number, a statement of what the payment settles — and it is what appears on their statement. The end-to-end reference is yours: the scheme carries it unchanged from your instruction to the entry that settles it, which is what lets a payment be matched back without anybody reading a sentence.

EPC · the scheme

SEPA is not a file format. It is the rulebook the file has to pass.

A euro transfer inside the area is a SEPA credit transfer when it obeys a short list of rules: the accounts are named by IBAN, the amount is in euro, each side pays its own bank, and the reference the payer sets travels the whole way. The file that carries it is a pain.001. The scheme is what makes that file executable.

The account every page here reads

EUR

Published by: EPC
What it carries: The rules a euro payment obeys before a bank in the area executes it.
Account: ES21 0049 0001 5323 4567 8901

Closing balance · Aug 14, 2026EUR 2,990,901.67

The definition

What SEPA actually is

A set of rulebooks published by the European Payments Council, and the reason a transfer between two euro accounts in different countries works like a domestic one.

SEPA is the Single Euro Payments Area: a set of payment schemes with a shared rulebook for euro payments across the countries that take part. Three schemes carry almost all of it. The credit transfer scheme moves money when the payer asks. The direct debit schemes let a creditor collect from a debtor who has signed a mandate for it, in a consumer version and a business version with different rights attached. The instant scheme is the credit transfer with a deadline on it: the payee’s bank makes the funds available to them within ten seconds, on any day of the year.

Who sends it: Everybody, in both directions. The scheme governs a payment rather than a party, so the same rules bind the file your treasury sends, the collection a creditor raises against you, and the statement entry that reports either one.
When it arrives: On every euro payment inside the area, unless something puts it outside: a currency that is not euro, a beneficiary account outside the participating countries, or a charge option the scheme does not allow. A payment that falls outside is simply not a scheme payment, and it takes a different route, a different price and a different timetable.
What it looks like: The scheme has no bytes of its own. What it does is constrain the ISO 20022 messages the banks already use — pain.001 for a credit transfer, pain.008 for a collection, camt for what comes back — by fixing which elements are mandatory, which are forbidden and what may go in them.

What its parts are called

SvcLvl SEPA
SEPA ChrgBr SLEV
SEPA direct debit mandate
SCT Inst
SEPA vs pain.001

The rules

What the scheme pins inside the file

The same instruction as the pain.001 page, cut down to the elements the credit transfer scheme decides. Everything here is a rule rather than a preference: a file that breaks one of them is not a scheme payment.

SEPAThe scheme-constrained elements, lifted out of the instruction

  <PmtInf>
    <PmtTpInf>
      <SvcLvl><Cd>SEPA</Cd></SvcLvl>
    </PmtTpInf>
    <ReqdExctnDt><Dt>2026-08-17</Dt></ReqdExctnDt>
    <DbtrAcct><Id><IBAN>ES2100490001532345678901</IBAN></Id></DbtrAcct>
    <ChrgBr>SLEV</ChrgBr>
    <CdtTrfTxInf>
      <PmtId><EndToEndId>PO-2026-8841</EndToEndId></PmtId>
      <Amt><InstdAmt Ccy="EUR">28450.00</InstdAmt></Amt>
      <CdtrAcct><Id><IBAN>ES6621000418401234567891</IBAN></Id></CdtrAcct>
    </CdtTrfTxInf>
  </PmtInf>

Where each fact lives in this file

What makes it a scheme payment at all: <PmtTpInf><SvcLvl><Cd>SEPA
The day execution is asked for: <PmtInf><ReqdExctnDt><Dt>
Accounts are named by IBAN, and by nothing else: <DbtrAcct><Id><IBAN> · <CdtrAcct><Id><IBAN>
The amount is in euro, whatever the parties hold: <Amt><InstdAmt Ccy="EUR">
Who pays the bank charges: <PmtInf><ChrgBr>SLEV
The reference that ties it to a payment: <PmtId><EndToEndId>

What it changes

Why “we support SEPA” and “we read pain.001” are two sentences

One is about a scheme and one is about a message. A system can have either without the other, and the difference shows up on the day a payment is refused.

Reading a pain.001 means parsing the elements. Satisfying the scheme means knowing which of them are mandatory here, which values are allowed, and what a bank does with the ones that are not. The end-to-end reference is the clearest case: the element exists in every ISO 20022 credit transfer, and the scheme is what guarantees it survives the trip unchanged, which is what makes it usable as the tie between an instruction and the entry that settles it.

The direct debit side is where the scheme carries the most weight, because that is where authority sits. A collection is only valid against a mandate the debtor signed, and the file carries that mandate’s own reference and the date it was signed. The consumer scheme lets an authorized collection be refunded for eight weeks after it is debited, and an unauthorized one for far longer; the business scheme trades that right for a shorter timetable and a mandate the debtor’s bank checks up front. Which one a collection ran under changes what can come back, and when.

So the honest sentence is the specific one. We read the message, we build it to the scheme’s rules, and we tell you which scheme a payment ran under — because that is the field that decides what happens next when somebody wants their money back.

The file, the standard and the channel

pain.001 is the message a SEPA credit transfer travels in. ISO 20022 is the standard that message belongs to. EBICS is one of the channels it leaves on, and the scheme has nothing to say about which one you use.

Formats to read beside it

What reads it here

The same day written in four formats, side by side, is on Format library

Asked about SEPA

The questions a payments team actually types

01Is SEPA a file format?: No. SEPA is a set of payment schemes, and the files are ISO 20022 messages: pain.001 for a credit transfer, pain.008 for a direct debit collection. The scheme decides which elements are mandatory and what may go in them — service level SEPA, accounts identified by IBAN, amounts in euro, each side paying its own bank. A system can parse a pain.001 perfectly and still produce a file no bank in the area will execute.
02What is a SEPA direct debit mandate?: The debtor’s written authorization for one named creditor to collect from their account, and for their bank to pay it. It carries its own reference and the date it was signed, and both travel inside the collection file that uses it. A collection with no valid mandate behind it is not a scheme collection, whatever the file says, and the mandate is the first thing a debtor’s bank asks about when the money is disputed.
03What is the difference between SEPA and SEPA Instant?: The deadline and the calendar. A standard credit transfer settles on a business day, on the timetable the two banks keep. An instant one has to reach the payee’s bank and be made available to them within ten seconds, at any hour, on any day of the year. Same rulebook family, same file, same IBANs — a different service level, and a different set of banks able to receive it.
04Which countries are in SEPA?: The euro area, the rest of the European Union, and a group of neighboring countries and territories that joined the schemes. The list moves, so it is not something to write into code: what matters operationally is whether the beneficiary’s account is reachable for the scheme you are sending under, and that is a property of the account rather than of the country.
05Does a SEPA payment carry a reference the beneficiary sees?: Two of them, and they are not the same. The remittance information is what you write to the beneficiary — an invoice number, a statement of what the payment settles — and it is what appears on their statement. The end-to-end reference is yours: the scheme carries it unchanged from your instruction to the entry that settles it, which is what lets a payment be matched back without anybody reading a sentence.

Send us a run and see it built to the scheme.

One account, one batch of payments. You get back the file your bank takes, with the scheme’s own rules satisfied on every payment in it and the references your systems already use.

Request a demo Back to the format library

Approvals stay where your policy puts them: nothing reaches a bank without them.