Following the go-live of EMIR REFIT Phase 2 reconciliation in the EU on 27 April 2026 (see our earlier article), the UK regime now follows. On 28 September 2026, the second phase of UK EMIR reconciliation requirements comes into effect two years to the day after the amended UK EMIR reporting rules went live on 30 September 2024.
The change was confirmed on 16 April 2026, when the FCA and the Bank of England published an update to the UK EMIR Validation Rules. The update does three things:
- sets 28 September 2026 as the reconciliation start date for all fields previously marked as “two years from the start date of the reporting obligation”;
- removes the requirement to reconcile the Name of the underlying index field (Table 2, Item 16); and
- aligns the validation rules for the Report Tracking Number field (Table 2, Item 2) with existing guidance in UK EMIR Q&A 4.13.
Here’s what matters most for UK reporting counterparties.
A more structured reconciliation process
Trade repositories reconcile UK EMIR reports in a clear sequence:
- Transaction pairing (UTI + LEI matching across both counterparties)
- Data comparison (only after successful pairing)
- Valuation reconciliation (with its own rules and exclusions)
Only the end-of-day “latest state” of a derivative is reconciled, so accurate lifecycle management modifications, corrections, terminations and revivals remains critical. A stale or missing lifecycle event will produce a break even where the original trade was reported correctly.
Phase 2 significantly raises the bar
Phase 1 (from 30 September 2024) limited reconciliation to a core subset of Table 1 and Table 2 fields. From 28 September 2026, the deferred fields join the scope, bringing the UK regime broadly in line with the EU’s 148-field reconciliation set with the notable UK-specific exclusion of the Name of the underlying index field.
The newly reconcilable fields cover:
- Contract linkages (e.g. prior UTI, subsequent position UTI, package identifiers)
- Product and underlying data, including complex and multi-leg instruments
- Detailed economic terms (prices, spreads, notional schedules, other payments)
- Asset-class-specific attributes across interest rates, FX, commodities, credit and equity derivatives
For many of these fields no tolerance is allowed, exact matching is required. Small differences in how two counterparties classify an instrument, source a reference rate or format a date will trigger a reconciliation break where previously they went unnoticed.
Valuation reconciliation becomes a focal point
As in the EU, valuation data is part of the Phase 2 scope:
- After a valuation update is submitted, all in-scope fields are reconciled not only the valuation fields.
- Valuation reconciliation carries its own status with three outcomes:
- RECO – fully reconciled
- NREC – not reconciled (outside tolerance or sign mismatch)
- NOAP – not applicable (excluded)
- Valuation reconciliation and general reconciliation are assessed separately. A trade can pass general reconciliation and still fail on valuation.
Valuation reconciliation logic
Two checks are applied to the paired valuations:
- Valuation amounts within tolerance (tolerance depends on the valuation method CCPV, MTMA, MTMO as set out in the UK EMIR Validation Rules)
- Opposite signs required (one counterparty positive, the other negative)
If either check fails → NREC. All valuation fields must reconcile → RECO.
Trades excluded from valuation reconciliation (status NOAP) include:
- Derivatives where one counterparty is a small non-financial counterparty (NFC-)
- Exchange-traded derivatives reported at trade level
- Derivatives whose execution date equals the expiration or early-termination date
- Position component reports (POSC), unless subsequently revised
What is different from the EU?
Firms reporting under both regimes should not assume a single configuration works for both:
| EU EMIR (ESMA) | UK EMIR (FCA / BoE) | |
|---|---|---|
| Phase 2 go-live | 27 April 2026 | 28 September 2026 |
| Name of underlying index (2.16) | Reconciled | Not reconciled |
| Report Tracking Number (2.2) | ESMA validation rules | Aligned to UK Q&A 4.13 |
| Trade repositories | EU-registered TRs | UK-registered TRs |
Dual-reporting firms will already have been through the EU cut-over in April; the UK go-live is an opportunity to apply the lessons learned especially around static data alignment and lifecycle handling before breaks surface on the UK side.
More granular reporting = more actionable insights
UK trade repositories will return richer mismatch detail in reconciliation reports. This helps firms locate the root cause of a break faster, but it also increases the volume of reported breaks where upstream data between counterparties is not aligned. Firms should expect an initial spike in NREC and unmatched statuses after 28 September and plan resolution capacity accordingly.
Early testing is critical
Point Nine’s UK EMIR reconciliation readiness follows the same programme applied to the EU go-live in April 2026. Our clients reporting to UK trade repositories are being taken through UAT on the expanded field set and valuation logic ahead of 28 September, and we will continue to work closely with each client through the transition.
Streamlining your regulatory compliance with Point Nine
As an industry-leading team of experts specialising in trade processing and multi-regime regulatory reporting since 2002, Point Nine Data Trust helps both buy-side and sell-side financial institutions navigate regulatory change across EU and UK EMIR, MiFIR, SFTR and beyond. Using an in-house, cloud-native validation engine, Point Nine provides an end-to-end managed service that ingests, enriches, validates and submits data directly to the major trade repositories maintaining a 99.95% successful submission rate across billions of processed transactions.
What UK reporting firms should prioritise now:
- Align static and reference data with counterparties, particularly for the newly reconcilable product and economic fields
- Review lifecycle event handling (modifications, corrections, terminations, revivals)
- Validate valuation methodologies, sign conventions and rounding logic
- Strengthen reconciliation monitoring and break-resolution processes ahead of the expected post-go-live spike
- If reporting under both EU and UK EMIR, confirm the two configurations diverge where the rules diverge
- Align static and reference data with counterparties, particularly for the newly reconcilable product and economic fields
- Review lifecycle event handling (modifications, corrections, terminations, revivals)
- Validate valuation methodologies, sign conventions and rounding logic
- Strengthen reconciliation monitoring and break-resolution processes ahead of the expected post-go-live spike
- If reporting under both EU and UK EMIR, confirm the two configurations diverge where the rules diverge
Frequently Asked Questions (FAQs)
When does UK EMIR reconciliation Phase 2 start?
Phase 2 takes effect on 28 September 2026, as confirmed in the FCA’s 16 April 2026 update to the UK EMIR Validation Rules. It applies to the fields originally deferred by two years from the 30 September 2024 reporting start date.
Is the UK Phase 2 field scope identical to the EU’s?
Broadly, yes the UK follows the same phased structure and deferred field set. The main UK-specific difference is that the FCA has removed the Name of the underlying index field (Table 2, Item 16) from reconciliation, and the Report Tracking Number rules have been aligned with UK Q&A 4.13.
Can a derivative pass general reconciliation but fail valuation reconciliation under UK EMIR?
Yes. Transaction reconciliation and valuation reconciliation are assessed separately. A trade can be paired and matched across all transactional fields and still receive an NREC valuation status if amounts fall outside tolerance or the signs do not oppose.
Does Phase 2 apply to trades reported before 28 September 2026?
Yes. Reconciliation is performed on the latest state of all outstanding derivatives, regardless of when they were originally reported. Open positions and legacy trades will be reconciled against the expanded field set from go-live.