Overview
Transaction reporting is one of the most technically demanding areas of financial regulation. MiFIR, MiFID II, and Dodd-Frank each impose distinct requirements: different fields, different reporting venues, different timelines, and different product scopes. For a large international bank operating across European and US markets, implementing all three simultaneously—across a fragmented landscape of source systems and product lines—required systematic business analysis and precise data mapping.
IndusEuro provided embedded business analysis support to the bank's transaction reporting programme, working across multiple teams in Germany and internationally to deliver functional specifications, data mappings, and field-level analysis for CFDs, equities, derivatives, FX options, exotic products, and swaps.
The Challenge
Scale and Complexity
The bank's transaction universe spanned a very large number of product types and booking locations. Each regulatory regime required mapping dozens of fields to source system data—often sourced from multiple upstream systems in different formats, with inconsistent naming conventions.
- MiFIR requires real-time transaction reporting of financial instruments admitted to trading on EU venues, with over 60 reportable fields per transaction.
- MiFID II adds transparency requirements—pre- and post-trade data publication obligations with waiver and deferral mechanisms.
- Dodd-Frank (US Commodity Exchange Act) imposes parallel reporting obligations for swap transactions to US Swap Data Repositories (SDRs), with different field sets and counterparty classification logic.
Coordination Challenge
The project involved multiple business units, front-office desks, IT teams, compliance, and legal—spread across Germany and other European locations. Getting consistent definitions, agreed scope, and sign-off across these stakeholders required careful facilitation and clear documentation.
Data Sourcing Complexity
Transaction data arrived from source systems in FpML and XML formats, each with different schemas by product type. Mapping the regulatory reporting fields to the correct source system attributes required deep analysis of system schemas, trade booking conventions, and business logic embedded in each product line.
Reporting Architecture
TRANSACTION LIFECYCLE & REPORTING FLOW
Front Office Systems (equities, derivatives, FX, swaps)
│
│ Trade capture
▼
┌──────────────────────────────────────────────────────────┐
│ Trade Booking Systems │
│ (FpML / XML trade representations) │
└──────────────┬────────────────────────────────┬──────────┘
│ │
▼ ▼
┌─────────────────────┐ ┌─────────────────────┐
│ MiFIR/MiFID II │ │ Dodd-Frank │
│ Reporting Engine │ │ Reporting Engine │
│ │ │ │
│ Field mapping: │ │ Field mapping: │
│ - UTI/LEI/ISIN │ │ - USI/LEI │
│ - Price/Qty/Venue │ │ - SDR field set │
│ - Product classif. │ │ - Counterparty │
│ - Waiver flags │ │ classification │
└──────────┬──────────┘ └──────────┬──────────┘
│ │
▼ ▼
┌─────────────────────┐ ┌─────────────────────┐
│ Deutsche Boerse │ │ CFTC / SEC │
│ Regulatory Hub │ │ Swap Data │
│ (EU reporting) │ │ Repositories │
└─────────────────────┘ └─────────────────────┘
│
▼
┌─────────────────────┐
│ T+1 Feedback Loop │
│ (acceptance, │
│ rejections, │
│ reconciliation) │
└─────────────────────┘
Our Approach
Regulatory Analysis & Scoping
We started with a detailed analysis of each regulation's technical standards and RTS (Regulatory Technical Standards) to establish a definitive field mapping matrix. For MiFIR, this covered the 65 reportable fields in Annex I of RTS 22. For Dodd-Frank, we mapped to CFTC swap reporting requirements with particular attention to counterparty classification (SD/MSP/non-SD) rules.
Product scoping was a significant workload—each regulation has different inclusion/exclusion criteria. We produced product-by-product scoping matrices covering equities, listed derivatives, OTC derivatives (IRS, CDS, FX options), CFDs, exotic products, and structured notes.
Data Mapping
For each in-scope product type, we created field-level data mapping documents covering:
- The regulatory field name and definition
- The source system field or business logic that populates it
- Data type, format, and validation rules
- Exception cases and conditional logic
- Enrichment sources (static data, reference data, counterparty master)
Mapping was performed by analysing FpML and XML representations of actual trades from the booking systems, and cross-referencing with IT teams to confirm data availability and transformation requirements.
MiFID II Transparency Analysis
Beyond transaction reporting, MiFID II introduced pre- and post-trade transparency requirements. We analysed the bank's instrument universe for systematic internaliser (SI) obligations and mapped the waiver/deferral mechanism logic for large-in-scale and illiquid instrument trades.
Deutsche Boerse Regulatory Hub Integration
We analysed the feedback loop from the Deutsche Boerse Regulatory Hub—specifically the T+1 rejection and acceptance reports—to identify reporting quality issues and define correction workflows. This included analysis of rejection reason codes and the operational processes needed to remediate and re-submit rejected reports.
Cross-Team Coordination
Given the number of teams in scope, we established a structured stakeholder engagement model: weekly working group sessions per regulation, a central requirements repository, and a sign-off process for each functional specification document.
Scope of Work
Functional Specification Documents:
- Dodd-Frank swap reporting implementation spec
- MiFIR transaction reporting spec (per product type)
- MiFID II transparency and SI determination spec
- Internal compliance project specs
Data Analysis Deliverables:
- Complete field mapping matrix: 65+ MiFIR fields × 10+ product types
- Source system attribute mapping (FpML/XML to regulatory fields)
- Product scoping matrices for each regulation
- Deutsche Boerse Regulatory Hub feedback analysis
- T+1 rejection reason analysis and remediation process design
Stakeholder Management:
- Interfacing between front-office desks, compliance, legal, and IT across multiple locations
- Structured working group facilitation
- Document review and sign-off coordination
Outcome
- Complete functional specifications delivered for MiFIR, MiFID II, and Dodd-Frank reporting requirements.
- Field-level data mappings produced for all major product types in scope, enabling IT implementation to proceed with clear requirements.
- Regulatory hub feedback analysis identified systematic rejection patterns and informed operational remediation workflows.
- Cross-team coordination model established a structured framework that reduced rework and ambiguity in requirements.
Technology & Standards
- Trade data formats: FpML, XML
- Reporting venues: Deutsche Boerse Regulatory Hub, ESMA registers, CFTC SDRs
- Data analysis: SQL (source system data validation), Excel-based mapping matrices
- Standards: ISO 20022 message schemas, ISIN/LEI/UTI classification standards
- Internal tooling: JIRA for issue tracking, Confluence for documentation
Compliance Coverage
- MiFIR: RTS 22 transaction reporting (all 65 fields), product scoping, SI determination
- MiFID II: Pre- and post-trade transparency, waiver/deferral framework, best execution
- Dodd-Frank: CFTC swap reporting, SDR submission, counterparty classification
Technology stack
Services delivered
Discuss a similar project
If this case study is relevant to a challenge you're facing, we'd welcome the conversation.
Book a consultation