Trade Repositories and Reporting Infrastructure

Before 2008, most derivatives trades — interest rate swaps, credit default swaps, and the like — were arranged privately between two counterparties with no central record anywhere. When Lehman Brothers collapsed, regulators had no way to quickly answer a basic question: who had exposure to whom, and how much? Trade repositories were built to close that gap. They are centralized databases where dealers and other market participants must report the economic details of every derivatives trade — counterparties, notional, maturity, underlying asset — shortly after execution.

In the U.S., Dodd-Frank requires swap data to be reported to registered swap data repositories (SDRs); in Europe, EMIR imposes a similar requirement funneling data to trade repositories overseen by ESMA. The reports don't just sit passively — regulators use aggregated repository data to monitor systemic concentration (is too much risk piled up at one dealer?) and, in many jurisdictions, a subset of the data is published to give the broader market a sense of trading activity and pricing, even though individual counterparty identities usually stay confidential to the public.

For a trading desk, this means every eligible derivatives trade generates a reporting obligation as a matter of course, handled by middle-office and compliance systems rather than the trader — but a quant building execution or post-trade infrastructure needs to know that a trade isn't "done" the moment it's filled; it also has to flow correctly into the firm's reporting pipeline, matched against the counterparty's own report, or the firm faces regulatory penalties for reporting breaks.