A day at the compliance desk

The desk sits across every stage of the order–trade–fulfillment lifecycle rather than inside any one of them. This traces what it works from, what it checks through the day, and what it borrows from the quantitative desks next door.

← The Primer

Lesson 01 · the compliance desk

The compliance desk works from a set of queues. Each queue holds the exceptions:

  • the trades that did not match
  • the alerts a review has yet to clear
  • the reports a regulator has yet to accept

Three tasks run through the day. Reconciliation compares the same trade as it appears in different systems and resolves where they disagree. Surveillance reviews the day's activity for patterns that may signal market abuse. Reconstruction assembles the full record of a trade, from order to settlement, whenever a regulator, a court, or the desk's own review calls for it. Reporting sits alongside all three, checking each transaction report for completeness before its deadline.

None of this belongs to a single stage of the lifecycle. The desk reads the record at every stage, across the order–trade–fulfillment lifecycle.

Where the desk's data comes from Four source systems feed into an alignment layer, which feeds the compliance desk and its four working areas: reconciliation, surveillance, reporting, and case files. Front office orders, fills Books of record official version Post-trade clearing, settlement Reference data prices, identifiers The records are aligned timestamps matched, identifiers mapped, tolerances applied THE COMPLIANCE DESK Reconciliation breaks, matching Surveillance alerts, cases Reporting submit, repair Case files escalations
Figure 1

Where the desk's data comes from, and where it converges. Four systems hold different versions of the same trade; the desk reconciles them.

The four sources hold different versions of the same trade. The front office knows what the trader intended and what filled. The books hold the firm's official version. Clearing and settlement hold what actually cleared and is due to settle. Reference data supplies the prices and identifiers that make the other three legible. They may differ in certain respects: a timing difference, a fee booked on one side, or an identifier mapped two ways. Reconciliation fixes them where feasible and escalates where they cannot.

What a supervisor sees is not the trades. It is the health of the queues: how many breaks are open, how old the oldest one is, which deadlines are close. The day's shape is set by what broke and what is late, not by what went right.

Rows marked risk / liquidity are the points where the desk draws on the quantitative desks. Every task carries the rule behind it, across three jurisdictions.

Overnight → morningReconciliation and break triage

Match trades against confirmations, clearing records, and the firm's books; work the exceptions for anything unmatched, broken, or unconfirmed.

USExchange Act Rules 17a-3 / 17a-4 (books and records); Rule 10b-10 (confirmations); Rule 15c6-1 (T+1, since May 28, 2024) EUMiFID II Art. 16(6); RTS 24 (order records, Reg. 2017/580); RTS 25 (clock synchronisation, Reg. 2017/574); EMIR Art. 11 (timely confirmation) UKOnshored UK RTS 24 / RTS 25; FCA SYSC 9; COBS 16A (confirmations); UK EMIR Art. 11. T+1 from October 11, 2027
MorningLimit and threshold checksrisk / liquidity

Check positions against exposure, concentration, and capital limits. A breach is flagged, timestamped, and routed, sometimes on a notification clock. The desk flags it; it does not resolve it.

USExchange Act Rule 15c3-5 (market access, pre-trade credit and capital checks); Rule 15c3-1 (net capital); CFTC Part 150 (position limits) EUMiFID II Art. 17 and RTS 6 (algorithmic-trading controls, Reg. 2017/589); MiFID II Art. 57 (commodity position limits) UKOnshored RTS 6 and FCA MAR 7A; IFPR / MIFIDPRU (prudential); commodity position limits reformed under FSMA 2023 and FCA PS25/1, venues setting limits from July 6, 2026
MorningMargin and collateral checksrisk / liquidity

Confirm margin calls match expected exposure and that collateral moved as expected. A mismatch is often the first sign of a broken trade, looping back into the reconciliation queue.

USUncleared margin rules (CFTC and prudential regulators, Dodd-Frank Title VII); Regulation T (Federal Reserve, securities margin) EUEMIR Art. 11 and the margin RTS (Reg. 2016/2251), for uncleared over-the-counter derivatives UKUK EMIR Art. 11 and the onshored UK margin RTS (Bank of England / PRA and FCA)
Mid-morningSurveillance alert review

