0554.15.05.a - attachment a chess release 9.0 … · date will be communicated by asx in the second...

CHESS Release 9.0

Business and Technical Overview

CHESS Release 9 Business & Technical Overview

© Copyright 2015 ASX Limited ABN 98 008 624 691. All rights reserved 2015 of 90

Table of Contents 1. ACRONYM GLOSSARY .................................................................................................................................. 4 2. OVERVIEW ...................................................................................................................................................... 5

2.1. CHESS RELEASE 9.0 INCLUSIONS ............................................................................................................ 5 3. SCOPE OF RELEASE ..................................................................................................................................... 6

3.1. TESTING ................................................................................................................................................... 8 3.2. IMPLEMENTATION DATE ............................................................................................................................. 8 3.3. PARTIES IMPACTED BY THIS CHANGE.......................................................................................................... 8 3.4. NEXT STEPS ............................................................................................................................................. 8 3.5. CONTACTING ASX – CHESS RELEASE 9.0 ................................................................................................ 8

4. OVERVIEW OF CHESS ENHANCEMENTS ................................................................................................... 9 4.1. MAINTENANCE OF POSSIBLE FATCA/CRS REPORTABLE ACCOUNTS ............................................................ 9 4.2. MFUND TRANSACTION SUITE ................................................................................................................... 12 4.3. SOPHISTICATED INVESTOR ...................................................................................................................... 13 4.4. CHESS TO CHESS MFUND TRANSFER – SAME PARTICIPANT .................................................................. 15 4.5. CHESS TO CHESS MFUND TRANSFER – DIFFERENT PARTICIPANT .......................................................... 16 4.6. MFUND ISSUER SPONSORED TO CHESS TRANSFER ................................................................................. 17 4.7. MFUND CHESS TO ISSUER SPONSORED TRANSFER ................................................................................. 18 4.8. CHANGED RECIPIENT FOR MFUND CHESS MESSAGE MT716, MT719....................................................... 19 4.9. DRP / RPP ELECTION............................................................................................................................. 20 4.10. PERIODIC INCOME STATEMENT ................................................................................................................ 21

5. TECHNICAL DETAILS FOR PARTICIPANTS .............................................................................................. 22 5.1. CHESS MESSAGE IMPACT ...................................................................................................................... 22

5.1.1. New CHESS Messages ............................................................................................................... 22 5.1.2. Modified CHESS Messages ......................................................................................................... 22

5.2. INVESTOR IMPACT ................................................................................................................................... 24 5.3. HOLDER MAINTENANCE ENHANCEMENTS.................................................................................................. 25

5.3.1. Holder Registration Enhancements ............................................................................................. 25 5.3.1.1. New Registration Details [201-05] ................................................................................................................. 26 5.3.1.2. Holding Registration Details [512-05] ............................................................................................................ 28

5.3.2. Update Holder Registration Enhancements ................................................................................. 30 5.3.2.1. Registration Details Update Request [203-05] .............................................................................................. 31

5.3.3. Holder Reporting Enhancements ................................................................................................. 33 5.3.3.1. Holder Detail [222-05] .................................................................................................................................... 33 5.3.3.2. Holder History [224-04] .................................................................................................................................. 35

5.3.4. mFund Enhancements ................................................................................................................. 37 5.3.4.1. Issuer Sponsored Fund to CHESS Conversion Request [718-02] ................................................................ 37 5.3.4.2. Application Request [726-02] ......................................................................................................................... 38 5.3.4.3. Application Order Request [727-02] .............................................................................................................. 40 5.3.4.4. Redemption Request [800-02] ....................................................................................................................... 42 5.3.4.5. Redemption Order Request [801-02] ............................................................................................................. 44 5.3.4.6. Switch Request [806-02] ................................................................................................................................ 46 5.3.4.7. Switch Order Request [807-02]...................................................................................................................... 48

5.4. MFUND HIN TO HIN TRANSFER (CONTROLLED BY THE SAME PARTICIPANT) ................................................ 50 5.4.1. Single Entry CHESS to CHESS Fund Transfer Request [851-01] ............................................... 51 5.4.2. Effected Fund Transfer [852–01] ................................................................................................. 52 5.4.1. CHESS Fund Transfer Notification [862-01] ................................................................................ 53

5.5. MFUND HIN TO HIN TRANSFER (CONTROLLED BY DIFFERENT PARTICIPANTS) ............................................. 54 5.5.1. Dual Entry CHESS to CHESS Fund Transfer Request [853-01] ................................................. 55 5.5.2. Unmatched Dual Entry CHESS to CHESS Fund Transfer [854-01] ............................................ 56 5.5.3. Rejected Demand Dual Entry CHESS to CHESS Transfer [024-01] ........................................... 57 5.5.4. Unmatched Dual Entry Request [194-01] .................................................................................... 58 5.5.5. Demand Dual Entry CHESS to CHESS Transfer Cancellation Request [037-01] ....................... 58 5.5.6. Cancelled Demand Dual Entry Transfer Request [048-01] .......................................................... 59

5.6. MFUND ISSUER SPONSORED FUND TO CHESS TRANSFER ........................................................................ 60 5.6.1. Issuer Sponsored Fund to CHESS Transfer Request [855-01] ................................................... 61



5.6.2. Issuer Sponsored Fund to CHESS Transfer Authorisation Request [856-01] ............................. 62 5.6.3. Registry Fund Transfer Authorisation [857-01] ............................................................................ 63 5.6.4. Registry Fund Transfer Rejection [859-01] .................................................................................. 63 5.6.5. Rejected Registry Authorisation [860-01]..................................................................................... 64 5.6.6. Fund Response [722-01].............................................................................................................. 65 5.6.7. Accepted Participant Request [720-01]........................................................................................ 66

5.7. MFUND CHESS TO ISSUER SPONSORED FUND TRANSFER ........................................................................ 67 5.7.1. CHESS to Issuer Sponsored Fund Transfer Request [861-01] ................................................... 68 5.7.2. CHESS to Issuer Sponsored Fund Transfer Authorisation Request [858-01] ............................. 70

5.8. CHANGED RECIPIENT FOR CHESS MESSAGE MT716 / MT719 ................................................................. 72 5.8.1. CHESS Conversion Request to Issuer Sponsored Fund [716-01]............................................... 72 5.8.2. Issuer Sponsored Fund to CHESS Conversion Authorisation Request [719-02] ......................... 73

5.9. DRP / RPP ELECTION............................................................................................................................. 74 5.9.1. DRP RPP Election Request [863-01] ........................................................................................... 75 5.9.2. DRP RPP Election Authorisation Request [864-01] ..................................................................... 76 5.9.3. DRP RPP Registry Authorisation [865-01] ................................................................................... 77 5.9.4. Accepted DRP RPP Election Request [866-01] ........................................................................... 77 5.9.5. DRP RPP Registry Rejection [867-01] ......................................................................................... 78 5.9.6. Effected Registry Transaction [762-01] ........................................................................................ 78

5.10. INCOME STATEMENT ............................................................................................................................... 79 5.10.1. Income Statement Request [869-01] ........................................................................................... 80 5.10.2. Income Statement Authorisation Request [868-01] ..................................................................... 81 5.10.3. Income Statement Authorisation [881-01] .................................................................................... 82 5.10.4. Accepted Income Statement Request [884-01] ........................................................................... 82 5.10.5. Income Statement Rejection [907-01] .......................................................................................... 83 5.10.6. Income Statement [813-01] .......................................................................................................... 84 5.10.7. Income Statement Advice [816-01] .............................................................................................. 85

6. APPENDICES ................................................................................................................................................ 86 6.1. APPENDIX 1: FOREIGN TAX STATUS DETERMINATION ................................................................................ 86 6.2. APPENDIX 2: CHESS FIELD DEFINITIONS ................................................................................................. 87



1. Acronym Glossary

Acronym Definition

AIC Access Identification Code (CHESS)

AML Anti-money Laundering

APG ASX Settlement Procedure Guidelines

AREIT Australian Real Estate Investment Trust

ATO Australian Tax Office

CHESS Clearing House Electronic Sub-Register System

DRP Dividend Reinvestment Plan

EIS CHESS External Interface Specification

EOD End of Day

ETF Exchange Traded Fund

ETP Exchange Traded Product

FATCA Foreign Account Tax Compliance Act

HIN Holder Indentication Number

ISV Independent Service Vendor

LIC Listed Investment Company & Trust

PDS Product Disclosure Statement

PID Participant Identifier

PISP Product Issuer Settlement Participant

RITS Reserve Bank Information & Transfer System

RPP Regular Purchase Plan

SDS Standard Statement

SRN Security Holder Reference Number

TFN Tax file Number (AUS)

TIN Taxpayer Identification Number (US)

UIC User Identification Code (interchangeable with PID)



2. Overview This Business and Technical Overview sets out draft specifications for CHESS Release 9.0 which includes the enhancements in section 2.1 below.

The enhancements that relate to FATCA/CRS remain subject to industry consultation and satisfactory resolution of outstanding issues arising from recent changes in regulatory guidance. As a result, they are in draft form and ASX reserves the right to withdraw or vary CHESS Release 9.0. Following further industry consultation, ASX will use its best endeavours to confirm its position on CHESS Release 9.0 by the end of June. Subject to satisfactory resolution, CHESS release 9.0 will be implemented in November, 2015 for issuers of FATCA reportable products to be able to meet their reporting obligations from 1 January, 2016. The precise date will be communicated by ASX in the second quarter of 2015.

2.1. CHESS Release 9.0 Inclusions Includes the introduction of changes to some of the Clearing House Electronic Sub-System (CHESS) messaging process flows and new messages, together with changes to the relevant ASX Settlement Pty Ltd (ASX Settlement) Operating Rules.

The changes can be broadly categorised as a regulatory driven change relating to FATCA and the introduction of a number of mFund related enhancements following the introduction of the service in May, 2014:

Additional data fields will be included in the Holder (HIN) and update messages (MT201/MT203) to incorporate responses to the FATCA/CRS Questions which will be maintained on the HIN.

Additional data will be included in the Holder (HIN) record and update messages (MT201/MT203) to allow the capture of data for: o Foreign Tax Status (FATCA and CRS) o Sophisticated Investor identification

A change to the mFund transaction message suite to synchronise the capture of the FATCA/CRS data from the HIN.

The introduction of a mFund transfer messages to enable: o transfers between HINs controlled by the same Participant o transfers between HINs controlled by different Participants o transfers between the CHESS sub-register and an Issuer Sponsored register o transfers between an Issuer Sponsored register and the CHESS sub-register

A change to the existing mFund Distribution Statement functionality to allow an mFund Participant to request a periodic Income Statement on behalf of their client. Currently the Registry initiates this process.

The introduction of a mFund message suite to facilitate the amendment of a distribution preference or a regular payment plan to a Registry.

A changed recipient (Registry) for the mFund 716 CHESS Conversion Request to Issuer Sponsored Fund. Currently the Product Issuer Settlement Participant (PISP). The Registry is only notified where ASX Settlement Operations initiate the conversion. The appropriate Registry will now be notified in all instances. The PISP will no longer be notified.

Refer 5. Technical Details for Participants for detailed specifications. Refer Appendix 3: Field Definitions for new and modified CHESS field definitions.



