The Trade Repository: The Flight Recorder for the Market Nobody Could See

A flight recorder doesn't fly the plane. It doesn't warn the pilot, correct a bad approach, or stop anything from going wrong. Its entire job is to remember — every instrument reading, every command, every second — so that if something does go wrong, someone can reconstruct exactly what happened, well after the fact, from a record nobody was watching in real time.

Markets built the identical thing for one very specific blind spot: the OTC derivatives market, where trades are negotiated privately between two parties, off any exchange, with no order book and no public tape recording any of it.

What a repository actually is

A trade repository doesn't execute a trade, clear it, or hold a single rupee or dollar of it — it isn't the market, it isn't a clearinghouse, and it isn't a bank. It's a permanent, standardized log: who entered into this swap, with whom, for how much, on what terms, and when. Before 2008, that information about the OTC derivatives market barely existed in one place at all — not for the banks trading it, and not for the regulators meant to be watching the whole system. AIG's collapse made painfully clear what happens when nobody, including the regulator, can see how concentrated that exposure has become until it's already failing.

Example 1: the US answer, and what happens when the record itself goes wrong

Dodd-Frank's Title VII made reporting to a registered swap data repository mandatory for the US OTC derivatives market, tied to three separate identifiers that have to travel with every trade: a Unique Swap Identifier for the transaction itself, a Legal Entity Identifier for each counterparty, and a Unique Product Identifier classifying what was actually traded. The rules themselves aren't static — the CFTC's "ReWrite" of its reporting requirements went live in December 2022, and the Unique Product Identifier only became mandatory for credit, equity, FX, and interest-rate swaps on January 29, 2024; commodity swaps still don't have a compliance date at all.

Having the rule doesn't guarantee the record is right. In 2024 the CFTC fined Barclays $4 million for failing to correctly or promptly report more than five million swap transactions between 2018 and 2023 — years of duplicate swap identifiers, wrong primary economic terms, misreported timestamps, and errors in the ongoing "continuation data" a swap keeps generating over its life. Nobody had to falsify anything or hide a position; the reporting pipe itself was just quietly, structurally wrong for half a decade before anyone caught it. Barclays wasn't alone — across roughly a year, the CFTC levied more than $60 million in penalties against six different swap dealers for the same underlying failure: a flight recorder that had been recording the wrong numbers the entire time.

Example 2: India's answer, doing the job years before it had the title

India's version predates Dodd-Frank's actual reporting mandate by more than the law itself suggests. Under RBI's direction, the Clearing Corporation of India (CCIL) started capturing data on rupee-denominated interest rate swaps in August 2007 — years before Dodd-Frank was even written. But CCIL didn't formally hold the legal title of India's designated Trade Repository until RBI granted it that status in June 2019, under the framework the Payment and Settlement Systems (Amendment) Act, 2015 created. For twelve years, CCIL was doing exactly the job this essay describes without holding the legal label for it at all. Forex derivatives reporting was phased in separately: interbank USD-INR forwards, swaps, and options from July 2012; client-level transactions from April 2013; cross-currency swaps and foreign-currency interest rate swaps by December 2013. Reporting is mandatory throughout, not optional — every scheduled commercial bank and primary dealer for interest rate swaps, every Category-I authorised dealer bank for the forex side.

India is also, right now, closing the exact gap that cost Barclays $4 million. In October 2025, RBI issued a draft circular mandating a Unique Transaction Identifier for every OTC derivative trade, built to conform to the same CPMI-IOSCO global technical standard the US identifiers already reference — aimed squarely at the duplication and cross-system mismatches that come from not having one consistent ID for the same trade. RBI originally planned to require it from April 1, 2026; after industry feedback, that date was pushed to January 1, 2027. The US learned this lesson by fining a bank after five years of quietly wrong records. India is legislating the fix before its own version of that failure has had the chance to happen.

Reality check: the recorder doesn't stop the crash

It's worth being exact about what a trade repository changes and what it doesn't. Before one exists, a regulator can't even ask the right question during a crisis, because the data to answer it doesn't live anywhere. After one exists, the regulator can reconstruct exactly who was exposed to whom — but only after the fact, and only if the record itself is accurate, which Barclays' five years of errors show is never guaranteed just because a system is technically "reporting." A mandatory identifier, whether it's the US's USI or India's incoming UTI, narrows exactly one way the record can go wrong — it doesn't touch any of the others Barclays also got fined for, like misreported timestamps or wrong economic terms. A flight recorder doesn't prevent a crash. It only prevents the crash from staying a mystery, and only for the parts of the story it was actually built to record.

Why this matters for a Business Analyst

Back to the flight recorder

A requirement that says "ensure swap reporting is accurate" is not a requirement yet — it's a direction without a destination. Accurate against which of the identifiers: the USI, the LEI, the UPI? Accurate at the moment of trade, or accurate across every piece of continuation data a swap generates for years afterward, the exact category Barclays got wrong? A system can pass every connectivity test, send every message, and receive every acknowledgment — exactly as Barclays' did for five straight years — while still being silently, structurally incorrect underneath. The lesson isn't "add a validation step." It's that "reporting is happening" and "reporting is correct" are two different claims, and only testing against the second one would ever have caught what the first one missed.

Lighthouse Insight

Nobody checks a flight recorder until something crashes. For years, nobody checked whether Barclays' swap reports were actually right, either — the pipe looked fine from the outside the entire time. CCIL was already doing this job in 2007, a dozen years before it held the legal title for it, and India's regulator is now writing the identifier fix into law before its own five-year Barclays moment gets the chance to happen. Both records exist for the identical reason: not to stop the next crisis, but to make sure that when someone finally has to ask what happened, an answer is sitting there waiting — and, increasingly, that the answer is actually correct.

Reference anchors

• CFTC: Data Recordkeeping (Dodd-Frank Title VII)
• CFTC: Designates Unique Product Identifier for Swaps Recordkeeping and Reporting
• CFTC Press Release: CFTC Orders Barclays to Pay $4 Million for Swap Reporting Violations
• CFTC Press Release: CFTC Orders Three Financial Institutions to Pay Over $50 Million for Swap Reporting Failures
• CCIL: Trade Repository
• CCIL: Introduction to Trade Repository Services
• Business Standard: RBI Defers UTI Framework for OTC Derivative Transactions to January 2027
• TaxGuru: RBI Mandates Unique Transaction Identifier for All OTC Derivatives, 1st January 2027