Surveillance and reporting requirements for trading

Surveillance and reporting requirements for trading appears in the official CIRO Trader Exam syllabus as part of Trade Desk Function, Supervision and Compliance. Questions in this area usually test whether you can identify the controlling rule, role, or workflow consequence in a trading scenario rather than simply restate a definition.

Learning Objectives

• Surveillance and reporting requirements for trading, including transaction reporting, conduct in debt securities markets, Consolidated Short Position Reporting (CSPR), MTRS, Extended Failed Trades (EFTR), Trade Variations or Cancellations Reporting (TVCR), Regulatory Marker Correction System (RMCS), and gatekeeper reporting.
• The surveillance, reporting, or escalation implication that best matches the facts.
• Distinguish the reporting system, debt-market conduct issue, or surveillance response that best fits the scenario.

Exam Angle

The stronger answer usually classifies the participant, marketplace, product, or control issue first, then applies the rule to the exact trading context. Watch for fact patterns that blur client service, market structure, supervision, and escalation, because those are the scenarios where this syllabus language becomes exam-relevant.

Key Takeaways

• Start by identifying which participant, desk role, marketplace, or control framework governs the fact pattern.
• Translate the rule into a trading consequence such as order handling, supervision, documentation, reporting, or escalation.
• Treat this section as scenario logic, not as isolated terminology.