FAQs - Messaging

Table of Contents

How can I tell what version of message is being used in each release of functionality?

 Answer

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?

 Answer

The ASX provides the following technical documentation to support the adoption of ISO 20022.

DocumentDescriptionFormatLocation
ISO 20022 Messaging Technical Manual
  • Describes the structure and conventions of an ISO 20022 message.
  • Covers Business Message Collections, Business Message attributes, the Business Application Header (BAH), elements, naming conventions, formats and tags.
  • Includes message samples.
OnlineASX website
ISO 20022
Message Catalogue
  • Explains how to create financial messages to communicate with the ASX using the ISO 20022 standard.
  • Includes message scope, message purpose, message flows (UML diagrams), Sender and Receiver details and any message pre-requisites.
  • Links to detailed ASX Usage Guidelines (UG) on MyStandards.
OnlineASX 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.

OnlineSWIFT 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.

 

OnlineSWIFT 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.

OnlineASX website
ISO 20022 websiteInformation about ISO 20022, business domains, catalogue of messages, external code sets and newsOnlineISO 20022 website
MyStandards Guide

Guide on SWIFT and MyStandards.

  • Register as a user on SWIFT
  • Log onto MyStandards
  • Request access to the ASX group
  • View groups and communities
  • View ASX Usage Guidelines (UG)
OnlineASX 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.

OnlineSWIFT website / MyStandards
XML Schema
  • An XML document that defines the structure of an ISO 20022 message.
  • Each XML Schema references ASX Usage Guidelines (UG).
XMLSWIFT website / MyStandards
CHESS Cross Reference Guide
  • A list of ISO 20022 messages that will replace CHESS messages (from – to)
  • Includes de-scoped and new messages.

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.

  • Provides a simple way to update code sets without any impact to existing messages.
  • Unlike other ISO 20022 code sets, codes are not included in the message schema.
  • Code validation occurs in the DLT application.

Online

ASX website

ASX Error Code ListA 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?

 Answer

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?

 Answer

The Spider diagrams have been replaced with UML diagrams.

How do I read the new ASX message flow diagrams (UML diagrams)?

 Answer

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?

 Answer

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?

 Answer

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?

 Answer

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?

 Answer

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?

 Answer

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?

 Answer

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? 

 Answer

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?

 Answer

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?

 Answer

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.. 

  1. <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"…>
  2. 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?

 Answer

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?

 Answer

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?

 Answer

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?

 Answer
ISO20222 MessageMessage Order Status / Reason CodesUse CaseEIS MessageTransaction Status BP 22
mfnd_401n/a
  • mFund Application Order Request
EIS 726/727n/a
acct_012n/a
  • Investor Details and Foreign Tax Status
EIS 735/736/737/738n/a
mfnd_407n/a
  • mFund Redemption Order Request
EIS 800/801n/a
mfnd_402‘RECE’ – Received
  • Initial mFund Application Order Request is accepted and received by the CSP and waiting for Investor Details and Foreign Tax Status
EIS 720n/a
mfnd_402‘STNP’ – Sent to Next Party
  • Subsequent mFund Application Order Request is accepted and received by the CSP. The mFund Application Order Request is sent to the PISP
  • Investor Details and Foreign Tax Status relating to an Initial mFund Application Order Request is accepted and received by the CSP. The mFund Application Order Request and Investor Details are sent to the PISP.
  • mFund Redemption Order Request is accepted and received by the CSP. The mFund Redemption Order Request is sent to the PISP.
EIS 720n/a
comm_809n/a
  • Acknowledgement Response to PISP
EIS 722n/a
comm_808n/a
  • Rejected Transaction (NACK) to PISP
EIS 518n/a

mfnd_402

Cancellation Order Reason – ‘HOUS’ – ASX Initiated Housekeeping

  • mFund Application Order is cancelled because Investor Details and Foreign Tax Status relating to an Initial mFund Application Order Request has not been received by the CSP within 5 business days.
  • New - mFund Application Order or mFund Redemption Order is cancelled because the PISP has not provided an acceptance or rejection response within 31 calendar days of being sent the order.

EIS 740

n/a

mfnd_402

Rejection Order Reason – as per ASX proprietary code list 'RejectionOrderReason_ASX_1'

  • mFund Application Order is Rejected by the PISP
  • mFund Redemption Order is Rejected by the PISP

Applications

  • EIS 729/730

Redemptions

  • EIS 802/803

‘R’ = Rejected

mfnd_402

‘PACK’ – Accepted

  • mFund Application Order is Accepted by the PISP
  • mFund Redemption Order is Accepted by the PISP

Applications

  • EIS 729/730

Redemptions

  • EIS 802/803

‘A’ = Accepted

mfnd_406

