Additional information regarding technical accreditation will be published in subsequent documentation, as per the Documentation Release Plan.

Table of Contents 1 Performing Message Accreditation 1.1 How to read 1.2 Performing messaging accreditation 1.2.1 Providing test evidence

Table of Contents 1 Performing Message Accreditation 1.1 How to read 1.2 Performing messaging accreditation 1.2.1 Providing test evidence

Performing Message Accreditation

Software providers can determine which functions they will need to be accredited for based on the CHESS User type their system will be supporting, as outlined in the CHESS User by Function table. Message accreditation scripts will be provided for each function and contain scenarios to test all relevant features. For example, the Account function is supported by 12 features, including Account and Holder Creation, Account and Holder Modification, Account and Holder Locking and Unlocking etc. The list of supporting features for each functions can be located in the CHESS User by Feature, Message Message table.

Where a software provider is developing services for more than one CHESS user type, and where a scenario are duplicated in the message accreditation scripts across the CHESS user types, it will be sufficient to only perform one scenario test. For example, it a software provider is accredited in the capacity of a Clearing & Settlement Participant, their system will also meet accreditation for Settlement and Account Participants assuming that the underlying scenarios as per test scripts are the same across all CHESS User scripts.

To ensure all appropriate scenarios are covered and all accreditation requirements are met we request that system providers notify the ASX which CHESS User types that their system will provide services for.

How to read

Message accreditation scripts will identify the required test scenarios and will be available in excel format to assist with filtering and editing. Each message accreditation scripts will contain the below content.

Content	Explanation
Scenario Code	Identifies the test case number. Scenario Code will contain representation of CHESS User type, function and a sequence number for each script.
Feature	Identifies the feature the test relates to.
Scenario	Describes the test case.
Required Fields	Lists the fields that must be included to meet the acceptance criteria. ASX element names are used to list required fields.
Value	Identifies explicit values to populate when required to determine scenario outcome. Where blank, system vendor can determine values.
Optional Fields	Identifies optional fields to include in the message. Acceptance Criteria will not validate against these fields. This column will be removed in next update of Accreditation Scripts.
Supplementary Information	Identifies notes or hints for successful testing, for example, message will be sent after EOD.
ISO 20020 Message - Sender	Identifies the party responsible for sending the message.
ISO 20022 Message -Recipient	Identifies the party responsible for receiving the message.
ISO 20022 - Message Reference	Identifies the message name and provides a link to the related messaging content on the ASX Technical Documentation portal.
Acceptance Criteria	Conditions required for a successful scenario (excludes optional criteria except when optional criteria drives functionality, or impacts production).
Business Message Identification	The business message identification must be provided by the system vendor for each scenario, so that ASX accreditation verification can be performed. This identifier is the basis for ASX scenario verification.
Security Code	Identifies the security in which units are being transferred. Either a Security Code, an ISIN or both elements may be populated. Where both elements are present, the ISIN and Security Code must refer to the same security. Refer to ISO 20022 Messaging - TM - Security Identification (ISIN and Security Code) for additional details on Security Code and ISIN.

Performing messaging accreditation

Software providers are will be requested to schedule their message accreditation directly with ASX Customer Technical Support team at CTS@asx.com.au and include the following information:

CHESS User type/s to be accredited for

Current software version

Further information on this process and scheduling will be available in a subsequent release.

Software providers are required to perform messaging accreditation in the Industry Test Environment (ITE).

Providing test evidence

As part of the accreditation process, software providers will be required to evidence each required scenario within a test script by providing the submitting message Business Message Identification for ASX to review. This information can be added to the test script in the designated column. Further details on this process will be provide in a subsequent release.