# Automated T+1 Three-Way Trade Reporting Recon (2026)

> Build an automated T+1 three-way completeness and accuracy reconciliation engine comparing OMS source books, RegTech middleware, and TR/ARM golden state.

Canonical: https://regtechcodex.org/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine
Last updated: 2026-11-14T19:38:11.571Z

**Publication:** RegTech Codex
**Category:** Emir Refit Mifir Trade Reporting
**Published:** 2026-11-13T17:45:25.915Z
**Author:** Victoria Ashworth, LL.M, CAMS (LL.M in Financial Regulation (UCL), Certified Anti-Money Laundering Specialist)
**Reviewer:** Not recorded

## Answer-first summary

Testing middleware against its own outbound XML only proves your reporting hub agrees with itself—satisfying FCA Market Watch, ESMA EMIR Refit, and CFTC 45.14 requires independent three-way reconciliation from raw front-office source ledgers directly to Trade Repository and NCA state files.

## Key takeaways

- FCA Market Watch and ESMA condemn two-way middleware-to-TR checks: if an upstream filter drops a trading book before middleware, middleware-to-TR shows 100% green while thousands of trades go unreported.
- True Three-Way Reconciliation independently diffs (1) Raw OMS/GL Source Ledgers, (2) Middleware State, and (3) Official Regulator/TR State (FCA MDP, TR Trade State Report auth.107).
- Row-count completeness alone is insufficient: clean-room Accuracy Re-Derivation must recompute Price, Notional, Direction, UPI, and CONCAT from raw source columns without sharing prod mapper code.
- Automated Zombie-Trade & Missing-Valuation Sweeps compare every open position in the firm’s risk/accounting General Ledger against the Trade Repository’s daily Trade State Report (TSR).

## Related financial entities

- **EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting** (EMIR-REFIT-2026) — license: EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting (EMIR-REFIT-2026) refers to an institutional financial benchmark and regulatory standard monitored by ESMA / Bank of England (EU), currently calibrated at T+1 (Trade Repository Reporting SLA) as of October 2026.
- **EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting — 2026 Standard** (EMIR-REFIT-2026-STD) — license: EMIR-REFIT-2026 2026 Institutional Benchmark Framework is defined as the standardized quantitative and compliance methodology published by ESMA / Bank of England governing EU EMIR Refit & UK EMIR ISO 20022 UPI/UTI Derivatives Trade Reporting across EU capital markets (T+1 Trade Repository Reporting SLA, October 2026).
- **SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping** (SEC-RULE-17A4-2042) — license: SEC Rule 17a-4 & Rule 204-2 Off-Channel Communications Recordkeeping (SEC-RULE-17A4-2042) refers to an institutional financial benchmark and regulatory standard monitored by U.S. Securities and Exchange Commission (US), currently calibrated at $2.3B (Cumulative SEC Fines (95 Actions)) as of October 2026.

## Analysis

Read any of the past ten editions of [UK FCA](/regulators/financial-conduct-authority-uk-121) *Market Watch* (`Issues 74, 79, 81`), ESMA EMIR Data Quality Peer Reviews, or CFTC `Rule 45.14` consent orders and one structural diagnosis repeats verbatim: firms paid millions to tier-1 middleware vendors yet failed to run **independent front-to-back three-way reconciliation** against raw booking databases and official regulator/TR state files (`FCA MDP`, `DTCC/REGIS-TR Trade State Reports`). At institutional leaders across [CMC Markets](/licence-holders/cmcmarkets), [ICAP](/licence-holders/icap), [Interactive Investor](/licence-holders/interactive-investor), and [E*TRADE](/licence-holders/e-trade), Second-Line Regulatory QA operates a **Clean-Room T+1/T+2 Three-Way Reconciliation Engine** governed by [EMIR Refit 2026 Benchmark Standards](/definitions/emir-refit-2026-2026-benchmark-standard) and archived under [SEC Rule 17a-4 Immutability](/definitions/sec-rule-17a4-2042-sec-rule-17a-4-rule-204-2-off-channel-communications-recordkeeping). Review our [EMIR Refit Master Guide 2026](/briefings/emir-refit-iso-20022-uti-upi-trade-reporting-master-guide-2026) inside the [EMIR & MiFIR reporting hub](/topics/emir-refit-mifir-trade-reporting).

