New Payment Formats according to ISO 20022
The ISO 20022 standard is constantly evolving to reflect development of the SEPA scheme. In this blog post, I would like to cover the particular changes in the affected ISO messages and their implementation into our payment formats.
In the table below you can see the affected ISO messages and the new version according to standard ISO 20022.
|ISO version 2009||ISO version 2019|
Changes to all messages
While the messaging standard ISO version 2019 is mostly focused on changes to the existing elements, it has also introduced some new elements to the XML payment messages structure. You can see a summary of these adjustments in the table below.
|Postal Address||Extension of the structured elements of postal address|
|UETR (Unique End-to-End Transaction Reference)||New sub-element under ‘Payment Identification’ to provide an end-to-end reference of a payment transaction|
|Structured Remittance Information||Extension of ‘Structured’ element of Remittance Information|
|Supplementary Data||For information that cannot be captured in any other specific block, there is a new element ‘Supplementary data’.|
|Service Level||Cardinality of element ‘Service Level’ increased from maximum 1 occurrence (ISO 2009) to “n” occurrences (ISO 2019)|
|Split between Party and Agent||
‘Party’ specifies the identification of a person or an organization, ‘Agent’ specifies the identification of a
|Proxy||Possibility to use a proxy/alias for the identification of an account (creditor and/or debtor account).|
While the changes presented before affect all messages of the standard, there are also some changes applicable only to specific messages.
Changes to pain.001
|Date Time||To further specify the requested execution date, a new sub-element ‘Date Time’ was added|
|Instruction for Debtor Agent||New element ‘Instruction for Debtor Agent’ (under ‘Payment Information’) to store information related to the processing of the payment instruction (for all credit transaction information occurrences present in the payment information)|
|Remittance location details||Extension of element ‘Remittance location details’|
Changes to pain.002
|Party – Agent||Data element ‘Party’ replaced by ‘Agent’|
|Tracker Data||To provide information on the charges related to the processing of the rejection of the instruction, the new element ‘Tracker Data’ was added under ‘Transaction Information and Status’|
New Payment Formats and Bank Statements
At the moment, you can use the new payment formats listed below:
|DE_CGI_XML_CT_V9 (based on pain.001.001.09)|
|CH_CGI_XML_CT_V9 (based on pain.001.001.09)|
You can use the SAP predefined format trees as templates to create your own format tree. Use the predefined format tree CGI_CT_V9 based on version 9 of the pain.001 message format. The SAP Note 2784858 offers the corresponding functionality for these formats.
It is also possible to use the new version of the CAMT.053 bank statement format (based on CAMT.053.001.08). The SAP Note 2881354 offers a transformation from version 2 to version 8 of CAMT.053 bank statement following the guidance of the Common Global Implementation (CGI) initiative.