Differences between pain.001.001.02 and pain.001.001.03
This document provides an overview of the most important changes between pain.001.001.02 and pain.001.001.03. At the moment of writing the EPC did not publish implementation guideline how to deal with pain.001.001.03.
70%-80% is changed in the layout. Types and tag names are changed causing the XML interpretation at banks, clearing hous and customers to be adapted. Becau the changes are on any level, from top to bottom, code changes are always needed when start using pain.001.001.03. It can be anticipated that both versions have to be supported concurrently for some time. Furthermore, due to changes in the format organizations that mapped the XML to another (relational) structure has to redo this mapping, and might migrate the current stored transactions to the new format to avoid data management problems.
Plea contact *************************** in ca of any questions.
Reference
1EPC RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS, EPC,DOC 188-09, 27 October 2009 (Version 1.01 Approved)
2SEPA CREDIT TRANSFER SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES, EPC, DOC EPC132-08, 30 October 2009, (Version 3.3 Approved)
高中补习班3Catalogue of ISO 20022 messages at
www.iso20022/catalogue_of_unifi_messages.page
Changes
Date Author Description
coms11-11-2009 P. Droppert Initial version
06-02-2010 P. Droppert Corrections in CtgyPurp, Purp and SvcLvl
08-02-2010 P. Droppert Add management summary (thanks to R. Kilg)
_______________________________________________________________________________________________________________
1Management summary
Summary of relevant XML structure changes
•Names of tags changed (example pain.001.001.02->CstmrCdtTrfInitn)
•BtchBooking moved to PmtInf level, Grpg removed
•NbOfTxs and CtrlSum added at PmtInf level
•CrdtrSchemeId added at PmtInf Level
•Length of the values incread (example: Nm from 70->140, EPC IG rule 70)
•Order of elements changed (example: PstlAdr - Ctry, AdrLine)
•Mandatory fields have become optional (example: PstlAdr - Ctry)
•Structure of Id’s (debtor, creditor, ultimates) changed
•Structure of Strd (structured remittance info) changed
•Structure of RgltryRptg (regulatory reporting) changed
•List of codes externalized (example: SvcLvl, CtgyPurp, maximum length changed from 4 to
ipo是什么的缩写
35)
•BBAN removed
Summary of changes introduced by EPC
•SDD: Creditor Scheme Id. available at payment level
•Reference ISO 11649 Structured Creditor reference to Remittance Information
•SCT: Local Instrument code changed to yellow
•SCT: New messages (camt.056.001.01 & camt.029.001.03)
2Overall Structure
Pain.001.001.02 pain.001.001.03
Both XML structures have as top level tag ‘Document’
Tag level below document is:
‘pain.001.001.02’ with type pain.001.001.02. Tag level below document level is:
‘CstmrCdtTrfInitn’. Type is CustomerCreditTransferInitiationV03. The next tag levels are the same as pain..02
3Group Header
pain.001.001.02 pain.001.001.03
_______________________________________________________________________________________________________________
lobotomy
Authstn has type Max128Text Authstn is of type Authorisation1Choice. This
type has two tags: Cd (type
Authorisation1Code) and Prtry
(type=Max128Text)
BtchBookg with type BatchBookingIndicator BtchBookg tag is removed and brought to the
transaction level. This allows a combination
of grouped and single transaction in a single
file.
Grpg with type Grouping1Code Grpg is removed. Allowing MIXED files only
did not add much value to this element any
longer.
purple怎么读4Person and organization identification
In pain.001.001.02 the PartyIdentification8 allows multiple ids. This was complex and did not allow identification types. In pain.001.001.03 the PartyIdentification32 allows more information but this information is simpler and allows additional type. The identification type can be bad on external tables.
pain.001.001.02 pain.001.001.03
PartyIdentification8 PartyIdentification32 is derived from
PartyIdentification8.
Nm type=Max70Text Nm type Max140Text
PstlAdr type=PostalAddress1 PstlAdr" type="PostalAddress6. Most
important change is additional department
information.
Id" type="Party2Choice Id" type="Party6Choice. This is probably the
change with the most impact. Both the
organization and person identification levels
are changes.
The organization identification is either
‘BICorBEI’, or other. This other is a t of
identifications which can be named, or linked
to an external organization identification关于朋友的英语谚语
scheme name. This allows a maximum on
flexibility with a minimal impact on the code
to be ud to handle this kind of
identification.
The same principle is ud for person
identification. This is ‘DtAndPlcOfBirth’, of
identification with the same concept as
described above.
CtctDtls (type=ContactDetails2) is added.
_______________________________________________________________________________________________________________
5Debtor transaction information
The type of the transaction is changed from PaymentInstructionInformation1 to PaymentInstructionInformation3. This ction describes the changes on this level of tags only. pain.001.001.02 pain.001.001.03
PmtInfId type=Max35Text Unchanged
PmtMtd type=PaymentMethod3Code Unchanged
Not available BtchBookg type=BatchBookingIndicator,
moved from the header to debtor transaction
level
Not available NbOfTxs type=Max15NumericText. Added on
afford什么意思debtor transaction level. This element is now
available here, as well as on header level. Not available CtrlSum type=DecimalNumber. Added on
debtor transaction level. This element is now
available here, as well as on header level. PmtTpInf type=PaymentTypeInformation1 PmtTpInf type= PaymentTypeInformation19.
Type changed described below. ReqdExctnDt type=ISODate Unchanged
PoolgAdjstmntDt type=ISODate Unchanged
Dbtr type=PartyIdentification8 Dbtr type=PartyIdentification32. Type change
described in a citon above.
DbtrAcct type=CashAccount7 DbtrAcct type=CashAccount16. Type changed
described below.
雅思是什么意思DbtrAgt type= BranchAndFinancialInstitutionIdentification3 DbtrAgt type= BranchAndFinancialInstitutionIdentification4
DbtrAgtAcct type=CashAccount7 DbtrAgtAcct type=CashAccount16. Type
changed described below.
UltmtDbtr type=PartyIdentification8 UltmtDbtr type=PartyIdentification32. Type
change described in a ction above. ChrgBr type=ChargeBearerType1Code Unchanged
ChrgsAcct type=CashAccount7 ChrgsAcct type=CashAccount16. Type
changed described below.
ChrgsAcctAgt
type=BranchAndFinancialInstitutionIdentificat ion3 ChrgsAcctAgt type= BranchAndFinancialInstitutionIdentification4. Type changed described below.
_______________________________________________________________________________________________________________
CdtTrfTxInf type= CreditTransferTransactionInformation1 CdtTrfTxInf type= CreditTransferTransactionInformation10. Type changed described below.
5.1PaymentTypeInformation1 versus PaymentTypeInformation19
pain.001.001.02 pain.001.001.03
InstrPrty type=Priority2Code Unchanged
SvcLvl type=ServiceLevel2Choice SvcLvl type=ServiceLevel8Choice. Instead of
3 fixed values of
4 characters, the code
defining the rvice level is linked with an
external 4 character code table. This allows
any code to be filled in (following the
externalized table). The Prtry field continues
to have 35 characters.
ClrChanl type=ClearingChannel2Code Removed
LclInstrm type=LocalInstrument1Choice LclInstrm type=LocalInstrument2Choice. The
type of the ‘Cd” is changed from
ExternalLocalInstrumentCode to
ExternalLocalInstrument1Code. The type
are constructed the same.
CtgyPurp
type=PaymentCategoryPurpo1Code CtgyPurp type= CategoryPurpo1Choice. The defined t is externalized.fox news
5.2CashAccount7 versus CashAccount16
pain.001.001.02 pain.001.001.03
Id type=AccountIdentification3Choice Id type=AccountIdentification4Choice. Type
changed described below.
Tp type=CashAccountType2 Unchanged
Ccy type=CurrencyCode Ccy type=ActiveOrHistoricCurrencyCode. The
name and type is changed, but the structure
of the type is the same.
Nm type=Max70Text Unchanged
5.3AccountIdentification3Choice versus AccountIdentification4Choice
The pain.001.001.02 element allowed four different types of account identification. With the pain.001.001.03 the account identification is by default IBAN, and when this is not applicable it can be any type. This is defined by the tag ‘Othr’.
pain.001.001.02 pain.001.001.03
IBAN type=IBANIdentifier IBAN type=IBAN2007Identifier. Almost the
same as the previous type, but allows upper
rbs
ca characters in the first 2 positions only.
This allows the first 2 characters to be the
_______________________________________________________________________________________________________________
