Corporate Cash Management

SEPA Direct
Debit Order
ISO 20022 STANDARD
pain.008.001.02

Guideline
to SEPA DIRECT DEBIT Instructions
transmitted to Societe Generale France and to Societe
Generales branches
(SEPA Core Direct Debit and SEPA B2B Direct Debit)
Version: February, 2013

CONTENTS

INTRODUCTION ....................................................................................................................................... 3

GENERAL PRESENTATION OF SDD ORDERS IN ISO 20022 FORMAT................................................ 3

2.1

SEPA DIRECT DEBIT ORDERS...........................................................................................................................3

2.2

CHARACTERISTICS.............................................................................................................................................3

2.2.1
2.2.2

General characteristics common to SEPA transactions .............................................................. 3

Data specific to SEPA Direct Debit orders.................................................................................. 3

2.3

FORMAT ISO 20022 "pain 008.001.02" ..............................................................................................................3

2.4

AMENDMENT OF MANDATE DATA....................................................................................................................3

DETAILED DESCRIPTION OF "SEPA DIRECT DEBIT ORDER" MESSAGE.......................................... 3

3.1

PRESENTATION OF DESCRIPTION ...................................................................................................................3

3.2

OPERATING RULES.............................................................................................................................................3

3.3

CONTROLS PERFORMED ON RECEIPT OF ORDER........................................................................................3

3.3.1
3.3.2
3.3.3

Controls of compliance with PAIN 008.001.02............................................................................ 3

Banking controls......................................................................................................................... 3
Characters used......................................................................................................................... 3

3.4

SEPA DIRECT DEBIT ORDERS UNDER ISO 20022 FORMAT ("pain.008.001.02") ........................................3

3.5

EXAMPLE..............................................................................................................................................................3

3.5.1

Example with matrix template ............................................................................................................................3

3.5.2

In XML format .......................................................................................................................................................3

APPENDIX 1 LIST OF SEPA COUNTRY CODES ............................................................................................ 3

APPENDIX 2 LIST OF BIC CODES FOR SG FRANCE, SG MONACO AND SOCIETE GENERALES
BRANCHES ...................................................................................................................................................... 3
APPENDIX 3 COUNTRIES SPECIFIC REQUIREMENTS................................................................................ 3

Additional information can be obtained from the following websites:

ISO 20 022: http://www.iso20022.org/
ISO (country codes): http://www.iso.org/iso/fr/french_country_names_and_code_elements

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 2/24

1 INTRODUCTION
This guide describes the rules of use governing SEPA Core Direct Debits (CORE SDD) and SEPA Business-to-Business
Direct Debits (B2B SDD) under the ISO 20022 standard. for direct debits initiated on accounts held:
- with Societe Generale France and Monaco included,
- with Societe Generales Branches within Europe; SG Amsterdam, SG Brussels, SG Frankfurt,
SG Madrid, SG Zurich
The message that must be used for these transactions is "CustomerDirectDebitInitiation", referenced as "pain.008.001.02"
based on version ISO 20022 of April 2009 and applicable as from 1 November 2010.

IMPORTANT
To prevent messages from being rejected due to failure to comply with ISO 20022, it is important to use standard,
proven applications that automatically generate strictly ISO 20022-compliant messages in XML format using an ISO
XSD processor.

Please note:
Specific agreements must be entered into prior to the initiation of SDD Core and SDD B2B direct debits.
This guide complies with:
the rules of use applicable to the ISO 20022 standards and their XML format,
version 6.1 of the European Payment Council's SDD Core Rulebook and and version 6.0 of the Implementation
Guidelines
version 4.1 of the European Payment Council's SDD B2B Rulebook and version 4.0 of the Implementation
Guidelines
For direct debits initiated from SG France or SG Monaco, this guideline also draws on the following CFONB brochures:
the "Remises informatises d'ordres de prlvement SEPA ISO 20022" (Guide to electronic initiation of SEPA ISO
20022 direct debit orders) published by the CFONB and the GUF (French SWIFT users group), available at
http://www.cfonb.org, pathway: documentations/publications/SEPA/Guide d'utilisation du standard ISO 20022.
- "Prlvement SEPA" (SEPA CORE Direct Debit),
- "Migration du prlvement national vers le prlvement SEPA" (Migration from the national direct debit scheme to
the SEPA CORE direct debit scheme) brochure.
These brochures are available at http://www.cfonb.org, pathway: documentations/publications/SEPA/
There are two parts to the document:
1. The general presentation of SEPA direct debit orders in ISO 20022 format, with a description and explanation of how
to complete the order.
2. The detailed description of the ISO 20022 format for SEPA direct debit orders transmitted to SOCIETE GENERALE,
with an example provided first in table form and then in XML format.
Socit Gnrale offers the following tools for issuing SEPA Direct Debits :
- International cash management tools, available in France and in other countries : SWIFTNet FileAct, FTP, SFTP,
Sogecash Web
- Cash Management solutions available in France : EBICS T, EBICS TS, Pe SIT
Files are processed identically regardless of the transmission protocol. Subscription to the SEPA Direct Debit service is
done on the basis of the corresponding teletransmission contract.

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 3/24

2 GENERAL PRESENTATION OF SDD ORDERS IN ISO 20022 FORMAT

2.1

SEPA DIRECT DEBIT ORDERS

The SEPA direct debit is an automated method of payment initiated by a creditor, which can be used to pay recurring or
one-off invoices. Before the initiation of the SEPA direct debit order by the creditor, the debtor must sign a mandate
beforehand, authorising the creditor to collect payments from the debtors account and also authorising the debtors bank
to debit the debtor's account to pay these collections.
The European authorities have defined two schemes of SEPA direct debits:
- the SEPA CORE Direct Debit: it can be used by any type of client and will eventually replace the national direct
debit schemes.
- the SEPA Business-to-Business Direct Debit allows companies, professionals and associations to pay some or all
of their transactions according to specific operating rules.
Both models can be used for recurring or one-off payments.

