Skip to content
Finance & Wealth

Comprehensive ASX DCC Overview: Navigating the New Data Communications Core

In this article

The ASX DCC (Data Communications Core) is the foundational connectivity and messaging layer designed to support the Australian Securities Exchange’s modernized post-trade infrastructure. It provides the high-performance gateway through which market participants access clearing, settlement, and sub-register services, facilitating the transition from legacy protocols to global ISO 20022 standards as part of the CHESS replacement program.

The landscape of the Australian financial markets has undergone a significant architectural shift. For decades, the Clearing House Electronic Subregister System (CHESS) served as the backbone of the Australian Securities Exchange (ASX). However, the move toward a more modular, resilient, and standardized environment led to the development of the Data Communications Core (DCC). As we operate in 2026, the DCC has become the primary conduit for interaction between the ASX and its diverse range of stakeholders, including clearing participants, settlement agents, and share registries.

The Evolution of ASX Infrastructure: From Legacy to DCC

To understand the ASX DCC, one must first look at the history of the CHESS replacement project. Following the 2022 pause of the original distributed ledger technology (DLT) solution, the ASX pivoted to a modular approach. This new strategy, developed in partnership with Tata Consultancy Services (TCS), prioritized a robust communication layer that could support multiple functional modules without the rigid dependencies of the previous architecture.

The DCC represents the "logical" layer of this new infrastructure. While the physical connectivity—the cables and data centers—often relies on the established ASX Net or co-location services, the DCC governs how data is packaged, secured, and routed. It serves as the translator between the internal ASX engines (responsible for complex tasks like netting and risk management) and the external systems managed by brokerage firms and custodians.

The Role of ISO 20022 in the DCC

A cornerstone of the ASX DCC is the adoption of the ISO 20022 messaging standard. Historically, CHESS used proprietary EIS (Electronic Interface Standard) messages, which were unique to the Australian market and required bespoke software to interpret.

By utilizing ISO 20022 within the DCC framework, the ASX has aligned itself with global financial standards. This transition allows participants to:

  1. Reduce Translation Risk: Using a global standard minimizes the need for complex "mappers" between international and local systems.
  2. Improve Data Richness: ISO 20022 messages can carry more metadata than legacy formats, facilitating better regulatory reporting and corporate action processing.
  3. Enhance Automation: Standardized schemas allow for easier implementation of Straight-Through Processing (STP), reducing manual intervention in the settlement cycle.

Core Architectural Components of the DCC

The ASX DCC is not a single piece of hardware but a sophisticated stack of software and networking protocols. It is designed to be "vendor-neutral" in its external interface, meaning that while the internal engines might change, the way participants talk to the exchange remains stable.

1. The Messaging Gateway

The gateway is the entry point for all participant traffic. It performs initial validation, ensuring that messages are correctly formatted and that the sender has the appropriate permissions. In the 2026 environment, these gateways are optimized for low latency, ensuring that clearing and settlement instructions are acknowledged in near real-time.

2. Digital Identity and Security

Security within the DCC is paramount. It utilizes modern encryption standards and digital signatures to ensure non-repudiation. Every instruction sent through the DCC is cryptographically linked to the participant, preventing unauthorized access and ensuring that the "Golden Record" of share ownership remains untampered.

3. Queue Management

Financial markets experience bursts of high activity, particularly during market open, close, or periods of high volatility. The DCC includes advanced queue management systems that prevent the core clearing engines from being overwhelmed. This ensures that even if one participant's system experiences a technical failure, the rest of the market remains unaffected.

ASX CGC Guidance: 8 Principles & 35 Recommendations Overview - Studocu
ASX CGC Guidance: 8 Principles & 35 Recommendations Overview - Studocu

Connectivity Methods: How Firms Access the DCC

Market participants have several options for connecting to the ASX DCC, depending on their volume of trade, latency requirements, and physical location.

ASX Net

ASX Net is the exchange’s managed private network. It provides a dedicated, high-availability link between the participant’s data center and the ASX. For most medium-to-large clearing participants, ASX Net is the preferred method for DCC access because it offers guaranteed bandwidth and is fully managed by the ASX technical team.

Co-location (ALC)

For firms requiring the lowest possible latency, connecting to the DCC from within the Australian Liquidity Centre (ALC) is the gold standard. By placing their servers in the same physical facility as the ASX matching and clearing engines, firms can reduce the physical travel time of data (latency) to microseconds.

External Network Providers (ENPs)

Some participants choose to access the DCC through third-party ENPs. These providers offer a shared infrastructure that can be more cost-effective for smaller firms or those with lower transaction volumes. The ENP handles the technical requirements of the DCC connection on behalf of the participant.

Feature ASX Net Co-location (ALC) External Network Providers
Primary User Clearing Participants High-Frequency Traders/Large Banks Small Brokers/Registries
Latency Low Ultra-Low Moderate
Management Managed by ASX Managed by Participant/ASX Managed by Third Party
Cost Structure Monthly Lease Cabinet Fee + Cross-connect Service Fee
Reliability Very High (Redundant) Highest Variable

Operational Requirements and Technical Specifications

Transitioning to or maintaining a connection with the ASX DCC requires adherence to specific technical standards. As of 2026, the following specifications are mandatory for all participants interacting with the core.

Protocols and API Access

The DCC supports multiple interaction patterns:

  • Synchronous APIs: Used for real-time queries, such as checking a participant’s current collateral balance or position.
  • Asynchronous Messaging: Used for the bulk of clearing and settlement instructions, where the system processes the request and sends a confirmation later.

Hardware and Software Prerequisites

