Operational Procedures & Guidelines

Section 06 - Transfers and conversions between subregisters (Update)

Updated s6.10 (CHESS Housekeeping for Unmatched Transactions) to clarify the amount of days that CHESS automatically removes unactioned transfer or conversion requests from six business days, to three business days (day of receipt plus 2 business days).

SRN Enquiry Process

SRN Enquiry Housekeeping Process (Update)

Updated step 3 of the SRN Enquiry Housekeeping Process, from 6 days to 2 or more business days.

Transfers and Conversions Overview

Issuer Sponsored to Participant Transfer and Conversion Housekeeping Process (Update)

Updated step 3 of the Issuer Sponsored to Participant Transfer and Conversion Housekeeping Process, from 6 days to 2 or more business days.

Transfers and Conversions Overview

Transfers and Conversions Overview (Update)

Updated the Issuer to Participant Transfer section to note that Unactioned Issuer Sponsored to Participant Transfer Requests will be housekept by the CSP at the end of the 2nd business day after the request was submitted. Previously this was after 6 business days.

Collateral Management Overview - Removal for ETO and CMM

Collateral Removal by ASX Clear Process (Update)

Removed step 4 of the process table “Where the Controlling Participant is not the ETO Clearing Participant, the CSP will also send an Intra Position Movement Confirmation to the ETO Clearing Participant.“ This step is no longer applicable in the Collateral Removal - ASX Clear process flow, noting it is also not applicable in present day CHESS.

mFund

mFund Changes (Update)

1. Updated Order Rejection Reason Codes to include; ‘Order is a duplicate of a previously received order'.

2. Updated to include the ‘Annual and Periodic Income Statements’ line item to both the 'mFund Application Changes’ and ‘mFund Redemption Changes’ tables.

mFund Redemption - Accepted Redemption Orders & Unit Redemption

mFund Redemption - Optional Update (Payment Date / Settlement Amount) (Update)

Updated step 1 of the process table to include CSP as the recipient. This change is cosmetic as the process flow diagram illustrates this.

Bilateral Demand Transfer

Bilateral Demand Transfer Cancellation Process (Update)

Updated the Demand Transfer Allegement Notification Cancellation business values and rules table to remove Cancellation Reason. This value is not applicable.

Investor Data

Bank Account Update/Delete Process (Update)

1. Updated Transaction Acknowledgement Advice business values and rules table heading (visual/font-size change only).

2. Updated the Transaction Acknowledgement Advice business values and rules entry for Transaction Id to correct the reference from “Corporate Action Election Cancellation” → “Bank Account Notification”.

Transfers and Conversions

Issuer Sponsored to Participant Conversion Process (Update)

Updated the business values and rules tables for Conversion Request - Issuer Sponsored to Participant Conversion and Conversion Confirmation - Participant to clarify that Registration Reference must not/is not be populated.

Bilateral Settlement Instruction

Bilateral Settlement Instruction Housekeeping Process (Update)

Updated Step 4 of the Bilateral Settlement Instruction Housekeeping Process table to include the following note; “Where a Settlement Instruction has fully failed in batch settlement (and has never been previously partially settled), the unmatched Settlement Instruction Cancellation Request will not be housekept by the CSP.“

Settlement Instruction Cancellation

Market Settlement Instruction Housekeeping Process (Update)

Updated Step 1 of the Market Settlement Instruction Housekeeping Process table to include the following note;
”Where a Settlement Instruction has fully failed in batch settlement (and has never been previously partially settled), the unmatched Settlement Instruction Cancellation Request will not be housekept by the CSP. The full failure of a Novated Rescheduled Instruction includes where the instruction fully fails to deliver or receive units but an SSP Adjustment is settled.”

Demand Reporting Process

Holding Balance (HBAL) (Update)

Removed the info box regarding rejection based on the As At Date = (blank).

ISO 20022 Messaging

ISO 20022 Messaging - Message Catalogue (MC) (Update)

Updated: ISO 20022 Messaging - MC - Account Management message collection

Updated ISO 20022 Messaging - MC - Payment Facilities

• Updated the Payment Facility Details Report (acct_004) reference table to clarify and correct PISPs as recipients.

Updated: ISO 20022 Messaging - MC - Settlement message collection

Updated: ISO 20022 Messaging - MC - Batch Settlement Aggregate Funds Obligation and Funds Movement

Updated: ISO 20022 Messaging - MC - Payment Provider Authorisation for RTGS Payments

Updated: ISO 20022 Messaging - MC - Cancellation of Scheduled Batch Settlement

Updated: ISO 20022 Messaging - MC - Reporting

• Updated the Participant Funds Notification (sett_134), Funds Movement (sett_137), Cancelled Funds Obligation (sett_138) and Event Notification (sett_170) reference tables to clarify and correct PISPs as recipients.

Updated: ISO 20022 Messaging - MC - Investor Data

• Updated to include missing Transaction Acknowledgment Advice (comm_809); and

• Updated the Bank Account Update/Delete UML to include missing Transaction Acknowledgment Advice (comm_809). This information was previously covered by Bank Account Update/Delete Process.

