Browse CIRO Exam Guides: CIRE, RSE, Trader, Supervisor & Derivatives

Counterparty risk and margin requirements for AI, AC, and RE

Apply to specific situations relevant to a CFO, counterparty risk and margin requirements for Acceptable Institution (AI), Acceptable Counterparty (AC) and Regulated Entity (RE).

Counterparty risk and margin requirements for AI, AC, and RE appears in the official CIRO Chief Financial Officer Exam syllabus as part of Credit risk management and client accounts. Questions here usually test whether you can identify the controlling rule, control, calculation, workflow, or escalation path in a realistic fact pattern rather than simply restate a definition.

What This Section Is Really Testing

The exam is usually less interested in whether you can repeat the heading than whether you can explain why it matters in the actual dealer, client, governance, capital, operations, market, or supervisory context. Start by identifying the participant, obligation, process, or risk that governs the situation, then ask what action, documentation, or consequence follows.

Learning Objectives

  • Apply to specific situations relevant to a CFO, counterparty risk and margin requirements for Acceptable Institution (AI), Acceptable Counterparty (AC) and Regulated Entity (RE).
  • Assess AI, AC, and RE margin requirements, counterparty risk, exposure control, and agreement quality in a financing scenario.

Exam Angle

The stronger answer usually classifies the participant, account, marketplace, report, control failure, or oversight duty first, then applies the rule to the exact context. Watch for fact patterns that blur documentation, supervision, escalation, calculations, and timing because that is where this syllabus language becomes exam-relevant.

Key Takeaways

  • Start by identifying which participant, account, process, control framework, or rule governs the fact pattern.
  • Translate the section heading into a practical consequence such as approval, calculation, documentation, reporting, monitoring, or escalation.
  • Treat this section as scenario logic, not as isolated terminology.
Revised on Thursday, April 23, 2026