IG Gemme RequestForCopy
- 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
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="none" source="ReqCopy_Intro.txt">
Introduction
This document describes the contents of the SEPAmail message used by a debtor -- or his bank -- to request from the creditor a copy of the mandate associated with a given transaction.
The full name of this message is sepamail_message_direct.debit_RequestForCopy.
This message should be generated and sent by the debtor's bank, possibly following a direct request from the debtor him/herself.
The message must be answered by the creditor with another “Request for Copy” message, with the same request identifier, and giving all required information and all necessary legal proof (copy of the contract, or digital signature evidence, as the case may be)
This message is derived from ISO schemas, but is not an actual extension of an existing ISO message. Thus, it only includes a non-ISO part, described here.
Please note that this message will be separated into a request message and a report message in the next version of the SEPAmail standard, to conform to the general SEPAmail organization. </svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="none" source="ReqCopy_Root.txt">
Message root
</svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="tab" source="ReqCopy_Root.tab">
| Mult | Message Element | SEPAmail requirement |
|---|---|---|
| [1..1] | DirectDebitRFCopy |
</svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="none" source="ReqCopy_Abstract.txt">
Internal abstraction level
To facilitate upgrades, an abstraction level has been inserted at the root of this element.
The actual contents of the DirectDebitRFCopy element must be any one of the following structures. </svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="tab" source="ReqCopy_Abstract.tab">
| Mult | Message Element | SEPAmail requirement |
|---|---|---|
| [1..1] | sepamail_message_direct_debit_request_for_copy_001 | First version of the structure |
</svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="none" source="ReqCopy_Group.txt">
Group Header
The group header contains information related to the message itself. </svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="tab" source="ReqCopy_Group.tab">
| Ref | Mult | Message Element | SEPAmail requirement |
|---|---|---|---|
| A | [1..1] | ++ GrpHdr | |
| A1 | [1..1] | +++ RequestId | Identifier of the request, may be any string. However, when this message is used as an answer to a request, this field must be set to the same identifier as the request. |
| A2 | [1..1] | +++ CreDtTm | Mandatory: Creation date and time, ISO format |
</svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="none" source="ReqCopy_Request.txt">
Request
This part of the message actually describes the transaction upon which the request is based -- or at least the actors of this transaction. </svnig>
<svnig date="Mon Sep 03 18:16:11 CEST 2012" revision="" repository="Gemme" last="" conversion="tab" source="ReqCopy_Request.tab">
| Ref | Mult | Message Element | SEPAmail requirement |
|---|---|---|---|
| B | [1..1] | ++ Request | |
| B1 | [1..1] | +++ CustRef | Customer Reference. Internal reference the creditor associates with the debtor, mandate, or the payment schedule described here |
| B2 | [1..1] | +++ Cdtr | |
| B2.1 | [0..1] | ++++ Nm | Mandatory |
| B2.2 | [0..1] | ++++ PstlAdr | |
| B2.3 | [0..1] | ++++ Id | |
| B2.3.1 | {Or | +++++ OrgId | |
| B2.3.2 | Or} | +++++ PrvtId | |
| B2.4 | [0..1] | ++++ CtryOfRes | |
| B2.5 | [0..1] | ++++ CtctDtls | |
| B3 | [0..1] | +++ CdtrAcct | IBAN of creditor |
| B4 | [0..1] | +++ CdtrAgt | BIC of creditor |
| B5 | [0..1] | +++ UltmtCdtr | Used when there is an intermediate creditor, acting for an ultimate creditor |
| B6 | [1..1] | +++ Dbtr | |
| B6.1 | [0..1] | ++++ Nm | Mandatory |
| B6.2 | [0..1] | ++++ PstlAdr | |
| B6.3 | [0..1] | ++++ Id | |
| B6.3.1 | {Or | +++++ OrgId | |
| B6.3.2 | Or} | +++++ PrvtId | |
| B6.4 | [0..1] | ++++ CtryOfRes | |
| B6.5 | [0..1] | ++++ CtctDtls | |
| B7 | [0..1] | +++ DbtrAcct | |
| B7.1 | [1..1] | ++++ Id | |
| B7.1.1 | {Or | +++++ IBAN | Mandatory |
| B7.1.2 | Or} | +++++ Other | |
| B7.2 | [0..1] | ++++ Tp | |
| B7.3 | [0..1] | ++++ Ccy | |
| B7.4 | [0..1] | ++++ Nm | |
| B8 | [0..1] | +++ DbtrAgt | |
| B8.1 | [1..1] | ++++ FinInstnId | |
| B8.1.1 | [0..1] | +++++ BIC | Mandatory |
| B8.1.2 | [0..1] | +++++ ClrSysMmbId | |
| B8.1.3 | [0..1] | +++++ Nm | |
| B8.1.4 | [0..1] | +++++ PstlAdr | |
| B8.1.5 | [0..1] | +++++ Other | |
| B9 | [1..1] | +++ Trans | |
| B9.1 | [1..1] | ++++ TrsDate | Mandatory, ISO format |
| B9.2 | [1..1] | ++++ TrsAmt | Mandatory. Usage rule: Currency attribute must be set to "EUR". |
| B9.3 | [0..1] | ++++ TrsId | Optional. Must be present only if known for sure -- this reference must come from a Gemme Prenotification message. |
| B9.4 | [0..1] | ++++ Accepted | MUST be omitted in this message |
| B10 | [0..1] | +++ Mandate | Any type of document or URL giving access to the original mandate. This field is mandatory only in the answer message. |
</svnig>