Updated: ISO 20022 Messaging - MC - Class Merger

• Updated UML message flow diagram to correct the business message identifier for Holding Adjustment Notification (hold_226) from 00001|00200 → 00001|00500. Business message identifiers must be unique and the previous value incorrectly corresponded to the business message identifier of the Applied Code Change (admn_852) in the subsequent step.

Updated: ISO 20022 Messaging - MC - Takeovers and Buy-backs (Bid Offers) - Controlling Participant

• Updated the related functional specification link to correct the link to the following reference; Controlling Participant Bid Withdrawal Process. Previously this incorrectly linked to the Controlling Participant Bid Election Process.

ISO 20022 Messaging - Technical Manual (TM) (Update)

Updated: ISO 20022 Messaging - TM - EIS to ISO 20022 Cross Reference Guide

• Updated the EIS to ISO cross reference table to clarify and correct PISPs as recipients of the Payment Facility Details Report (acct_004), Participant Funds Notification (sett_134), Funds Movement (sett_137), Cancelled Funds Obligation (sett_138) and Event Notification (sett_170).

FIX Messaging

FIX Messaging - Message Catalogue (MC) (Update)

Updated: FIX Messaging - MC - Common Message Structure

• Updated FIX messaging pages to remove broken anchor link on ‘Req’ (required) table header. This hyperlink previously linked to the requirements key at the end of each FIX messaging page but instead resulted in a permissions error.

Updated: FIX Messaging - MC - Error Code List

• Updated the Type <3> (Session Level) Reject Validation and Type <J> (Session Level) Reject Validation tables to include missing business validation values.

Updated: FIX Messaging - MC - Business Message Reject (Type j)

• Updated to correct the following tag classifications Tag 372 (RefMsgType) and Tag 380 (BusinessRejectReason) from Optional (O) → Mandatory (M)

Failover and Recovery Guide

Section 02 - Connectivity Specific Failure and Recovery (Update)

Updated s2.3.3 Reconnection and Recovery to clarify the reference to NextExpectedMsgSeqNum (789) from ‘must’ (implying that it is mandatory) to ‘is recommended'. This corresponds to the tag 789 being optional per FIX Messaging - MC - Logon (Type A).

Connectivity Guide

Section 04 - Networking Details for ITEs (Update)

1. Removed placeholder for the Ledger API token acquisition guide, replacing it with a link to the Obtaining a Ledger API Token.

2. Updated s4.1.2 Ledger API Networking for ITE-M and s4.1.3 Ledger API Networking for ITE2 host name to include the node-1 and node-2 naming convention.

3. Updated s4.4.2 CHESS UI Networking for ITE-M and s4.4.3 CHESS UI Networking for ITE2 to include ITE-M and ITE2 CHESS User Interface (Authentication) details.

Customer Development Environment (CDE)

CDE Known Issues & Limitations (Update)

Updated to include the following defect:

• Unit Quantity is not populated correctly in the response to holding administration lock request.

Accreditation Guide

Section 05 - Messaging Accreditation Testing (Update)

Updated the Messaging Accreditation Timeline attachment.

Section 06 - Messaging Accreditation Scenarios (Update)

1. Updated page to include scenario file version control. Version 1.0 was baselined from the accreditation files released in January 2022 and all subsequent versions have been incremented and link out to the release notes corresponding to these changes.

2. Updated the following Scenario File: Clearing and Settlement & Settlement Participant (v1.0 → v1.1).

   • Scenarios: CS-AC-19, CS-AC-20

     • Change: Holder Update Reason value Notification of death (NODE) removed

     • Reason for change: Incorrect value

   • Scenarios: CS-DS-08

     • Change: Removed field Cancellation Reason

     • Reason for change: Functional Specification updated

   • Scenarios: CS-DS-16

     • Change:

       • Field Value Amended:

         • Payment = Against Payment Settlement (APMT)

       • New fields added

         • Trade Date;

         • Settlement Amount;

         • Settlement Currency; and

         • Credit Debit Indicator.

     • Reason for change: ASX acknowledge the market response that more participants will use Bilateral Settlement Instruction against Payment)

   • Scenarios: CS-RN-03

     • Change: ALL is removed from Account Identifier (HIN) value

     • Reason for change: Incorrect value without security code

   • Scenarios: CS-AC-12, CS-AC-21, CS-PF-01, CS-PF-02, CS-HT-06, CS-BD-01, CS-BS-12, CS-SI-01, CS-SI-02, CS-CA-11, CS-CA-13, CS-RN-09

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