2.2

CHARACTERISTICS

2.2.1

General characteristics common to SEPA transactions

SEPA Direct Debits contain the following general characteristics:

- amount denominated in EUR
- amount ranging from EUR 0.01 to EUR 999 999 999.99
- creditor and debtor accounts located in the SEPA area* and identified by their BIC and IBAN
- end-to-end reference number assigned by the creditor and transmitted to the debtor
- reason for payment (maximum 140 characters) assigned by the creditor and transmitted to the debtor
The SEPA area currently consists of 32 countries (see Appendix for a list of SEPA countries and related codes).

2.2.2

Data specific to SEPA Direct Debit orders

Identification of SDD models (index 2.12)

"CORE" for SEPA Core Direct Debits
"B2B" for SEPA Business-to-Business Direct Debits

Sequence Type (index 2.14)

The transaction sequence codes are applied to SEPA Core Direct Debits and SEPA B2B Direct Debits.
Type of
payment
Recurring
One-off

Sequence Type
"FRST"
"RCUR"
"FNAL"
"OOFF"

Definition
First transaction of a recurrent collection
Subsequent transactions
Last transaction of a recurrent collection
One-off direct debit

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 4/24

SEPA Creditor Identifier (index 2.27)

The creditor must have a SEPA Creditor Identifier (SCI) to issue SEPA Core Direct Debits and SEPA B2B Direct Debits.
The general structure of the SCI was defined by the EPC.

Data

Content

Maximum number
of characters

Country
code

ISO code of the country which assigned the identifier.

2 characters
See ISO Code Countries in appendix 1
Control key This key is determined using the country code and national
2 characters
identifier
This code, managed by the creditor at its discretion, is used by
the creditor to identify different business activities.
Creditor
3 characters.
business If the creditor does not wish to use the business code, the
code
characters "ZZZ" are assigned.
The business code is not used to determine the control key.
National
identifier

This national identifier is defined by each community.

An overview of National Identifiers taken of each SEPA
country is published on EPC web site:
http://www.europeanpaymentscouncil.eu/

.
28 characters
maximum

Unique Mandate Reference

For a given creditor, this reference identifies each mandate signed with the debtor. The Unique Mandate Reference
embodies the commercial agreement signed with the debtor.

2.3

FORMAT ISO 20022 "pain 008.001.02"

There are three levels in the ISO 2022 "pain.008.001.02" message:

1. GroupHeader
This building block is mandatory and present once. It contains one or several PaymentInformation blocks.
2. PaymentInformation
This building block is mandatory and repetitive:a set of transactions (or direct debit orders) concerning a single account to
be credited, a single sequence type (index 2.14), a single execution date (index 2.18) and a single creditor identifier, a
single scheme (index 2.12).
3. CreditTransferTransactionInformation
This building block is mandatory and repetitive. This block is a set of elements providing specific information to each
individual transaction(s) included in the Payment Information block

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 5/24

The message is structured as follows:

The + sign
appearing in
the first column
indicates a
composite
element
consisting of a
set of
sub-elements.

CustomerDirectDebitInitiation ISO 20022 Standard

Message item

A.

+
+
B.

Elements
shaded in grey
are not used for
SEPA direct
debit orders
(status "N").

M = Mandatory
O = Optional
D = Dependent
R = Required
A = Advised
N = Not Used

GROUPHEADER
MessageIdentification
CreationDateTime
Authorisation
NumberOfTransactions
ControlSum
InitiatingParty
ForwardingAgent
PAYMENTINFORMATION

Occur.

M
M
M
N
M
R
M
N
[1..n]

+
+
+

PaymentInformationIdentification
PaymentMethod
BatchBooking
NumberOfTransactions
ControlSum
PaymentTypeInformation
RequestedCollectionDate
Creditor
CreditorAccount
CreditorAgent
CreditorAgentAccount
UltimateCreditor
ChargeBearer
ChargesAccount
ChargesAccountAgent
CreditorSchemeIdentification

M
M
N
R
R
R
M
M
M
M
N
O
O
N
N
R

C.

DIRECTDEBITTRANSACTIONINFORMATION

[1..n]

+
+
+
+
+
+

+
+

+
+
+
+
+
+
+
+
+
+
+
+

PaymentIdentification
PaymentTypeInformation
InstructedAmount
ChargeBearer
DirectDebitTransaction
UltimateCreditor
DebtorAgent
DebtorAgentAccount
Debtor
DebtorAccount
UltimateDebtor
InstructionforCreditorAgent
Purpose
RegulatoryReporting
Tax
RelatedRemittanceInformation
Remittanceinformation

GROUP HEADER

M
N
M
N
R
O
M
N
M
M
O
N
O
N
N
N
R

Guide to SEPA Direct Debit Orders in ISO 20022 format

PAYMENT INFORM

"TRANSACTION"
INFORMATION

V05 2011

P 6/24

2.4

AMENDMENT OF MANDATE DATA

For amendments of one or more elements in the mandate, the data entry rules are as follows for the ISO 20022 format:
- the amendment indicator positioned in index 2.50 "AmendmentIndicator" must be set to "true".
- the original mandate data must be entered in specific indexes. The list and indexes which must be completed are
indicated below.
- The new mandate data are entered in the corresponding indexes.

Original data

New data

Mandate data
Index

2.52

Element

Definition

OriginalMandateIdentification

Original
mandate
identification
number

Unique Mandate Reference

Name of creditor

SEPA Creditor Identifier

2.53

Name

2.53

Identification

2.53

SchemeName

Original name
of creditor
Original SEPA
creditor
identifier

