FAQs - Messaging
Table of Contents
How can I tell what version of message is being used in each release of functionality?
We have published details of how message schema versions are being managed and can be identified in the MyStandards Usage Guidelines.
Link to Technical Documentation messaging page on version control.
Where do I find documentation on ISO 20022?
The ASX provides the following technical documentation to support the adoption of ISO 20022.
Document | Description | Format | Location |
---|---|---|---|
ISO 20022 Messaging Technical Manual |
| Online | ASX website |
ISO 20022 Message Catalogue |
| Online | ASX website |
ISO 20022 for Dummies | This book removes the mystery from ISO 20022, helps you understand why it matters, and lets you see how you can benefit from it. Request an electronic copy of the ISO 20022 for Dummies book from the SWIFT website. Enter your contact details and "ASX CHESS Replacement on ISO 20022" as the Initiative you are interested in (last field). Note: You will need Adobe Flash Player 10 or newer in order to view this publication. | Online | SWIFT website |
ISO 20022 Harmonisation | Details on the SWIFT-led industry program to ensure a cost effective and seamless adoption of ISO 20022 by Market Infrastructures and their communities. The ASX has endorsed the ISO 20022 harmonisation principles.
| Online | SWIFT website |
Information Paper: ISO 20022 Implementation Strategies | Published in July 2017, this information paper includes a case study on the Australian Securities Exchange (ASX) CHESS Replacement project. | Online | ASX website |
ISO 20022 website | Information about ISO 20022, business domains, catalogue of messages, external code sets and news | Online | ISO 20022 website |
MyStandards Guide | Guide on SWIFT and MyStandards.
| Online | ASX website |
ASX Usage Guidelines on MyStandards | An Excel document that presents the logical layout of the XML Schema. The document shows the elements that will be used in the message; elements that will not be used are marked as “excluded (x)” The document also contains ASX market practice usage for each element e.g. ASX definitions, annotations, rules, new data requirement, data type, restrictions, as well as ASX synonyms that are the ASX names well as ASX synonyms that are the ASX names of the element. | Online | SWIFT website / MyStandards |
XML Schema |
| XML | SWIFT website / MyStandards |
CHESS Cross Reference Guide |
| Online | ASX website |
ASX Proprietary Code List | The ASX has published an ASX Proprietary Code List for reference and use alongside the ISO 20022 usage guidelines.
| Online | ASX website |
ASX Error Code List | A list of common error codes sent back to the Sender when a message fails Technical and/or Business validation. | Online | ASX website |
Where are the CHESS (EIS) message numbers?
The ASX has adopted the ISO 20022 messaging standard and will not support CHESS (EIS) proprietary format messaging.
/wiki/spaces/WD/pages/15205893EIS to ISO 20022 Cross Reference Guide is a list of CHESS message numbers (EIS) and their corresponding ISO 20022 base message numbers.
Where are the Spider diagrams?
The Spider diagrams have been replaced with UML diagrams.
How do I read the new ASX message flow diagrams (UML diagrams)?
UML diagrams have replaced the Spider diagrams. The following diagram describes how to read the new ASX message flow diagrams (UML diagrams).
ASX UML message flow diagrams show acceptance paths only. Rejection and Invalid message flows are described in a separate message flow diagram.
Where can I find ASX Usage Guidelines?
ASX Usage Guidelines are now hosted on SWIFT's MyStandards platform. For more information, please refer to the MyStandards section of this site.
How will ISO 20022 schemas be distributed and will the ASX provide them in a machine readable format? Will full message examples be available?
ASX is using MyStandards, a tool that allows users to export three types of artefacts; the schema, usage guideline as well as the hierarchy, multiplicity and patterns for data types. A machine readable .xsd will be generated out of the MyStandards tool.
Will the ASX provide document mapping of existing CHESS messages to the XML messages? Is it possible to indicate where the processes differ?
Yes, in terms of the ISO 20022 deliverables, the ASX are providing a mapping between the EIS message definitions and the ISO 20022 equivalents. Note however that they are not backward compatible nor are they logically equivalent. Users will not find every EIS field mapped to an ISO message and vice versa. It is important to understand the business processes and take a top-down approach rather than a bottom-up one.
How do I know which ISO 20022 schema to use for a particular Business Message?
The schemas to use for a particular message can be derived from contents of the BizSvc and MsgDefIdr fields from the BAH. Note that It is not possible to rely on the ISO 20022 namespace as a way to identify the correct schema to use. This is because the ISO 20022 standard requires that the base message namespace be used rather than a usage guideline specific namespace. For convenience, the schemaLocation attribute is populated for all outbound messages.
Will payload, references and identifiers be harmonised with payment related instructions, in particular NPP?
Unfortunately harmonisation between securities and payments has not happened within the ISO 20022 standard. For instance, there is no concept of an end-to-end identifier in the securities domain. As part of the Technical Committee (TC), the ASX has recommended an E2E like ID and detailed transaction ID usages. The securities domain does however have the concept of a MITI, a market infrastructure transaction ID and the ASX will be using that in some cases, but there is no formal convergence in the ISO standard between payments and securities yet.
Is it possible to get the new schemas ahead of time? When will all schemas be available to the market?
Releases will be in tranches but tranch timelines are not available. The end of 2019/early 2020 for IWT can be thought of as a rough guideline for the availability of all schemas.
Is there any structural difference between an ISO 20022 xml business message transported using AMQP and SWIFTNet?
Yes. For SWIFTNet, the xml message is located within an InterAct Header <Payload> element. For AMQP, the xml message is located within ASX's Business Message Wrapper (comm.802) <BizMsg> element.
Where can I find samples of the ASX xml messages, and how can I test any messages I create ‘offline’ before connecting to CDE?
Sample xml messages for each ASX Usage Guideline are provided in a .zip file attached to each collection in MyStandards.
Each sample contains the business message of Business Application Header and ISO Document.
A Business Message Wrapper <BizMsg> tag is included which is used with AMQP but not SWIFTNet.
The message can be validated ‘offline’ by parsing the xml assigning against the xml schema (.xsd).
- In an xml editor, this might be done by assigning the .xsd to the .xml and using the validate function.
- It will be necessary to have all of the referenced ASX schemas available for export form the MyStandards collection.
- ASX has also provided the MyStandards Readiness Portal as a tool that validates xml against the selected Usage Guideline
How are the Business Application Header (BAH) and ISO Document tag values related?
The Business Service <BizSvc> and Message Definition Identifier <MsgDefIdr> determine certain Document tag values. These relationships are shown in the sample xml messages attached to the MyStandards collections..
- <Document> namespace (xmlns) includes the value of the Message Definition Identifier <MsgDefIdr> and represents the ISO 20022 base message Id.
e.g. for <MsgDefIdr> sese.023.001.07</MsgDefIdr> then <Document xmlns="urn:iso:std:iso:20022:tech:xsd:sese.023.001.07"…> - The .xsd schema filename is derived from the Business Service <BizSvc>, <MsgDefIdr>
e.g. for <BizSvc>hold_201_001_03_!p</BizMsg> and <MsgDefIdr> sese.023.001.07</MsgDefIdr> plus the ASX Collection name of “ASX_AU_CHS_hold” then
<Document … xsi:schemaLocation="… ASX_AU_CHS_hold_201_001_03_sese_023_001_07.xsd">
Also the Business Service <BizSvc> contains an optional environment variable that distinguishes between Production (Live), and Test (CDE, IWT, other) business messages.
e.g. <BizSvc>hold_201_001_03_!p</BizMsg> for Pilot (CDE Test) and <BizSvc>hold_201_001_03</BizMsg> for Production (Live)
Is there a bulk download message functionality in the SWIFT MyStandards portal?
The SWIFT MyStandards portal does provide a bulk export of Usage Guidelines or Schema Files.
Usage Guidelines can be selected (multiple) from a collection or collections and by navigating to and clicking on the folder icon (right) the selection is then exported as a single zip file.
Details about MyStandards have been provided in our Technical Documentation and will be updated with further details in the Technical Documentation release scheduled for end of July 2019.
Why are ISO message Supplementary Data child elements displayed at the same level as ‘Supplementary Data’ in message usage guidelines?
Some CSP ISO message have supplementary data. The supplementary data elements definitions are presented in the usage guidelines supplied by ASX (both as an excel usage guideline and on the MyStandards Portal).
It has been observed that the ‘Supplementary Data’ child elements are represented at the same level as the ‘Supplementary Data‘ <SplmtryData> element within the usage guideline and that this is not aligned with the XML sample generated using the XSDs (ISO Base message and the Supplementary Data Schema).
Usage guidelines published by ASX are auto generated by SWIFT MyStandards platform. Participants are advised to refer to the sample XMLs attached with each collection for the correct hierarchy of the elements.
Refer to the below example:
ISO base messages have supplementary data element defined at level 1 (i.e. child element of a level 0 element) and the ASX defined supplementary data schema is inserted as a child element of supplementary data.
However, when this is represented on the Usage Guideline (auto generated by SWIFT tool) or on SWIFT my standards portal they are both shown at level 1.
When an xml message is generated for such messages they appear as a child elements of supplementary data.
What is the difference between the Transaction Id in the Business Application Headers (BAH) and the Transaction Id in ISO Messages?
The Transaction Id within the BAH of an ISO message is a Message Id (Identified by the tag <BizMsgIdr>). Each ingress/egress message exchanged with the CSP will have a unique Message Id.
ISO message also have a Transaction Id within the body of the message. This is contained within different xml tags depending upon the ISO base message used (e.g. TransactionIdentification, AccountOwnerTransactionIdentification, etc.). This Transaction Id identifies a transaction and could be same for multiple messages involved within that transaction. For example, an Account Creation Request (acct_001) request message and Account Notification (acct_002) response message will have the same Transaction Ids, but different Message Ids.
Further details on the ISO 20022 message structure, the BAH, and Transaction Ids are available in the ISO 20022 Messaging - Technical Manual (TM).
Where can I find a mapping of mFund Order Status from CHESS and CHESS Replacement?
ISO20222 Message | Message Order Status / Reason Codes | Use Case | EIS Message | Transaction Status BP 22 |
---|---|---|---|---|
mfnd_401 | n/a |
| EIS 726/727 | n/a |
acct_012 | n/a |
| EIS 735/736/737/738 | n/a |
mfnd_407 | n/a |
| EIS 800/801 | n/a |
mfnd_402 | ‘RECE’ – Received |
| EIS 720 | n/a |
mfnd_402 | ‘STNP’ – Sent to Next Party |
| EIS 720 | n/a |
comm_809 | n/a |
| EIS 722 | n/a |
comm_808 | n/a |
| EIS 518 | n/a |
mfnd_402 | Cancellation Order Reason – ‘HOUS’ – ASX Initiated Housekeeping |
| EIS 740 | n/a |
mfnd_402 | Rejection Order Reason – as per ASX proprietary code list 'RejectionOrderReason_ASX_1' |
| Applications
Redemptions
| ‘R’ = Rejected |
mfnd_402 | ‘PACK’ – Accepted |
| Applications
Redemptions
| ‘A’ = Accepted |
mfnd_406 | Confirmation Reason ‘MAPP’ - Application Order Issue |
| Order Details
Unit Adjustment
| ‘A’ = Accepted |
mfnd_409 | Confirmation Reason ‘MRED’ - Order Unit Redemption |
| Order Details
Unit Adjustment
| ‘A’ = Accepted |
mfnd_402 | ‘PACK’ – Accepted |
| EIS 810/811 | ‘U’ = Update Payment or Unit Allotment Date |
Applications
Redemptions
| ‘A’ = Accepted | |||
mfnd_402 | Update Order Reason - ‘UPDT’ – Accepted |
| EIS 810/811 | ‘U’ = Update Payment or Unit Allotment Date |
mfnd_402 | Cancellation Order Reason – as per ASX proprietary code list 'CancellationOrderReason_ASX_1' |
| EIS 810/811 | ‘C’ = Cancel Order |
mfnd_404 | Cancellation Reason – ‘CANI’ Participant Request |
| n/a | n/a |
mfnd_405 | Cancellation Status – ‘CAND’ Cancellation Completed |
| EIS 720/811 | ‘C’ = Cancel Order |
mfnd_408 | Cancellation Reason – ‘CANI’ Participant Request |
| EIS 804 | n/a |
mfnd_402 | Cancellation Order Reason – ‘CANI’ Participant Request |
| EIS 805 | n/a |
mfnd_402 | Payment Status – ‘SCHD’ Payment Scheduled |
| EIS 731 | n/a |
mfnd_402 | Payment Status – ‘PAID’ Payment Completed |
| EIS 156 | n/a |
mfnd_402 | Payment Status – ‘PAID’ Payment Completed (message includes Total Reminder Count) |
| EIS 812 | n/a |
mfnd_402 | Update Order Reason – ‘UPSI’ Updated Scheduled Payment Instruction |
| EIS 824 | n/a |
mfnd_402 | Update Order Reason
|
| EIS 731 | n/a |
mfnd_402 | Cancellation Order Reason – ‘CSPI’ – Cancellation of Scheduled Payment Instruction |
| EIS 822 | n/a |
hold_226 | Reason – as per ASX proprietary code list 'HoldingAdjustmentReason_ASX_1' |
| EIS 732/733 | n/a |
evnt_744 | n/a |
| EIS 817/818 | n/a |
mfnd_406 mfnd_409 (Issuer) | Confirmation Reason (other than ‘MAPP’ & ‘MRED’) |
| EIS 729/730 (RPP) EIS 845/846 | EIS 729/730 for RPP
EIS 845/846
|
Related Pages:
There are no related labels.
Browse Popular Pages:
No labels match these criteria.
This document provides general information only. ASX Limited (ABN 98 008 624 691) and its related bodies corporate (“ASX”) makes no representation or warranty with respect to the accuracy, reliability or completeness of the information. To the extent permitted by law, ASX and its employees, officers and contractors shall not be liable for any loss or damage arising in any way (including by way of negligence) from or in connection with any information provided or omitted or from anyone acting or refraining to act in reliance on this information.
© 2022 ASX Limited ABN 98 008 624 691