Venor MarketsMarket PulseHome

Regulatory Reporting and Record-Keeping for Retail Brokers: How Order Records, Communications and Retention Schedules Are Specified and Audited

Why Brokers Keep Records of Orders Nobody Ended Up Placing

The paperwork behind a trade is not bureaucracy for its own sake — it is how regulators reconstruct what really happened.

Published · 2026-11-13

Two different questions, one filing cabinet

Here is a quiet distinction that shapes a lot of retail brokerage life. There is reporting, and there is record-keeping. They sound like siblings, but they answer different questions. As one specialist source puts it neatly: transaction reporting asks “what trade must be reported to the regulator?”, while order record-keeping asks “can the regulator reconstruct everything that happened before, during and after that transaction?”

That second question is why a broker’s records include orders that never became trades. An order that was amended six times, half-filled, then cancelled tells a story a completed-trade report cannot. If a regulator is investigating something that looks like spoofing — placing orders with no intention of executing them, to nudge prices — the evidence lives in the order book’s paper trail, not in the trade tapes. Regulation is rarely glamorous. It is, however, extremely good at keeping receipts.

What actually has to be recorded

In Europe, the rulebook for trading venues — regulated markets, multilateral trading facilities (MTFs) and organised trading facilities (OTFs) — is Commission Delegated Regulation (EU) 2017/580, usually called RTS 24. It sets out the minimum records venues must keep so a competent authority can reconstruct every stage of an order’s life.

The ingredient list, drawn from the RTS 24 specification, is practical. A unique order identifier. The venue’s identifier. Timestamps for submission and every later event. Client or participant identification, which may include a Legal Entity Identifier (an LEI — a standard global code for a firm), a national client identifier, or an account reference. The financial instrument, typically by ISIN. Order characteristics: buy or sell, order type, quantity, price, currency, validity, and whether the firm acted as agent or principal. Where algorithms are involved, identifiers tied to automated decision-making. And then the lifecycle events themselves — amendments, partial executions, suspensions, resumptions, cancellations, full executions.

Alongside sits Annex IV of Commission Delegated Regulation (EU) 2017/565, which covers the firm side: Section 1 for orders and decisions to deal, Section 2 for executions. The two sections are designed as a pair. Section 1 captures the intent to trade; Section 2 captures the result. Together they let an investigator answer questions like: which order produced this trade, and had it been amended beforehand?

The European legal backbone

Behind the detailed standards sits Article 25 of MiFIR, which requires investment firms to keep relevant data on all orders and transactions at the disposal of the competent authority for five years. For client transactions, that includes client identity details. Trading venues must keep order data advertised through their systems, in machine-readable format, for at least five years.

Article 25 also sets out the fields ESMA’s technical standards should cover: the identification code of the member or participant transmitting the order, the order’s own identification code, transmission date and time, order characteristics such as type, limit price and validity, specific instructions, details of modifications, cancellations and executions, and agency or principal capacity. There is a transition note worth knowing about: amendments to Article 25 apply once the revised version of RTS 24 starts applying. Until then, the consolidated Article 25 text of 9 January 2024 and the current RTS 24 apply.

Across the Atlantic, a numbers game

The United States takes a different architecture. Under Rule 17a-4, broker-dealers must preserve certain records for at least six years, with the first two in an easily accessible place. Other categories — including originals of communications received and copies of communications sent relating to the business, which explicitly covers sales scripts and required telephone call recordings — carry a three-year period, again with two years of easy access. Account records relating to opening and maintaining an account must be kept for six years after the account closes. Some documents, like partnership articles and minute books, are kept for the life of the enterprise.

Rule 17a-3 is the companion provision: it says which books and records must be created in the first place. One detail that matters enormously in practice is that transaction orders must record the time the order was received and the time it was executed. That timestamp pair is what lets regulators detect schemes such as late trading.

On communications, the rule is deliberately technology-neutral. It is a standard, not a gadget list — which is why it has stretched to cover email and social media as those became part of ordinary business conversation.

How electronic storage is policed

Both regimes converged on a similar insight: keeping records electronically is fine, provided you cannot quietly rewrite history. Under Rule 17a-4, an electronic recordkeeping system must either preserve records in a non-rewriteable, non-erasable format, or maintain a complete time-stamped audit trail capturing every modification and deletion, when it happened, and who did it. It must automatically verify the completeness and accuracy of its storage processes, allow records and their audit trails to be downloaded in human-readable and reasonably usable electronic formats, and include a backup system or equivalent redundancy.

There are human safeguards too. A designated executive officer must file an undertaking with the firm’s designated examining authority promising to furnish records promptly on request, and to download copies if the firm itself fails to. That officer may appoint up to two designated officers and three designated specialists — but appointing them does not shed the obligation.

The CFTC’s Regulation 1.31 travelled a parallel road. Its amendments allowed recordkeepers to store most categories of required records on micrographic or electronic media for the full five-year maintenance period, harmonising procedures for firms regulated by both the CFTC and the SEC. The stated goals were cost reduction, time savings, and — crucially — continued timely access for auditors and investigators to a reliable system of records.

Current CFTC language adds texture. Regulatory records stored electronically include the data necessary to access, search or display them, plus all data describing how and when they were created, formatted or modified. Records must be kept in a form and manner ensuring authenticity and reliability, with systems that maintain security and signatures, that can produce records even during an emergency or disruption, and an up-to-date inventory of every system holding information needed to access them. Paper-only records must be readily accessible for two years; electronic records must be readily accessible for the whole retention period.

The paper order ticket that refused to die