Index

2.48

2.23

2.27

Proprietary Value =

"SEPA
Case 1
change of
account within
the same bank

Debtor
Account
Case 2 change
of bank

2.57

OriginalDebtorAccount

2.58

OriginalDebtorAgent

IBAN

2.73 (IBAN)

Value =
"SMNDA"
(Same
Mandate with
New Debtor
Agent)
In this case, the
SEPA direct
debit must be
associated with
a sequence
type set to
"FRST"

2.70 (BIC)
2.73 (IBAN)

In the event the amendment indicator "false" is entered and amended data are present, the amended data will be ignored.
In the event the amendment indicator "true" is entered and no amended data are present, the value of the amendment
indicator will be changed to "false".

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 7/24

3 DETAILED DESCRIPTION OF "SEPA DIRECT DEBIT ORDER" MESSAGE

3.1

PRESENTATION OF DESCRIPTION

The detailed description is provided in paragraph 3.4 in the form of a table with nine columns and as many lines as
elements of information.
The table shows the presentation adopted by the ISO 20022 (except for the selection indicator "Or", which is not shown
because it does not pertain to any of the items used in this guide).
Index: ISO 20022 index of the element (element = information)
Level: hierarchical level of the item "+": Level 1 element, "++": Level 2 element, etc.
Message Item name of the item as indicated in ISO 20022 standard
<XML tag>: name of the XML tag of the element
Mult.: minimum and maximum number of occurrences of the ISO 20022 standard, presented as follows [x..y]. If x = 0,
then the element is optional. If x = 1, it is mandatory.
Format: type and length of the element (Text = alphanumeric)
Amount format: the maximum length contains fraction digits and the decimal separator. Decimals are separated by a
decimal point.
External code tables: the tables and values that can be used are available on the ISO's website at the following address:
http://www.iso20022.org/External_Code_Lists_and_DSS.page
Code format: always uppercase
Indicator format: always lowercase
Status: indicates whether or not an element is mandatory or optional for a SEPA direct debit order sent to Societe
Generale
Code
M
R
D
A
O
N

Meaning
Mandatory
Required
Dependent
Advised
Optional
Not Used

Comments
Mandatory in the standard ISO 20022 message.
Item required by this guide but optional under the ISO 20022 standard.
Mandatory under certain conditions, depending on other data in the
message.
Usage strongly advised (the information is useful for one of the
intermediaries or for the beneficiary of the transaction).
May be useful for the beneficiary but is not required to process the
transaction.
Not used by Societe Generale to process the transaction.

Name and definition: description of the item

Comments: additional information on using the element. Information provided in quotation marks indicates the value to be
indicated for this item.

3.2

OPERATING RULES

The matrix only shows the elements recommended by Societe Generale for issuing SEPA direct debit orders. For any
specific questions not covered by this document, please contact your regular Societe Generale contact person.
The inclusion of items not indicated in this guideline, but which are compliant with "pain.008.001.02", will not prevent the
transaction from being processed. In such case, these elements are ignored. The same is true for elements with
"IGNORED" indicated in the Comments column.
If an item used is a Composed element (group of items), it is mandatory to fill in at least one of the elementary item that
is part of the composed element..

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 8/24

An individual element in a composite element marked M for mandatory must be provided if the composite element to
which it is attached is present.
Example: element 2.65 "Code" (M) is part of the composite element "Purpose" (O). Users who do not wish to complete
element 2.65 must not complete element 2.64.
If an element can be indicated at the "PaymentInformation and at the "Transaction" levels, it is advised to choose the
PaymentInformation level if possible. Example: index 2.23 and 2.69 "ultimate creditor".
3.3

CONTROLS PERFORMED ON RECEIPT OF ORDER

Three levels of controls are carried out:

- Syntax: compliance with pain.008.001.02 and with XML syntax
- Banking: compliance with Societe Generale recommendations (see Comments column of table 3.4)
- Characters: use of authorised characters (see 3.3.3).

3.3.1

Controls of compliance with PAIN 008.001.02

For the purposes of automated order processing, the message must observe the rules of the "pain.008.001.02" message
under the ISO 20022 standard, independently of the presence and relevance of the banking data provided.
Otherwise, the GroupHeader, the PaymentInformation and/or Transaction will be rejected, even if the error is not related
to data that is required to issue the requested SEPA direct debit order.
The controls examine the following:
- accuracy of tag names
- the hierarchy of the XML marker
- consistency of tag arrangement
- appropriate use of a closing tag for every opening tag
- validity of codes used
- use of mandatory characters (or dependent characters where necessary)
- etc.
The level of rejection depends on the positioning of the anomaly.
Positioning of anomaly
GroupHeader

Entire message

PaymentInformation
CreditTransferTransactionInformation

3.3.2

Rejection level

The related PaymentInformation is rejected. The remaining

correct PaymentInformations are processed
The related transaction is rejected. The remaining correct
transactions are processed)

Banking controls (*)

These controls examine the banking data that must be provided when the "S" (Status) column of the table indicates:
- "M" (Mandatory)
- "R" (Required)
- "D" (Dependent), i.e. the information is mandatory if the given condition is met.
The data must be present and accurate.
As for the syntax control, depending on whether the anomaly is found in the GroupHeader, at the PaymentInformation
level or at the transaction level, the rejection will be related to the GroupHeader,,the PaymentInformation or the
transaction.
(*) Regarding uploaded files through Sogecash Web, wherever is the anomaly positioning (GroupHeader level,
PaymentInformation level, Credit Transfer TransactionInformation), the whole file is rejected.

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 9/24

3.3.3

Characters used

The characters accepted by the European clearing systems are those listed below (see list of authorized characters).
However, Socit Gnrale does not always reject the messages containing characters that are not listed.
If specific XML characters are used (see list of forbidden characters below) the message will be rejected.
Other non listed characters will be accepted by Socit Gnrale but they may be changed through the processing.

