Outils personnels

IG Gemme MandateAcceptanceReport

De documentation SEPAmail.

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 indicate acceptance, rejection or debtor-initiated modification of a mandate.

The full name of this message is sepamail_message_direct.debit_MandateAcceptanceReport.

This message must be generated and sent by the debtor's bank. The generating events can be, for instance:

  • notification by the debtor of his acceptance of the mandate
  • notification by the debtor of his refusal of the mandate
  • request by the debtor for an account change, either within the same bank or to another bank

This message is based upon ISO 10022 pain.012 schema. To allow additional features, it also includes non-ISO parts. All message parts are described in this document.

source MndAcc_Intro.txt, date Wed Aug 29 16:04:21 CEST 2012


Message Root

source MndAcc_Root.txt, date Wed Aug 29 16:04:21 CEST 2012


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

source MndAcc_Root.tab, date Wed Aug 29 16:04:21 CEST 2012


ISO and Non-ISO parts

source MndAcc_Body.txt, date Wed Aug 29 16:04:21 CEST 2012


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

source MndAcc_Body.tab, date Wed Aug 29 16:04:21 CEST 2012


ISO Part : MandateAcceptanceReportV01

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.

source MndAcc_ISO.txt, date Wed Aug 29 16:04:21 CEST 2012


Group Header

The group header contains information required for the processing of the entire message.

source MndAcc_Group.txt, date Wed Aug 29 16:04:21 CEST 2012


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

source MndAcc_Group.tab, date Wed Aug 29 16:04:21 CEST 2012


Underlying Acceptance Details

source MndAcc_Accept.txt, date Wed Aug 29 16:04:21 CEST 2012