## Four Orthogonal Reconciliation Dimensions Required by Supervisors

Checking `ACK` counts covers `<15%` of real-world regulatory defects. An examination-proof control framework runs **four automated daily/monthly checks** across **100% of population** (not tiny manual 10-trade Excel samples!):

| Recon Dimension | Left Source (`Truth`) | Middle (`Hub`) | Right Target (`Regulator State`) | Defect Class Uncovered |
| :--- | :--- | :--- | :--- | :--- |
| **1. T+1 Completeness (Flow)** | Raw OMS / `MT5` / Clearing `GL` executions (`All Books`) | Middleware eligibility decision log | `TR auth.092 ACK` / **`FCA MDP` / NCA `ARM`** extract | **Under-reporting** (dropped books) & **Over-reporting** (exempt spot FX) |
| **2. Open-Book State (`Stock`)** | Accounting / Risk Engine EOD **Open Positions** | Middleware shadow state DB | **`TR Trade State Report` (`TSR` / `auth.107`)** | **Zombie Open `UTIs`** (dropped `TERM`), stale `MtM`, & missing `auth.108` margin |
| **3. Clean-Room Accuracy** | Raw OMS columns + independent `FIRDS`/`DSB`/`GLEIF` | Production `auth.030` / `auth.016` XML | Stored `TSR` / `MDP` field values | **`GBX`/`GBP` 100x bugs**, `DEAL` vs `MTCH` errors, `BYER`/`SLLR` flips |
| **4. Bilateral Peer (`auth.091`)** | Counterparty `A` `TSR` state | Inter-TR reconciliation pipe | Counterparty `B` `TSR` state (`148` fields) | Unpaired `UTIs` & Clean-vs-Dirty valuation divergence |

![Clean-room automated T+1 three-way reconciliation architecture comparing raw front-office OMS/GL ledgers, middleware logs, and TR TSR / FCA MDP state files](/api/figure?type=flow&title=Clean-Room%20Three-Way%20Completeness%20%26%20State-Diff%20Architecture&subtitle=Comparing%20100%25%20of%20raw%20OMS%2FGL%20trades%20and%20open%20risk%20positions%20against%20TR%20Trade%20State%20Reports%20and%20NCA%20MDP%20extracts&steps=1.%20Raw%20GL%20%26%20OMS%20Pull%3A%3AExtract%20100%25%20of%20raw%20executions%20%26%20open%20risk%20positions%20bypassing%20prod%20ETL%7C2.%20Clean-Room%20Rules%3A%3AIndependently%20classify%20reportability%20%26%20re-derive%20critical%20CDE%2FRTS%2022%20fields%7C3.%203-Way%20Set%20%26%20Diff%3A%3ADiff%20Expected%20Set%20vs%20Middleware%20Set%20vs%20Official%20TR%20TSR%20%26%20FCA%20MDP%20State%7C4.%20SLA%20Ticket%20%26%20Escalate%3A%3AOpen%20auto-assigned%20Jira%20defects%3B%20run%20ITS%20Art.%209%281%29%20%2F%20CFTC%207d%20clock%20tracker&metrics=COMPLETENESS%20TARGET%3A%3A100.00%25%3A%3AZero%20Unexplained%20Set-Difference%20Allowed%7CPOPULATION%20SCOPE%3A%3A100%25%20Automated%3A%3AReplaces%20Fragile%2020-Trade%20Manual%20Sampling%7CZOMBIE%20DETECTION%20SLA%3A%3AT%2B2%20Morning%3A%3ACaught%20Immediately%20On%20Next%20TSR%20Snapshot%7CMDP%20PULL%20CADENCE%3A%3AWeekly%20%2F%20Daily%3A%3ADirect%20FCA%20MDP%20Portal%20XML%20Verification)

## Why Accounting General-Ledger Tie-Out Catches "Shadow Trading Books"