3. Scope of Release The scope of CHESS enhancements are:

Enhancement Benefits Impact

1 Inclusion of additional data fields within the Holder (HIN) Record and update messages (MT201/MT203) to incorporate responses to the FATCA/CRS Questions which will be maintained on the HIN. Sponsoring Participants will be required to obtain responses to a series of FATCA/CRS Questions in relation to the US citizenship and foreign tax residency status for the creation of a HIN record. This information is then sent to registries through an expanded Holder Registration Details CHESS message (MT512)

Benefits will flow to issuers of FATCA reportable products who will have a regulatory reporting obligation from 1/1/2016. By soliciting responses to the FATCA/CRS Questions from CHESS holders, Sponsoring Participants will reduce the number of holders that are required to be followed up by issuers to determine whether they are reportable to the ATO (acting as an agent for the US tax authority). This process will also provide a better experience for sponsored holders through a single point of notification for responses to the FATCA/CRS Questions to capture their reportable status.

Mandatory for: ASX Clearing & Settlement Participants (as sponsor), Registries

2 Sponsoring Participant can optionally nominate whether a client has been established as a ‘Sophisticated Investor’ on the HIN through the HIN set-up/update CHESS messages (MT201/203). This information is then sent to registries through an expanded Holder Registration Details CHESS message (MT512)

This allows the participant to offer potential mFund products that may be admitted in the future and only available to sophisticated investors.

Mandatory message change, optional to use it for: ASX Clearing & Settlement Participants (as sponsor), Registries.

3 A change to the mFund transaction message suite to synchronise the capture of the FATCA/CRS data from the HIN.

Synchronises the capture of the FATCA/CRS data from the HIN rather than at transaction level.

Mandatory for: mFund ASX Clearing & Settlement Participants, mFund PISPs, mFund Registries.

4 The introduction of CHESS messages for mFund unit transfers: i. CHESS to CHESS within the same Sponsoring Participant ii. CHESS to CHESS across two Sponsoring Participants iii. CHESS to Issuer Sponsored iv. Issuer Sponsored to CHESS

Enables mFund Participants and registries with the ability to transfer units similar to the way shares can be transferred through CHESS.




Enhancement Benefits Impact This will also allow for a more automated way to handle deceased estates relating to mFund holdings.

5 A changed recipient (Registry) for the mFund 716 CHESS Conversion Request to Issuer Sponsored Fund. Currently the Product Issuer Settlement Participant (PISP). Currently the PISP receives the MT716 CHESS Conversion Request to Issuer Sponsored Fund notification. The Registry is only notified where ASX Operations initiate the conversion. The appropriate Registry will now be notified in all instances. The PISP will no longer be notified. Currently the PISP receives the MT719 Issuer Sponsored fund to CHESS Authorisation Request for authorisation. This will now be directed to the appropriate Registry for authorisation.

This change maintains consistency between the registry and PISP functions within mFund by ensuring that the settlement activity remains with the PISP and register activity remains with the registry.

Mandatory for: mFund PISPs, mFund Registries.

6 Allow a Sponsoring Participant to request a preference update for a distribution to/from cash-DRP for a client’s mFund holding or to set-up or amend a regular payment plan with the registry. The registry will either accept and process the request or reject it.

Sponsoring Participants will be able to provide a fuller service to their clients.


7 A modification to the existing mFund Distribution Statement functionality to allow a Participant to request a periodic Income Statement. Currently the Registry initiates this process. The registry will send the HIN statement data through CHESS.

Enables mFund Sponsoring Participants to request, on behalf of their client, a periodic income statement. This will allow Sponsoring participants to control the process around the receipt of this information.




3.1. Testing To facilitate stakeholder readiness for the changes, the CHESS Release Test Environment (RTE) will be made available in Q4 2015. The exact date/s and scope of testing will be communicated separately soon.

Mandatory and Conditional Mandatory data changes will require CHESS Accreditation. Accreditation completion times and information will be communicated closer to the time. Users can choose to be Accredited for optional messages.

Impacted parties are required to have their CHESS Interface (‘system’) accredited for the processing of the following new and modified messages.

3.2. Implementation Date CHESS Release 9.0 will be effective in November 2015. The date will be confirmed over the coming weeks.

3.3. Parties Impacted by this Change ASX Market Participants, Clearing and Settlement Participants, Registries, mFund Registries and PISPs and CHESS ISVs.

3.4. Next Steps Parties impacted by this change should use the information in this document to carry out analysis and assessment of changes required within their systems and processes. Further technical details, for example rejection reasons, will be confirmed prior to the commencement of user acceptance testing.

An RTE schedule with dates will be communicated separately soon.

Following the consultation process stated in section 2.2, ASX will confirm its position and re-issue this document accordingly.

3.5. Contacting ASX – CHESS Release 9.0 For information regarding CHESS Release 9.0 please contact:

Chan Arambewela – Product Development Manager, Listing & Issuer Services T: 61 2 9227 0627, E: [email protected]

Arno Boeser – Senior Business Analyst T 61 2 9227 0784, E: [email protected].

mailto:[email protected]

mailto:[email protected]



4. Overview of CHESS Enhancements

4.1. Maintenance of possible FATCA/CRS reportable accounts

Impacted Parties ASX Clearing and Settlement Participants (as HIN sponsor), Registries, PISPs, CHESS ISVs.

What is the Proposal? CHESS Sponsoring Participants will obtain responses to the FATCA/CRS Questions from all new clients and seek responses to the FATCA/CRS Questions from all existing clients, and submit this data as part of creating a new HIN or updating an existing HIN. The FATCA/CRS responses will be held on the HIN record and passed to issuers’ registries where the HIN has a current holding or when a new holding is established.

Description CHESS Release 9.0 is driven by the need to implement an industry-wide solution to the regulatory requirement for issuers of certain investment products to report on US investors that hold their products under the Foreign Account Tax Compliance Act (FATCA) which will come into effect from 1 January, 2016. The affected products (new FATCA Reportable Products) include Exchange Traded Products (ETPs/ETFs), Real Estate Investment Trusts (REITs) and Listed Investment Entities (LEIs/LICs). FATCA requirements will be superseded by the introduction of the Common Reporting Standards (CRS) which will come into effect in 2017-18. CHESS release 9.0 is intended to provide flexibility to capture information that may be required under CRS. However, the regulatory requirements for CRS have not been finalised and further changes may be required in the future for the implementation of CRS

Although CHESS sponsoring participants do not have a reporting obligation under FATCA, it is recognised that under their Know Your Client (KYC) requirements and the general client on-boarding process, they are positioned to assist issuers identify potential FATCA reportable CHESS holders, and for those issuers to undertake a ‘Day 2’ process with the relevant holders.

Under the proposed solution, sponsoring participants will seek responses to the following FATCA/CRS Questions and submit this information via CHESS 201 and 203 messages. In summary this is:

i. Account Type [Individual, Joint, Superannuation Fund, Other Entity] ii. Are you a US Citizen? [YES/NO] iii. Are you a Foreign Tax Resident? [YES/NO] iv. If ‘YES’ to ii or iii the Foreign Tax Resident Code, Date of Birth and Tax

Identification Number (TIN) for up to three parties. v. Are there any Additional Foreign Parties? [YES/NO].

This information will be passed to issuers’ registries where the holder has a current holding or where a new holding is established via a CHESS 512 Holding Registration Details message. This change will therefore impact all registries, but only those that relate to a FATCA reportable holding will need to action the FATCA data. This may require the issuer to follow up with the holder (Day 2 process) based on the responses to the FATCA/CRS Questions. By making this a universal change to the CHESS 512 message, it removes the need to re-visit this issue if for example other financial products become FATCA reportable in the future. Sponsoring participants will be required to make the necessary changes to their new CHESS sponsored customer on boarding processes to submit the



FATCA/CRS responses from the implementation date of CHESS Release 9.0, in November, 2015. The responses to the FATCA/CRS Questions will then be able to be submitted via MT201 New Registrations Details. CHESS will store the responses on the HIN. Sponsoring participants will also be required to seek responses to the FATCA/CRS Questions from their existing CHESS sponsored clients. The responses to the FATCA/CRS Questions will be able to be submitted via the MT203 Registration Details Update.

For mFund accredited Participants and PISPs, the fields currently used for FATCA within a number of mFund messages will be removed. Refer 4.2 mFund Transaction Suite.

The ASX Settlement Rules will be changed to recognise the maintenance of the responses to the FATCA Questions by sponsoring participants on the HIN record.

Note:

CHESS will store the responses to the FATCA/CRS Questions on the HIN.

All registries will receive the responses to the FATCA/CRS Questions but only those that manage FATCA reportable products will need to take any action with the data received.

ASX will consult over the coming weeks with participants and issuers specifically on the costs and transition plan to implement the FATCA/CRS solution for issuers and the capture of the responses from current sponsored holders.

Impacted Parties Mandatory for: ASX Clearing and Settlement Participants (as sponsor), PISPs, Registries, CHESS ISVs.

Likely Impact Considerations Sponsoring participants:

Changes to new CHESS sponsored client on boarding process. Once-off process to capture FATCA/CRS responses for existing clients.

Registries:

Changes to processes for Registries that support FATCA reportable issuers’ products.

Registries that do not support FATCA reportable issuers’ products will need to adopt processes to receive but not act on the FATCA data received.

Products Impacted mFund (already FATCA reportable), ETFs, ETPs, REITS and LICs.

ASX Rules The ASX Settlement Rules and Procedures will be amended to incorporate these changes. These rule changes will be similar to what is currently in place for the mFund settlement service.

ASX Documentation The CHESS External Interface Specification (EIS), ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. CHESS Admin Authorisation FATCA/CRS changes will not be subject to CHESS Admin authorisation.

CHESS PC



CHESS PC will be upgraded for all new and modified CHESS fields and messaging.

CHESS MT503 Reports CHESS Holder reports will be modified to include FATCA/CRS details:

MT222 Holder Detail (HLD)

MT224 Holder History (HLH) CHESS Holder Notifications to Investors An additional CHESS Holder Notification will include FATCA/CRS related details both at initial setup and all subsequent modifications. Modified Messages MT201 New Registration Details MT203 Registration Details Update Request MT222 Holder Detail MT224 Holder History MT512 Holding Registration Details MT718 Issuer Sponsored to Fund CHESS Conversion Request MT719 Issuer Sponsored to Fund CHESS Authorisation Request MT726 Application Request MT727 Application Order Request MT800 Redemption Request MT801 Redemption Order Request MT806 Switch Request MT807 Switch Order Request

Refer 5. Technical Details for Participants for detailed specifications. Refer Appendix 1: Foreign Tax Status Determination Refer Appendix 3: Field Definitions for new and modified CHESS field definitions.



4.2. mFund Transaction Suite

Impacted Parties ASX Clearing and Settlement Participants (as sponsor), PISPs, mFund Registries, CHESS ISVs system vendors.

What is the Proposal? A change to the mFund transaction message suite to synchronise the capture of the FATCA/CRS data from the HIN. Also refer 4.3 Sophisticated Investor.

Description The FATCA data currently included in the mFund transaction messages will be replaced with the FATCA/CRS information maintained on the HIN.