LIST OF THE AUTHORISED CHARACTERS

abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
/-?:().,+
Espace

LIST OF FORBIDDEN CHARACTERS

<>"&

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 10/24

3.4

SEPA DIRECT DEBIT ORDERS UNDER ISO 20022 FORMAT ("pain.008.001.02")

Index Level

Message Item

<XMLtag>

Mult Format

S Name and definition

1.0

GroupHeader

<GrpHdr>

[1..1] Composite

M Message Header

Message
Identification

<MsgId>

[1..1] Max35Text

M Message reference no.

<CreDtTm>

Date and time the message

was created in
[1..1] ISODateTime M YYYY-MM-DDThh:mm:ss
format
(T is used as a separator)

1.1

1.2

CreationDateTime

Comments

IGNORED

IGNORED

Rejected if
inconsistent with the
Total number of transactions
M
number of
in message
transactions in the
message
Rejected if
inconsistent with the
total amount for the
This total is an arithmetic sum
Decimal
transactions in the
of the amounts given for each
[0..1] Number
R
message
transaction (instructed
fractionDigits 17
totalDigits :18
amount) in the message
Decimals are
separated by a
decimal point.
15 numbers
[1..1] max., no
decimal

1.6

NumberOf
Transactions

<NbOfTxs>

1.7

ControlSum

<CtrlSum>

1.8

InitiatingParty

<InitgPty>

[1..1] Composed

M Issuer of message

1.8

++

Name

<Nm>

[0..1] Max140text

Name of party issuing the

message

Guide to SEPA Direct Debit Orders in ISO 20022 format

IGNORED

IGNORED

V05 2011

P 11/24

Index Level

2.0

Message Item

<XML tag>

Mult Format

S Name and definition

Comments

Payment
Information

<PmtInf>

[1..n] Composed

M PaymentInformation level

To be repeated as
many times as there
is Payment
Information
(a)

2.1

Payment
Information
Identification

<PmtInfId>

[1..1] Max35Text

Reference assigned to
M idenftify the
PaymentInformation block

Provided on the
creditor's account
statement

2.2

PaymentMethod

<PmtMtd>

[1..1] Code

M Payment method

"DD" for Direct Debit

2.4

NumberOfTransactions <NbOfTxs>

Rejected if
Total number of transactions inconsistent with the
Max15Numeric
[0..1]
R
number of
Text
of the PaymentInformation
transactions in the
paymentinformation
Rejected if
inconsistent with the
Total amount for transactions sum of the amounts
[0..1]
R
fractionDigits 17
of the PaymentInformation
for the transactions in
totalDigits :18,
the
PaymentInformation
Group of information
identifying the level of
[0..1] Composed
R
Type of direct debit
service associated with the
direct debit
Decimal
Number

2.5

ControlSum

<CtrlSum>

2.6

PaymentType
Information

<PmtTpInf>

2.8

++

ServiceLevel

<SvcLvl>

[0..1] Composed

2.9

+++

Code

<Cd>

[1..1]

2.11

++

LocalInstrument

<LclInstrm>

[0..1]] Composite

2.12

+++

Code

<Cd>

R Processing method

ExternalService
M Code of processing method
Level1Code
R

ExternalLocal
[1..1] Instrument1Co M
de

"SEPA"
Indicates the SEPA
direct debit model
The possible values
are:
"CORE": SEPA Core
Direct Debit
"B2B": SEPA
Business-to-Business
Direct Debit
Indicates the
sequence.type
The possible values
are
- for a recurrent
collection:
"FRST"
"RCUR"
"FNAL"

2.14

++

SequenceType

<SeqTp>

[0..1] Code

- for a one-off SEPA

direct debit
"OOFF"
Note: if the value of
the
OriginalDebtorAgent
element is "SMNDA",
the value "FRST"
must be used.
(see explanation in
section 2.4)

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 12/24

Index Level

Message Item

<XML tag>

Mult Format

S Name and definition

Comments
Any past date is
replaced with the best
possible collection
date.
Maximum period
accepted: 60
business days

2.18

RequestedCollection
<ReqdColltnDt>
Date

[1..1]

2.19

Creditor

<Cdtr>

[1..1] Composed

2.19

++

Name

<Nm>

[0..1] Max140text

R Name of creditor

2.20

CreditorAccount

<CdtrAcct>

[1..1] Composed

M Creditor account

2.20

++

Identification

<Id>

[1..1] Composed

M Account ID

2.20

+++

IBAN

<IBAN>

[1..1] IBANIdentifier M IBAN of creditor account

2.21

CreditorAgent

<CdtrAgt>

[1..1] Composed

M Creditor bank

2.21

++

FinancialInstitution
Identification

<FinInstnId>

[1..1] Composed

M Bank ID

2.21

+++

BIC

<BIC>

BICIdentifier,
[0..1] 8 or 11
characters

R BIC of creditor bank

[0..1] Composed

Ultimate party
(if different from the holder of
O the account to be credited)
particularly where a collection
factory is involved.

2.23

UltimateCreditor

<UltmtCdtr>

ISODate
M Requested collection date
YYYY-MM-DD

2.23

++

Name

<Nm>

[0..1] Max140text

2.24

ChargeBearer

<ChrgBr>

[0..1]

2.27

CreditorSchemeIden <CdtrSchmeId>
tification

2.27

++

2.27

+++

2.27

++++

2.27

+++++

2.27

+++++

2.27

++++++

Identification

<Id>

PrivateIdentification <PrvtId>
Other

<Othr>

Identification

<Id>

SchemeName

<SchmeNm>

Proprietary

<Prtry>

Creditor, holder of the account