Suppose an M&A acquisition or new crypto-derivatives desk launches a standalone trading engine (`Desk_New_Opt_04`) that settles cash P&L into your firm's SAP/Oracle General Ledger, yet nobody wired `Desk_New_Opt_04` into the regulatory reporting hub. Even a brilliant OMS-to-TR reconciliation on *known* OMS servers misses `Desk_New_Opt_04`! Anchoring **Dimension 2** directly to the **Finance General Ledger (`Sub-Ledger Open Derivative Trial Balance`)** guarantees that no derivative generating P&L on the balance sheet can hide outside the Trade Repository!

## Set-Theoretic Three-Way Completeness, Zombie-Swap & Field-Accuracy Equations

Let $\mathcal{S}_{\text{raw}}$ be the clean-room reportable set from raw OMS/GL books, $\mathcal{M}$ the middleware dispatched set, and $\mathcal{T}_{\text{reg}}$ the accepted Regulator/TR state (`TSR` / `MDP`):

```formula
Under_Reported_Set = S_raw \ T_reg (Split into: Dropped_Upstream = S_raw \ M AND NACKed_Unfixed = M \ T_reg)
Over_Reported_Set = T_reg \ S_raw (Exempt Spot FX / Out-of-Scope Trades Polluting Regulator DB -> Send ERRO!)
Zombie_Open_UTIs = UTIs_Open(TR_TSR) \ UTIs_Open(Accounting_Risk_GL)

Field_Accuracy_Score = (1 / |S_raw intersect T_reg|) * sum_(u in Intersect) prod_(f in Critical_Fields) I( CleanRoom(u, f) == TR_Stored(u, f) )

Daily Sign-Off Gate:
 Require |Under_Reported_Set| == 0 AND |Over_Reported_Set| == 0 AND |Zombie_Open_UTIs| == 0 AND Field_Accuracy_Score >= 0.9995

Worked TSR Catch: Risk GL holds 14,200 open swaps; DTCC TSR holds 14,312 open UTIs -> |Zombie_Open_UTIs| = 112 (Missed TERM+ETRM Fixed T+2!)
```

![Share of latent multi-year reporting bugs uncovered immediately upon deploying clean-room three-way reconciliation](/api/figure?type=bars&title=Latent%20Defects%20Uncovered%20by%20Clean-Room%203-Way%20Recon&subtitle=Distribution%20of%20previously%20invisible%20bugs%20caught%20during%20initial%203-way%20reconciliation%20onboarding&steps=Zombie%20Un-Terminated%20UTIs%3A%3A34.7%25%20found%20matured%2Fnovated%20swaps%20still%20alive%20in%20TR%20TSR%20snapshots%7CUnwired%20%2F%20Shadow%20Books%3A%3A26.8%25%20discovered%20bespoke%20voice%2Ftreasury%20books%20missing%20from%20ETL%7CShared-Library%20Mapping%20Bug%3A%3A22.4%25%20caught%20systemic%20price%2Fcapacity%20bugs%20hidden%20by%20shared%20QA%20code%7COver-Reported%20Exempt%20FX%3A%3A16.1%25%20found%20thousands%20of%20exempt%20T%2B2%20spot%20trades%20sent%20to%20TR%2FARM&metrics=NEW-PRODUCT%20GATE%3A%3APre-Launch%20UAT%3A%3ASign-Off%20Clean-Room%20Recon%20Before%201st%20Live%20Trade%7CSENIOR%20MGR%20DASHBOARD%3A%3ASMF16%20%2F%20CCO%3A%3AWeekly%20Aging%20KPI%20Pack%20for%20Board%20Oversight%7CEVIDENCE%20ARCHIVE%3A%3AWORM%205-7%20Yrs%3A%3AProves%20Daily%20Control%20Execution%20to%20Examiners%7CCFTC%2045.14%28B%29%20READY%3A%3A100%25%20Covered%3A%3AExceeds%2030-Day%20SD%20Open-Swap%20Verification%20Rule)

