Regulatory & Transaction Reporting Reconciliation
Regulatory reporting reconciliation, with proof for the regulator.
Reconcile what you reported to trade repositories, competent authorities and central banks against your source of truth — with lineage, evidence and completeness testing on every field.
The problem
The reconciliation problems this solves
Between source systems and the TR/NCA lies transformation, enrichment and rejection — differences here are enforcement risk.
EMIR REFIT, MiFID/MiFIR, SFTR, CFTC Part 45 and Dodd-Frank each demand per-field accuracy testing, not just record counts.
Unpaired trades, rejected submissions and back-reporting corrections need explicit reconciliation and remediation SLAs.
Regulators expect on-demand evidence of controls, exceptions and remediation — not screenshots of Excel.
Capabilities
What ReconIQ does for this use case
Reconcile every submitted field back to the golden source, with lineage down to the record and transformation step.
AI clusters reporting breaks by rule, jurisdiction and source system, then drafts remediation aligned to your MI/EPS control.
Ingest ACK/NACK, pairing/matching and reconciliation reports from DTCC, UnaVista, REGIS-TR, KDPW, ESMA / FCA / CFTC feeds.
Detects universe drops, over-reporting and duplicate submissions with tenant-configurable materiality.
Signed, hash-chained evidence packs exportable to CSV/JSON/PDF for SREP, ARROW and Skilled Person reviews.
Native handling of corrections, cancellations and terminations with linked audit history.
Data sources supported
- EMIR REFIT (ESMA & FCA UK EMIR)
- MiFIR RTS 22 transaction reporting
- SFTR, CFTC Part 45/46 (Dodd-Frank), MAS OTC, HKMA, ASIC
- Trade repositories: DTCC GTR, UnaVista, REGIS-TR, KDPW, CME TR
- Front-office trade booking systems (Murex, Calypso, Summit, in-house)
- Reference data (LEI, ISIN, UPI, UTI)
What this gives you
Designed with reference to the frameworks that matter here
Controls are designed with reference to these frameworks and regimes. See Security & Compliance for the full picture.
ReconIQ does not hold SOC 2 or ISO 27001 certification. Entries marked “(target)” or “(aligned)” describe design references and roadmap targets, not certifications we have earned.
Questions
Frequently asked
Does ReconIQ replace our reporting engine?+
No — ReconIQ is the assurance layer around your reporting engine. It reconciles what was submitted vs. what should have been submitted, and evidences the control to regulators.
Which regimes are supported?+
EMIR REFIT, MiFIR, SFTR, CFTC Parts 45/46, MAS, HKMA and ASIC out of the box. Additional regimes are configurable via the Data Prep pipeline and canonical schema.
How does the regulator-evidence pack work?+
Every reconciliation, exception, override and remediation is written to a SHA-256 hash-chained log. Evidence packs are exportable per regime, per date, signed and ready for supervisory review.
See it on your data.
Try the live demo, or book a session to walk a regulatory & transaction reporting reconciliation workflow end to end.