EMIR Refit and Claude AI: Derivatives Reporting, UTI Matching, and Compliance Workflows (2026)

EMIR Refit: The Updated EU Derivatives Reporting Framework

EMIR Refit (formally, the amendments to European Market Infrastructure Regulation under the 2019 revision and subsequent technical standards) made comprehensive changes to the EU derivatives trade reporting framework. The most significant changes: adoption of ISO 20022 XML format replacing CSV submissions, expanded field count from 129 to 203 reportable fields, mandatory Unique Transaction Identifier (UTI) generation and matching between counterparties, and the introduction of the Unique Product Identifier (UPI). For compliance teams at banks, asset managers, and corporate treasury functions with EMIR reporting obligations, EMIR Refit created a substantial implementation and ongoing operational burden.

Claude is used in EMIR Refit compliance for the analysis and documentation layer: mapping legacy fields to the new 203-field schema, drafting UTI matching process documentation, analyzing reconciliation break patterns, preparing responses to trade repository queries, and building compliance gap assessments for internal audit. The trade data and technical reporting remain in dedicated trade repository submission systems; Claude handles the surrounding compliance analysis and documentation.

Field Mapping and XML Schema Analysis

• "EMIR Refit field mapping for interest rate swaps: We need to map our internal IRS trade data fields to the EMIR Refit 203-field reporting schema. Our internal system fields for a vanilla EUR interest rate swap: Trade ID, Trade Date, Effective Date, Maturity Date, Notional (EUR), Fixed Rate, Day Count (Act/360), Payment Frequency (Quarterly), Floating Index (EURIBOR 6M), Counterparty LEI, Our LEI, Direction (pay/receive fixed). Map these internal fields to the corresponding EMIR Refit fields under the ISO 20022 schema. For each field: (1) identify the EMIR Refit field number and name, (2) note any transformation required (e.g., date format conversion to ISO 8601, direction field encoding), (3) flag any EMIR Refit required fields that have no internal equivalent (gaps we need to source from elsewhere), (4) note fields where EMIR Refit accepts conditional reporting vs. mandatory."
• "EMIR Refit UPI requirement analysis: EMIR Refit introduced mandatory Unique Product Identifier (UPI) reporting, replacing the prior CFI/ISIN-based product identification. UPIs are issued by ANNA-DSB. Our product mix: (1) vanilla EUR IRS — UPI exists on DSB, fetch by querying with instrument type + underlier + template, (2) cross-currency swaps (EUR/USD, EUR/GBP) — UPI exists for standard structures, (3) exotic equity total return swaps (bespoke underliers) — UPI may need to be generated via DSB on-demand, (4) commodity forwards (OTC energy) — scope clarification needed. For each product: (1) how to obtain the UPI (DSB query vs. generation), (2) what data we need to provide DSB to generate a UPI for non-template products, (3) timing — when must the UPI be included in the report (T+1 for most asset classes), (4) what to report if UPI is not yet available at time of submission."

UTI Generation and Matching

The UTI identifies a specific trade uniquely across all trade repositories and counterparties. Under EMIR Refit, counterparties must agree on the UTI before or at reporting and use the same UTI in their respective submissions. UTI disputes — where both sides report under different UTIs — are a leading cause of trade repository reconciliation breaks and can attract regulatory attention.

• "UTI matching process documentation: We need to document our UTI generation and matching process for EMIR Refit compliance. Our approach: (1) for trades where we are execution venue (inter-dealer broker trades) — we generate the UTI using ISO 23897 format: [LEI of generating entity][trade date YYYYMMDD][unique internal reference]. (2) For dealer-client trades where the dealer generates the UTI — we receive the UTI via confirmation (SWIFT MT or FpML/ISDA CDM), extract it, and load it to our reporting system. (3) For intra-group trades — we use the EMIR Refit waterfall to determine who generates: if one party is a financial counterparty and one is a non-financial, the financial counterparty generates. Write the process document covering: UTI generation methodology, UTI receipt and extraction from counterparty confirmations, the matching waterfall (who generates in each scenario), break resolution process when counterparty UTI does not match."
• "Reconciliation break analysis: Our monthly EMIR trade repository reconciliation shows 847 open breaks. Break categorization: (1) UTI mismatch — both sides reported different UTIs: 312 breaks. (2) Valuation discrepancy — UTI matches but mark-to-market differs by more than 10%: 198 breaks. (3) Position-level differences — trade exists on our side but counterparty has no matching record: 187 breaks. (4) Field-level differences — UTI matches, valuation within tolerance, but specific fields differ (notional, maturity): 150 breaks. Analyze: (1) root cause hypotheses for each break type and what they indicate about our process, (2) priority order for resolution (regulatory risk by break type), (3) the UTI mismatch population — is this concentrated in specific counterparties or asset classes? (4) what the valuation discrepancies tell us about our pricing vs. counterparty pricing."

Compliance Gap Assessment

• "EMIR Refit gap assessment for non-financial counterparty (NFC): We are a European corporate treasury with derivatives exposure above the NFC+ clearing threshold in FX (above the €3B net notional threshold in FX category). This means we are NFC+ for FX but not for other asset classes. EMIR Refit obligations as NFC+: (1) clearing obligation for FX NDFs and other cleared products, (2) trade reporting obligation (applies to all NFCs regardless of threshold), (3) collateral/margin requirements for uncleared trades (EMIR margin rules apply to NFC+). Conduct a gap assessment: (1) what trades in our treasury portfolio are in scope for clearing, (2) what trade reporting fields are we currently not capturing (new EMIR Refit fields), (3) do we have a threshold monitoring process to detect if we become NFC+ in other asset classes, (4) are we meeting the EMIR margin rules for our uncleared IRS book?"

EMIR Refit and Post-Brexit UK EMIR

UK counterparties are subject to UK EMIR (onshored into UK law at Brexit), which retained the pre-Refit framework initially but is being updated. For firms with counterparties on both sides of the EU/UK divide, understanding the differences and managing dual reporting obligations is an ongoing compliance task.

• "EU EMIR Refit vs. UK EMIR comparison: We are a UK-headquartered firm trading with EU counterparties. We have dual reporting obligations: UK EMIR reporting to DTCC UK trade repository, and EU EMIR reporting where our EU subsidiary is the counterparty. Key differences to manage: (1) UK EMIR is currently pre-Refit (ISO 20022 migration not yet complete for UK), (2) EU EMIR Refit uses 203 fields, UK still on 129-field schema, (3) UTI formats differ between UK and EU technical standards, (4) margin reporting requirements diverge. Write the compliance matrix covering each key difference between EU EMIR Refit and UK EMIR and how our reporting system handles the bifurcation."

Resources for Derivatives Compliance Teams

For compliance teams managing EMIR Refit alongside other derivatives reporting obligations, the Compliance & Risk category includes regulatory documentation tools, gap assessment frameworks, and compliance memo drafting assistants. For DORA ICT risk and third-party reporting obligations that often apply to the same institutions, see Claude AI for DORA Compliance. For the market risk analysis underlying the derivatives positions being reported, the Derivatives AI guide covers XVA, options Greeks, and trading desk analytics.