Impact Status Mandatory for: mFund ASX Clearing and Settlement Participants (as sponsor), PISPs, Registries, CHESS ISVs.

Likely Impact Considerations mFund Participants:

Process change to current inclusion of FATCA data. PISPs:

Will receive the enhanced consistent FATCA/CRS data captured from the HIN.

CHESS Admin Authorisation Changes to mFund transactions will not be subject to CHESS Admin authorisation.

CHESS PC CHESS PC will be upgraded for all new and modified CHESS messaging.

ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. Modified CHESS Messages MT222 Holder Detail MT224 Holder History MT512 Holding Registration Details MT716 CHESS to Issuer Sponsored Conversion Request MT718 Issuer Sponsored to Fund CHESS Conversion Request MT719 Issuer Sponsored to Fund CHESS Authorisation Request MT720 Accepted Participant Request MT722 Fund Response MT726 Application Request MT727 Application Order Request MT762 Effected Registry Request MT800 Redemption Request MT801 Redemption Order Request MT806 Switch Request MT807 Switch Order Request

Refer 5. Technical Details for Participants for detailed specifications. Refer Appendix 1: Foreign Tax Status Determination Refer Appendix 3: Field Definitions for new and modified CHESS field definitions.



4.3. Sophisticated Investor

Impacted Parties ASX Clearing and Settlement Participants (as sponsor), Registries, CHESS ISVs.

What is the Proposal? Sponsoring Participant can optionally nominate whether a client has been established as a ‘Sophisticated Investor’ on the HIN. This allows the participant to offer potential mFund products that may be admitted in the future and only available to sophisticated investors.

Description The Participant may include ‘YES’, ‘NO’ or leave the Sophisticated Investor indicator ‘BLANK’ when setting up a HIN for a new client through the CHESS MT201.

The Participant may update the Sophisticated Investor indicator for an existing HIN with ‘YES’, to confirm that the holder is a Sophisticated Investor or ‘NO’ where the holder is no longer a sophisticated investor through the CHESS MT201.

The Sophisticated Investor indicator will be left ‘BLANK’ for all existing HINs when the field is added as part of the release.

The Sophisticated Investor indicator (YES where nominated) will be forwarded to the appropriate Registry via the existing CHESS MT512. The Sophisticated Investor Indicator will also be included on the CHESS mFund Application Request message suite (MT726/MT7270). Note: CHESS will store the Sophisticated Investor indicator on the HIN.

Impact Status Mandatory for: ASX Clearing and Settlement Participants (as sponsor), PISPs, Registries, CHESS ISVs.

Likely Impact Considerations Sponsoring Participants:

Maintain the up to date details of the clients’ sophisticated investor status to allow them to potentially invest in additional products.

PISPs:

Process transactions for mFund products that may only apply to sophisticated investors.

ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. CHESS Admin Authorisation Sophisticated Investor changes will not be subject to CHESS Admin authorisation.


CHESS MT503 Reports Holder reports will modified to include the Sophisticated Investor indicator:

MT222 Holder Detail (HLD)

MT224 Holder History (HLH)



CHESS Holder Notifications to Investors CHESS Holder Notifications will not include details of the Sophisticated Investor indicator either at initial setup or subsequent modification. Modified Messages MT201 New Registration Details MT203 Registration Details Update Request MT222 Holder Detail MT224 Holder History MT512 Holding Registration Details MT726 Application Request MT727 Application Order Request MT800 Redemption Request MT801 Redemption Order Request MT806 Switch Request MT807 Switch Order Request




4.4. CHESS to CHESS mFund Transfer – Same Participant

Impacted Parties mFund ASX Clearing and Settlement Participants (as sponsor), PISPs, Registries, CHESS ISVs.

What is the Proposal? mFund Participants will be able to transfer mFund units held on CHESS from one HIN to another HIN.

Description Both the Receiving HIN and the Delivering HIN must be present in the message and the requesting Participant must be the sponsor of both HINs.

The Participant must ensure that the destination HIN has the required FATCA/CRS assessment in place prior to the transfer, as CHESS will validate this condition.

The Participant is advised where the transfer request was effected or rejected by CHESS.

The Registry is notified via the existing CHESS (MT512) message where the transfer has resulted in the holding moving to a zero balance. Where the holding has not resulted in the holding moving to a zero balance, a (MT503) Holding Net Fund Movement report (HMV) may be requested by the Registry.


Likely Impact Considerations Consideration needs to be given to the following

Ensure FATCA/CRS assessments are established for each transfer. Ensure internal and external workflows/systems can process mFund

specific CHESS to CHESS transfer requests for the one Participant.


ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. New CHESS Messages MT851 Single Entry CHESS to CHESS Fund Transfer Request MT852 Effected Fund Transfer MT862 CHESS Transfer Notification

Modified CHESS Messages MT512 Holding Registration Details




4.5. CHESS to CHESS mFund Transfer – Different Participant


What is the Proposal? mFund Participants will be able to request the transfer of mFund units between a HIN under its control to a HIN under the control of another Participant. Both parties to the transfer must be mFund accredited. If not, CHESS will reject the transfer request.

Description One Participant initiates the transfer. The counterparty is required to enter a matching request for the transfer to be completed.

The counterparty Participant must ensure that the destination HIN has the required FATCA/CRS assessment in place prior to the transfer, as CHESS will validate this condition.

If no match is made the request is flagged as unmatched and both the submitting Participant and the counterparty are advised.

The requesting Participant may cancel the transfer at any time if the transfer request remains unmatched. CHESS will housekeep all unmatched transfer requests after 2 business days.

The Registry is notified via the existing MT512 message where the transfer has resulted in a change of controlling Participant. .




specific CHESS to CHESS transfer requests between Participants.


ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. New CHESS Messages MT852 Effected Fund Transfer MT853 Dual Entry CHESS to CHESS Fund Transfer Request MT854 Unmatched Dual Entry CHESS to CHESS Fund Transfer MT862 CHESS Transfer Notification

Modified CHESS Messages MT024 Rejected Demand Dual Entry CHESS to CHESS Transfer Request MT037 Demand Dual Entry CHESS to CHESS Transfer Cancellation Request MT048 Cancelled Demand Dual Entry Transfer Request MT194 Unmatched Dual Entry Request



4.6. mFund Issuer Sponsored to CHESS Transfer


What is the Proposal? The proposal is that a mFund Participants or ASX Operations are able to transfer mFund units from an Issuer Sponsored register to the CHESS sub-register.

Description The Participant is advised whether the transfer request was effected or rejected by CHESS or by the Registry. The Registry may authorise or reject the request.

Both the delivering SRN details, Receiving PID and Receiving HIN must be present in the message.






ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. New CHESS Messages MT852 Effected Fund Transfer MT855 Issuer Sponsored Fund to CHESS Transfer Request MT856 Issuer Sponsored Fund to CHESS Transfer Authorisation Request MT857 Registry Fund Transfer Authorisation MT859 Registry Fund Transfer Rejection MT860 Rejected Registry Authorisation

Modified CHESS Messages MT512 Holding Registration Details MT720 Accepted Participant Request MT722 Fund Response


MT512 Holding Registration Details




4.7. mFund CHESS to Issuer Sponsored Transfer


What is the Proposal? The proposal is that a mFund Participant or ASX Operations are able to transfer mFund units from CHESS to an issuer sponsored register.

Description The Participant is advised whether the transfer request was effected or rejected by CHESS or by the Registry. The Registry may authorise or reject the request. Both the delivering SRN details, Receiving PID and Receiving HIN must be present in the message.

Impact Status Mandatory for: mFund ASX Clearing and Settlement Participants (as sponsor), PISPs, Registries, CHESS ISVs





ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. New CHESS Messages MT852 Effected Fund Transfer MT857 Registry Fund Transfer Authorisation MT858 CHESS to Issuer Sponsored Fund Transfer Authorisation Request MT859 Registry Fund Transfer Rejection MT860 Rejected Registry Authorisation MT861 CHESS to Issuer Sponsored Fund Transfer Request

Modified CHESS Messages MT512 Holding Registration Details MT720 Accepted Participant Request MT722 Fund Response




4.8. Changed Recipient for mFund CHESS message MT716, MT719

Impacted Parties PISPs, Registries, CHESS ISVs

What is the Proposal? Currently the PISP receives the MT716 CHESS Conversion Request to Issuer Sponsored Fund notification. The Registry is only notified where ASX Operations initiate the conversion. The appropriate Registry will now be notified in all instances. The PISP will no longer be notified. Currently the PISP receives the MT719 Issuer Sponsored to Fund CHESS Authorisation Request for authorisation. This will now be directed to the appropriate Registry for authorisation.

Description A Participant request to convert a nominated holding from CHESS to the Issuer Sponsored register is received by CHESS and processed. The result is sent via the MT716 to the Registry. Where ASX Operations initiate the conversion request, CHESS will pass details through to the appropriate Registry for that issuer.

A Participant request to convert a nominated holding from the Issuer Sponsored register to CHESS is received by CHESS and passed to the appropriate Registry for authorisation via the MT719.

Impact Status Mandatory for: PISPs, Registries, CHESS ISVs


Ensure internal and external workflows/systems recognise the fact that the recipient of the MT716 and MT719 is now the Registry, not the PISP.


ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. Modified CHESS Messages MT716 CHESS Conversion Request to Issuer Sponsored Fund MT719 Issuer Sponsored to Fund CHESS Authorisation Request




4.9. DRP / RPP Election

Impacted Parties ASX Clearing and Settlement Participants, Registries, CHESS ISVs

What is the Proposal? The proposal is that a sponsoring Participant is able to maintain an investor’s DRP and RPP preferences via a dedicated CHESS message suite

Description Provides ASX Clearing and Settlement Participants with an ability to elect/amend both Dividend (cash/DRP) and RPP (Regular Payment Plan) preferences with the appropriate Registry. Where the preference value is ‘N’ (no) and the investor chooses not to use their Primary Bank Account details, then they may enter specific Bank Account details via this function Initial entry of DRP Preferences will remain within the MT726 Application request message.

Impact Status Optional for: ASX Clearing and Settlement Participants , Registries, CHESS ISVs.


Ensure internal and external workflows/systems can process Dividend elections and RPP Preferences for a clients.


ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. New CHESS Messages MT860 Rejected Registry Authorisation MT863 DRP RPP Election Request MT864 DRP RPP Election Authorisation Request MT865 DRP RPP Registry Authorisation MT866 Accepted DRP RPP Election Request MT867 DRP RPP Registry Rejection

Modified CHESS Messages MT762 Effected Registry Transaction




4.10. Periodic Income Statement

Impacted Parties mFund ASX Clearing and Settlement Participants, Registries, CHESS ISVs.

What is the Proposal? Currently Statement functionality (known as Distribution Statement) puts the onus on the Registry to provide unsolicited periodic Income Statement details to the Participant for all holders based on an agreement. The modification to this process would allow the Participant to request a periodic Income Statement on behalf of their client.

Description A Participant may request a periodic Income Statement. Additionally the Participant may select either to have the statement as an on-demand or as a regular standing report. Based on this request, the Registry will populate and return Income Statement data.

The Registry may accept or reject the request.

Periodic Income Statements for periods other than the last completed period will not be available.