to be credited
Name of account
holder, limited to 70
characters

IBAN of the account

to be credited

"See Appendix 2 for

the list of BIC Codes

R Name of the ultimate Creditor

ChargeBearer
Specifies which parties will
O
Type1Code
bear the payment charges
R

[0..1] Composed

[1..1] Composed

[0..n] Composed

Only one occurrence is

R authorised:

[0..1] Composed

[1..1] Max35Text

"SLEV"

SEPA creditor Identifier

Elements

[0..1] Composed

[1..1] Max35Text

Provided on the
creditor's account
statement,
Limited to 70
characters

SEPA creditor
identifier (see
structure in section
2.2)

The value "SEPA"

must be used

(a) : In the web site Sogecash Web, only one Payment Information sequence is allowed.

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 13/24

Index Level

Message Item

<XML tag>

Mult. Format

S Name and definition

2.28

DirectDebit
TransactionInform <DrctDbtTxInf> [1..n] Composed
ation

M Transaction level

2.29

++

Payment
Identification

M Transaction Identification

<PmtId>

[1..1] Composed

Comments
The level must be
repeated the same
number of times as
the number of
transactions (=
direct debit orders)

2.30

+++

InstructionIdentificati
on
<InstrId>
I

[0..1] Max35Text

Transaction reference. for the

creditor

2.31

+++

EndToEnd
Identification

<EndToEndId>

[1..1] Max35Text

End-to-end reference
transmitted to debtor

<InstdAmt>

12 num
[1..1]
maximum

Currency and Amount of

payment, from
M EUR 0.01
to EUR 999 999 999.99

2.44

++

InstructedAmount

2.46

++

DirectDebitTransacti
<DrctDbtTx>
on

[0..1] Composed

2.47

+++

MandateRelatedInfo
<MndtRltdInf>
rmation

[0..1] Composed

2.48

++++

MandateIdentificatio
<MndtId>
n

[0..1] Max35Text

Original mandate reference

number

2.49

++++

DateOfSignature

[0..1] ISODate

Date on which the mandate

was signed

<DtOfSgntr>

[0..1]

TrueFalse
Indicator

Information pertaining
to the mandate

Indicator of amendment to
mandate data

2.50

++++

AmendmentIndicator <AmdmntInd>

2.51

++++

AmendmentInformati
<AmdmntInfDtls> [0..1] Composed
onDetails

2.52

+++++

OriginalMandateIden
<OrgnlMndtId>
tification

Reference of the original

O
mandate

2.53

+++++

OriginalCreditorSche
<OrgnlCdtrSchm
me
[0..1] Composite
eId>
Identification

O Original creditor data

2.53

++++++

Name

<Nm>

[0..1] Max140text

O Original name of creditor

2.53

++++++

Identification

<Id>

[0..1] Composed

2.53

+++++++ PrivateIdentification <PrvtId>

[1..1] Composed

[0..1] Max35Text

Provided on the
creditor's account
statement in case of
reject/return/refund
iissued by the
debtors bank (unitary
batchbooking)
Provided on the
creditor's account
statement in case of
reject/return/erfund
iissued by the
debtors bank (unitary
batchbooking
Amount in EUR > 0
Where applicable,
decimals are
separated by a
decimal point.

Guide to SEPA Direct Debit Orders in ISO 20022 format

Indicator referring to
any modifications to
one or more data in
the mandate.
Value:
"true" if amendment
"false" if no
amendment (default
value)

Must be completed if
an amendment is
made to the original
mandate.
Original data
pertaining to the
creditor
Limited to 70 char.
Must be completed if
the creditor's name is
changed

V05 2011

P 14/24

Index Level

Message Item

<XML tag>

Mult. Format

S Name and definition

[0..n] Composed

[1..1] Max35Text

[0..1] Composed

2.53

++++++++ Other

<Othr>

2.53

++++++++ Identification
+

<Id>

2.53

++++++++ SchemeName
+

<SchmeNm>

2.53

++++++++ Proprietary
++

2.57

<Prtry>

[1..1] Max35Text

+++++

OriginalDebtorAccou
<OrgnlDbtrAcct> [0..1] Composed
nt

2.57

++++++

Identification

2.57

+++++++ IBAN

Comments

Only one occurrence is

authorised
Original creditor
identifier

Value = "SEPA" in
most cases.
See appendix 3 for
migration rules in
France
Only needs to be
completed if there is a
change of account
number within the
same financial
institution

Original debtor account

number

<Id>

[1..1] Composed

<IBAN>

[1..1] Max 34Text

IBAN
Only used if the
debtor changes
financial institutions.
In this case, the
SEPA direct debit
must be associated
with a transaction
sequence set at
"FRST" (index 2.14)
Also see paragraph
2.4.

2.58

+++++

OriginalDebtorAgent <OrgnlDbtrAgt>

[0..1] Composed

2.58

++++++

FinancialInstitution
Identification

<FinInstnId>

[1..1] Composed

2.58

+++++++ Other

<Othr>

[0..1] Composed

2.58

++++++++ Identification

<Id>

[1..1] Max 35Text

"SMNDA" = Same
Mandate With New
Debtor Agent

2.69

++

UltimateCreditor

<UltmtCdtr>

[0..1] Composed

Third party creditor

(if different from the holder of
O the account to be credited)
particularly where a collection
firm is involved.

2.69

+++

Name

<Nm>

[0..1] Max140text

R Name of third party creditor

2.70

++

DebtorAgent

<DbtrAgt>

[1..1] Composed

2.70

+++

FinancialInstitutionId
<FinInstnId>
entification

[1..1] Composed

M Bank Identification

Use index 2.23 unless

there is more than
one "ultimate creditor"
in the batch.
Limited to 70
characters

Bank where debtors account is

held

2.70

++++

BIC

<BIC>

BICIdentifier
[0..1] 8 or 11
characters

R BIC of the debtor bank

2.72

++

Debtor

<Dbtr>

[1..1] Composed

The BIC code must

be in the SEPA area
(see list of SEPA
countries in Appendix
1) The debtor's bank
must have adhered to
the SEPA direct debit
model used by the
creditor

Debtor (name of account

holder)

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 15/24

Index Level

Message Item

<XML tag>

Mult. Format

S Name and definition

2.72

+++

Name

<Nm>

[0..1] Max140text

R Name of debtor

2.73

++

DebtorAccount

<DbtrAcct>

[1..1] Composed

M Debtor Account

2.73

+++

Identification

<Id>

[1..1] Composed

M Account identification

2.73

++++

IBAN

<IBAN>

[1..1] IBANIdentifier M IBAN of ot the debtor

2.74

++

UltimateDebtor

<UltmtDbtr>

0..1]

