IG Gemme MandateInitiationRequest

SEPAmail – Norme 1206
Cette page fait partie de la version 1206 de la norme. Sauf indication contraire, elle a été validée par les instances concernées et s'impose à tous les adhérents SEPAmail. ATTENTION ! La version 1606 de la norme est disponible, vérifiez si cette page est toujours valable.

These implementation rules shall be applied in accordance with ISO20022 and SEPA own implementation rules. Thus, unless explicitly specified, data contained within a field or XML structure of a SEPAmail message must comply with the constraints related to the equivalent field or XML structure in ISO20022 or SEPA messages.
for an explanation of the color coding used in the tables below, see this page
for general rules applying to all fields, see this page
for business rules directing these IG, see this page

Introduction

This document describes the contents of the SEPAmail message used to request or indicate the creation of a mandate.

The full name of this message is sepamail_message_direct.debit_MandateInitiationRequest.

This message must be generated on behalf of the creditor, and sent by itself or by its bank. The generating events can be, for instance:

creation of a new mandate, associated for instance with a new contract
modification of an existing mandate

The second case occurs when the debtor wishes to change the bank account associated with the mandate : the debtor sends a request for this change, currently as a “Mandate Acceptance Report” message, and the creditor is expected to answer with a modified “Mandate Initiation Request” message, including the new bank account. The debtor can then check and validate this new mandate.

This message is based upon ISO 10022 pain.009 schema. For adaptability reasons, it also includes non-ISO parts. All message parts are described in this document. </svnig>

Message Root

</svnig>

Mult	Message Element	SEPAmail requirement
[1..1]	+ DirectDebitMandat

</svnig>

ISO and Non-ISO parts

The "Mandat" element (A, below) has an optional attribute named id. This attribute is meant to be used when the optional signature is being used, to allow a precise designation of the element being signed. </svnig>

Ref	Mult	Message Element	SEPAmail requirement
A	[1..1]	++ Mandat	MandateInitiationRequestV01, as per ISO pain.009
B	[0..1]	++ DSExt	Non-ISO part, described further in this document

</svnig>

ISO Part : MandateInitiationRequestV01

Please note : this whole part is directly copied from "EPC002-09 e-mandate service IG 4.0 Approved" and is only provided here for ease of reference. </svnig>

Group Header

The group header contains information required for the processing of the entire message. </svnig>

Ref	Mult	Message Element	SEPA/SEPAmail requirement
1.0	[1..1]	+ Group Header
1.1	[1..1]	++ Message Identification
1.2	[1..1]	++ Creation Date Time
1.3	[0..2]	++ Authorisation
1.4	{Or	+++ Code
1.5	Or}	+++ Proprietary	(AT-60 – The reference of the validation made by the Debtor Bank)
1.6	[0..1]	++ Initiating Party
1.7	[0..1]	++ Instructing Agent
1.8	[0..1]	++ Instructed Agent

</svnig>

Mandate

</svnig>

