Devancore Inc.
Devancore Post-Trade Glossary
Glossary
SEC Rule 606 Reporting
An SEC Rule 606 reporting workflow turns order-routing, venue, rebate, fee, and payment-for-order-flow records into reviewed public quarterly disclosures and customer-specific reports with retained evidence.
Document source: https://devancore.com/glossary/sec-rule-606-reporting/
Devancore Post-Trade Glossary
SEC Rule 606 Reporting
An SEC Rule 606 reporting workflow turns order-routing, venue, rebate, fee, and payment-for-order-flow records into reviewed public quarterly disclosures and customer-specific reports with retained evidence.
Definition
An SEC Rule 606 reporting workflow is the operating process that turns order-routing activity into disclosure. Rule 606 of Regulation NMS requires broker-dealers to disclose where they routed customer orders and what economic arrangements attach to those routes. The practical control problem is lineage. A public XML file or a customer PDF is only useful if the firm can show which orders, venues, rebates, fees, and payment-for-order-flow amounts produced it, and who reviewed it before it left the firm.
This page explains the workflow, not a legal determination of whether a particular firm, order, or venue is in scope. Coverage, exemptions, and disclosure content remain with the firm and its counsel. Software can support records, review, and evidence. It cannot replace that ownership.
Rule 606 disclosure records
Rule 606 disclosure records
The report is only as strong as the routing, economics, and review records behind it.
| Record area | What the workflow holds | Control question |
|---|---|---|
| Order class | Held or not-held, directed or non-directed, NMS stock or listed option, marketable versus non-marketable limit | Was the order tagged the way the disclosure rule uses it? |
| Routing path | Parent order, child orders, first venue, later venues, and FIX or API route messages | Can each disclosed venue be traced to a source routing event? |
| Venue economics | PFOF, rebates, fees, profit-sharing, and net aggregate by venue and category | Do disclosed amounts reconcile to venue invoices and internal books? |
| Material aspects | Described terms of payment, ownership, or other relationships that may affect routing | Does the qualitative text match the arrangements actually in force for the quarter? |
| Customer request | Request date, customer, lookback window, 606(b)(1) or 606(b)(3) scope, and delivery evidence | Was the request owned, clocked, produced, and retained? |
| Review package | Draft report, break list, approver, publication or delivery timestamp, and amendment reason | Can a reviewer show the file was checked before it left the firm? |
Rule 606(a) is the public quarterly report. It covers routing of held, non-directed customer orders in NMS stocks and listed options. NMS stocks are grouped as S&P 500 constituents as of the first day of the quarter and as other NMS stocks. Order types are split, including market, marketable limit, and non-marketable limit. The report identifies venues, the mix of orders sent to each venue, and the net aggregate amount of payment for order flow, profit-sharing, transaction fees, and rebates. Payment for order flow disclosure material aspects describe the terms of those arrangements. The report is produced in the Commission's XML schema and associated PDF renderer, posted on a free public website, and kept posted for three years.
Rule 606(b) is the customer-request path. Rule 606(b)(1) requires, on request, venue identity and related routing facts for the customer's orders over the prior six months. Rule 606(b)(3) institutional order routing disclosure goes further for not-held NMS stock orders: a customer-specific report covering the prior six months by calendar month, including child orders derived from the parent, directed and non-directed sections, principal handling, indications of interest, venue-level routing and execution facts, and average rebates or fees. That report is due within seven business days of the request, using the same XML and PDF formats, subject to de minimis exceptions in Rule 606(b)(4) and (b)(5).
Rule 605 is a different obligation. It concerns execution-quality statistics at market centers. Rule 606 concerns routing disclosure by the broker-dealer. Mixing the two populations, or treating a 605 file as 606 evidence, produces a report that cannot be defended.
FINRA exam requirements for order routing records follow the same chain. FINRA Rule 9217 treats failure to timely disclose or provide complete order routing information as a reportable violation type. Examiners commonly ask for the public file, the underlying order and venue data, rebate and fee support, material-aspects text, and evidence that a supervisor reviewed the output. Rule 17a-3 and Rule 17a-4 still require the firm to make and preserve the source records. FINRA Rule 3110 still requires the supervisory system around that work.
SEC Rule 606 reporting — source to disclosure
Devancore Glossary · devancore.com
SEC Rule 606 reporting — source to disclosure
Devancore Glossary · devancore.com
How it works
A Rule 606 reporting workflow starts with the order population and ends when a public report is posted or a customer report is delivered, with retained evidence. The work is classification, capture, economics, assembly, review, and request handling.
Rule 606 workflow control points
Rule 606 workflow control points
Breaks appear where a published XML file cannot be tied back to orders, venues, and payments.
| Step | Data required | Failure mode |
|---|---|---|
| Classify | Held or not-held intent, directed flag, security universe, and order type | Institutional not-held flow is rolled into the public held report, or the reverse |
| Capture routes | OMS, EMS, FIX route, child-order IDs, and first venue outside the firm | Re-routes and child orders disappear, so venue percentages cannot be explained |
| Net economics | Venue invoices, PFOF, rebates, fees, and internal commission or payment ledgers | Netting rebates and fees for 606 quarterly reports does not match the venue statement |
| Assemble report | XML schema, PDF renderer, S&P 500 versus other NMS grouping, and options categories | Public file is generated without lineage to the underlying order population |
| Review and publish | Maker-checker, material-aspects text, publication time, and public-site copy | File is posted with no recorded review or no retained copy of what was posted |
| Serve requests | 606(b) clock, six-month extract, customer identity, and delivery record | Customer-specific report is late, incomplete, or cannot be reproduced |
Classification is the first control. Held orders are those the broker is expected to attempt immediately. Not-held orders give price and time discretion. Directed versus non-directed status, NMS stock versus listed option, and marketable versus non-marketable limit status all change which disclosure path applies. If the OMS flag is wrong, every later total is wrong.
Routing capture is the second control. The source is usually the order management system, execution management system, and FIX or API route messages. Parent and child orders must stay linked. Rule 606(a) public reports focus on venues to which held orders were routed for execution. Rule 606(b)(3) customer reports use a broader venue concept that can include intermediate brokers that further route without executing. Re-routes that are not retained become unexplained venue percentages.
Economics is the third control. Netting rebates and fees for 606 quarterly reports should reconcile to venue invoices, payment-for-order-flow records, and internal ledgers. A report that uses a planning estimate instead of posted amounts will not survive a books-and-records request. Material-aspects text should describe the arrangements actually in force for that quarter, including profit-sharing or ownership that may influence routing.
Assembly produces the XML and PDF outputs. The population, grouping, venue list, and net amounts should remain traceable to source rows. A generator that cannot re-run from the same extract is not an operating record.
Controls, approvals, and supervisory review sit on both paths. A maker-checker review should cover data breaks, venue mapping, rebate reconciling items, and qualitative text before publication. A 606(b) request needs an owner, received time, seven-business-day clock for 606(b)(3), delivery evidence, and a retained copy of what was sent.
Reporting or examination readiness is the last control. The firm should be able to show the posted public file, the date it was posted, the source extract, the rebate and fee support, the review trail, and any amendment. CAT reporting is a separate order-lifecycle feed. It may help explain routing events, but it does not replace Rule 606 disclosure or the evidence package behind it.
Rule 606 — public report or customer request path
Devancore Glossary · devancore.com
Rule 606 — public report or customer request path
Devancore Glossary · devancore.com
In Devancore™
Devancore — Rule 606 evidence chain
Devancore · evidence stack
Source orders
Orders, routes, child orders, and FIX or API messages enter with identifiers, timestamps, and venue references.
Classification
Held or not-held, directed flag, security grouping, and order type remain attached to the source event.
Economics map
PFOF, rebate, fee, and net-payment inputs stay reconcilable to venue statements and internal ledgers.
Review state
Breaks, material-aspects text, maker-checker approval, publication or delivery, and amendments are owned workflow.
Disclosure package
The public file or customer report can be traced to the same operating records rather than to a one-off extract.
Devancore supports an SEC Rule 606 reporting workflow as a post-trade operating record around orders, routes, venues, economics, exceptions, and review evidence. It can help teams keep source lineage, classification state, break ownership, approval history, and the package used to assemble a disclosure.
Devancore does not act as a broker-dealer, routing venue, market center, or disclosure agent. It does not determine whether an order is in scope, whether a de minimis exception applies, what material-aspects text must say, or whether a published report satisfies Rule 606. Those determinations remain with the firm, its supervisors, and its counsel.
In a Devancore-style workflow, an order, route, child order, venue assignment, rebate or fee input, customer request, or amendment enters as a source event. The record is mapped to account, instrument, order class, venue, amounts, and workflow state. Open, broken, reviewed, published, delivered, or amended remains visible with owner, timestamp, reason, and source reference.
That structure is what operations and compliance actually use. The OMS may know the route. The venue invoice may know the rebate. The website may host last quarter's XML. The 606 problem is whether those facts still join as one explainable disclosure record.
Conversational finance depends on the same chain. A user can ask which venues in the draft 606(a) file have unreconciled rebates, which not-held requests are still inside the seven-business-day clock, which orders lack a held or not-held flag, or which public files were posted without recorded review. The answer should resolve to source orders, routes, amounts, owners, and evidence.
Related terms
- Trade Surveillance
https://devancore.com/glossary/trade-surveillance/
Trade surveillance is the automated monitoring systems broker-dealers use to detect manipulative trading patterns, insider trading indicators, and behavioral anomalies across proprietary, market-making, and customer order trading activity.
- Broker-Dealer Compliance Technology
https://devancore.com/glossary/broker-dealer-compliance-technology/
The software layer that enables broker-dealers to meet SEC and FINRA regulatory obligations — books and records, net capital, supervisory controls, and audit trail — through automation rather than manual processes.
- FIX Protocol in Securities Trading
https://devancore.com/glossary/fix-protocol-securities-trading/
The open messaging standard governing order routing, execution reporting, and allocation between broker-dealers, buy-side firms, and trading venues — upstream of SWIFT.
- Regulatory Reporting — Securities
https://devancore.com/glossary/regulatory-reporting-securities/
The post-trade obligation to submit structured trade data — transactions, positions, and order lifecycle events — to regulators under MiFID II, EMIR, Dodd-Frank, and CAT to establish the supervisory record of each trade.
- Broker-Dealer Audit Trail
https://devancore.com/glossary/broker-dealer-audit-trail/
The immutable, chronologically linked record of every trade lifecycle event — from order receipt through settlement — maintained to satisfy SEC Rules 17a-3 and 17a-4, FINRA clock synchronization requirements, and CAT reporting obligations.
- Rule 17a-3
https://devancore.com/glossary/rule-17a-3-books-and-records/
The SEC rule requiring registered broker-dealers to create and maintain current books and records for every securities transaction - including the blotter, general ledger, customer account ledgers, order tickets, and net capital computation.
- Trade Capture System
https://devancore.com/glossary/trade-capture-system/
The system that books an executed trade into the firm's official records and initiates the post-trade processing workflow from enrichment and matching through to settlement instruction.
- FINRA Supervision Technology
https://devancore.com/glossary/finra-supervision-technology/
FINRA supervision technology is the software infrastructure broker-dealers use to implement, enforce, and document the supervisory controls required under FINRA Rules 3110 and 3120.
- CAT Reporting (Consolidated Audit Trail)
https://devancore.com/glossary/cat-reporting-broker-dealer/
The obligation under FINRA Rule 6800 Series and SEC Rule 613 for broker-dealers to report every NMS and OTC equity order event to the CAT Central Repository by 8:00 AM ET on T+1, with customer account data updated daily through CAIS.
- OMS To Post Trade Integration
https://devancore.com/glossary/oms-to-post-trade-integration/
OMS to post-trade integration is the controlled handoff from order and execution records into allocation, confirmation, enrichment, settlement instruction, reconciliation, supervision, and reporting workflows.
- Maker-Checker Workflow
https://devancore.com/glossary/maker-checker-workflow/
A two-person segregation of duties control requiring that any action entered by one operator must be reviewed and approved by a second before it takes effect.
- Written Supervisory Procedures
https://devancore.com/glossary/written-supervisory-procedures/
The compliance policies a broker-dealer must establish, maintain, and enforce under FINRA Rule 3110 to supervise all business lines and associated persons.
- FIX Engine Connectivity for Broker-Dealers
https://devancore.com/glossary/fix-engine-connectivity/
The software layer managing FIX session state, message sequencing, heartbeats, and failover for broker-dealers connecting to brokers, venues, and ECNs.
- FIX Protocol Trade Capture
https://devancore.com/glossary/fix-protocol-trade-capture/
Open financial messaging standard where MsgType 8 Execution Reports trigger real-time trade capture and settlement pipeline processing for broker-dealers.
- Trade Blotter Post Trade Workflow
https://devancore.com/glossary/trade-blotter-post-trade-workflow/
A trade blotter post-trade workflow turns blotter rows into governed operating records for allocation, enrichment, confirmation, settlement instruction, exception management, reconciliation, supervision, and audit evidence.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/