Standards:IG Scheme CreditorUpdateRequest
Elle est en cours de révision par les instances officielles, et devrait devenir une norme définitive prochainement.
- 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 conversion="none" date="Mon Feb 18 10:13:32 CET 2013" last="" repository="Scheme" revision="238" source="CupReq_Intro.txt">
Introduction
This document describes the contents of the SEPAmail message used to update a creditor in the icqx@scheme repository.
The full name of this message is sepamail_message_scheme_CreditorUpdateRequest.
This message must be generated and sent by the creditor's bank. It can also be used by the creditor, to communicate the identification elements to its bank.
This message is not based upon any existing ISO schema, but carries a specific structure : an ICQXCard. </svnig>
<svnig conversion="none" date="Thu Aug 16 07:33:09 CEST 2012" last="" repository="Scheme" revision="171" source="CupReq_Root.txt">
Message root
</svnig>
<svnig conversion="tab" date="Wed Aug 29 16:56:20 CEST 2012" last="" repository="Scheme" revision="195" source="CupReq_Root.tab">
| Mult | Message Element | SEPAmail requirement |
|---|---|---|
| [1..1] | CreditorUpdateRequest |
</svnig>
<svnig conversion="none" date="Thu Aug 16 07:33:09 CEST 2012" last="" repository="Scheme" revision="171" source="CupReq_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 CreditorUpdateRequest element must be any one of the sepamail_creditor_update_request_xxx structures. </svnig>
<svnig conversion="tab" date="Wed Aug 29 16:56:20 CEST 2012" last="" repository="Scheme" revision="195" source="CupReq_Abstract.tab">
| Mult | Message Element | SEPAmail requirement |
|---|---|---|
| [1..1] | sepamail_creditor_update_request_001 | First version of the message |
</svnig>
<svnig conversion="none" date="Thu Aug 16 07:33:09 CEST 2012" last="" repository="Scheme" revision="171" source="CupReq_Body.txt">
Message Body
Please note that the ICQX element is mandatory in this message. It must be present even if the creditor changed bank since its creation. </svnig>
<svnig conversion="tab" date="Thu Aug 16 08:03:58 CEST 2012" last="" repository="Scheme" revision="175" source="CupReq_Body.tab">
| Ref | Mult | Message Element | SEPAmail requirement |
|---|---|---|---|
| A1 | [1..1] | + RequestId | Unique identifier, which will be used to match this message with the UpdateReport one. |
| A2 | [1..1] | + ICQXCard | See detailed contents below. |
</svnig>
ICQXCard
Here is the detailed contents of the ICQXCard :
<svnig conversion="tab" date="Wed Aug 29 16:56:20 CEST 2012" last="" repository="Scheme" revision="195" source="ICQXCard.tab">
| Ref | Mult | Message Element | SEPAmail requirement |
|---|---|---|---|
| I | [1..1] | + ICQXCard | |
| I1 | [0..1] | ++ ICQX | Mandatory in all messages, except CreditorCreationRequest where it MUST be absent. |
| I2 | [1..1] | ++ BIC | BIC of the bank issuing the request |
| I3 | [1..1] | ++ Identity | |
| I3.1 | [1..1] | +++ PartyName | Name by which a party is known and which is usually used to identify that party. For a company, this must be the registered name. |
| I3.2 | [0..1] | +++ DisplayName | Name by which the party is designated (can be a commercial name, an alias ...). Defaults to PartyName (I3.1). |
| I3.3 | [0..1] | +++ Logo | |
| I3.4 | [0..1] | +++ Thumbnail | |
| I3.5 | [1..1] | ++ PostalAddress | Information that locates and identifies the address of the Party, as defined by postal services and at which the business is legally domiciled. |
| I3.5.1 | [0..1] | +++ AddressType | Code |
| I3.5.2 | [0..1] | +++ Department | Text |
| I3.5.3 | [0..1] | +++ SubDepartment | Text |
| I3.5.4 | [0..1] | +++ StreetName | Text |
| I3.5.5 | [0..1] | +++ BuildingNumber | Text |
| I3.5.6 | [0..1] | +++ PostCode | Text |
| I3.5.7 | [0..1] | +++ TownName | Text |
| I3.5.8 | [0..1] | +++ CountrySubdivision | Text |
| I3.5.9 | [0..1] | +++ Country | Code |
| I3.5.10 | [0..7] | +++ AddressLine | Text |
| I4 | [1..1] | ++ Identification | |
| I4.1 | [1..n] | +++ OrgId | |
| I4.1.1 | [1..1] | ++++ Id | Identification data (SIREN, legal structure ...) |
| I4.1.2 | [0..1] | ++++ SchmeNm | |
| I4.1.3 | [0..1] | ++++ Issr | Mandatory, type of data. Allowed values are SIRET SIREN APE TVA_intracomm legal_structure other |
| I5 | [1..1] | ++ Validity | |
| I5.1 | [1..1] | +++ ValidStartDate | ISO format |
| I5.2 | [1..1] | +++ ValidEndDate | ISO format |
| I5.3 | [1..1] | +++ LastUpdateDate | ISO format |
| I5.4 | [0..1] | +++ Test | True if this is a testing account [usefulness to be confirmed] |
</svnig>