September 2020 - CDE Code Drop Notes

Code Drop 8

The release notes detail the scope of the eighth drop of CDE code, released on 11 September 2020, including details of the available functionality in the CDE environment. This CDE code drop is accompanied by the September 2020 What’s New documentation update. Full details of the functionality are provided below.

CDE Drop 8 includes breaking changes to both the Business Application Header (BAH) and Ledger API Connectivity. For further information, refer to the September 2020 What's New.


CDE Release

Technical Documentation Release

Supporting Documentation

DA SDK Version

CDE Release

Technical Documentation Release

Supporting Documentation

DA SDK Version

CDE Drop 8

April 2020
February 2020
January 2020

Known Issues & Limitations
Ledger API Connectivity
Manual Upload Tools
-| Trade Ingest API
-| Self-Service Holding Administration Locks
-| Self-Service Payment Authorisation of BDSI
-| Bilateral Demand Settlement Instruction
-| Change Margin Settlement Amount
-| BSSI Match & Cancellation
Code Change

DAML SDK: 1.4.0-snapshot.20200729.4851.0.224ab362
Bindings Rx Java: 1.4.0-snapshot.20200729.4851.0.224ab362 
DAML LF Archive: 1.4.0-snapshot.20200729.4851.0.224ab362
CSP Java Stubs [Updated 22/10]: 1.30.344.2

For further details refer to the Forward Release Plan.

Release Notes

Please note the following points for your consideration:

  • [Updated 21/09] On CDE reset, corporate actions with dates in the past will be removed from seeding to avoid incomplete corporate action lifecycles.

  • [Updated 17/09] To assist software provider testing of ISO message pagination the number of records included in the Netting Obligation Report (NOR) (sett_102) has been reduced from 100 to 10, software providers therefore can test pagination with a reduced number of trades. This value has been lowered in CDE8 for the purpose of testing, the number of trades which will be included in the production environment will be defined at a later date.

  • Opt-in ISO Message Signing is available. To opt-in to ISO Messaging signing in CDE, click here.

  • Takeover and Buy-back functionality introduced Bid Offerors. To opt-in as a Bid Offeror, click here.

  • Party Identification in CDE Drop 8 is limited to UIC format only. BIC support will be available in a subsequent release.

  • For Ledger API connectivity, both ISO 20022 ingress and egress instructions are supported. Please note, resultant state change contracts may be visible, but are not documented in this release and are subject to change.

  • Final security, resiliency and fail-over models are not present in the CDE Environment.

  • Transactional data may be lost in the event of a system restart or upgrade. The ASX will re-populate environments with seeded data.

  • For internal CDE maintenance, ASX may refresh environment every two weeks. ASX will always notify CDE Subscribers prior to any environment refresh.

  • As part of CDE Drop 7, CDE subscribers were unable to act as the ETO Clearing Member in the collateral management process via the Collateral Management Auto-Responder. This limitation has been resolved as part of CDE8. Refer to Collateral Creation / Removal for further details.

  • CDE Drop 8 includes an update to the Bilateral Demand Settlement Instruction workflow that now incorporates the Payment Provider Authorisation process.

  • CDE 8 includes a breaking change discussed in earlier ISO 20022 Technical Committees to include the Business Date in the Business Application Header (BAH). As such, the BAH version must be adjusted from v1 to v2 to use the new ISO schema. Further details are available in the September 2020 What's New.

Available Functionality



Release Notes



Release Notes

Holding Administration Locks

The ability to lock holdings of an account (the entire holding balance or a portion of the holding balance) in response to a request from an Issuer (Registry), ASX, Controlling Participant, Regulators or Law Enforcement Agencies.

CDE Drop 8 includes the workflow for Holding Administration Locking and Unlocking.

Call Payment (Partly Paid Securities)

The ability to process call payments (partly paid securities).

CDE Drop 8 includes the corporate action workflow for Call Payment (Partly Paid Securities).

Code Change

The ability to process a code change effected where a company name change gives rise to a change in Security Code for securities issued by that company.

CDE Drop 8 includes the corporate action workflow for Code Change.

Class Merger

The ability to process a class merger effected when an Issuer merges one Security Code with another when the securities rank equally.

CDE Drop 8 includes the corporate action workflow for Class Merger.

Diary Adjustments

The ability to apply and adjust outstanding settlement instructions should a transaction fail to settle by end of day on the record date.

CDE Drop 8 includes the corporate action workflow for Diary Adjustments.

Isolate Counterparty

The ability for a Clearing Participant (who is a Settlement Participant) or a Settlement Participant (acting on behalf of a Clearing Participant) due to receive units from a failed Novated Settlement Obligation to request isolation of a number of units together with the disclosure of the UIC of the failing Clearing/Settlement Participant

CDE Drop 8 includes the workflow for Isolate Counterparty.

Change Margin Settlement Amount

The ability for a Clearing Participant, while managing their daily margin obligations, to request a change in the Margin Settlement Amount.

CDE Drop 8 includes the cash market margin workflow for Change Margin Settlement Amount.

Payment Provider Authorisation for RTGS Payments for Bilateral Demand Settlement Instructions

The ability for participants to use the RTGS payment service for Bilateral Demand Settlement Instructions where the required arrangements and Payment Facility set-up has taken place between the Payment Provider and the Participant.

CDE Drop 8 includes the payment provider authorisation for RTGS payments workflow for Bilateral Demand Settlement Instructions.


The ability to receive reports on a daily basis from the CSP.

To enable Holding Movement (HMVT) and Cum Entitlement Movement (CEMV) reporting.

The Issuer (Registries) should use the Holding Adjustment Notification (hold_226) workflow to allow for applicable data to be available for these reports.


CDE Drop 8 includes the following Issuer (Registry) EOD reports:

  • Cum Entitlement Balance (CEBL);

  • Holding Movement (HMVT); and

  • Cum Entitlement Movement (CEMV).

These workflows include the End of Overnight Reporting Notification.

A sample of the AMO Security Details Report (AMOS) has been published as part of the AMO Overview.