2.74

+++

Name

<Nm>

[0..1] Max140text

R Name of third party debtor

2.76

++

Purpose

<Purp>

[0..1] Composed

O Type of payment

2.77

+++

Code

<Cd>

[1..1]

2.88

++

Remittance
Information

<RmtInf>

[0..1] Composed

2.89

+++

Unstructured

<Ustrd>

Composed

Comments
Limited to 70 char.

Properly structured
IBAN

Third party debtor, if different

from debtor

Limited to 70 char.

Code defining the type of

External
M
Purpose1Code payment

[0..n] Max140text

Reason for payment to the

debtor
Text describing reason for
payment

Payment Identification
elements expected by
the debtor
(Only 1 occurrence)

2.90

+++

Structured

<Strd>

[0..n] Composed

2.110

++++

CreditorReferenceInf
<CdtrRefInf>
ormation

[0..1] Composed

2.111

+++++

Type

<Tp>

[0..1] Composed

R Type of reference

2.112

++++++

CodeOrProprietary

<CdOrPrtry>

[1..1] Composed

2.113

+++++++ Code

<Cd>

[1..1]

2.116

+++++

<Ref>

[0..1] Max35Text

Reference

DocumentType
M
3Code

Guide to SEPA Direct Debit Orders in ISO 20022 format

Reference no. given

by the creditor. If this
element is used, the
Type and Reference
elements must also
be used.

"SCOR" =
StructuredCOmmunic
ationReference
Reference no. of
SEPA direct debit
given by creditor.
There is no control
key.

V05 2011

P 16/24

3.5

EXAMPLE

Message issued by TELECOM S.A.

Date: 4 February 2011
PaymentInformation
Scheme = CORE, two recurring transactions
Collection date: 8 February 2011
PaymentInformation identification.: Remittance 20110204 No. 000132
Name of creditor: TELECOM FIXE
BIC: SOGEFRPP
IBAN. FR7630003012340001122334489
Creditor identifier: FR26ZZZ666999
SEPA direct debit No. 1
Name of debtor: MRDEBITEUR1
BIC: BANKFRPP
IBAN: FR7612345123450123456789006
Amount: EUR 60.29
Unique Mandate Reference : Mandate NO1234
Instruction Identification. REFOPE1246
End-to-end Identification. FAC20080100348
Remittance Information: fixed invoice January 2011

SEPA direct debit No. 2

Second transaction to an account in Germany. Amendment to the Unique Mandate Reference.
Name of debtor: MRDEBITEUR2
BIC: DRTJDEFF
IBAN: DE89370400440532013000
Amount: EUR 58.10
Unique Mandate Reference.: Mandate NO 4567
Instruction Identification.; REFOPE1247
End-to-end Identification FAC20080100349
Remittance Information: fixed invoice January 2011
Original Mandate Identification.: Mandate NO 4467

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 17/24

3.5.1

Example with matrix template

Index Level
1.0

1.1

1.2

Message Item
GroupHeader

<XML tag>

Mult
S
.

Example

<GrpHdr>

[1..1]

Group Header

MessageIdentification

<MsgId>

[1..1]

MESS2011-123456

CreationDateTime

<CreDtTm>

[1..1]

2011-04-02T09:07:00

1.6

NumberOfTransactions

<NbOfTxs>

[1..1]

1.7

ControlSum

<CtrlSum>

[0..1]

118.39

1.8

InitiatingParty

<InitgPty>

[1..1]

1.8

++

<Nm>

[0..1]

2.0

<PmtInf>

[1..n] M

2.1

PaymentInformationIdentification

<PmtInfId>

[1..1]

Remittance 20110204 No.

000132

2.2

PaymentMethod

<PmtMtd>

[1..1]

DD

2.4

NumberOfTransactions

<NbOfTxs>

[0..1]

2.5

ControlSum

<CtrlSum>

[0..1]

118.39

2.6

PaymentTypeInformation

<PmtTpInf>

[0..1]

2.8

++

<SvcLvl>

[0..1]

2.9

+++

<Cd>

[1..1]

2.11

++

<LclInstrm>

[0..1]

2.12

+++

<Cd>

[1..1]

CORE

2.14

++

<SeqTp>

[0..1]

RCUR

2.18

RequestedCollectionDate

<ReqdColltnDt>

[1..1]

2011-02-08

2.19

Creditor

<Cdtr>

[1..1]

2.19

++

<Nm>

[0..1]

2.20

CreditorAccount

<CdtrAcct>

[1..1]

2.20

++

Identification

<Id>

[1..1]

2.20

+++

<IBAN>

[1..1] M

Name
PaymentInformation

ServiceLevel
Code
LocalInstrument
Code
SequenceType

Name

IBAN

TELECOM S.A

SEPA

TELECOM FIXE

FR76300030123400011223344
89

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 18/24

2.21

