Nordea STP Guide For Iso 20022 MX Messages
Nordea STP Guide For Iso 20022 MX Messages
Nordea STP Guide For Iso 20022 MX Messages
v1.0
Open Page 0 of 9
Contents
Description.......................................................................................................................................................................1
General Principles ..........................................................................................................................................................1
Central Banks Market Infrastructures ..........................................................................................................................1
pacs.008 Customer Credit Transfer ................................................................................................................................2
pacs.009 FI-to-FI Customer Credit Transfer ..................................................................................................................6
pacs.004 Payment Return ................................................................................................................................................9
Description
This ISO 20022 formatting guideline is based on the ISO 20022 financial messaging format and only contains elements
which differ to CBPR+ or where Nordea provides additional explanation. This information applies to Nordea in the
Nordics (NDEADKKK, NDEAFIHH, NDEANOKK, NDEASESS) and for incoming pacs.008, pacs.009, pacs.009COV.
General Principles
To ensure a high straight through processing rate during the MT-to-MX migration coexistence period from March 2023 to
November 2025, Nordea Bank encourages along with the majority of banking peers to employ a like-for-like
methodology.
A like-for-like methodology means that while the richer MX format may be utilised, the content of the message should
be similar to the corresponding MT format. Utilising the richer data elements in the MX format may lead to the omittion or
the truncation of data which in turn may lead to non-straight through processing delays.
Examples of this is utilising the extended available space in an MX element which is not supported in the corresponding
MT tags, or the use of ultimate debtor and/or ultimate debtor elements which are neither supported in a corresponding
MT message.
The Danish, Norwegian and Swedish central banks will not support MX messages in the beginning of the transition
period and will continue to use FIN MT until migrated to MX. All three central banks have communicated a readiness by
approximately March-April 2024, approximately six months before the end of the coexistence period. Applying the like-
for-like methodology will ensure a smoother process with central bank market infrastructures and reduce the risk of
losing and truncation of information.
Open Page 1 of 9
pacs.008.001.08 STP FI to FI Customer Credit Transfer
M – Mandatory, O – Optional
M
O XML Tag Type Formatting Option Description
M GrpHdr Group Header Text This field contains the primary details of
the underlying transaction
M CreDtTm Creation Date Time Numerical: Date and time at which the message
CBPR DateTime was created
.*(\+|-)((0[0-9])| expressed in local time with UTC offset
(1[0-3])):[0-5][0-9] format (YYYY-MM-DDThh:mm:ss.sss+/-
hh:mm)
Open Page 2 of 9
M
O XML Tag Type Formatting Option Description
M CdtTrfTxInf Credit Transfer Transaction Non-repetetive For each Credit Transfer Transaction
Information Information the following elements are
mutually exclusive: A) Related
Remittance Information, B) Remittance
Information or C) all may be absent
M ChrgbrAgt Charge Bearer Agent Text BICFI and/or Clearing System Member
Open Page 3 of 9
M
O XML Tag Type Formatting Option Description
Open Page 4 of 9
M
O XML Tag Type Formatting Option Description
O Ultmtcdtr Ultimate Creditor Text This field is used to denote the Ultimate
[A-Z0-9]{4,4} Creditor party for which the money is
[A-Z]{2,2} pending
[A-Z0-9]{2,2}
([A-Z0-9]{3,3}){0,1}
O InstrForCdtrAgt Instruction For Creditor Text This element should not be used to
Agent [A-Z0-9]{4,4} facilitate Straight-Through-Processing.
[A-Z]{2,2} Please use service level proprietary tag
[A-Z0-9]{2,2} Please note that element is not allowed
([A-Z0-9]{3,3}){0,1} in the pacs.008 STP version
Open Page 5 of 9
pacs.009.001.08 FI-to-FI Customer Credit Transfer
M – Mandatory, O – Optional
M
O Element Field Name Formatting Option Comments
M SttlmMtd Settlement Method Plain text This field used to identify method used
to settle payment instructions
INDA: Settlement is done by Nordea as
Instructed Agent and the Account
Servicing Institution (an account held
with Nordea to be debited)
Pacs.009 COR & COV both use
Settlement method
INGA: Settlement is done by the
Instructing Agent who has credited an
account they service for Nordea in their
books
COVE: Settlement is done through a
Cover Payment
Pacs.009 ADV uses COVE settlement
method
M CdtTrfTxInf Credit Transfer Transaction Non-repetitive Present only once per message
Information containing all credit transaction details
Open Page 6 of 9
M
O Element Field Name Formatting Option Comments
Open Page 7 of 9
M
O Element Field Name Formatting Option Comments
O Ultmtcdtr Ultimate Creditor Text This field is used to denote the Ultimate
[A-Z0-9]{4,4} Creditor party for which the money is
[A-Z]{2,2} pending
[A-Z0-9]{2,2}
([A-Z0-9]
{3,3}){0,1}
O Rmtinf Remittance Information Plain text Information provided for more details
Ustrd Unstructured about the remittance
Open Page 8 of 9
pacs.004.001.09 Payment Return
M – Mandatory, O – Optional
M
O Element Field Name Formatting Option Comments
M TxInf TransactionInformation ReturnID: Length This field contains the details of the
(1,35) underlying transaction
M OrgnlEndToEndId Original End-To-End Length (1,35) This element relates to the End-To-End
Identification Identification of the underlying payment,
e.g. pacs.008/ pacs.009
M OrgnlUETR Original UETR Length (1,36) This element relates to the UETR of the
underlying payment, e.g. pacs.008/
pacs.009
O OrgnlIntrBkSttlmAmt Original Interbank Settlement ISO Date Format It is recommended to populate the
Amount Original Information, if pacs.004 follows
the original payment route. to ensure
automated processing of the Return
message.
M OrgID Organisation Identification Text (1,35) Helps to Identify the Organisation that
had triggered the Return
M Cd Code Length (1,4) This element provides the Reason for the
Return
Open Page 9 of 9
Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.
Alternative Proxies: