Implementation of your derivatives reporting under EMIR Refit — field mapping, trade repository connectivity, ESMA validation and reconciliation. We absorb the technical complexity so your operations team can focus on execution.
The Refit replaced the schema, not just a few fields. Rebuilding it right the first time is cheaper than remediation under supervisory pressure.
Health check first if you are unsure where you stand.
The Refit fundamentally changed the reporting regime: an ISO 20022 XML schema, 203 reportable fields, stricter pairing and matching at the trade repositories, and a duty to notify your regulator of material reporting errors. Mappings and controls built for old-EMIR do not carry over — which is why so many firms live with chronic reconciliation breaks and silent data quality issues.
We rebuild the chain end to end: from trade capture through enrichment and mapping to repository submission — with the validation, reconciliation and governance that turn reporting from a daily worry into a controlled process. What changed and why it matters is covered in our EMIR Refit guide.
All 203 Refit fields mapped against your trade and reference data. Gaps identified at source-system level, with a concrete remediation plan per gap.
Objective repository selection, onboarding management and connectivity implementation — including UTI generation and sharing logic with your counterparties.
Schema implementation and structured testing against the ESMA validation rules, so rejections surface in test — not in production.
Pairing/matching monitoring, break categorisation, escalation thresholds and documented resolution. The evidence trail your regulator expects.
Delegation agreements structured properly: scope, data flows, oversight controls and periodic verification against your own records.
A process for absorbing future ESMA schema and validation updates as routine changes instead of emergency projects.
Weeks 1–2. Reporting scope, data flows, existing breaks and repository statistics reviewed. You get an honest picture of where you stand.
Weeks 3–8. Field mapping, data sourcing fixes, XML generation and repository connectivity — documented so it survives staff turnover.
Weeks 8–12. Structured test cycles against ESMA validation rules and repository acceptance testing, including error and rejection handling.
Final weeks. Production cutover, first reconciliation cycles supervised, break management handed to your operations team with a playbook.
Financial and non-financial counterparties with EMIR reporting obligations — investment firms, asset managers, trading firms and corporates with derivatives exposure. Whether you report directly, through delegation, or are re-insourcing after a delegation that did not work out.
Also see our EMIR Refit reporting pack for the template-based starting point, or the wider MiFID II compliance framework.
No. Under EMIR you remain legally responsible for the accuracy and completeness of reports submitted on your behalf. Delegated reporting needs a proper agreement, oversight controls and periodic reconciliation against your own records — we set all three up.
The Refit replaced the reporting schema with ISO 20022 XML, expanded the field set to 203 fields, tightened ESMA validation rules and introduced mandatory reporting of errors and omissions to your regulator. Legacy mappings built for old-EMIR do not survive this.
We design the break management process: pairing and matching monitoring at the trade repository, root-cause categories, escalation thresholds and evidence of resolution. Breaks are inevitable; unmanaged breaks are a supervisory finding.
That depends on your volumes, asset classes, counterparty landscape and budget. We run the selection objectively, manage onboarding and implement the connectivity — we have no commercial ties to any repository.
A rebuild of the reporting chain typically takes 10–14 weeks including testing against ESMA validation rules and a reconciliation cycle. A health check of an existing setup takes 2–3 weeks.
We use strictly necessary cookies to run this site. With your permission we also set statistics cookies (Google Analytics) and marketing cookies (Calendly scheduling). You can change this choice anytime via the footer. See our privacy statement and cookie statement.