2.21

++

2.21

+++

2.24

2.27

2.27

++

2.27

+++

2.27

++++

2.27

+++++

2.27

CreditorAgent

<CdtrAgt>

[1..1]

<FinInstnId>

[1..1]

<BIC>

[0..1]

SOGEFRPP

ChargeBearer

<ChrgBr>

[0..1]

SLEV

CreditorSchemeIdentification

<CdtrSchmeId>

[0..1]

<Id>

[0..1]

<PrvtId>

[1..1]

<Othr>

[0..n]

Identification

<Id>

[1..1]

+++++

SchemeName

<SchmeNm>

[0..1]

2.27

++++++

Proprietary

<Prtry>

[1..1]

2.28

<DrctDbtTxInf>

[1..n] M

2.29

++

<PmtId>

[1..1]

2.30

+++

InstructionIdentification

<InstrId>

[0..1]

REFOPE1246

2.31

+++

EndToEndIdentification

<EndToEndId>

[1..1]

FAC20080100348

2.44

++

InstructedAmount

<InstdAmt>

[1..1]

60.29

2.46

++

DirectDebitTransaction

<DrctDbtTx>

[0..1]

2.47

+++

<MndtRltdInf>

[0..1]

2.48

++++

MandateIdentification

<MndtId>

[0..1]

Mandate NO1234

2.49

++++

DateOfSignature

<DtOfSgntr>

[0..1]

2010-11-02

2.70

++

<DbtrAgt>

[1..1]

2.70

+++

<FinInstnId>

[1..1]

2.70

++++

<BIC>

[0..1]

2.72

++

<Dbtr>

[1..1]

2.72

+++

<Nm>

[0..1]

2.73

++

<DbtrAcct>

[1..1]

2.73

+++

<Id>

[1..1]

FinancialInstitutionIdentification
BIC

Identification
PrivateIdentification
Other

DirectDebit
TransactionInformation
PaymentIdentification

MandateRelatedInformation

DebtorAgent
FinancialInstitutionIdentification
BIC
Debtor
Name
DebtorAccount
Identification

FR26ZZZ666999

SEPA

BANKFRPP

MRDEBITEUR1

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 19/24

IBAN

++++

2.88

++

2.89

+++

2.28

2.29

++

PaymentIdentification

<PmtId>

[1..1]

2.30

+++

InstructionIdentification

<InstrId>

[0..1]

REFOPE1247

2.31

+++

EndToEndIdentification

<EndToEndId>

[1..1]

FAC20080100349

2.44

++

InstructedAmount

<InstdAmt>

[1..1]

58.1

2.46

++

DirectDebitTransaction

<DrctDbtTx>

[0..1]

2.47

+++

MandateRelatedInformation

<MndtRltdInf>

[0..1]

2.48

++++

MandateIdentification

<MndtId>

[0..1]

Mandate NO 4567

2.49

++++

DateOfSignature

<DtOfSgntr>

[0..1]

02/11/2010

2.50

++++

AmendmentIndicator

<AmdmntInd>

[0..1]

true

2.51

++++

AmendmentInformationDetails

<AmdmntInfDtls>

[0..1]

2.52

+++++

OriginalMandateIdentification

<OrgnlMndtId>

[0..1]

2.70

++

DebtorAgent

<DbtrAgt>

[1..1]

2.70

+++

FinancialInstitutionIdentification

<FinInstnId>

[1..1]

2.70

++++

BIC

<BIC>

[0..1]

2.72

++

Debtor

<Dbtr>

[1..1]

2.72

+++

Name

<Nm>

[0..1]

2.73

++

DebtorAccount

<DbtrAcct>

[1..1]

2.73

+++

Identification

<Id>

[1..1]

2.73

++++

IBAN

<IBAN>

[1..1] M

2.88

++

Remittanceinformation

<RmtInf>

[0..1]

2.89

+++

Unstructured

<Ustrd>

[0..n]

Remittanceinformation
Unstructured

<IBAN>

[1..1] M

<RmtInf>

[0..1]

<Ustrd>

[0..n]

FR76123451234501234567890
06

2.73

DirectDebit TransactionInformation <DrctDbtTxInf>

fixed invoice January 2011

[1..n] M

ORIGINAL Mandate NO 4467

DRTJDEFF

MRDEBITEUR2

DE89370400440532013000

fixed invoice January 2011

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 20/24

3.5.2

In XML format

<?xml version="1.0" encoding="utf-8"?>

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:iso:std:iso:20022:tech:xsd:pain.008.001.02 pain.008.001.02.xsd">
<CstmrDrctDbtInitn>
<GrpHdr>
<MsgId>MESS2011-123456</MsgId>
<CreDtTm>2011-04-02T09:07:00</CreDtTm>
<NbOfTxs>2</NbOfTxs>
<CtrlSum>118.39</CtrlSum>
<InitgPty>
<Nm>TELECOM S.A</Nm>
</InitgPty>
</GrpHdr>
<PmtInf>
<PmtInfId> Remittance 20110204 No 000132</PmtInfId>
<PmtMtd>DD</PmtMtd>
<NbOfTxs>2</NbOfTxs>
<CtrlSum>118.39</CtrlSum>
<PmtTpInf>
<SvcLvl>
<Cd>SEPA</Cd>
</SvcLvl>
<LclInstrm>
<Cd>CORE</Cd>
</LclInstrm>
<SeqTp>RCUR</SeqTp>
</PmtTpInf>
<ReqdColltnDt>2011-02-08</ReqdColltnDt>
<Cdtr>
<Nm>TELECOM FIXE</Nm>
</Cdtr>
<CdtrAcct>
<Id>
<IBAN>FR7630003012340001122334489</IBAN>
</Id>
</CdtrAcct>
<CdtrAgt>
<FinInstnId>
<BIC>SOGEFRPP</BIC>
</FinInstnId>
</CdtrAgt>
<ChrgBr>SLEV</ChrgBr>
<CdtrSchmeId>
<Id>
<PrvtId>
<Othr>
<Id> FR26ZZZ666999</Id>
<SchmeNm>
<Prtry>SEPA</Prtry>
</SchmeNm>
</Othr>
</PrvtId>
</Id>
</CdtrSchmeId>
<DrctDbtTxInf>
<PmtId>
<InstrId> REF OPE 1246</InstrId>
<EndToEndId> FAC20080100348</EndToEndId>
</PmtId>
<InstdAmt Ccy="EUR">60.29 </InstdAmt>
<DrctDbtTx>
<MndtRltdInf>
<MndtId> Mandate NO1234</MndtId>
<DtOfSgntr>2010-11-02</DtOfSgntr>
</MndtRltdInf>
</DrctDbtTx>
<DbtrAgt>
<FinInstnId>
<BIC>BANKFRPP</BIC>
</FinInstnId>
</DbtrAgt>
<Dbtr>
<Nm>MRDEBITEUR1</Nm>
</Dbtr>
<DbtrAcct>
<Id>

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 21/24