Impact Status Optional for: mFund ASX Clearing and Settlement Participants, Registries, CHESS ISVs.


Ensure internal and external workflows/systems can process Income Statement requests/outcomes.


ASX Documentation The ASX Settlement Operating Rules, the CHESS External Interface Specification (EIS), the ASX Settlement Procedure Guidelines (APG) and the mFund Service Technical Overview will be updated. Modified CHESS Messages MT762 Effected Registry Transaction MT813 Income Statement MT816 Income Statement Advice MT868 Income Statement Authorisation Request MT869 Income Statement Request MT881 Income Statement Authorisation MT884 Accepted Income Statement Request MT907 Income Statement Rejection




5. Technical Details for Participants This section outlines modifications and additions to CHESS data fields and messaging to complement the business initiatives.

5.1. CHESS Message Impact

5.1.1. New CHESS Messages MT851 Single Entry CHESS to CHESS Fund Transfer Request MT852 Effected Fund Transfer MT853 Dual Entry CHESS to CHESS Fund Transfer Request MT854 Unmatched Dual Entry CHESS to CHESS Fund Transfer MT855 Issuer Sponsored Fund to CHESS Transfer Request MT856 Issuer Sponsored Fund to CHESS Transfer Authorisation Request MT857 Registry Fund Transfer Authorisation MT858 CHESS to Issuer Sponsored Fund Transfer Authorisation Request MT859 Registry Fund Transfer Rejection MT860 Rejected Registry Authorisation MT861 CHESS to Issuer Sponsored Fund Transfer Request MT862 CHESS Fund Transfer Notification MT863 DRP RPP Election Request MT864 DRP RPP Election Authorisation Request MT865 DRP RPP Registry Authorisation MT866 Accepted DRP RPP Election Request MT867 DRP RPP Registry Rejection MT868 Income Statement Authorisation Request MT869 Income Statement Request MT881 Income Statement Authorisation MT884 Accepted Income Statement Request MT907 Income Statement Rejection

5.1.2. Modified CHESS Messages MT024 Rejected Demand Dual Entry CHESS to CHESS Transfer Request MT037 Demand Dual Entry CHESS to CHESS Transfer Cancellation Request MT048 Cancelled Demand Dual Entry Transfer Request MT194 Unmatched Dual Entry Request MT201 New Registration Details MT203 Registration Details Update Request MT222 Holder Detail MT224 Holder History MT512 Holding Registration Details

Refer Appendix 2: Field Definitions for new and modified CHESS field definitions.



MT716 CHESS to Issuer Sponsored Conversion Request MT718 Issuer Sponsored to Fund CHESS Conversion Request MT719 Issuer Sponsored to Fund CHESS Authorisation Request MT720 Accepted Participant Request MT722 Fund Response MT726 Application Request MT727 Application Order Request MT762 Effected Registry Request MT800 Redemption Request MT801 Redemption Order Request MT806 Switch Request MT807 Switch Order Request MT813 Income Statement MT816 Income Statement Advice



5.2. Investor Impact The modified Holder maintenance message suite (MT201/203) applies to CHESS holders (HIN) only.

As the mFund Settlement Service applies to both HIN and SRN investors, the table below outlines how both these types of investors are managed in terms of holder/investor details.

Function Investor Type

Investor Creation Investor Amendment CHESS Storage

Foreign Tax Status HIN MT201 MT203 Y

SRN MT726 (mFund) MT726 (mFund) N

Sophisticated Investor HIN MT201 MT203 Y

SRN via Registry

MT726 (mFund)

via Registry N

DRP Preference

RPP Preference

HIN Message suite: refer 5.9

MT726 (mFund)

Message suite: refer 5.9 N

SRN via Registry

MT726 (mFund)

via Registry N



5.3. Holder Maintenance Enhancements Additional elements will be included on the Holder (HIN) registration and update messages MT201/MT203 Holder maintenance suite to facilitate the following: Foreign Tax Status identification Sophisticated Investor identification Other impacted functionality is also described: MT503 requested Holder reports mFund Application, Redemption, Switch and Issuer Conversion message suites MT512 Registry messaging

5.3.1. Holder Registration Enhancements

CHESS

Registry512 Holding Registration

Details (modified)202 Accepted New Registration

Details

Participant 201 New Registration Details (modified)

Participant



5.3.1.1. New Registration Details [201-05] The allow a Participant to setup a new holder on the CHESS subregister. A HIN is allocated to the holder by CHESS as part of the setup procedure.

The Participant is required to ascertain an investors foreign tax status where applicable. Please refer to Appendix 1: Foreign Tax Status Determination.

The Entrepot Type is only specified if the Holder Type is an entrepot.

Sender: Participant Recipient: CHESS

Bit Position

Field Name Format Mandatory/Optional(M/O)

1 Bit Map 2 Marker On M 18 Holder Type 1 Character M 48 Transaction Id 16 Character M 59 Registration Details 180 Character M 65 Bit Map 3 Marker On M 71 Entrepot Type 1 Character O 129 Bit Map 4 Marker On M 175 Residency Indicator 1 Character M 186 Sophisticated Investor 1 Character M 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 265 Account Type 1 Character M 266 US Citizen 1 Character M 267 Foreign Tax Resident 1 Character M 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



Transmission Cut off times: Settlement Cut-off Time - if the message is to be processed prior to the next settlement process End of Day - if the message is to be processed prior to the end of day process. Prerequisites: None



5.3.1.2. Holding Registration Details [512-05] To notify a Registry of:

new registration details on creation of a new CHESS holding; changed registration details on notification by a Participant; changed Sophisticated Investor indicator on notification by a Participant; changed foreign tax status details on notification by a Participant; changed or cancelled Email details on notification by a Participant; changed residency of the holder on notification by a Participant (only provided when the

security is subject to Foreign Ownership Restrictions); changed holder status on notification by a Participant; the application or release of a holding lock; the registration details of a CHESS holding that has moved to a zero balance; or the Controlling PID of a HIN that has changed its Controlling Participant.

Sender: CHESS Recipient: Registry

Bit

Position Field Name Format Mandatory/Optional

(M/O) 1 Bit Map 2 Marker On M 2 Security Code 12 Character M 16 HIN 10 Numeric M 18 Holder Type 1 Character M 19 Controlling PID 5 Numeric M 21 Processing Timestamp 22 Character M 26 Registration Details Indicator 1 Character M 59 Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 174 Holder Status 1 Character O 175 Residency Indicator 1 Character O 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 209 Email Cancellation 1 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O



Transmission Cut off times: None Prerequisites:

One of the following:

Creation of a new holding An authorised change to registration details, Email details (including cancellation), foreign tax

status details, Sophisticated Investor indicator, residency and/or holder status of a CHESS holder (203 Update Registration Details)

Movement of an existing holding to or from a zero balance A change of Controlling Participant of a holding Registration Address Cleansing performed by ASX Settlement Conversion of Holdings

279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.2. Update Holder Registration Enhancements

CHESS

203 Registration Details UpdateRequest (modified)

Followed by CHESS Administration authorisation

CHESS Admin

Authorisation

Participant

Registry512 Holding Registration Details (modified)

218 Accepted Registration Details UpdateParticipant

220 Authorised Registration DetailsParticipant

Or CHESS Administration rejection

CHESS Admin

Authorisation

080 Rejected Registration DetailsUpdateParticipant

Additional elements will be included in the Holder (HIN) update messages MT203 Holder maintenance suite to facilitate the following: Foreign Tax Status Sophisticated Investor identification



5.3.2.1. Registration Details Update Request [203-05] To enable the registration details of a CHESS holder to be maintained on the CHESS subregister.

The Participant is required to ascertain an investor’s foreign tax status where applicable. Please refer to Appendix 1: Foreign Tax Status Determination.

Changes involving registration name, other than those involving select Account Designation changes only are passed to ASX Settlement for authorisation.

Changes involving the registration address, sophisticated investor, foreign tax status, residency indicator or email details do not require authorisation by ASX Settlement.

Changes involving application and release of death and bankruptcy holder record locks do not require authorisation as long as valid holder status change values are provided and valid values for other required field designations are provided. Refer to the APG section 5 for further detail.

Changes involving a change in a holder’s status may require authorisation by ASX Settlement, depending on the status change requested.

Multiple registration updates are possible on one message.

Date of Event must only be populated for:

Date of bankruptcy upon application of a bankruptcy lock. Date of death upon release of a death holder lock.

Note: If any change submitted on the message requires authorisation by ASX Settlement, all relevant changes specified on the message are authorised or rejected together.

Refer to Section 8 of this manual for more information on CHESS validation of registration details.


Bit Position


1 Bit Map 2 Marker On M 12 Date Of Event 8 Numeric O 16 HIN 10 Numeric M 34 Contact Reference 16 Character O 48 Transaction Id 16 Character M 59 Registration Details 180 Character O 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 142 Registration Name Update Reason 1 1 Character O 145 Registration Name Update Reason 2 1 Character O 173 Holder Status Change 1 Character O 175 Residency Indicator 1 Character O 179 Holder Lock Release Reason 1 Character O 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 209 Email Cancellation 1 Character O



Transmission Cut off times:

None Prerequisites: None

265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.3. Holder Reporting Enhancements

CHESS

222 Holder Detail or224 Holder History

Participant503 Reporting Request

PISP

ParticipantPISP

5.3.3.1. Holder Detail [222-05] To notify a Participant or PISP of the current details of a holder that they control on the CHESS subregister. Sender: CHESS Recipient: Participant or PISP

Bit Position


1 Bit Map 2 Marker On M 16 HIN 10 Numeric M 18 Holder Type 1 Character M 19 Controlling PID 5 Numeric M 21 Processing Timestamp 22 Character M 56 Statement Required 1 Character M 59 Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 71 Entrepot Type 1 Character O 129 Bit Map 4 Marker On M 154 Advice Reason 1 Character M 174 Holder Status 1 Character O 175 Residency Indicator 1 Character O 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O




Receipt of a 503 Reporting Request; or

Transfer of control of an existing HIN to the recipient




5.3.3.2. Holder History [224-04] To notify a Participant or PISP of historical details of a holder that they control on the CHESS subregister. A series of these messages is received in response to a Participant's reporting request. Sender: CHESS Recipient: Participant or PISP

Bit Position


1 Bit Map 2 Marker On M 16 HIN 10 Numeric M 18 Holder Type 1 Character M 19 Controlling PID 1 Character M 21 Processing Timestamp 22 Character M 56 Statement Required 1 Character M 59 Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 71 Entrepot Type 1 Character O 87 Timestamp 22 Character M 88 Response Timestamp 22 Character M 129 Bit Map 4 Marker On M 174 Holder Status 1 Character O 175 Residency Indicator 1 Character O 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O




Receipt of a 503 Reporting Request

289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4. mFund Enhancements FATCA requirements have been incorporated into the relevant mFund functions. The interim solution value ‘FATCA Questions’ has been removed.

In line with the introduction of mFund specific transfer functions, the existing mFund conversion messages will now be directed to the relevant Registry, not the PISP.

5.3.4.1. Issuer Sponsored Fund to CHESS Conversion Request [718-02] To enable Fund Units in an Issuer Sponsored holding to be converted to the CHESS sub-register. The conversion request requires authorisation by the Product Issuer Settlemen(PISP).Registry.