Ref	Mult	Message Element	SEPA/SEPAmail requirement
2.0	[1..1]	+ Mandate
2.1	[0..1]	++ Mandate Identification	(AT-01 Unique Mandate Reference) Usage Rule: If "Mandate Identification" is available at the time of the sending of the Mandate Initiation Request Message, then it should be given. It will be used in all later opportunities to track messages related to this mandate.
2.2	[1..1]	++ Mandate Request Identification	Usage Rule: If "Mandate Identification" is available at the time sending of the Mandate Initiation Request Message, then "Mandate Request Identification" may be a copy of "Mandate Identification".
2.3	[0..1]	++ Type	Mandatory
2.4	[0..1]	+++ Service Level	Mandatory
2.5	{Or	++++ Code	(AT-20 The identification code of the Scheme) Usage Rule : Only "SEPA" is allowed.
2.6	Or}	++++ Proprietary
2.7	[0..1]	+++ Local Instrument	Mandatory
2.8	{Or	++++ Code	(AT-20 The identification code of the Scheme). Allowed values are CORE: SDD CORE mandate B2B: SDD B2B mandate empty: direct debit
2.9	Or}	++++ Proprietary
2.10	[0..1]	++ Occurrences	Mandatory
2.11	[1..1]	+++ Sequence Type	(AT-21 Transaction Type)
2.12	[0..1]	+++ Frequency
2.13	[0..1]	+++ Duration
2.14	[0..1]	+++ First Collection Date
2.15	[0..1]	+++ Final Collection Date
2.16	[0..1]	++ Collection Amount
2.17	[0..1]	++ Maximum Amount
2.18	[0..1]	++ Creditor Scheme Identification	Mandatory
2.18	[0..1]	+++ Name
2.18	[0..1]	+++ Postal Address
2.18	[0..1]	+++ Identification	Mandatory (AT-02 Identifier of the Creditor)
2.18	{Or	++++ Organisation Identification
2.18	Or}	++++ Private Identification	Usage Rule: "Private Identification" is mandatory to identify either an organisation or a private person. Usage Rule : "Scheme Name" under "Other" must specify "SEPA" under "Code". Usage Rule : "Identification" under "Other" is allowed using an identifier described in General Message Element Specifications, Chapter 1.5.2. Usage Rule : Only one occurrence of "Other" is allowed. The SCI (ICS) must appear here and not in the 2.19 (Creditor) element.
2.18	[0..1]	+++ Country of Residence
2.18	[0..1]	+++ Contact Details
2.19	[1..1]	++ Creditor
2.19	[0..1]	+++ Name	Mandatory (AT-03 Name of the Creditor) Usage Rule : "Name" is limited to 70 characters in length.
2.19	[0..1]	+++ Postal Address	(AT-05 Address of the Creditor)
2.19	[0..1]	++++ Address Type
2.19	[0..1]	++++ Department
2.19	[0..1]	++++ Sub-Department
2.19	[0..1]	++++ Street Name
2.19	[0..1]	++++ Building Number
2.19	[0..1]	++++ Postal Code
2.19	[0..1]	++++ Town Name
2.19	[0..1]	++++ Country Sub-Division
2.19	[0..1]	++++ Country
2.19	[0..7]	++++ Address Line	Usage Rule : Only two occurrences are allowed.
2.19	[0..1]	+++ Identification
2.19	[0..1]	+++ Country of Residence
2.19	[0..1]	+++ Contact Details
2.20	[0..1]	++ Creditor Account	IBAN
2.21	[0..1]	++ Creditor Agent	BIC
2.22	[0..1]	++ Ultimate Creditor
2.22	[0..1]	+++ Name	(AT-38 Name of the Creditor Reference Party) Usage Rule : "Name" is limited to 70 characters in length.
2.22	[0..1]	+++ Postal Address
2.22	[0..1]	+++ Identification	(AT-39 Identification code of the Creditor Reference Party)
2.22	{Or	++++ Organisation Identification	Usage Rule : Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.22	Or}	++++ Private Identification	Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.22	[0..1]	+++ Country of Residence
2.22	[0..1]	+++ Contact Details
2.23	[1..1]	++ Debtor
2.23	[0..1]	+++ Name	Mandatory (AT-14 Name of the Debtor) Usage Rule : "Name" is limited to 70 characters in length.
2.23	[0..1]	+++ Postal Address	Mandatory (AT-09 Address of the Debtor)
2.23	[0..1]	++++ Address Type
2.23	[0..1]	++++ Department
2.23	[0..1]	++++ Sub Department
2.23	[0..1]	++++ Street Name
2.23	[0..1]	++++ Building Numb
2.23	[0..1]	++++ Post Code
2.23	[0..1]	++++ Town Name
2.23	[0..1]	++++ Country Subdivision
2.23	[0..1]	++++ Country
2.23	[0..7]	++++ Address Line	Mandatory Usage Rule : Only two occurrences are allowed.
2.23	[0..1]	+++ Identification	(AT-27 Debtor identification code)
2.23	{Or	++++ Organisation Identification	Usage Rule : Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.23	Or}	++++ Private Identification	Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.23	[0..1]	+++ Country of Residence
2.23	[0..1]	+++ Contact Details
2.24	[0..1]	++ Debtor Account	Mandatory
2.25	[1..1]	++ Debtor Agent	Mandatory (AT-13 BIC of the Debtor Bank) Usage Rule: Only BIC is allowed.
2.26	[0..1]	++ Ultimate Debtor	Usage Rule: Mandatory, if provided by the Debtor in the Mandate.
2.26	[0..1]	+++ Name	(AT-15 Name of the Debtor Reference Party) Usage Rule : "Name" is limited to 70 characters in length.
2.26	[0..1]	+++ Postal Address
2.26	[0..1]	+++ Identification	(AT-37 Identification code of the Debtor Reference Party)
2.26	{Or	++++ Organisation Identification	Usage Rule: Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.26	Or}	++++ Private Identification	Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.26	[0..1]	+++ Country of Residence
2.26	[0..1]	+++ Contact Details
2.27	[0..1]	++ Referred Document
2.28	[0..1]	+++ Type
2.33	[0..1]	+++ Number	(AT-08 Identifier of the underlying Contract)
2.34	[0..1]	+++ Related Date