Ref Mult Message Element SEPA/SEPAmail requirement
2.0 [1..1] + Underlying Acceptance Details
2.1 [0..1] ++ Original Message Information Mandatory
2.1 [1..1] +++ Message Identification The value MUST be taken from the Gemme MandateInitiationRequest message (field 1.1)
2.1 [1..1] +++ Message Name Identification
2.1 [0..1] +++ Creation Date Time
2.2 [1..1] ++ Acceptance Result
2.3 [1..1] +++ Accepted (AT-61 Result of the Debtor validation)
2.4 [0..1] +++ Reject Reason
2.5 {Or ++++ Code See Message Element Specifications below.
2.6 Or} ++++ Proprietary
2.7 [0..n] +++ Additional Reject Reason Information
2.8 [1..1] ++ Original Mandate
2.9 {Or +++ Original Mandate Identification
2.10 Or} +++ Original Mandate
2.11 [1..1] ++++ Mandate Identification (AT-01 Unique Mandate Reference) Usage Rule: If no "Mandate Identification" is available at the time that the acceptance/validation report is sent, "Mandate Identification" is to be populated with the text "NOTPROVIDED".
2.12 [0..1] ++++ Mandate Request Identification
2.13 [0..1] ++++ Type
2.14 [0..1] +++++ Service Level Mandatory
2.15 {Or ++++++ Code (AT-20 Identification code of the Scheme) Usage Rule : Only "SEPA" is allowed.
2.16 Or} ++++++ Proprietary
2.17 [0..1] +++++ Local Instrument Mandatory
2.18 {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.19 Or} ++++++ Proprietary
2.20 [0..1] ++++ Occurrences Mandatory
2.21 [1..1] +++++ Sequence Type (AT-21 Transaction type (recurrent, one-off)
2.22 [0..1] +++++ Frequency
2.23 [0..1] +++++ Duration
2.24 [0..1] +++++ First Collection Date
2.25 [0..1] +++++ Final Collection Date
2.26 [0..1] ++++ Collection Amount
2.27 [0..1] ++++ Maximum Amount
2.28 [0..1] ++++ Creditor Scheme Identification Mandatory
2.28 [0..1] +++++ Name
2.28 [0..1] +++++ Postal Address
2.28 [0..1] +++++ Identification Mandatory (AT-02 Identifier of the Creditor)
2.28 {Or ++++++ Organisation Identification
2.28 Or} ++++++ Private Identification Usage Rule: Private Identification is used 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" must be used with an identifier described in General Message Element Specifications, Chapter 1.5.2. Usage Rule : Only one occurrence of "Other" is allowed.
2.28 [0..1] +++++ Country of Residence
2.28 [0..1] +++++ Contact Details
2.29 [1..1] ++++ Creditor
2.29 [0..1] +++++ Name Mandatory (AT-03 Name of the Creditor) Usage Rule : "Name" is limited to 70 characters in length.
2.29 [0..1] +++++ Postal Address Mandatory (AT-05 Address of the Creditor)
2.29 [0..1] ++++++ Address Type
2.29 [0..1] ++++++ Department
2.29 [0..1] ++++++ Sub Department
2.29 [0..1] ++++++ Street Name
2.29 [0..1] ++++++ Building Number
2.29 [0..1] +++++ Post Code
2.29 [0..1] ++++++ Town Name
2.29 [0..1] ++++++ Country Sub Division
2.29 [0..1] ++++++ Country
2.29 [0..7] ++++++ Address Line Mandatory Usage Rule : Only two occurrences are allowed.
2.29 [0..1] +++++ Identification
2.29 [0..1] +++++ Country of Residence
2.29 [0..1] +++++ Contact Details
2.30 [0..1] ++++ Creditor Account
2.31 [0..1] ++++ Creditor Agent
2.32 [0..1] ++++ Ultimate Creditor
2.32 [0..1] +++++ Name (AT-38 Name of the Creditor Reference Party) Usage Rule : "Name" is limited to 70 characters in length.
2.32 [0..1] +++++ Postal Address
2.32 [0..1] +++++ Identification (AT-39 Identification code of the Creditor Reference Party)
2.32 {Or ++++++ Organisation Identification Usage Rule : Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.32 Or} ++++++ Private Identification Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.32 [0..1] +++++ Country of Residence
2.32 [0..1] +++++ Contact Details
2.33 [1..1] ++++ Debtor
2.33 [0..1] +++++ Name Mandatory (AT-14 Name of the Debtor) Usage Rule : "Name" is limited to 70 characters in length.
2.33 [0..1] +++++ Postal Address Mandatory (AT-09 Address of the Debtor)
2.33 [0..1] ++++++ Address Type
2.33 [0..1] ++++++ Department
2.33 [0..1] ++++++ Sub Department
2.33 [0..1] ++++++ Street Name
2.33 [0..1] ++++++ Building Number
2.33 [0..1] ++++++ Post Code
2.33 [0..1] ++++++ Town Name
2.33 [0..1] ++++++ Country Subdivision
2.33 [0..1] ++++++ Country
2.33 [0..7] ++++++ Address Line Mandatory Usage Rule : Only two occurrences are allowed.
2.33 [0..1] +++++ Identification (AT-27 Debtor identification code)
2.33 {Or ++++++ Organisation Identification Usage Rule : Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.33 Or} ++++++ Private Identification Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.33 [0..1] +++++ Country of Residence
2.33 [0..1] +++++ Contact Details
2.34 [1..1] ++++ Debtor Account (AT-07 Account Number of the Debtor) Usage Rule : Only IBAN is allowed.
2.35 [1..1] ++++ Debtor Agent (AT-13 BIC of the Debtor Bank) Usage Rule: Only BIC is allowed.
2.36 [0..1] ++++ Ultimate Debtor
2.36 [0..1] +++++ Name (AT-15 Name of the Debtor Reference Party) Usage Rule : "Name" is limited to 70 characters in length.
2.36 [0..1] +++++ Postal Address
2.36 [0..1] +++++ Identification (AT-37 Identification code of the Debtor Reference Party)
2.36 {Or ++++++ Organisation Identification Usage Rule : Either "BIC or BEI" or one occurrence of "Other" is allowed.
2.36 Or} ++++++ Private Identification Usage Rule : Either "Date and Place of Birth" or one occurrence of "Other" is allowed.
2.36 [0..1] +++++ Country of Residence
2.36 [0..1] +++++ Contact Details
2.37 [0..1] ++++ Referred Document
2.38 [0..1] +++ Type
2.43 [0..1] +++ Number (AT-08 Identifier of the underlying Contract)
2.44 [0..1] +++ Related Date

source MndAcc_Accept.tab, date Wed Aug 29 16:04:21 CEST 2012


Non-ISO Part : AroundAcceptance

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

In the current version, they are only used when the debtor wishes to alter the bank account to which the mandate is related.

source MndAcc_NonISO.txt, date Wed Aug 29 16:04:21 CEST 2012


Ref Mult Message Element SEPAmail requirement
B1 [0..1] ++ BIC Mandatory when the mesage is used for an account change
B2 [0..1] ++ IBAN Mandatory when the mesage is used for an account change

source MndAcc_NonISO.tab, date Wed Aug 29 16:04:21 CEST 2012