Understand how Supervisors should handle approval of leveraged, derivatives, and OEO accounts where manual review, restrictions, and client-capability concerns become decisive.
Leveraged, derivatives, and OEO account approval issues appears in the official CIRO Supervisor Exam syllabus as part of Specific supervision responsibilities in relation to account approvals. Questions here usually test whether you can recognize when higher-risk access should be narrowed, delayed, or refused even if the client strongly wants the feature.
The exam often pairs leverage, derivatives, and OEO because each one reduces the margin for error in a different way:
That means the Supervisor has to look not only at client wealth or experience, but at whether the client can realistically use the account as designed.
| Feature | Key approval question | Typical reason to restrict or decline |
|---|---|---|
| Leveraged account | Does the client understand amplified losses and ongoing funding pressure? | Leverage risk disclosure is weak or the client cannot absorb losses |
| Derivatives account | Is the client ready for the products and strategies requested, and are the required agreements complete? | Missing derivatives agreement, thin knowledge, or unsupported strategy scope |
| OEO account | Is this client actually seeking self-directed execution, or are they looking for advice and guidance? | The client appears unable to handle online processes or expects suitability-style advice |
CIRO’s account-appropriateness guidance makes clear that for OEO accounts, the account-appropriateness obligation is narrower than for advisory accounts, but it still exists. The Supervisor still has to decide whether it is appropriate for the person to open that type of account at the dealer.
That is why the exam often rewards answers that refuse or limit OEO access where the client:
Higher-risk account features are exactly where automated onboarding should hand off to human judgment. Manual review is often justified where the file shows:
The stronger answer sees those facts as review triggers, not as edge cases to wave through.
The stronger answer starts with the service model the client is really asking for. If the requested account type, feature set, and client capability do not line up, the right response is usually to limit access, move the client to a different relationship, or decline the feature.
A client wants an OEO account with access to higher-risk options strategies and also asks the representative which trades to place first after the account opens. What is the supervisory problem?
The problem is that the client appears to want advisory support inside an execution-only relationship while also requesting higher-risk access. That combination should trigger closer review and may justify restricting or declining the requested features.