EMIR derivative reporting requirements
The European Market Infrastructure Regulation requires derivative contracts to be reported to a trade repository. Both counterparties report, which makes identifiers and reconciliation the whole game — most failures are data quality, not intent.
REGREP is an independent software provider. This page explains the framework in plain language and is not legal or regulatory advice — confirm your reporting obligations with your competent authority.
- Instrument
- Regulation (EU) No 648/2012
- Scope
- Financial and non-financial counterparties to derivatives
- Reporting artefact
- Derivative reports
- Format
- ISO 20022 XML to a trade repository
- Supervisor
- ESMA and national competent authorities, via trade repositories
- Penalties
- Administrative measures and sanctions set by each member state
What EMIR asks of you
The short version: what the framework requires, who it applies to and when it bites.
What it requires
Both counterparties report the conclusion, modification and termination of every derivative contract to a registered trade repository, together with valuation and collateral data.
Who it applies to
Financial counterparties and non-financial counterparties alike — which pulls in corporates hedging commercial risk, not only regulated financial firms.
When it applies
Promptly after the reportable event, with reconciliation, pairing and matching running continuously alongside the reporting itself.
What has to be done
Penalty powers derive from Regulation (EU) No 648/2012 as applied through national law.
| Obligation | What it means in practice |
|---|---|
| Report contract lifecycle events | Report conclusion, modification and termination of derivative contracts, along with valuation and collateral updates over the life of the trade. |
| Keep identifiers valid | Legal entity, unique trade and unique product identifiers must be valid and agreed between counterparties, since identifier mismatches are the dominant rejection and break cause. |
| Handle dual-sided reporting | Both counterparties report the same trade. Where reporting is delegated, responsibility for accuracy does not transfer with the task. |
| Reconcile and resolve breaks | Reported data is paired and matched at the trade repository; breaks must be investigated and resolved rather than allowed to age. |
| Correct errors and omissions | Errors are corrected through the prescribed route, and significant misreporting is notified to the competent authority. |
From your data to a validated filing
Activate only the module the obligation needs. Every price covers one regulated entity unless stated otherwise, and excludes VAT.
EMIR reporting
Delivered as a scoped project on the REGREP ISO 20022 engine. The field-level mapping, identifier handling and reconciliation logic are specific to your trade flow.
Talk to usScoped to your derivative flow Talk to usISO 20022 messaging
The same engine generates and validates ISO 20022 messages, including SEPA payment messaging, as a scoped engagement.
Talk to usScoped to your message set Talk to usRelated to EMIR
MiFIR
The transaction reporting counterpart: executed transactions reported to your competent authority rather than a trade repository.
Read the requirements →Structured data guide
Plain-language explainers on ISO 20022, structured messaging and high-volume reporting.
Read the guide →ISO 20022 module
See the messaging engine behind our EMIR project work, including SEPA content.
See the module →Questions, answered
Who reports under EMIR — both sides?
Does delegating reporting transfer responsibility?
How does EMIR relate to REMIT for energy contracts?
Why is EMIR not a self-serve module?
Scope your derivative reporting flow.
Tell us where your trade data comes from and where breaks are coming from today.