Confirmation Reason ‘MAPP’ - Application Order Issue

  • Provides full application order completion details and performs unit allotment

Order Details

  • EIS 729/730

Unit Adjustment

  • EIS 732/733

‘A’ = Accepted

mfnd_409

Confirmation Reason ‘MRED’ - Order Unit Redemption

  • Provides full redemption order completion details and performs unit redemption

Order Details

  • EIS 802/803

Unit Adjustment

  • EIS 732/733

‘A’ = Accepted

mfnd_402

‘PACK’ – Accepted


  • mFund Application Order Unit Pricing Date or Unit Allotment Date is updated by the PISP
  • mFund Redemption Order Unit Pricing Date or Expected Settlement Date is updated by the PISP (before units are redeemed)

EIS 810/811

‘U’ = Update Payment or Unit Allotment Date

Applications

  • EIS 729/730

Redemptions

  • EIS 802/803
‘A’ = Accepted

mfnd_402

Update Order Reason - ‘UPDT’ – Accepted

  • mFund Redemption Order Scheduled Settlement Date or Settlement Amount (New) is updated by the PISP (after units are redeemed)

EIS 810/811


‘U’ = Update Payment or Unit Allotment Date

mfnd_402

Cancellation Order Reason – as per ASX proprietary code list 'CancellationOrderReason_ASX_1'

  • PISP Cancels mFund Application Order
  • PISP Cancels mFund Redemption Order

EIS 810/811


‘C’ = Cancel Order

mfnd_404

Cancellation Reason – ‘CANI’ Participant Request

  • New – Requesting Participant cancellation of mFund Application Order

n/a

n/a

mfnd_405

Cancellation Status – ‘CAND’ Cancellation Completed

  • Confirmation to Requesting Participant that requested cancellation of mFund Application Order has been completed
  • Confirmation to Requesting Participant that requested cancellation of mFund Redemption Order has been completed

EIS 720/811


‘C’ = Cancel Order

mfnd_408

Cancellation Reason – ‘CANI’ Participant Request

  • Requesting Participant cancellation of mFund Redemption Order (change – PISP authorisation descoped)

EIS 804

n/a

mfnd_402

Cancellation Order Reason – ‘CANI’ Participant Request

  • Notification to PISP that mFund Application Order has been cancelled by the Requesting Participant
  • Notification to PISP that mFund Redemption Order has been cancelled by the Requesting Participant (change – PISP authorisation descoped)

EIS 805

n/a

mfnd_402

Payment Status – ‘SCHD’ Payment Scheduled

  • Notification of Scheduled Payment Instruction

EIS 731

n/a

mfnd_402

Payment Status – ‘PAID’ Payment Completed

  • Confirmation of Payment Completed

EIS 156

n/a

mfnd_402

Payment Status – ‘PAID’ Payment Completed

(message includes Total Reminder Count)

  • Reminder notice to advise units have not been issue by the notified unit allotment date

EIS 812

n/a

mfnd_402

Update Order Reason – ‘UPSI’ Updated Scheduled Payment Instruction

  • Payment Date or Settlement Amount Updated by PISP

EIS 824

n/a

mfnd_402

Update Order Reason

  • ‘RPSS’ Rescheduled Payment Security Suspended
  • ‘RPSC’ Rescheduled Payment Security Closed
  • ‘RPAO’ Rescheduled by ASX Operations
  • ‘RPFR’ Rescheduled Payment Funds Rejection
  • ‘CANC’ Rescheduled Scheduled Batch Settlement Cancelled
  • Payment Rescheduled (e.g. within batch settlement or by ASX Ops)

EIS 731

n/a

mfnd_402

Cancellation Order Reason – ‘CSPI’ – Cancellation of Scheduled Payment Instruction

  • Notification of Cancellation of Scheduled Payment Instruction

EIS 822

n/a

hold_226

Reason – as per ASX proprietary code list 'HoldingAdjustmentReason_ASX_1'

  • Unit Adjustment (outside of the order workflow e.g. Misc, DRP, RPP etc)

EIS 732/733

n/a

evnt_744

n/a

  • Distribution re-investment plan advice

EIS 817/818

n/a

mfnd_406

mfnd_409

(Issuer)

Confirmation Reason (other than ‘MAPP’ & ‘MRED’)

  • Regular Payment Plan Advice
  • Regular Withdrawal Plan Advice
  • Order Reapply Advice
  • Order Reversal Advice
  • Advice to accompany a Unit Adjustment
  • Correction to confirmation sent within order workflow

EIS 729/730 (RPP)

EIS 845/846


EIS 729/730 for RPP

  • ‘A’ = Accepted

EIS 845/846

  • ‘P’ = Reapply the corrected Unit Adjustment
  • ‘V’ = Reverse the original Unit Adjustment




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