While the DCC aims for software neutrality, participants must typically run a DCC-compatible Gateway Client. This software handles the encryption and the "handshake" with the ASX. Hardware must support modern TLS (Transport Layer Security) versions and have sufficient processing power to handle high-frequency ISO 20022 XML parsing.

The Impact of DCC on the Clearing and Settlement Cycle

The implementation of the DCC has fundamentally changed the "day in the life" of an Australian trade. Before the DCC and the modular CHESS replacement, the system was often described as a "black box." The DCC provides greater visibility into the lifecycle of a trade.

Real-Time Data Dissemination

One of the primary benefits of the DCC architecture is the ability to provide real-time data updates. When a trade is cleared, the DCC ensures that the updated position is reflected almost immediately across the participant's view. This reduces the "overnight" risk that was prevalent in older settlement systems.

Improved Corporate Actions

Corporate actions—such as dividends, rights issues, and stock splits—have historically been manual-heavy processes. The DCC’s rich data format allows the ASX to broadcast corporate action details in a structured way that participant systems can ingest automatically. This reduces the likelihood of errors that can lead to financial loss or regulatory scrutiny.

Costs and Fee Structures in 2026

Accessing the ASX DCC involves several layers of costs. These are generally divided into technical access fees and transactional fees.

  1. Technical Access Fees: This covers the physical or virtual "pipe" into the DCC. Costs vary based on the bandwidth required (e.g., 1Gbps vs. 10Gbps) and the type of connection (ASX Net vs. ALC).
  2. Messaging Fees: The ASX employs a fee structure based on the volume of ISO 20022 messages processed. In 2026, there are often incentives for "clean" messaging—firms that send fewer rejected or malformed messages may receive rebates.
  3. Testing and Certification Fees: Before a firm can connect to the production DCC environment, they must pass rigorous testing in the ASX Customer Development Service (CDS). There are costs associated with maintaining these testing environments.

For a detailed breakdown of current pricing, participants should consult the ASX Managed Solutions Price List.

Troubleshooting and Participant Support

Maintaining a 24/7 connection to the DCC is a critical requirement for market stability. The ASX provides several tools for participants to monitor their DCC health:

  • ASX Service Desk: A dedicated 24-hour technical support team available for connectivity issues.
  • DCC Dashboard: A real-time portal where participants can see the status of the DCC gateways and their own connection heartbeat.
  • Message Reconciliation Tools: In the event of a disconnect, these tools allow participants to "replay" messages to ensure no data was lost during the outage.

Common Connectivity Issues

  1. Certificate Expiry: The most common cause of DCC connection failure is the expiration of digital identity certificates.
  2. Schema Mismatches: If a participant updates their internal software but fails to align with the latest ISO 20022 schema version released by the ASX, messages will be rejected by the DCC gateway.
  3. Network Latency Spikes: Congestion on a participant’s internal network can lead to DCC timeouts, which the system may interpret as a connection failure.

Future Outlook: The DCC Beyond 2026

As the Australian market continues to evolve, the DCC is expected to expand its capabilities. Future roadmaps suggest the integration of more "T+0" (same-day) settlement capabilities and the potential for the DCC to handle a wider range of asset classes, including tokenized assets and carbon credits.

The modularity of the DCC ensures that the ASX can upgrade its internal engines—moving from the current TCS-based system to even more advanced technologies in the 2030s—without requiring every broker in Australia to rewrite their connectivity code. This "future-proofing" is perhaps the most significant legacy of the DCC project.

Frequently Asked Questions

What is the difference between ASX Net and ASX DCC? ASX Net is the physical telecommunications infrastructure (the network) provided by the ASX. The ASX DCC is the logical software layer (the core) that manages the messaging, security, and routing of data over that network. Think of ASX Net as the highway and the DCC as the traffic control system and the rules of the road.

Does every broker need to connect directly to the DCC? No. While clearing participants must have a connection to the DCC, smaller brokers or "Non-Principal" participants often use a third-party service bureau or a larger clearing house to handle their DCC interactions. This allows smaller firms to avoid the significant technical overhead of managing ISO 20022 infrastructure.

How does the DCC handle cybersecurity threats? The DCC utilizes a multi-layered security approach, including dedicated private network paths (avoiding the public internet), mutual TLS authentication, and digital signatures for every message. Furthermore, the ASX performs continuous monitoring for anomalous traffic patterns that might indicate a cyber-attack or a compromised participant system.

What happens to my connection if the ASX DCC goes down? The DCC is built with high redundancy. There are primary and secondary sites located in different geographic regions. In the event of a total site failure, the DCC is designed to failover to the secondary site with minimal data loss. Participants are required to maintain their own redundant connections to both ASX sites to ensure continuity.

Is the DCC compatible with the old CHESS EIS messages? No. The DCC is built specifically for modern standards like ISO 20022. While there was a transition period where translation services were available, the 2026 environment requires native or mapped ISO 20022 connectivity for all primary clearing and settlement functions.

Where can I find the technical documentation for DCC integration? Technical specifications, including the ISO 20022 message definitions and API documentation, are available through the ASX Technical Documentation Portal. Access to some documents may require a non-disclosure agreement (NDA) or an active participant agreement.

Practical Recommendation: For firms currently auditing their connectivity or planning a migration, the first step is to perform a Gap Analysis between your current messaging capabilities and the ISO 20022 standards required by the DCC. Ensure your technical team is subscribed to the ASX Technical Notices to receive updates on gateway maintenance and schema changes. If you are a high-volume participant, consider moving to a co-located solution in the ALC to maximize the efficiency of your DCC connection.