Series 57 Reporting Trades to the Designated Reporting Facility Guide
May 12, 2026
Study reporting trades to the designated reporting facility for FINRA Series 57 with learning objectives, trader workflow controls, decision rules, and exam traps.
On this page
This Series 57 lesson covers reporting trades to the designated reporting facility within Books, Records, Trade Reporting, Clearance, and Settlement. Read it as a securities-trader exam lesson: the question usually asks what the trader, firm, supervisor, or reporting function must do next when an order, quote, market state, product restriction, customer interest, or post-trade record creates a control issue.
For this section, the working frame is trade reporting, CAT and books-and-records evidence, confirmation, clearance, settlement, and exception handling. Strong answers treat post-trade records as part of the regulated trade lifecycle, not as clerical cleanup.
Learning Objectives
Differentiate key FINRA trade reporting facilities at a high level (ADF, TRFs, OTC Reporting Facility) and identify when each is used.
Explain the concept of trading otherwise than on an exchange at a high level and identify trade reporting implications.
Identify core trade reporting data elements and common modifiers (capacity, short sale indicator, late/correction) at a high level.
Explain timeliness concepts for trade reporting at a high level and why accurate timestamps and prompt reporting matter.
Describe trade acceptance/rejection at a high level and identify common reasons a trade report may be rejected.
Explain the obligation to honor trades at a high level and identify what happens when a reported trade is disputed.
Given a scenario, select the appropriate reporting facility based on the security type and where/how the trade was executed (high level).
Identify exemptions or special handling for trade reporting by certain ATS activity at a high level.
Explain the concept of multiple MPIDs for trade reporting and why firms may use multiple MPIDs for operational and compliance purposes (high level).
Identify audit trail requirements associated with trade reporting at a high level and explain how audit trails support regulatory review.
Describe common trade reporting errors (wrong symbol/price/size/modifier) and identify high-level remediation steps (cancel/correct/“as of”).
Identify supervisory controls for trade reporting quality, including reconciliations and exception monitoring (high level).
Explain, at a high level, how reporting rule violations are identified and handled, including documentation of corrective actions.
Exam Focus
Series 57 is not a broad equity-market vocabulary exam. It tests trading judgment under controls. The best answer normally identifies the trading event, asks whether a restriction or customer duty applies, and then chooses the compliant execution, correction, reporting, or escalation step.
The dominant Function 1 material is front-end trading control: market making, order handling, market access, quote behavior, offerings, OTC activity, options, short sales, customer orders, and Regulation NMS. Function 2 is the proof layer: trade reports, audit trails, records, confirmations, and settlement.
How to Apply This Section
Use this sequence when a Series 57 vignette combines several facts:
Step
Question
Why it matters
Identify the event
Is this about an order, quote, market access path, product restriction, customer duty, report, record, or settlement step?
It prevents treating every stem as ordinary execution.
Check the gate
Is there a halt, Reg SHO issue, Reg M setting, market access control, customer-order duty, or reporting requirement?
Restrictions and controls come before execution preference.
Preserve the record
What ticket, timestamp, CAT field, report, approval, or exception record proves the action?
Series 57 often tests the audit trail behind the trade.
Choose the next step
Route, reject, clarify, correct, report, document, supervise, or escalate.
The best answer protects market integrity and creates a clean record.
Decision Table
If the stem includes…
First concern
Stronger answer pattern
execution occurred off exchange or under a special condition
trade reporting path
report to the correct facility with accurate timing and modifiers
CAT, timestamp, LTID, or order route field is wrong
audit-trail integrity
correct the record and preserve the correction trail
confirmation or settlement problem appears
post-trade completion
resolve through the proper confirmation, clearing, settlement, or close-out process
execution was clean but records are defective
standalone compliance issue
do not treat the trade as fully handled until records and reports are correct
What Stronger Answers Usually Do
apply the restriction before judging execution quality
clarify unclear order instructions instead of inferring customer intent
respect market access, Reg SHO, Reg M, Reg NMS, and venue/system controls
correct trade reports, CAT fields, timestamps, and settlement exceptions promptly
escalate manipulative, clearly erroneous, restricted, or poorly documented activity
Common Pitfalls
assuming a correct execution cures a bad report
treating timestamps or identifiers as minor details
ignoring settlement or close-out consequences after execution
treating a profitable or well-priced trade as acceptable even when the process was restricted
fixing the execution problem while ignoring the reporting or recordkeeping consequence
Review Checklist
Before leaving this section, make sure you can address these prompts from memory:
Differentiate key FINRA trade reporting facilities at a high level (ADF, TRFs, OTC Reporting Facility) and identify when each is used.
Explain the concept of trading otherwise than on an exchange at a high level and identify trade reporting implications.
Identify core trade reporting data elements and common modifiers (capacity, short sale indicator, late/correction) at a high level.
Explain timeliness concepts for trade reporting at a high level and why accurate timestamps and prompt reporting matter.
Describe trade acceptance/rejection at a high level and identify common reasons a trade report may be rejected.
Explain the obligation to honor trades at a high level and identify what happens when a reported trade is disputed.
Given a scenario, select the appropriate reporting facility based on the security type and where/how the trade was executed (high level).
Identify exemptions or special handling for trade reporting by certain ATS activity at a high level.
Explain the concept of multiple MPIDs for trade reporting and why firms may use multiple MPIDs for operational and compliance purposes (high level).
Identify audit trail requirements associated with trade reporting at a high level and explain how audit trails support regulatory review.
Identify the control, report, record, or escalation step that proves the correct next action.
Explain why the wrong answer would create a market-integrity, customer-protection, or audit-trail defect.