Skip to main content

ASIC reporting

The Australian Securities and Investments Commission (ASIC) Derivative Transaction Rules (DTRs) require Australian entities and entities trading through an Australian branch to report all OTC and exchange-traded derivatives transactions to ASIC's derivatives trade repository (Trade Repository Service or TRS). Falcon Veritas Intelligence (FVI) provides an ASIC DTR reporting pipeline for ADIs, AFSLs, and corporate treasuries operating in Australia or with AUD-denominated derivatives exposure.

Scope and applicability​

ASIC DTRs apply to entities that:

  • Are incorporated in Australia (or registered foreign company) and enter a derivative
  • Have an Australian branch that enters a derivative
  • Are a central counterparty (CCP) or trade repository operating in Australia

Reporting threshold: there is no de-minimis threshold under ASIC DTRs — every derivative must be reported, regardless of notional or counterparty status. The reporting deadline is T+1 (next business day).

FVI's ASIC DTR module supports reporting to ASIC's TRS (Trade Repository Service) via sFTP or AS4, and cross-border reporting to the DTCC Data Repository (Australia) for foreign entities that elect ASIC-only reporting.

Field mapping​

ASIC DTRs align with CPMI-IOSCO's global harmonisation framework. The 105 actionable fields include:

  1. Unique Transaction Identifier (UTI) — ASIC requires the UTI to be generated according to the CPMI-IOSCO Technical Guidance. FVI implements all four fallback UTI generation algorithms.

  2. Unique Product Identifier (UPI) — based on ISO 4914. FVI maintains the full UPI list and rejects submissions with deprecated UPIs.

  3. Counterparty classification — RDC, NFC, Other. FVI's counterparty graph resolves the classification based on the LEI and ASIC registration.

  4. Execution timestamp — UTC at millisecond precision. FVI's swaps.execution_at column is stored at millisecond precision and converted to UTC at submission.

  5. Notional and currency — with FX rate at execution. FVI's FX rate provider pulls daily RBA rates for accurate T+1 conversion.

How FVI supports ASIC DTR​

FVI treats ASIC reporting as a downstream consumer of the reconciled derivatives ledger. The match engine pairs execution records from your swaps system with confirmation messages and clearing records, producing a canonical derivatives state. The ASIC DTR pipeline then enriches each transaction with the required fields, performs client-side validation against ASIC's DTR XSD, and submits via ASIC's TRS or DTCC.

Step-by-step: enabling ASIC DTR reporting​

  1. Register the tenant. In FVI, navigate to Settings → Compliance → ASIC and enter the ABN/ACN, the LEI, and the TRS election (ASIC TRS or DTCC-Australia). FVI validates the ABN/ACN against the Australian Business Register.

  2. Configure counterparty classification. Add the RDC/NFC status and the derivatives activity. FVI applies the appropriate submission profile.

  3. Map source systems. Connect each swap execution platform, confirmation system, and clearing house to FVI's ingestion pipeline. FVI normalizes FpML 4.x/5.x and FIX 5.0SP2 into the canonical swap record.

  4. Run a dry-run. FVI's compliance console supports a 30-day dry-run submission to ASIC's TRS sandbox. Review the validation report.

  5. Enable production submission. Once dry-run passes, flip the tenant to live. FVI begins the T+1 morning submission window.

  6. Monitor acknowledgements. FVI polls the TRS for ACK/NACK and surfaces unresolved validation errors as exceptions.

Code samples​

curl​

curl -X POST https://api.falconveritas.com/v1/compliance/asic/submissions \
  -H "Authorization: Bearer $FVI_JWT" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "'$FVI_TENANT_ID'",
    "abn": "12345678901",
    "lei": "529900T8BM49AURSDO55",
    "trs": "asic-trs",
    "fromDate": "2026-08-01",
    "toDate": "2026-08-22",
    "idempotencyKey": "asic-fvi-$RANDOM"
  }'

TypeScript​

import { FVI } from '@falconveritas/sdk';

const fvi = new FVI({
  baseUrl: 'https://api.falconveritas.com',
  bearer: process.env.FVI_JWT!,
  tenantId: process.env.FVI_TENANT_ID!,
});

const submission = await fvi.compliance.asic.submit({
  abn: '12345678901',
  lei: '529900T8BM49AURSDO55',
  trs: 'asic-trs',
  fromDate: '2026-08-01',
  toDate: '2026-08-22',
});

console.log('Submission ID:', submission.id);

Python​

from falconveritas import FVI

client = FVI(
  bearer=os.environ["FVI_JWT"],
  tenant_id=os.environ["FVI_TENANT_ID"],
)

submission = client.compliance.asic.submit(
  abn="12345678901",
  lei="529900T8BM49AURSDO55",
  trs="asic-trs",
  from_date="2026-08-01",
  to_date="2026-08-22",
)
print("Submission ID:", submission.id)

Troubleshooting​

Last updated: 2026-08-22 · Page owner: Documentation · Source: src/lib/compliance/asic/.