Work the alert queue: spoofing and layering, wash trades, marking the close, threshold breaches. Most clear as false positives once context is added; the rest escalate to a case file.

USExchange Act §9(a) and §10(b) / Rule 10b-5 (manipulation); Commodity Exchange Act §4c(a)(5) (spoofing, Dodd-Frank §747); FINRA Rule 3110 (supervision) EUMarket Abuse Regulation (Reg. 596/2014) Art. 12 (manipulation), Art. 15 (prohibition), Art. 16 (suspicious transaction and order reports) UKUK MAR (retained Reg. 596/2014) Art. 12, 15, 16; administered by the FCA, with supervision under SYSC and SUP
Applied through reviewMarket-liquidity contextrisk / liquidity

Read each alert against the market it came from: typical volume, spread, and depth. A pattern that looks like manipulation in a liquid name may be ordinary in a thin one. A lens, not a queue.

USAnalytical context; anchored in the manipulation standard above, with no separate reporting duty EUMiFID II / MiFIR liquid-market determination and transparency regime, as reference UKOnshored UK MiFIR transparency regime, as reference
MiddayTransaction reporting

Check completeness and field accuracy before submission deadlines; correct and resubmit prior-cycle rejections. A large share of the desk's hours goes here.

USConsolidated Audit Trail (Rule 613 / NMS Plan); large trader reporting (Rule 13h-1); CFTC swap data reporting (Parts 43 and 45) EUMiFIR Art. 26 and RTS 22 (Reg. 2017/590); EMIR Art. 9 (derivatives); SFTR (Reg. 2015/2365) UKUK MiFIR Art. 26 and UK RTS 22 (FCA); UK EMIR Art. 9; UK SFTR not onshored for non-financial counterparties. No UK CAT equivalent
AfternoonRecord requests and reconstruction

On request from the front office, legal, or a regulator, assemble the record across systems: order, execution, allocation, confirmation. The desk's most labor-intensive task.

USExchange Act Rule 17a-4 (retention); CFTC Rule 1.35 (records of commodity interest transactions) EUMiFID II Art. 16(7) (recording of telephone and electronic communications) and Delegated Reg. 2017/565; record retention UKOnshored MiFID organizational regulation; FCA COBS 11.8 (telephone recording); SYSC 9 (retention)
Pre-close → handoffSettlement liquidity checkrisk / liquidity

Check expected inflows against obligations ahead of settlement; a funding gap surfaces as a settlement fail, itself reportable and reconstructible. Capture the day's trades for tomorrow; flag what is unresolved.

USSEC Rule 15c6-1 (T+1, since May 28, 2024); Regulation SHO Rule 204 (close-out of failures to deliver) EUCSDR (Reg. 909/2014) Art. 7 (settlement discipline, cash penalties for fails); T+1 from October 11, 2027 (CSDR Art. 5 amendment) UKUK CSDR onshored, but the settlement discipline regime was not adopted; industry contractual frameworks apply. T+1 from October 11, 2027 (aligned)
Figure 2

The desk's day, and the rule behind each task, across the United States, the European Union, and the United Kingdom. Where the three diverge, the difference is named in the row.

The quantitative layer

Some of what the desk checks is quantitative. None of it is the desk's own arithmetic. The risk and treasury desks produce the numbers; the compliance desk consumes them, as an input to a reporting, surveillance, or reconciliation decision.

Four dependencies recur. Exposure and limit figures, so a breach can be flagged and timestamped; some breaches carry a notification clock, set by rules such as the market access rule in the United States (Exchange Act Rule 15c3-5). Margin and collateral valuations, so a mismatch surfaces as a broken trade rather than a silent gap; the duty to exchange margin on uncleared derivatives sits in EMIR Article 11 in the European Union. Liquidity context, the typical volume, spread, and depth of an instrument, so an alert can be read against the market it came from. Settlement funding, so a shortfall is caught before it becomes a settlement fail.