<IBAN>FR7612345123450123456789006</IBAN>
</Id>
</DbtrAcct>
<RmtInf>
<Ustrd> fixed invoice January 2011</Ustrd>
</RmtInf>
</DrctDbtTxInf>
<DrctDbtTxInf>
<PmtId>
<InstrId> REFOPE1247</InstrId>
<EndToEndId> FAC20080100349</EndToEndId>
</PmtId>
<InstdAmt Ccy="EUR">58.10</InstdAmt>
<DrctDbtTx>
<MndtRltdInf>
<MndtId> Mandate NO 4567</MndtId>
<DtOfSgntr>2010-11-02</DtOfSgntr>
<AmdmntInd>true</AmdmntInd>
<AmdmntInfDtls>
<OrgnlMndtId> ORIGINAL Mandate NO 4467</OrgnlMndtId>
</AmdmntInfDtls>
</MndtRltdInf>
</DrctDbtTx>
<DbtrAgt>
<FinInstnId>
<BIC>DRTJDEFF</BIC>
</FinInstnId>
</DbtrAgt>
<Dbtr>
<Nm>MRDEBITEUR2</Nm>
</Dbtr>
<DbtrAcct>
<Id>
<IBAN>DE89370400440532013000</IBAN>
</Id>
</DbtrAcct>
<RmtInf>
<Ustrd> fixed invoice January 2011</Ustrd>
</RmtInf>
</DrctDbtTxInf>
</PmtInf>
</CstmrDrctDbtInitn>
</Document>

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 22/24

APPENDIX 1 LIST OF SEPA COUNTRY CODES

DE
AT
BE
BG
CY
DK

Germany
Austria
Belgium
Bulgaria
Cyprus
Denmark
Spain
Including the Canary Islands, Ceuta and

ES

Melilla

EE
FI
FR

Estonia
Finland
France
Guadeloupe
French Guyana
Martinique
Mayotte
Reunion
Saint Barthlemy
Saint Martin
Saint Pierre and Miquelon

GP
GF
MQ

IS
IT
LV
LI
LT
LU
MT

Monaco

MC

Norway
The Netherlands
Poland
Portugal

NO
NL
PL
PT

Including Azores and Madeira

YT
RE
BL
MF
PM

GR
HU
IE

Greece
Hungary
Ireland

Iceland
Italy
Latvia
Lichtenstein
Lithuania
Luxembourg
Malta

CZ
RO
GB

Czech Republic
Romania
United Kingdom
Gibraltar

GI

Slovakia
Slovenia
Sweden
Switzerland

SK
SI
SE
CH

APPENDIX 2 LIST OF BIC CODES FOR SG FRANCE, SG MONACO AND SOCIETE

GENERALES BRANCHES
Name of Societe Generales outlet

BIC Code

SOCIETE GENERALE FRANCE

SOGEFRPP

SOCIETE GENERALE MONACO

SOGEMCM1

SOCIETE GENERALE, BRUSSELS (BELGIAN HEAD OFFICE)

SGABBEB2

SOCIETE GENERALE, PARIS, ZURICH BRANCH, ZURICH

SGABCHZZ

SOCIETE GENERALE S.A., FRANKFURT AM MAIN

SOGEDEFF

SOCIETE GENERALE, SUCURSAL EN ESPANA, MADRID

SOGEESMM

SOCIETE GENERALE, AMSTERDAM

SOGENL2A

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 23/24

APPENDIX 3 COUNTRIES SPECIFIC REQUIREMENTS

FRANCE: principles of data input in ISO 20022 format for the first post-migration SDD order
Migration refers to the transition from the national direct debit scheme to the SEPA direct debit scheme.
The CFONB uses the following principles of data input in ISO 20022 format for the first post-migration SEPA direct debit:
- association with a transaction sequence with the value "FRST",
- means of identifying the first migrated SEPA direct debit:
Case 1: the National Identifier Number incorporated in the SEPA Credit Identifier is the same as the identifier used in the
national direct debit scheme.

Index

Element

Definition

2.14
2.50

SequenceType
AmendmentIndicator

Value = "FRST"
Value = "false"

Case 2: the National Identifier Number incorporated in the SEPA Credit Identifier is different from the one used in the
national direct debit scheme.

Index

Element

Definition

2.14

SequenceType

Value = "FRST"

2.50
2.53

AmendmentIndicator
Identification

Value = "true"

2.53

SchemeName
Proprietary

Original NIN

Not entered after migration to

SDD

Guide to SEPA Direct Debit Orders in ISO 20022 format

V05 2011

P 24/24