The Participant is advised if the conversion request has been passed to the Product Issuer Settlement Registry or rejected by CHESS. The conversion request details are forwarded to the Product Issuer Settlement Registry. The conversion request is held in CHESS and not actioned until a response is received from the Product Issuer Settlement Registry. Sender: Participant Recipient: CHESS

Transmission Cut off times: None Prerequisites: None

Bit Position

Field Name Format Mandatory/Optional (M/O)

1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 Receiving HIN 10 Numeric M 25 Movement Reason 1 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character M 65 Bit Map 3 Marker On M 70 Underlying Reference 16 Character O 129 Bit Map 4 Marker On M 209 AML/CTF Check Flag 1 Character M 210 FATCA Questions 1 Character M 232 Number of Units 18 Numeric; 6 decimal M 245 APIR Code 9 Character O



5.3.4.2. Application Request [726-02] To allow a Participant to request the lodgement of an application to purchase a dollar amount of units in an ASX admitted Fund. Email details and foreign tax status details within this message relate only to SRN investors. HIN Email details and foreign tax status details are entered or amended via the MT201/203 Registration Details message suite. Bank Account details apply to both SRN and HIN investors.

Please refer to Appendix 1: Foreign Tax Status Determination.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal M 11 Initial Application 1 Character M 16 HIN 10 Numeric O 18 DRP Preference 1 Character O 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 59 Registration Details 180 Character O 63 Tax Residence 1 3 Character O 65 Bit Map 3 Marker On M 78 Tax Residence 2 3 Character O 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 99 Tax Residence 3 3 Character O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 208 Email Purpose 1 Character O 209 AML / CTF Flag 1 Character M




Fund Request Cut-off Time - If the request is to be processed in the next settlement process

Prerequisites: None

210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 231 Current PDS Provided 1 Character M 234 Product Name 50 Character O 236 PDS Issue Date 8 Numeric M 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O 245 APIR Code 9 Character O 247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O 249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4.3. Application Order Request [727-02] To notify a Product Issuer Settlement Participant of a request for lodgement of an application order to purchase a dollar amount of Fund units in a Fund under their control. Email details and foreign tax status details within this message relate only to SRN investors. HIN Email details and foreign tax status details are entered or amended via the MT201/203 Registration Details message suite. Bank Account details apply to both SRN and HIN investors. Sender: CHESS Recipient: Product Issuer Settlement Participant (PISP)

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal M 11 Initial Application 1 Character M 16 HIN 10 Numeric O 18 DRP Preference 1 Character O 20 PID 5 Numeric M 21 Processing Timestamp 22 Character M 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 59 Registration Details 180 Character O 62 Origin Transaction Id 16 Character M 63 Tax Residence 1 3 Character O 65 Bit Map 3 Marker On M 78 Tax Residence 2 3 Character O 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 99 Tax Residence 3 3 Character O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 186 Sophisticated Investor 1 Character O 193 Bit Map 5 Marker On M 200 Email Address 50 Character O 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 208 Email Purpose 1 Character O 209 AML / CTF Flag 1 Character M




None

Prerequisites: Receipt of a 726 Application Request

210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 231 Current PDS Provided 1 Character M 234 Product Name 50 Character O 236 PDS Issue Date 8 Numeric M 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O 245 APIR Code 9 Character O 247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O 249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4.4. Redemption Request [800-02] To allow a Participant to request the redemption of:

Nominated Number of Units Nominated Fund Amount Full Redemption

o Where Full Redemption = ‘Y’, if Fund Amount and/or Number of Units populated – CHESS will reject Participants Redemption Request.

o Where Full Redemption = ‘N’, If both Fund Amount and Number of Units populated - CHESS will reject Participants Redemption Request

o Where Full Redemption = ‘N’, neither Fund Amount or Number of Units populated - CHESS will reject Participants Redemption Request

The foreign tax status details within this message relate only to SRN investors. HIN foreign tax status details are entered or amended via the MT201/203 Registration Details message suite.

Please refer to Appendix 1: Foreign Tax Status Determination.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal O 11 Full Redemption 1 Character M 16 HIN 10 Numeric O 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 190 Nett or Gross 1 Character M 191 Redemption Request Reason 1 Character O 193 Bit Map 5 Marker On M 209 AML / CTF Flag 1 Character M 210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 232 Number of Units 18 Numeric, 6 decimal O 234 Product Name 50 Character O 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O 245 APIR Code 9 Character O 247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O




None

Prerequisites: None

249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4.5. Redemption Order Request [801-02] To notify a Product Issuer Settlement Participant of a request for redemption of units in a Fund for either of the following:

If Full Redemption equals “Y” then “Fund Amount” and “Number of Units” will not be populated

If Full Redemption equals “N” then either a specific “Number of Units” or “Fund Amount” will be populated.

The foreign tax status details within this message relate only to SRN investors. HIN foreign tax status details are entered or amended via the MT201/203 Registration Details message suite. Sender: CHESS Recipient: Product Issuer Settlement Participant (PISP)

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal O 11 Full Redemption 1 Character M 16 HIN 10 Numeric O 20 PID 5 Numeric M 21 Processing Timestamp 22 Character M 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 190 Nett or Gross 1 Character M 191 Redemption Request Reason 1 Character O 193 Bit Map 5 Marker On M 209 AML / CTF Flag 1 Character M 210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 232 Number of Units 18 Numeric, 6 decimal O 234 Product Name 50 Character O 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O 245 APIR Code 9 Character O 247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O 249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O




None

Prerequisites: Receipt of an 800 Redemption Request

267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4.6. Switch Request [806-02] To allow a Participant to request a switch (in effect a pari passu redemption and application) of units in one Fund to another Fund that is under the control of the Product Issuer Settlement Participant for the same Issuer. The switch of units can occur for a Fund in a CHESS or Issuer Sponsored Holding

The Participant is to indicate if the Switch Request is a “full” or “partial” switch.

To indicate that a “full” switch is requested, a “Y” must be provided in the Full Switch field. If “Y” is entered then Fund Amount and Units Redeemed are not applicable

To indicate that a “partial” switch is requested, an “N” must be provided in the Full Switch field. If “N” is entered then either Fund Amount or Units Redeemed must be entered.

The foreign tax status details within this message relate only to SRN investors. HIN foreign tax status details are entered or amended via the MT201/203 Registration Details message suite.

The Participant is required to ascertain an investor’s foreign tax status where applicable. Please refer to Appendix 1: Foreign Tax Status Determination.


Bit Position


1 Bit Map 2 Marker On M 2 Redemption Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal O 10 Application Fund Code 12 Character M 11 Full Switch 1 Character M 16 HIN 10 Numeric O 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 190 Nett or Gross 1 Character M 193 Bit Map 5 Marker On M 200 Application Product Name 50 Character O 209 AML / CTF Flag 1 Character M 210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 231 Current PDS Provided 1 Character M 232 Units Redeemed 18 Numeric, 6 decimal O 234 Redemption Product Name 50 Character O 236 PDS Issue Date 8 Numeric M 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O




None

Prerequisites: None

245 Redemption APIR Code 9 Character O 246 Application APIR Code 9 Character O 247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O 249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.3.4.7. Switch Order Request [807-02] To notify a Product Issuer Settlement Participant of a request to switch units in a Fund either:

Where Full Switch equals “Y”, Fund Amount and Units Redeemed are not applicable Where Full Switch equals “N”, then a Participant would have requested to switch a

specific number of units or switch units to the value of Fund Amount provided.

The Redemption Fund Code and Application Fund Code must be under the control of the one Product Issuer Settlement Participant within the same Issuer.

The foreign tax status details within this message relate only to SRN investors. HIN foreign tax status details are entered or amended via the MT201/203 Registration Details message suite. Sender: CHESS Recipient: Product Issuer Settlement Participant (PISP)

Bit Position


1 Bit Map 2 Marker On M 2 Redemption Fund Code 12 Character M 3 Fund Amount 15 Numeric; 2 decimal O 10 Application Fund Code 12 Character M 11 Full Switch 1 Character M 16 HIN 10 Numeric O 20 PID 5 Numeric M 21 Processing Timestamp 22 Character M 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character O 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 190 Nett or Gross 1 Character M 193 Bit Map 5 Marker On M 200 Application Product Name 50 Character O 209 AML / CTF Flag 1 Character M 210 FATCA Questions 1 Character M 217 Dealer Group AFSL Number 10 Character O 218 Participant Advisor Name 30 Character O 219 Participant Advisor Code 30 Character O 231 Current PDS Provided 1 Character M 232 Units Redeemed 18 Numeric, 6 decimal O 234 Redemption Product Name 50 Character O 236 PDS Issue Date 8 Numeric M 240 Participant Advisor Email 50 Character O 243 Dealer Group Advisor Email 50 Character O 245 Redemption APIR Code 9 Character O 246 Application APIR Code 9 Character O




None

Prerequisites: Receipt of an 806 Switch Request

247 Dealer Group Name 30 Character O 248 Dealer Group Advisor Name 30 Character O 249 Dealer Group Advisor Code 30 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.4. mFund HIN to HIN Transfer (controlled by the same Participant)

CHESS


852 Effected Fund Transfer (new)

Participant851 Single Entry CHESS to CHESS

Fund Transfer Request (new)

Participant

Registry



5.4.1. Single Entry CHESS to CHESS Fund Transfer Request [851-01] The purpose of this transfer request is to enable a Participant to transfer fund units between two CHESS holdings under its control. Note that the details are from the Transferee perspective.

The Participant is advised whether the transfer request was effected or rejected.

Both the Receiving HIN and the Delivering HIN must be present in the message.



Settlement Cut-off Time - if the message is to be processed prior to the next settlement process End of Day - if the message is to be processed prior to the end of day process.

Prerequisites: None

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 Receiving HIN 10 Numeric M 17 Delivering HIN 10 Numeric M 18 DRP Preference 1 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character M 231 Current PDS Provided 1 Character M 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric M 245 APIR Code 9 Character O



5.4.2. Effected Fund Transfer [852–01] The purpose of this message is to notify a Participant that a transfer of fund units has been effected between:

Two CHESS holdings (HIN) under the control of the same Participant (PID) Two CHESS holdings (HIN) under the control of different Participants (PID) An Issuer Sponsored holding (SRN) and a CHESS holding (HIN) A CHESS holding (HIN) and an Issuer Sponsored holding (SRN)

Sender : CHESS Recipient: Participant

Bit Position


1 Bit Map 2 Marker On M 21 Processing Timestamp 22 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 90 Matching Transaction Id 16 Character O 129 Bit Map 4 Marker On M 232 Transferor Holding Balance 18 Numeric; 6 Decimal O 233 Transferee Holding Balance 18 Numeric; 6 Decimal O

Transmission Cut off times: None Prerequisites: Receipt of an 851 Single Entry CHESS to CHESS Fund Transfer Request; or Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request; or Receipt of an 857 Issuer Sponsored to CHESS Fund Transfer Request



5.4.1. CHESS Fund Transfer Notification [862-01] The notify the Registry that a Single Entry or Dual Entry HIN to HIN transfer request from a Participant has been processed by CHESS.