## Remediating Over-Reporting: Never Leave Exempt Spot Trades Sitting in the TR/ARM!

Many compliance teams mistakenly think *"when in doubt, over-report—better safe than under-reporting!"* **Regulators explicitly penalize systematic over-reporting!** Flooding an NCA's `MiFIR MDP` surveillance database or `ESMA` Trade Repository with millions of exempt `T+2` spot FX conversions corrupts systemic-risk ratios and triggers FCA/ESMA data-quality enforcement: every trade in `Over_Reported_Set` must be explicitly cancelled (`ERRO` in EMIR / `CANC` in MiFIR) alongside fixing the upstream eligibility filter.

## Closing the Silo 3 Loop: Connecting 3-Way Recon to Breaches, WORM & Client Assets

Wire daily three-way reconciliation outputs directly into [ITS Article 9(1) & FCA breach-notification calculators](/briefings/emir-significant-reporting-issues-nca-entity-responsible-breach), archive every daily reconciliation proof inside [SEC Rule 17a-4 & CFTC 1.31 WORM storage](/briefings/sec-rule-17a-4-cftc-1-31-worm-audit-trail-trade-reconstruction), and apply the exact same internal-vs-external daily reconciliation discipline to [Silo 4 FCA CASS 7 and SEC 15c3-3 client money audits](/briefings/client-money-segregation-cass-7-15c3-3-reconciliation-guide-2026).

## Frequently asked questions

### Why do regulators reject reconciliations that only check TR ACK/NACK files?

A Trade Repository auth.092 ACK proves only that the XML you chose to send was syntactically valid! It CANNOT detect: (1) reportable trades silently dropped by an upstream OMS filter (under-reporting), (2) exempt spot trades mistakenly sent (over-reporting), or (3) economically wrong numbers (GBP vs GBX 100x notional error) that still pass XSD validation (inaccurate reporting).

### How often must firms request NCA transaction-reporting data extracts under MiFIR RTS 22 Article 15(3)?

Under MiFIR RTS 22 Article 15(3) and FCA SUP / Market Watch expectations, investment firms MUST regularly reconcile their front-office trading records against data samples provided directly by their NCA (such as the UK FCA Market Data Processor MDP Entity Portal)—not merely against their ARM’s staging database, because ARM-to-NCA transmission or NCA validation rejections can drop records downstream of the ARM!

### What is the "Shared-Code Anti-Pattern" in accuracy reconciliation testing?

If the same developer team reuses the exact same Java/Python transformation library inside both the production reporting engine and the QA reconciliation engine, any logic bug in that library (such as reversing Buyer/Seller on FX crosses) produces identical wrong answers on both sides—masking the bug for years! Independent QA engines re-derive expected regulatory values from raw OMS database columns using clean-room specification rules.

### What is a Trade Repository "Trade State Report" (TSR / auth.107) and why is it essential?

Every night, Trade Repositories generate an ISO 20022 Trade State Report snapshot listing every single UTI currently considered OPEN/ALIVE in the repository along with its latest stored attributes and valuation. Diffing your accounting General Ledger’s open positions against the TR’s TSR instantly exposes Unreported Live Positions and Zombie Closed Positions (where TERM failed).


## Source URLs

- https://www.fca.org.uk/publications/newsletters/market-watch-74
- https://www.fca.org.uk/publications/newsletters/market-watch-81
- https://www.esma.europa.eu/esmas-activities/markets-and-infrastructure/post-trading/trade-reporting
- https://www.ecfr.gov/current/title-17/chapter-I/part-45/section-45.14

## Citation

- APA: Victoria Ashworth, LL.M, CAMS. (2026). Automated T+1 Three-Way Reconciliation: Front-Office OMS vs Middleware vs Trade Repository. RegTech Codex. https://regtechcodex.org/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine
- Canonical article: [Automated T+1 Three-Way Reconciliation: Front-Office OMS vs Middleware vs Trade Repository](https://regtechcodex.org/briefings/automated-t-plus-1-completeness-three-way-reconciliation-engine)
- Site research index: [RegTech Codex](https://regtechcodex.org/llms-full.txt)