One of the more revealing episodes in the CFTC’s rulemaking history concerns original written trading cards and customer order tickets. Commenters argued hard for electronic storage, citing the cost of organising, indexing, storing and retrieving paper — one exchange estimated it spent $100,000 a year retrieving records requested under Regulation 1.31.

The Commission declined to rely solely on electronic versions at that time. Its reasoning was investigative rather than nostalgic: scanning errors, such as missing information on the back of an order ticket, could deprive investigators of material facts. Investigators might struggle to distinguish ink colours, or to detect erasure or the use of correction fluid — precisely the discrepancies that can show someone added information after the bulk of it was recorded. A one-year retention compromise was also rejected, because the Commission found no reliable basis for predicting when a particular original record would be needed.

What emerged instead was a practical accommodation: firms could initially respond to requests with electronic reproductions, unless staff requested otherwise, and staff would generally review those reproductions before asking for originals.

Communications, retention and the jurisdiction question

Under MiFID II Article 16(7), investment firms must record relevant conversations and electronic communications relating to client orders or that could lead to a transaction — telephone, video, chat, email, instant messaging, and internal coordination connected to client orders. Customers must be told at the start that recording is taking place and may request a copy during the archiving period; if a customer refuses, advice relating to accepting, transmitting or executing orders cannot be given. Recordings are kept at least five years, extendable to seven at a supervisor’s request, in tamper-proof form with every change traceable.

Retention periods, then, are not one number. MiFID II is generally described as requiring at least five years, with many jurisdictions extending to seven or more. In the US, Rule 17a-4 uses six years, three years and life-of-enterprise depending on the record. CFTC rules use five years generally, one year for oral communications where retention is required, and for certain swap records the life of the transaction plus five years. Rule 17a-4 also does not preempt other legal requirements, so a firm may need to keep something longer than the securities rule demands.

This is where jurisdiction stops being an abstraction. The same brokerage, the same order, the same chat message can attract different clocks and different storage conditions depending on where it operates and which regulator supervises it. National competent authorities enforce locally — the FCA in the UK, BaFin in Germany, and so on — and local law can add its own layer. Germany’s criminal code, for instance, treats unauthorised recording of conversations seriously, with the MiFID II obligation providing the legal basis. None of this is advice about any specific firm’s obligations; it is a map of why the answer to “how long do we keep this?” begins with “where are you?”

What audits actually probe

Supervisory attention tends to focus less on whether data exists and more on whether it is complete, accurate and retrievable. A specialist source notes that since MiFID II took effect in January 2018, publicly available enforcement has concentrated far more on transaction reporting failures than on RTS 24-specific breaches — with the FCA imposing substantial penalties for deficiencies in transaction reporting controls. That is not reassurance. It reflects visibility: transaction reports are transmitted constantly and generate rejections and feedback, while order records sit quietly until someone asks.

And someone increasingly does. The same source reports a marked increase in RTS 24 and Annex IV requests from regulators across the UK and EU, citing greater emphasis on data integrity and audit trails. Practical failure modes are mundane: order and execution data spread across multiple front-office systems in inconsistent formats; tactical storage such as CSV files lacking immutable, write-once storage or proper audit trails; and retrieval that takes months because the data must be collated and transformed.

Perhaps the most useful point in the source material is that Annex IV does not come with the equivalent of a validation rulebook. Unlike MiFIR transaction reporting under RTS 22 — which has XML schemas, validation rules and rejection codes — the order record-keeping provisions define what must be recorded but stop short of prescribing a common technical implementation standard. Where Annex IV fields overlap with Article 25 and 26 data, the regulation requires consistency; in practice, firms build their own internal data models and validation logic. The result is broad agreement on what to keep, and variation in how it is populated and linked.

Where systems cannot automatically link an execution to its originating order — voice brokerage, telephone-negotiated trades — regulators still expect the trail to hold. The suggested compensating controls are unglamorous: manual unique reference numbers assigned at the point of receipt, precise timestamps, retained voice recordings and telephone metadata, broker notes referencing the originating instruction, and written procedures describing how manual correlations are made and independently reviewed. “Reasonable compensating controls” is the phrase to remember. It is not an exemption; it is a proportionate answer to a real constraint.

For retail brokers, the through-line is simple. Records are not a filing chore bolted on after the trade. They are the reconstructable version of the trade — orders that never filled, calls that shaped a decision, timestamps that prove which came first. Get them right and an audit becomes a conversation. Get them wrong and it becomes an excavation.

Ovi
Ask OviThis entire article is in Ovi's context. Ask in any language.
I’m here with the complete article in front of me. What would you like me to explain?

Educational explanations only—not personalised trading instructions.

Research sources reviewed

  1. Article 25 Obligation to maintain records (esma.europa.eu)
  2. Final Rule 1.31 (cftc.gov)
  3. 17 CFR 1.31 -- Regulatory records; retention and production. (ecfr.gov)
  4. 17 CFR Part 1 - Recordkeeping (ecfr.gov)
  5. 17 CFR § 240.17a-4 - Records to be preserved by certain ... (law.cornell.edu)
  6. Broker-Dealer Recordkeeping Requirements (law.temple.edu)
  7. 17 CFR § 1.31 - Regulatory records; retention and production. (law.cornell.edu)
  8. MiFID II RTS 24 & Annex IV Order Record-Keeping Explained (reg-x.co.uk)
  9. 160624-rts-24_en.pdf - European Commission (ec.europa.eu)
  10. MiFID II: A Guide to Storing and Preserving Financial Records (archondatastore.com)
  11. MiFID II Directive: Recording Obligations and Retention Periods ... (asctechnologies.com)
  12. MiFID II RTS 24 & Article 16(6) 16(7) Record-Keeping Guide (reg-x.co.uk)

Comments

Comments are coming soon.