Note that the details are from the Transferee perspective. The Transferee may not be an existing holder of mFund products.


Transmission Cut off times: None

Prerequisites: Receipt of an 851 Single Entry CHESS to CHESS Fund Transfer Request; or Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 HIN 10 Numeric M 17 Delivering HIN 10 Numeric M 18 DRP Preference 1 Character O 20 PID 5 Numeric M 21 Processing Timestamp 22 Character M 25 Movement Reason 1 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 59 Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character M 231 Current PDS Provided 1 Character M 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric M 245 APIR Code 9 Character O



5.5. mFund HIN to HIN Transfer (controlled by different Participants)

CHESS

853 Dual Entry CHESS to CHESS Fund Transfer Request

(new)

Followed by Participant 2 matching:

CHESS

852 Effected Fund Transfer (new)

OR

Participant 1

Participant 1

Participant 1

Participant 2194 Unmatched Dual Entry Request

Cancellation can be initiated by Participant 1 while request remains unmatched:

CHESS

037 Demand Dual Entry CHESS to CHESS Transfer Cancellation Request

048 Cancelled Demand Dual Entry Transfer RequestParticipant 1

Participant 1 Participant 2048 Cancelled Demand Dual Entry Transfer Request

Participant 2853 Dual Entry CHESS to

CHESS Fund Transfer Request(new)

Participant 2852 Effected Fund Transfer

(new)OR


Registry862 CHESS Fund Transfer Notification(new)

Participant 1 024 Rejected Demand Dual EntryCHESS to CHESS Transfer Participant 2024 Rejected Demand Dual Entry

CHESS to CHESS Transfer



5.5.1. Dual Entry CHESS to CHESS Fund Transfer Request [853-01] The purpose of the transfer request is to transfer fund units between CHESS holdings controlled by different Participants in CHESS. Both parties to the transfer must be mFund accredited. Both Participants are required to enter requests which are then matched.

CHESS matches dual entry fund transfers against the following data items:

Fund Code Counterparty PID Number of Units

The Receiving PID must include the following:

AML/CTF Flag Current PDS Provided PDS Issue Date

If a match occurs, the transfer will be effected immediately, and the result advised to both parties.

If no match is made the request is flagged as unmatched and both parties are advised.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 HIN 10 Numeric M 18 DRP Preference 1 Character O 19 Receiving PID 5 Numeric M 20 Delivering PID 5 Numeric M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character O 231 Current PDS Provided 1 Character O 232 Number of Units 18 Numeric, 6 Decimal M



Transmission Cut off times: Settlement Cut-off Time - if the message is to be processed prior to the next settlement process End of Day - if the message is to be processed prior to the end of day process. Prerequisites: None

5.5.2. Unmatched Dual Entry CHESS to CHESS Fund Transfer [854-01] The purpose of the message is to notify a Participant that a dual entry CHESS to CHESS fund transfer request has been received from the counterparty to the transfer. The Participant is requested to enter a corresponding message so that the transfer can be matched and effected.

Sender: CHESS Recipient: Participant

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 19 Receiving PID 5 Numeric M 20 Delivering PID 5 Numeric M 21 Processing Timestamp 22 Character M 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 232 Number of Units 18 Numeric, 6 Decimal M 245 APIR Code 9 Character O

Transmission Cut off times: None Prerequisites: Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request.

236 PDS Issue Date 8 Numeric O 245 APIR Code 9 Character O



5.5.3. Rejected Demand Dual Entry CHESS to CHESS Transfer [024-01] To notify a Participant that a transfer request has been matched with a counterparty request, BUT the transfer has been rejected by CHESS. Reasons for rejection may include insufficient units or entitlements to cover the transfer.


Bit Position


1 Bit Map 2 Marker On M 21 Processing Timestamp 22 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 90 Matching Transaction Id 16 Character M 129 Bit Map 4 Marker On M 198 Rejected Transfer Reason 1 Character M

Transmission Cut off times: None Prerequisites: Receipt of a 005 Demand Dual Entry CHESS to CHESS Transfer Request or an 853 Dual Entry CHESS to CHESS Fund Transfer Request matched with a counterparty request, BUT subsequently rejected by CHESS.



5.5.4. Unmatched Dual Entry Request [194-01] To notify a Participant that a transfer request previously submitted to CHESS has been processed but cannot currently be matched against a corresponding instruction from a counterparty.


Bit Position


21 Processing Timestamp 22 Character M 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M

Transmission Cut off times: None Prerequisites: Receipt of a 101 Dual Entry Settlement Instruction; or Receipt of a 005 Demand Dual Entry CHESS to CHESS Transfer Request; or Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request

5.5.5. Demand Dual Entry CHESS to CHESS Transfer Cancellation Request [037-01] To cancel a demand dual entry transfer request which has yet to be matched with a counterparty request.


Bit Position


48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M

Transmission Cut off times: None Prerequisites: Receipt of a 005 Demand Dual Entry CHESS to CHESS Transfer Request; or Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request



5.5.6. Cancelled Demand Dual Entry Transfer Request [048-01] To notify both Participants that an unmatched dual entry CHESS to CHESS transfer request has been cancelled as requested by the originator or as a result of CHESS housekeeping actions.


Bit Position


1 Bit Map 2 Marker On M 21 Processing Timestamp 22 Character M 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 89 Cancelling Transaction Id 16 Character M 129 Bit Map 4 Marker On M 127 Cancellation Reason 1 Character M

Transmission Cut off times: None Prerequisites: Receipt of a 005 Demand Dual Entry CHESS to CHESS Transfer Request and an associated 037 Demand Dual Entry CHESS to CHESS Transfer Request; or Receipt of an 853 Dual Entry CHESS to CHESS Fund Transfer Request and an associated 037 Demand Dual Entry CHESS to CHESS Transfer Request; or CHESS has received a 005 Demand Dual Entry CHESS to CHESS Transfer Request or an 853 Dual Entry CHESS to CHESS Fund Transfer Request that have remained unmatched as at the end of the next business day (or same day if day is a record date); i.e. CHESS has deleted the message due to routine housekeeping.



5.6. mFund Issuer Sponsored Fund to CHESS Transfer

CHESS

855 Issuer Sponsored Fund to CHESS Transfer Request (new)

720 Accepted Participant Request

Followed by either Registry authorisation:

CHESS 852 Effected Fund Transfer (new)

Participant

Participant

Participant

856 Issuer Sponsored Fund to CHESS Transfer Authorisation Request (new)

857 Registry Fund TransferAuthorisation (new)

722 Fund Response

Or Registry rejecting:

CHESS 860 Rejected Registry Authorisation

(new)Participant

859 Registry Fund TransferRejection (new)

722 Fund Response


Registry

Registry

Registry

Registry

Registry



5.6.1. Issuer Sponsored Fund to CHESS Transfer Request [855-01] The purpose of the transfer request is to enable fund units held on an Issuer Sponsored register to be transferred to the CHESS sub-register. The transfer request requires authorisation by the Registry. Note that the details are from the Transferee perspective.

The Participant is advised if the transfer request has been passed to the Registry or rejected by CHESS. The transfer request details are forwarded to the Registry.



Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 Receiving HIN 10 Numeric M 18 DRP Preference 1 Character M 25 Movement Reason 1 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 Securityholder Reference Number 12 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character M 231 Current PDS Provided 1 Character M 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric M 245 APIR Code 9 Character O



5.6.2. Issuer Sponsored Fund to CHESS Transfer Authorisation Request [856-01] The purpose of the message is to request a Registry to authorise an Issuer Sponsored Fund to CHESS transfer. The units being transferred will be added to the CHESS holding where the Registry authorises. Note that the details are from the Transferee perspective.


Transmission Cut off times: None Prerequisites: Receipt of a 855 Issuer Sponsored Fund to CHESS Transfer Request

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 Receiving HIN 10 Numeric M 18 DRP Preference 1 Character O 19 Receiving PID 5 Numeric M 21 Processing Timestamp 22 Character M 25 Movement Reason 1 Character M 35 Supplementary Reference 16 Character O 36 Broker Non Broker Indicator 1 Character M 48 Transaction Id 16 Character M 51 Securityholder Reference Number 12 Character M 59 Receiving Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character O 231 Current PDS Provided 1 Character O 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric O 245 APIR Code 9 Character O



5.6.3. Registry Fund Transfer Authorisation [857-01] The purpose of the message is to allow a Registry to authorise an Issuer Sponsored Fund to CHESS transfer request. The units being transferred will be added to the CHESS holding where the Registry authorises.

Sender: Registry Recipient: CHESS

Transmission Cut off times: None Prerequisites: Receipt of a 856 Issuer Sponsored Fund to CHESS Transfer Authorisation Request

5.6.4. Registry Fund Transfer Rejection [859-01] The purpose of the message is to allow a Registry to reject an Issuer Sponsored Fund to CHESS transfer request.


Transmission Cut off times: None Prerequisites: Receipt of a 856 Issuer Sponsored Fund to CHESS Transfer Authorisation Request

Bit Position


2 Fund Code 12 Character M 34 Registry Reference 16 Character O 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M 59 Delivering Registration Details 180 Character M

Bit Position


2 Fund Code 12 Character M 34 Registry Reference 16 Character O 37 Rejected Movement Reason 1 Character M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M



5.6.5. Rejected Registry Authorisation [860-01] The purpose of the message is to notify a Participant that a request has been rejected:

Transfer units from a CHESS HIN to an Issuer Sponsored holding Transfer units from an Issuer Sponsored holding to a CHESS HIN Election of DRP and/or RPP Preferences Provision of a periodic Income Statement


Transmission Cut off times: None Prerequisites: Receipt of a 859 Registry Fund Transfer Rejection Receipt of a 867 DRP RPP Registry Rejection Receipt of a 907 Income Statement Rejection

Bit Position


21 Processing Timestamp 22 Character M 34 Registry Reference 16 Character O 37 Rejected Registry Reason 1 Character M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M



5.6.6. Fund Response [722-01] An acknowledgment that a response from a Product Issuer Settlement Participant (PISP) or Registry has been received by CHESS

Sender: CHESS Recipient: PISP, Registry

Bit Position




Receipt of one of the following:

721 Fund to CHESS Conversion Authorisation 724 Fund to CHESS Conversion Rejection 729 Application Order / Payment Plan Application Response 732 Unit Adjustment 802 Redemption Order Response 808 Switch Order Response 857 Registry Fund Transfer Authorisation 859 Registry Fund Transfer Rejection



5.6.7. Accepted Participant Request [720-01] To notify a Participant that their request for any of the following transactions has been accepted:

Lodgement of an application to purchase fund units; or Redemption of fund units; or Switch of units between funds; or Cancellation of a Redemption or Switch order that was previously placed ‘On-Hold’ by the

Product Issuer Settlement Participant; or Issuer Sponsored Fund to CHESS Conversion Request; or Issuer Sponsored Fund Holding Balance request; or Issuer Sponsored Fund to CHESS Transfer Request; or CHESS to Issuer Sponsored Fund Transfer Request; or DRP RPP Election Request; or Income Statement Request



Receipt of one of the following:

718 Issuer Sponsored Fund to CHESS Conversion Request 726 Application Request 800 Redemption Request 804 Funds Order Cancellation Request 806 Switch Request 837 Participant to CHESS Fund Balance Request 855 Issuer Sponsored Fund to CHESS Transfer Request 861 CHESS to Issuer Sponsored Fund Transfer Request 863 DRP RPP Election Request 869 Income Statement Request

Bit Position





5.7. mFund CHESS to Issuer Sponsored Fund Transfer

CHESS

861 CHESS to Issuer Sponsored FundTransfer Request (new)


Followed by either Registry authorisation:

CHESS 852 Effected Fund Transfer (new)

Participant

Participant

Participant

858 CHESS to Issuer Sponsored Fund Transfer Authorisation Request (new)

857 Registry Fund TransferAuthorisation (new)

722 Fund Response


CHESS 860 Rejected Registry Authorisation

(new)Participant

859 Registry Fund TransferRejection (new)

722 Fund Response


Registry

Registry

Registry

Registry

Registry



5.7.1. CHESS to Issuer Sponsored Fund Transfer Request [861-01] The purpose of the transfer request is to enable fund units held on the CHESS sub-register to be transferred an Issuer Sponsored register. Note that the details are from the Transferee perspective.

The Participant is advised if the transfer request has been passed to the Registry or rejected by CHESS. The transfer request details are forwarded to the Registry.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 17 Delivering HIN 10 Numeric M 18 DRP Preference 1 Character O 25 Movement Reason 1 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 48 Transaction Id 16 Character M 51 Securityholder Reference Number 12 Character O 59 Receiving Registration Details 180 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number/ABN 1 12 Character O 101 Tax File Number/ABN 2 12 Character O 102 Tax File Number/ABN 3 12 Character O 129 Bit Map 4 Marker On M 193 Bit Map 5 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML/CTF Flag 1 Character M 231 Current PDS Provided 1 Character M 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric M 245 APIR Code 9 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O 278 Tax Identifier 1A 16 Character O



Bit Position






5.7.2. CHESS to Issuer Sponsored Fund Transfer Authorisation Request [858-01] The purpose of the message is to request a Registry to authorise a CHESS to Issuer Sponsored Fund transfer. The units being transferred will be removed from the CHESS holding where the Registry authorises. Note that the details are from the Transferee perspective.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 17 Delivering HIN 10 Numeric M 18 DRP Preference 1 Character O 21 Processing Timestamp 22 Character M 25 Movement Reason 1 Character M 35 Supplementary Reference 16 Character O 36 Broker Non Broker Indicator 1 Character M 48 Transaction Id 16 Character M 51 Securityholder Reference Number 12 Character O 59 Receiving Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 94 Date of Birth 1 8 Numeric O 95 Date of Birth 2 8 Numeric O 98 Date of Birth 3 8 Numeric O 100 Tax File Number / ABN 1 12 Character O 101 Tax File Number / ABN 2 12 Character O 102 Tax File Number / ABN 3 12 Character O 129 Bit Map 4 Marker On M 193 Bit Map 5 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 209 AML / CTF Flag 1 Character O 231 Current PDS Provided 1 Character O 232 Number of Units 18 Numeric, 6 Decimal M 236 PDS Issue Date 8 Numeric O 245 APIR Code 9 Character O 265 Account Type 1 Character O 266 US Citizen 1 Character O 267 Foreign Tax Resident 1 Character O 276 Foreign Tax Resident Codes 1 9 Character O 277 Foreign Date of Birth 1 8 Numeric O



Transmission Cut off times: None Prerequisites: Receipt of a 861 CHESS to Issuer Sponsored Fund Transfer Request

278 Tax Identifier 1A 16 Character O 279 Tax Identifier 1B 16 Character O 280 Tax Identifier 1C 16 Character O 281 Foreign Tax Resident Codes 2 9 Character O 282 Foreign Date of Birth 2 8 Numeric O 283 Tax Identifier 2A 16 Character O 284 Tax Identifier 2B 16 Character O 285 Tax Identifier 2C 16 Character O 286 Foreign Tax Resident Codes 3 9 Character O 287 Foreign Date of Birth 3 8 Numeric O 288 Tax Identifier 3A 16 Character O 289 Tax Identifier 3B 16 Character O 290 Tax Identifier 3C 16 Character O 291 Additional Foreign Parties 1 Character O



5.8. Changed Recipient for CHESS message MT716 / MT719

5.8.1. CHESS Conversion Request to Issuer Sponsored Fund [716-01] To notify a Registry of the details of a CHESS to Issuer Sponsored Fund Conversion Request that the Fund Units being converted have been deducted from the CHESS holding.

Note: To notify the Registry of the details of the CHESS to Issuer Sponsored Fund Conversion Request that was initiated by ASX Settlement.


Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 17 Delivering HIN 10 Numeric M 20 Delivering PID 10 Numeric M 21 Processing Timestamp 22 Character M 25 Movement Reason 1 Character M 34 Participant Reference 16 Character O 35 Supplementary Reference 16 Character O 36 Broker Non Broker Indicator 1 Character M 48 Transaction Id 16 Character M 51 Securityholder Reference Number 12 Character O 59 Delivering Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 100 Tax File Number/ABN 1 12 Character O 101 Tax File Number/ABN 2 12 Character O 102 Tax File Number/ABN 3 12 Character O 129 Bit Map 4 Marker On M 200 Email Address 50 Character O 208 Email Purpose 1 Character O 232 Number of Units 18 Numeric, 6 Decimal M 245 APIR Code 9 Character O

Transmission Cut off times: None Prerequisites: Receipt of a 715 CHESS to Issuer Sponsored Fund Conversion Request message submitted by a Participant

Action by ASX Settlement



5.8.2. Issuer Sponsored Fund to CHESS Conversion Authorisation Request [719-02] To request a Production Issuer Settlement Registry to authorise an Issuer Sponsored Fund to CHESS Conversion Request received from a Participant.

Sender: CHESS Recipient: Product Issuer Settlemen(PISP)Registry

Transmission Cut off times: None Prerequisites: Receipt of a 718 Issuer Sponsored Fund to CHESS Conversion Request

Bit Position


1 Bit Map 2 Marker On M 2 Fund Code 12 Character M 16 Receiving HIN 10 Numeric M 19 Receiving PID 5 Numeric M 21 Processing Timestamp 22 Character M 25 Movement Reason 1 Character M 36 Broker non Broker Indicator 1 Character M 48 Transaction Id 16 Character M 51 SecurityHolder Reference Number 12 Character M 59 Receiving Registration Details 180 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 209 AML/CTF Check Flag 1 Character M 210 FATCA Questions 1 Character M 232 Number of Units 18 Numeric; 6 decimal M 245 APIR Code 9 Numeric O



5.9. DRP / RPP Election

CHESS

000 DRP RPP Election Request (new)

000 Accepted DRP RPP ElectionRequest (new)Participant

Participant Registry000 DRP RPP ElectionAuthorisation (new)

CHESS

863 DRP RPP Election Request (new)


Followed by either Registry acceptance:

CHESS

866 Accepted DRP RPP Election Request (new)

Participant

Participant

Participant

864 DRP RPP Election Authorisation Request

(new)

865 DRP RPP RegistryAuthorisation (new)

762 Effected Registry Transaction

Or Registry rejection:

CHESS

860 Rejected Registry Authorisation

(new)Participant


Registry

Registry

Registry

Registry

Registry

867 DRP RPP RegistryRejection (new)



5.9.1. DRP RPP Election Request [863-01] To allow a Participant to request the amendment of an investor’s Dividend Reinvestment Plan (DRP) or Regular Payment Plan (RPP) preferences.

Where the Holder DRP Preference value is ‘P’ (Partial); DRP Units Participating must be populated.

Where the Holder RRP Preference value is ‘Y’, both RPP Amount and RPP Frequency must be populated.

Where a DRP or RPP preference is ‘N’ (cash), the Bank Account details must be entered.

For mFund securities, the Participant would have indicated an investor’s initial DRP Preference and bank account details via MT726 Application Request. This function allows the DRP Preference to be amended.


Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 16 HIN 10 Numeric M 19 PID 5 Numeric M 25 Holder DRP Preference 1 Character O 36 Holder RPP Preference 1 Character O 48 Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 232 DRP Units Participating 18 Numeric, 6 Decimal O 235 RPP Frequency 1 Character O 237 RPP Amount 15 Numeric, 2 Decimal O 245 APIR Code 9 Character O




5.9.2. DRP RPP Election Authorisation Request [864-01] To request Registry approval of a Participant request to amend an investor’s Dividend Reinvestment Plan (DRP) or Regular Payment Plan (RPP) preferences.

For mFund securities, the Participant would have indicated an investor’s initial preference for both DRP and RPP via the MT726 Application Request. This function allows those preferences to be amended.


Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 16 HIN 10 Numeric M 19 PID 5 Numeric M 21 Processing Timestamp 22 Character M 25 Holder DRP Preference 1 Character O 36 Holder RPP Preference 1 Character O 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 201 BSB Number 7 Character O 203 Account Number 9 Character O 204 Account Name 32 Character O 205 Account Purpose 1 Character O 232 DRP Units Participating 18 Numeric, 6 Decimal O 235 RPP Amount 15 Numeric, 2 Decimal O 237 RPP Frequency 1 Character O 245 APIR Code 9 Character O

Transmission Cut off times: None Prerequisites: Receipt of a 863 DRP RPP Election Request



5.9.3. DRP RPP Registry Authorisation [865-01] Acceptance of a Participant request for amendments to an investor’s DRP and/or RPP preferences.

Sender: Registry

Recipient: CHESS

Bit Position


48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M


None Prerequisites: Receipt of a 864 DRP RPP Election Authorisation Request

5.9.4. Accepted DRP RPP Election Request [866-01] To notify a Participant that a request to amend an investor’s DRP and/or RPP preferences has been accepted by the Registry.

Sender: CHESS

Recipient: Participant

Bit Position




None Prerequisites: Receipt of a 865 DRP RPP Registry Authorisation



5.9.5. DRP RPP Registry Rejection [867-01] Registry rejection of a Participant request for amendments to an investor’s DRP and/or RPP preferences.

Sender: Registry

Recipient: CHESS

Bit Position


37 Rejected DRP RPP Reason 1 Character M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M


None Prerequisites: Receipt of a 864 DRP RPP Registry Authorisation Request

5.9.6. Effected Registry Transaction [762-01] To notify a registry that a message previously submitted by the Registry has been processed successfully.

Sender: CHESS

Recipient: Registry

Bit Position




None Prerequisites: Receipt of a 759 Holding Advice Acceptance; or Receipt of a 813 Income Statement; or Receipt of a 865 DRP RPP Registry Authorisation; or Receipt of a 867 DRP RPP Registry Rejection; or Receipt of a 881 Income Statement Authorisation; or Receipt of a 907 Income Statement Rejection



5.10. Income Statement The existing mFund Distribution Statement function allowed a PISP to initiate the distribution of Income Statement details to a Participant for their clients. Changes will now enable Participants to request specific Income Statement details by HIN and Fund Code. The request will be directed to the Registry, not the PISP.

The 813 Distribution Statement will be renamed 813 Income Statement and the 816 Distribution Statement Advice will be renamed 816 Income Statement Advice

CHESS

869 Income Statement Request (new)