The quantitative work is ancillary to the compliance function. It enters as evidence and as context. The desk's own obligations lie elsewhere: in the record-keeping, reporting, and surveillance rules that require it to account for a risk or liquidity event after the fact, in terms a reconstruction can defend. The desk does not manage the exposure; its task is to explain it later, on the record.

What the desk borrows from the quantitative desks The risk and treasury desks produce numbers that the compliance desk consumes as four inputs: limit and exposure figures, margin and collateral values, liquidity context, and settlement funding. Risk and treasury produce the numbers THE DESK CONSUMES Limit and exposure figures so a breach can be flagged and timed Margin and collateral values so a mismatch surfaces as a break Liquidity context volume, spread, depth for an alert Settlement funding so a fail is caught before it lands
Figure 3

What the desk borrows from the quantitative desks, and why. The numbers are produced elsewhere; the desk uses them as evidence and as context.

Further reading

United States

  • Exchange Act Rules 17a-3, 17a-4 — the books-and-records and retention rules a broker-dealer works to (SEC).
  • Rule 10b-10; Rule 15c3-5 — customer confirmations; the market access rule (SEC).
  • Rule 15c6-1; Reg SHO Rule 204 — the T+1 settlement cycle; close-out of failures to deliver (SEC).
  • Rule 613; Rule 13h-1 — the Consolidated Audit Trail; large trader reporting (SEC).
  • CEA §4c(a)(5); Parts 43, 45, 150; Rule 1.35 — spoofing; swap data reporting; position limits; records (CFTC).
  • FINRA Rule 3110 — the supervision rule.

European Union

  • Directive 2014/65/EU (MiFID II) — Arts. 16, 17, 57: organization and records, algorithmic-trading controls, commodity position limits.
  • Regulation 600/2014 (MiFIR) Art. 26 — with RTS 22 (Reg. 2017/590) reporting, RTS 24 (2017/580) order records, RTS 25 (2017/574) clocks, RTS 6 (2017/589) algorithmic trading.
  • Regulation 648/2012 (EMIR) — Arts. 9 and 11, with the margin RTS (Reg. 2016/2251).
  • Regulation 596/2014 (MAR) — Arts. 12, 15, 16: manipulation, prohibition, and suspicious transaction and order reports.
  • Regulation 909/2014 (CSDR) — Arts. 5 and 7: settlement periods and discipline. T+1 from October 11, 2027.
  • Regulation 2015/2365 (SFTR) — securities financing transaction reporting.

United Kingdom

  • FCA Handbook — SYSC 9 (records), COBS 11.8 (telephone recording), COBS 16A (confirmations), MAR 7A (algorithmic trading).
  • UK MAR, UK MiFIR, UK EMIR — retained EU law, administered by the FCA.
  • UK CSDR — onshored, but the settlement discipline regime (cash penalties, mandatory buy-in) was not adopted.
  • FSMA 2023; FCA PS25/1 — the reform of commodity derivatives position limits, effective July 6, 2026.
  • MIFIDPRU (IFPR) — the prudential regime for investment firms.

Books and background

  • Baker, The Trade Lifecycle — the trading process end to end; the book closest to this site's remit (Wiley).
  • Weiss, After the Trade Is Made — the operations canon: order to processing to books and records (New York Institute of Finance).
  • Simmons, Securities Operations — trade and position management, the desk's daily material (Wiley).
  • Loader, Clearing, Settlement and Custody — the post-trade mechanics behind fulfillment (Butterworth-Heinemann).
  • Harris, Trading and Exchanges — market microstructure for practitioners (Oxford, 2003).
  • Moloney, EU Securities and Financial Markets Regulation — the rulebook in context, market abuse included (Oxford, 4th ed. 2023).

Several of these are in revision. The MiFIR transaction-reporting standards are being remade under Regulation 2024/791, and the EU's settlement-discipline standards are being finalized ahead of T+1. Confirm the current text against the issuing body before relying on any detail.