Regulatory Reporting
This document outlines the reporting capabilities designed into the DEUSS platform from a business and regulatory perspective.
1. Executive Summary
DEUSS is a regulated financial infrastructure for tokenized fixed-income instruments (corporate bonds). The platform architecture has been designed to capture, store, and expose all data elements required for regulatory reporting under MiFID II/MiFIR, the EU DLT Pilot Regime.
The platform provides:
- Complete data capture across all relevant services (Registry, Payment, Indexer, Partner, Blockchain Event)
- Data mappings of source fields
- A proven report generation architecture
The operating entity is responsible for:
- Deploying and scheduling the report generators
- Configuring jurisdiction-specific parameters (LEI, MIC, country codes)
- Establishing submission channels to NCAs, ESMA, APAs, and CPTs
- Operating the Backoffice reporting workflows (cancellations, corrections)
2. Report Catalog
2.1 MiFIR Transaction Reporting (Art. 26 / RTS 22)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
currentTradeReport | After each trade (marketplace or OTC) or correction by Back Office | XML (ISO 20022) inside ZIP | NCA via ARM |
Data availability: All required fields are sourced from Payment Service, Registry Service, Indexer, and configuration. Key attributes include transaction reference, buyer/seller LEI, ISIN, price, quantity, net amount, venue MIC, trading date/time, and instrument classification. The report supports both NEWT (new) and CANC (cancellation) flows initiated by Back Office.
Operator responsibility: Schedule T+1 submission, configure ARM connection, manage CANC/correction workflows via Backoffice.
2.2 Financial Instrument Reference Data — FIRDS (Art. 27 / RTS 23)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
currentApprovedOrTradedBondsReport | Daily at 18:00 CET | XML (ISO 20022) inside ZIP | NCA / ESMA FIRDS |
Data availability: Covers all bonds with status PUBLISHED, ISSUED, SUSPENDED, REDEEMED, or REPLACED. Fields include ISIN, instrument full name, issuer LEI, trading venue MIC, admission dates, maturity, nominal value, currency, and fixed rate. Data sourced from Registry Service, Indexer (Bond entity and BondHistory), and Bond Issuance Service.
Operator responsibility: Deploy the daily scheduled job, configure ESMA submission credentials, handle incremental report numbering.
2.3 Post-Trade Transparency — APA / CPT (RTS 2 / Art. 10, 21 MiFIR)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
eachTradeReportForAPA_OR_CPT | After each trade (marketplace or OTC), or manually by Back Office | Database entry → venue data feed | APA or Consolidated Tape Provider |
Data availability: Captures trading date/time, ISIN, price, quantity, notional amount, venue MIC, and applicable flags/waivers. Price notation distinguishes marketplace trades (monetary value) from OTC (NOAP). Data sourced from Payment Service, Indexer (MarketDeal, MarketOffer, Bond), and Transfer Events.
Operator responsibility: Establish APA/CPT data feed connection, configure real-time or near-real-time publication, manage deferral flags for large-in-scale transactions.
2.4 Internal Order Record Keeping (RTS 24 / RTS 25)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
eachTradeInstructionReport | On each new MarketOffer (seller) or MarketDeal (buyer) creation | Database entry (retained for regulator on request) | Internal — available to NCA upon request |
Data availability: Full order lifecycle captured: client LEI, order type, limit price, validity period, ISIN, buy/sell indicator, order status (ACTI/INAC), initial and remaining quantities, traded quantity. Event tracking per order: new order, modification, cancellation, expiry, partial fill, full fill — each with timestamp and sequence number. Data sourced from Indexer (MarketOffer, MarketOfferHistory, MarketDeal, MarketDealHistory).
Operator responsibility: Ensure retention per regulatory requirements (minimum 5 years), provide export capability for NCA inspections, optionally implement PDF/CSV export for manual review.
2.5 Trading Venue Status Report — CPT Data Feed
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
tradingVenueStatusReport | On trading venue status change | Database entry → CPT venue data feed | Consolidated Tape Provider |
Data availability: Reports venue MIC, trading system type (OTHR), system status (ACTV, OTAG, POTG), and effective date/time.
Operator responsibility: Integrate with CPT data feed, configure automated status change detection.
2.6 Per-Bond Status Report — CPT Data Feed
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
eachBondReport | After bond status change (post-publication) | Database entry → CPT venue data feed | Consolidated Tape Provider |
Data availability: Reports ISIN, status change timestamp, currency, instrument status (SUSP/RMOV/ACTV), venue MIC, and trading system type. Derived from Indexer Bond.status and BondHistory events.
Operator responsibility: Publish to CPT feed upon each bond lifecycle event.
2.7 DLT Pilot Regime — Monthly Value Report (EU 2022/858, Art. 3)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
monthlyDLTValueReport | First day of each month (for previous month) | Database entry | NCA / ESMA |
Data availability: Monthly average market value calculated from daily closing prices (last MarketDeal price per ISIN per day) multiplied by total on-chain supply (sum of TokenOwner.amount per token). Data sourced from Core Payment Service and Indexer.
Operator responsibility: Schedule monthly calculation, format and submit per NCA requirements.
2.8 DLT Pilot Regime — Semi-Annual Report (EU 2022/858, Art. 11)
| Report ID | Trigger | Output Format | Destination |
|---|---|---|---|
sixmonthlyDLTValueReport | Every 6 months | Database entry | NCA / ESMA |
Data availability: Aggregates: number of bonds (count where status ≠ UNREGISTERED), total value of bonds (sum of amount × denomination), total value of transactions (marketplace + OTC settlement values). All data available from Indexer and Core Payment Service.
Operator responsibility: Schedule semi-annual generation, submit to NCA and ESMA.
2.9 Compliance & Surveillance Reports
| Report Type | Regulation | Trigger | Destination |
|---|---|---|---|
| STOR (Suspicious Transaction/Order Report) | MAR Art. 16 | Manual (compliance officer investigation) | NCA (e.g. HCMC) |
| STR (Suspicious Transaction Report) | AML Directive | Manual (compliance officer investigation) | FIU (e-STR channel) |
Data availability: The Compliance Data Mart aggregates all evidence items needed for case construction: subject identities (Company/User with LEI), market orders, trades, settlements, chain transactions, governance actions, bond snapshots, portfolio snapshots, and attachments. Auth context (non-repudiation) is captured per event.
Operator responsibility: Staff compliance function, operate case management workflow (DRAFT → READY → SUBMITTED → ACKNOWLEDGED), configure submission channels to FIU and NCA.
3. Regulatory References
- MiFIR Art. 26 / RTS 22 (Transaction Reporting): EU 2017/590
- MiFIR Art. 27 / RTS 23 (FIRDS Reference Data): EU 2017/585
- RTS 24/25 (Order Record Keeping): EU 2017/580
- MiFIR Post-Trade Transparency (APA/CPT): EU 2017/583 (consolidated 2026)
- CPT Bond Data Feed: EU 2025/1155
- DLT Pilot Regime: EU 2022/858
- ESMA FIRDS Instructions: ESMA65-11-1193 v2.1