3. Updated the following Scenario File: Settlement Participant (v1.0 → v1.1).

   • Scenario: SP-AC-19, SP-AC-20

     • Change: Holder Update Reason value Notification of death (NODE) removed

     • Reason for change: Incorrect value

   • Scenario: SP-RN-03

     • Change: ALL is removed from Account Identifier (HIN) value

     • Reason for change: Incorrect value without security code

   • Scenario: SP-DS-08

     • Change: Removed field Cancellation Reason

     • Reason for change: Functional Specification updated

   • Scenario: SP-DS-15

     • Change:

       • Field Value Amended:

         • Payment = Against Payment Settlement (APMT)

       • New fields added

         • Trade Date;

         • Settlement Amount;

         • Settlement Currency; and

         • Credit Debit Indicator.

     • Reason for change: ASX acknowledge the market response that more participants will use Bilateral Settlement Instruction against Payment)

   • Scenarios: SP-AC-12, SP-AC-21, SP-PF-01, SP-PF-02, SP-HT-06, SP-BD-01, SP-BS-08, SP-SI-01, SP-SI-02, SP-CA-11, SP-CA-13, SP-RN-08

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

4. Updated the following Scenario File: Account Participant (v1.0 → v1.1).

   • Scenario: AP-AC-17, AP-AC-18

     • Change: Holder Update Reason value Notification of death (NODE) removed

     • Reason for change: Incorrect value

   • Scenario: AP-DS-08

     • Change: Removed field Cancellation Reason

     • Reason for change: Functional Specification updated

   • Scenario: AP-RN-03

     • Change: ALL is removed from Account Identifier (HIN) value

     • Reason for change: Incorrect value without security code

   • Scenarios: AP-AC-11, AP-AC-19, AP-HT-06, AP-CA-11, AP-CA-13, AP-RN-06

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

5. Updated the following Scenario File: Issuer (Registry) (v1.0 → v1.1).

   • Scenario: IR-AC-01 to IR-AC-05

     • Change: Supplementary Information – Account Management Self Service Tool reference replaced with CHESS UI

     • Reason for change: Account Management Self Service Tool does not support Account Modification for Account and Holder details

   • Scenario: IR-RN-02

     • Change: ALL is removed from Account Identifier (HIN) value

     • Reason for change: Incorrect value without security code

   • Scenarios: IR-AC-09, IR-CA-02, IR-CA-03, IR-RN-12

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

6. Updated the following Scenario File: Payment Provider (v1.0 → v1.1).

   • Scenarios: PP-PF-01, PP-PF-02, PP-CR-01, PP-RN-01

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

7. Updated the following Scenario File: Offeror (v1.0 → v1.1).

   • Scenario: OF-RN-01

     • Change: Scenario amended to make in Offeror HIN specific

     • Reason for change: Holding Balance Report for offeror only related to Offeror HIN

   • Scenario: OF-RN-02

     • Change: Scenario removed

     • Reason for change: Holding Subposition Balance (HSBL) Report is not related to Offeror

   • Scenarios: OF-HT-02, OF-RN-03

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

8. Updated the following Scenario File: PISP (v1.0 → v1.1).

   • Scenarios: PS-PF-01

     • Change: Updated Supplementary Information for Assistance Required scenarios and linked them with ITE1 ASX Assisted Testing page

     • Reason for change: Usability enhancement

Section 07 - CHESS User by Feature, Message (Update)

1. Updated to clarify the following message is applicable to Issuer (Registries); Securities Message Cancellation Advice (hold_215).

2. Updated to clarify the following messages are applicable to PISPs; Participant Funds Notification (sett_134), Funds Movement (sett_137), Cancelled Funds Obligation (sett_138) and Event Notification (sett_170).

User Guide

Section 07 - Operational Schedule (Update)

Updated s7.3 ASX Assisted Transactions to include a reference to 5.2.4 ASX Assisted Testing (Guide to Testing Services).

Operational Readiness Guide

Section 04 - Supplementary Information (Update)

Updated: Operational Readiness Scenarios

• Updated to include the following operational readiness scenarios:

  • Corporate action events, including:

    • Corporate actions;

    • Takeovers and Buybacks;

    • Issuer code change and Issuer name change;

    • Diary adjustments; and

    • Corporate actions holding adjustments.

  • Dividend reinvestment plan and Bonus share plan; and

  • mFund (PISP/Issuer (Registry)), including:

    • Payment facilities;

    • Applications; and

    • Redemptions.

ITE Application Forms

ITE2 Application Forms (Update)

Updated to clarify the BIC party identifier usage.

CHESS Replacement Scope

CHESS User by Function (NEW)

Updated the CHESS User by Function table to include the following amendments:

• The addition of a mFunds table heading and subsequent movement of the PISP column to correspond to this new category.

• The addition of Distribution Status Advice and separation of mFunds Applications and Redemptions (initial applications, subsequent applications and redemptions).

• Minor corrections and clarifications on mandatory, optional and non-applicable values.

What's New 2022

28 February 2022 - ITE1 Reset (NEW)

NEW what’s new update incorporating changes to ITE1 supporting documentation supporting the February ITE1 scheduled maintenance reset including:

1. Updates to to ISO Message Signing to incorporate information provided in the January 19 Software Provider Readiness Working Group.

2. Updates and clarifications to the ITE1 Test Tool documentation.

3. Updates to the ITE1 Known Issues and Limitations page.

Frequently Asked Questions (FAQs)

FAQs - Software Provider Readiness

Updated to include 9 February 2022 – webinar questions and answers.