Followed by either Registry accepting:

CHESS 884 Accepted IncomeStatement Request (new)

Participant

Participant

Participant

868 Income StatementAuthorisation Request (new)

881 Income Statement Authorisation (new)



CHESS 860 Registry Authorisation Rejection

(new)Participant

907 Income Statement Rejection (new)


Registry

Registry

Registry

Registry

Registry

Following Registry acceptance

CHESS

816 Income StatementAdvice (modified)Participant Registry813 Income Statement

(modified)

Registry762 Effected Registry Transaction



5.10.1. Income Statement Request [869-01] The purpose of the income statement selection request is to enable a Participant, on behalf of an investor, to request an income statement from a Registry.

The Participant may select the report as an on-demand report or as a regular standing report.

The Participant is advised where the request has been accepted or rejected.

Sender: Participant

Recipient: CHESS

Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 16 HIN 10 Numeric O 25 Income Statement Report Type 1 Character M 48 Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 245 APIR Code 9 Character O


None Prerequisites: None



5.10.2. Income Statement Authorisation Request [868-01] The notify a Registry that a Participant has requested an income statement on behalf of an investor. Based on this request, the Registry is expected to accept or reject the request to provide a periodic Income Statement.

Additionally the Participant may select an on-demand report or a regular standing report.


Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 16 HIN 10 Numeric O 19 PID 5 Numeric M 21 Processing Timestamp 16 Character M 25 Income Statement Report Type 1 Character M 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 245 APIR Code 9 Character O

Transmission Cut off times: None Prerequisites: Receipt of a 869 Income Statement Request



5.10.3. Income Statement Authorisation [881-01] To accept a Participant request for an Income Statement.

Sender: Registry

Recipient: CHESS

Bit Position


19 Target UIC 5 Numeric M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M


None Prerequisites: Receipt of an 868 Income Statement Authorisation Request.

5.10.4. Accepted Income Statement Request [884-01] To accept a Participant request for an Income Statement.

Sender: CHESS

Recipient: Participant

Bit Position


21 Processing Timestamp 22 Character M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M


None Prerequisites: Receipt of an 881 Income Statement Authorisation



5.10.5. Income Statement Rejection [907-01] To notify the rejection of a Participant request for an Income Statement.

Sender: Registry

Recipient: CHESS

Bit Position


19 Target UIC 5 Numeric M 37 Rejected Income Statement Reason 1 Character M 48 Transaction Id 16 Character M 49 Target Transaction Id 16 Character M


None Prerequisites: Receipt of an 868 Income Statement Authorisation Request.



5.10.6. Income Statement [813-01] The purpose of this message is to provide a requesting Participant with a statement of an investor’s s based on the parameters selected through the Income Statement Selection function.


Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 3 Gross Income Amount 15 Numeric, 2 Decimal M 11 Income Notification Flag 1 Character M 16 HIN 10 Numeric M 19 PID 5 Numeric M 48 Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 221 Income Amount Per Unit 11 Numeric, 6 Decimal O 223 Tax Deducted 15 Numeric, 2 Decimal O 224 Nett Amount 15 Numeric, 2 Decimal O 232 Units Participating 18 Numeric, 6 Decimal O 237 Fees 15 Numeric, 2 Decimal O 242 Payment Date 8 Numeric M 244 Record Date 8 Numeric M 245 APIR Code 9 Character O

Transmission Cut off times: None Prerequisites: Receipt of an 884 Accepted Income Statement Request



5.10.7. Income Statement Advice [816-01] The purpose of this message is to provide a requesting Participant with a statement of an investor’s income based on the parameters selected through the Income Statement Selection function.


Bit Position


1 Bit Map 2 Marker On M 2 Security Code 12 Character M 3 Gross Income Amount 15 Numeric, 2 Decimal M 11 Income Notification Flag 1 Character M 16 HIN 10 Numeric M 21 Processing Timestamp 22 Character M 48 Transaction Id 16 Character M 62 Origin Transaction Id 16 Character M 65 Bit Map 3 Marker On M 129 Bit Map 4 Marker On M 221 Income Amount Per Unit 11 Numeric, 6 Decimal O 223 Tax Deducted 15 Numeric, 2 Decimal O 224 Nett Amount 15 Numeric, 2 Decimal O 232 Units Participating 18 Numeric, 6 Decimal O 237 Fees 15 Numeric, 2 Decimal O 242 Payment Date 8 Numeric M 244 Record Date 8 Numeric M 245 APIR Code 9 Character O 250 Tax Credit Amount 15 Numeric, 2 Decimal O

Transmission Cut off times: None Prerequisites: Receipt of an 813 Income Statement



6. Appendices

6.1. Appendix 1: Foreign Tax Status Determination The structure offers 3 groups (Group 1, Group 2, Group 3); allowing up to 3 Foreign Tax Residents per Account Type to be identified.

US Citizen Foreign Tax Resident Foreign Date of Birth Foreign Tax Resident Codes* Tax Identifier A-C

Account Type

I (individual) Y Y Mandatory Must state USA (Group1) Optional

I (individual) N Y Mandatory One per foreign tax residency (Group 1) Optional

I (individual) N N No requirements

J (Joint) Y Y Mandatory Must state USA (Group 1) Optional

J (Joint) N Y Mandatory One per foreign tax residency (Group 1) Optional

J (Joint) N N No requirements

S (Superannuation Fund) Y Y No requirement Optional Optional

S (Superannuation Fund) N Y No requirement Optional Optional

S (Superannuation Fund) N N No requirements

O (Other Entity) Y Y Optional Must state USA (Group1) Optional

O (Other Entity) N Y Optional One per foreign tax residency (Group 1) Optional

O (Other Entity) N N No requirements

* Up to 3 X 3 Character ISO Country Codes may be entered per Foreign Tax Resident



6.2. Appendix 2: CHESS Field Definitions Account Type Format 1 Character Definition Indicates the type of business entity for regulatory foreign tax status

determination. Allowable Values ‘I’ = Individual ‘J’ = Joint Account ‘S’ = Superannuation Fund ‘O’ = Other Entity

‘U’ = Unknown or data unavailable (MT512 only) Additional Foreign Parties Format 1 Character Definition Indicates that there are more than 3 Foreign Tax Residents associated with

an account (refer Account Type). Allowable Values ‘Y’ = Yes ‘N’ = No DRP Units Participating Format 18 Numeric, 6 decimal Definition The number of units that an investor wishes to include in a DRP

arrangement. Allowable Values Foreign Date of Birth 1 Format 8 Numeric Definition Specifies the birth date of a Foreign Tax Resident. Allowable Values (See Date)

Foreign Date of Birth 2 Format 8 Numeric Definition Specifies the birth date of a Foreign Tax Resident. Allowable Values (See Date) Foreign Date of Birth 3 Format 8 Numeric Definition Specifies the birth date of a Foreign Tax Resident. Allowable Values (See Date) Foreign Tax Resident Format 1 Character Definition Identifies an investor as a Foreign Tax Resident for tax reporting purposes. Allowable Values ‘Y” = Yes ‘N’ = No

‘U’ = Unknown or data unavailable (MT512 only) Foreign Tax Resident Codes 1 Format 9 Character Definition Identifies up to 3 tax residencies for a holder Allowable Values 3 Character ISO Country Codes



Foreign Tax Resident Codes 2 Format 9 Character Definition Identifies up to 3 tax residencies for a joint holder Allowable Values 3 Character ISO Country Codes Foreign Tax Resident Codes 3 Format 9 Character Definition Identifies up to 3 tax residencies for a joint holder Allowable Values 3 Character ISO Country Codes Gross Distribution Income Amount Format 15 Numeric, 2 decimal Definition The gross dollar value of an Fund income distribution in CHESS. Allowable Values Holder DRP Preference Format 1 Character Definition Identifies the investor preference as regards a Reinvestment Plan (DRP). Allowable Values ‘F’ = Full ‘P’ = Partial

‘N’ = No Holder RPP Preference Format 1 Character Definition Identifies the investor preference as regards a Regular Payment Plan (RPP). Allowable Values ‘Y’ = Yes

‘N’ = No Distribution Income Amount per Unit Format 11 Numeric, 6 decimal Definition The amount in cents that will be applied to each Fund unit held by a holder

as the result of an Fund income distribution payment. Allowable Values Distribution Income Notification Flag Format 1 Character Definition The state of the Distribution Income Statement Advice; whether it is the initial

advice or a subsequent amended advice. Allowable Values ‘I” = Initial ‘A’ = Amendment Income Statement Report Type Format 1 Character Definition Identifies whether the income statement details are to be provided as an on-

demand report or as a regular standing report. Allowable Values ‘A” = On-demand ‘S’ = Standing Rejected DRP RPP Reason Format 1 Character Definition Identifies the reason a Registry has rejected a request for a DRP or RPP

preference to be amended. Allowable Values TBD



Rejected Income Statement Reason Format 1 Character Definition Identifies the reason a Registry has rejected a request for an Income

statement preference to be amended. Allowable Values TBD Rejected Registry Reason Format 1 Character Definition Identifies the reason a Registry has rejected a request. Allowable Values TBD RPP Amount Format 15 Numeric, 2 decimal Definition The RPP amount that an investor wishes to invest in additional units based

on the RPP Frequency. Allowable Values RPP Frequency Format 1 Character Definition Identifies the frequency with which an investor wishes to invest in additional

units. Allowable Values ‘W’ = Weekly

‘M’ = Monthly ‘Q’ = Quarterly

Sophisticated Investor Format 1 Character Definition Identifies a Holder (HIN) as a ‘Sophisticated Investor’; allows access to a

wider range of financial products. Allowable Values ‘Y” = Yes ‘N’ = No

‘U’ = Unknown or data unavailable (MT512 only) Tax Identifier 1A - Tax Identifier 3C Format 16 Character Definition Identifies the foreign tax identifier for a foreign tax resident.

As an example, for US Citizens a valid Tax Identifier may be one of: Social Security Number SSN Employer Identification Number EIN Individual Taxpayer Identification Number ITIN Taxpayer Identification Number for Pending U.S. Adoptions ATIN Preparer Taxpayer Identification Number PTIN

Allowable Values US Citizen Format 1 Character Definition Identifies an investor as a US citizen for US tax reporting purposes (FATCA

related). Allowable Values ‘Y” = Yes ‘N’ = No ‘U’ = Unknown or data unavailable (MT512 only)

http://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-(TIN)#ssn

http://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-(TIN)#ein

http://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-(TIN)#itin

http://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-(TIN)#atin

http://www.irs.gov/Individuals/International-Taxpayers/Taxpayer-Identification-Numbers-(TIN)#ptin



Disclaimer

This document provides general information only and may be subject to change at any time without notice. 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 this 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. The information in this document is not a substitute for any relevant operating rules, and in the event of any inconsistency between this document and the operating rules, the operating rules prevail to the extent of the inconsistency.

ASX Trademarks

The trademarks listed below are trademarks of ASX. Where a mark is indicated as registered it is registered in Australia and may also be registered in other countries. Nothing contained in this document should be construed as being any licence or right to use of any trademark contained within the document.

ASX®, CHESS®

0554.15.05.a - attachment a chess release 9.0 … · date will be communicated by asx in the second...

Documents