</svnig>

Non-ISO Part : AroundMandat

This part of the message adds information used by the SEPAmail/GEMME system, either for routing purposes or to provide users with richer functionalities. </svnig>

Ref	Mult	Message Element	SEPAmail requirements
B1	[0..1]	++ SndMaxDT	Latest validity date
B2	[1..1]	++ Status	Mandate status. Only values accepted are “ACCP” (accepted : the mandate is validated, either through SEPAmail or through some creditor-specific mechanism) “PNDG” (pending : the mandate must still be validated through SEPAmail)
B3	[1..1]	++ SignTp	Signature Type. Possible values are “manual” : mandate has been signed by non-SEPAmail means “sepamail” : mandate has been signed through SEPAmail.
B4	[0..1]	++ RtrPmt	Charge bearer. Possible values are “CRED” (creditor), “DEBT” (debitor), “SHAR” (shared) and “SLEV” (depending on servce level)
B5	[0..n]	++ Document	Attached documents. The contract or other document may be present for clarity.
B5.1	[1..1]	+++ Type	May be “mandate” (legal document) or “information” (other document)
B5.2	[0..1]	+++ Date	Document date, ISO format
B5.3	[1..1]	+++ Title	Document title, max 200 characters
B5.4	[1..1]	+++ Reference	Document reference, max 100 characters
B5.5	[1..1]	+++ Lang	Mandatory, Language code for document language
B5.6	[0..1]	+++ Contents
B5.6.1	[1..1]	++++ mime-type	Mandatory
B5.6.2	[0..1]	++++ name	document name, may or may not differ from the title above
B5.6.3	[1..1]	++++ data	actual contents of the document, may be anything depending on MIME type. It can for example contain simply an URL where the document is accessible.
B6	[1..1]	++ DbtrSignature	Signature of debtor
B6.1	[1..1]	+++ signature-type	Type of signature, may be “handwritten”, “electronic” or “other”
B6.2	[1..1]	+++ data	Actual signature, contents depending on the above type
B7	[0..1]	++ CdtrSignature
B7.1	[1..1]	+++ signature-type	Type of signature, may be “handwritten”, “electronic” or “other”
B7.2	[1..1]	+++ data	Actual signature, contents depending on the above type
B8	[0..1]	++ CdtrLogo	Creditor logo, will be displayed along with the mandate if technically possible
B8.1	[1..1]	+++ mime-type	Mandatory
B8.2	[1..1]	+++ data	actual contents of the image, may be anything depending on MIME type.
B9	[0..1]	++ DbtFirstName	First name of the debtor, used for validation
B10	[0..1]	++ DbtLastName	Last name of the debtor, used for validation
B11	[0..1]	++ DbtLastNameType	Type of above last name. Can be “birthName”, “maritalName” or “alias”. To be used only when known for sure.

</svnig>

IG Gemme MandateInitiationRequest

Introduction

Message Root

ISO and Non-ISO parts

ISO Part : MandateInitiationRequestV01

Group Header

Mandate

Non-ISO Part : AroundMandat

Navigation menu

Search