Study this credential by drilling concept boundaries: for each topic, write a one-line decision rule, learn what the adjacent wrong answer would be, and practise identifying the rule a scenario tests before doing any calculation. Two worked scenarios, an order-type decision table, a self-check rubric, and a three-week applied sequence are set out below.
Trade Date, Settlement Date, and Ex-Date Are Three Different Questions
A trade is agreed on the trade date, securities and cash actually change hands on the settlement date, and dividend entitlement follows the ex-date. A scenario stem may supply all three dates; your answer must cite the one the question actually asks about.
Trace the chain once, carefully. Trade date is when buyer and seller agree terms. Settlement date is when the exchange of security for cash completes, after a fixed number of business days set by the market's cycle. The ex-date is derived from the issuer's record date: buyers who settle after the record date do not receive the pending distribution, so the price typically adjusts on the ex-date. Because settlement cycles have been shortening in European markets, learn the mechanism — how ex-date relates to record date and cycle — rather than memorising one number as permanent.
Worked scenario: a client buys shares on the ex-dividend date and later complains that the dividend was withheld because 'I owned the shares that day.' The tempting mistake is to agree, assuming purchase equals entitlement. The better decision is to check whether the purchase was cum-dividend or ex-dividend: buying on or after the ex-date means the seller retains the dividend, which is why the price was already adjusted. This matters because entitlement tracking, client communication, and any complaint response all hinge on naming the correct date rather than the most recent one.
Limit, Stop, and Stop-Limit: Choosing the Instruction the Client Means
A limit order bounds the price but not execution; a stop order bounds the trigger but not the resulting price. The classic near-miss is placing a limit sell below the current market, which executes immediately and disposes of the holding against the client's intent.
Fix the boundary cases. A market order guarantees execution, not price. A limit order guarantees a worst-case price — a ceiling when buying, a floor when selling — but may never execute. A stop order is dormant until the price touches the trigger, then becomes an active order with no price guarantee, so a fast-falling market can fill far below the stop. A stop-limit adds a price bound after triggering, accepting the risk of no execution at all. Use the table to map each order type to the outcome it fixes and the outcome it leaves open.
Worked scenario: a client holding shares at €21 says, 'Sell them if the price drops to €18.' The plausible mistake is entering a limit sell at €18; because the market is above €18, that order executes straight away, selling the client out on the spot. The better decision is a stop order at €18 (or a stop-limit if the client also names a floor price), which stays dormant until triggered. This matters because the error is not a small pricing issue — it is an unintended, immediate disposal that can create a real tax event and a direct breach of the instruction given.
| Order type | What it fixes | What it leaves uncertain | Best fit in a stem |
|---|---|---|---|
| Market | Immediate execution | The execution price | Client says 'sell now' |
| Limit | A worst-case price (buy ceiling, sell floor) | Whether and when it executes | Client names a maximum or minimum acceptable price |
| Stop | The trigger level that activates the order | The price obtained after triggering | Client says 'exit if the price reaches €X' |
| Stop-limit | Trigger level plus a price bound | Whether it executes after triggering | Client wants an exit near €X but never below €Y |
Suitability and Appropriateness Depend on the Service, Not the Product Alone
Suitability is the duty when the firm advises a client personally. Appropriateness is the lighter check for non-advised sales of complex products. Execution-only involves neither, but requires recording the request. Identify the service type first; the product's complexity alone does not tell you which duty applies.
These two terms appear across Irish and European investor-protection frameworks and are easy to blur. Suitability looks at the person in full: objectives, financial situation, and knowledge and experience, because the firm is recommending something for them. Appropriateness asks a narrower question in a non-advised context: does this client, given their knowledge and experience of this product class, plausibly understand the risks of what they are asking to buy? If the answer is no, the firm warns the client; the duty is to assess understanding, not to steer the choice.
Application scenario: a retail client phones an execution platform and asks to buy a complex structured note. One tempting response is to run a full suitability assessment and recommend an alternative — but that converts a non-advised service into advice the firm does not provide, and creates a record that overstates what happened. The better decision is to apply the appropriateness check for that product class, warn if it appears unsuitable for the client's profile, and record the request and warning. Matching the duty to the service is the decision the question is testing.
Client Money and Asset Segregation: What the Protection Does Not Cover
Client money and client assets must be held separately from the firm's own property so the firm's creditors cannot reach them. Segregation governs holding and record-keeping; it does not protect a client from investment losses or from the performance of the securities themselves.
Understand the logic before the labels. Segregation exists so that if the firm fails, client holdings and cash can be identified and returned rather than absorbed into the firm's estate. That is why reconciliation — continuously matching the firm's internal records to actual holdings and cash — sits at the centre of the rules. A stem may describe operational details such as client cash sitting in the firm's own bank account or records not matching custody statements; the testable move is recognising that the breach is about mixing and record-keeping, not about market outcomes.
Contrast two stems. In the first, a firm uses client cash to fund its own settlement obligation: that is a segregation failure, because client property has been treated as the firm's property. In the second, a client's segregated holding falls 30% in value: nothing about client-asset handling is wrong, and no protection rule was breached — the loss is investment risk. Practise writing one sentence for each that names which concept applies and why, so that when an option describes a falling segregated holding you can immediately check whether it answers the segregation question or a different one entirely.
Reading Case Stems: Decide Which Rule Applies Before Touching the Numbers
Run a three-question pass on every scenario: who is the client, what service is being provided, and what is the question verb asking for? Then eliminate options that answer a different question, even if they state true facts.
Work the pass in order. First, is the client retail or professional, since the level of protection described changes with categorisation? Second, is the service advised, non-advised, or execution-only, since that selects suitability, appropriateness, or recording duties? Third, does the question ask you to identify a breach, choose the next action, or compute an outcome? Only after those three are settled should you evaluate the options, checking each one against the question the stem actually posed rather than against general plausibility.
Trace one example. A stem describes an execution-only platform, a complex product, and a client with no experience of that product class; the question asks for the correct next step. An option reading 'obtain full suitability information and recommend a suitable alternative' may look attractive, but it answers an advised-service question. The stem's service label governs the duty, and the product's complexity triggers an appropriateness check instead. When two options both seem compliant, return to the question verb and the service label, and ask which concept each option is answering — this routinely resolves the tie without changing any facts in the stem.
A Three-Week Applied Sequence with a Self-Check Rubric
Week one, build decision rules from notes. Week two, drill scenarios and write your own stems. Week three, run mixed timed sets and keep an error log organised by concept, then rework every logged error into a corrected rule.
In week one, convert each topic into a one-line decision rule, for example: 'Stop = trigger, not price; limit = price, not execution.' In week two, write five short stems yourself and swap them with a study partner: authoring the near-miss distractor is the fastest way to see how a stem hides the governing fact. In week three, run mixed timed sets and log every error with the concept it came from, not the topic heading, so patterns in your decision-making become visible rather than buried in generic revision.
Practical exercise: build a ten-case deck covering settlement dates, order types, service duties, and client asset handling. For each case, record three things — the rule you identified, the action you chose, and how confident you were before checking. Expected observations: early in week two you should notice you misidentify the rule more often than you misapply it, and by the rubric milestone of correctly naming the governing rule in 8 of 10 cases, your errors should shift from wrong-concept to wrong-detail. Treat that 8/10 as a learning milestone only, not a prediction of any exam outcome.
- Rule named correctly: can you state which single concept the stem tests, in one sentence?
- Boundary case handled: does your answer explain why the adjacent concept (limit vs stop, suitability vs appropriateness) does not apply?
- Detail accuracy: dates, prices, and order parameters consistent with the stem?
- Error classification: logged by concept with a rewritten rule, not by topic or question number?
Readiness Checks for the Final Week
You are ready for applied practice when you can state every decision rule without notes, classify a case by client type and service within seconds, and articulate why the distractor is wrong rather than only why your answer is right.
Use three concrete checks. First, cover your notes and write the full set of one-line rules from memory; any rule you cannot reproduce is a concept you only recognise, not one you can apply. Second, take five unfamiliar stems and classify each — client type, service type, question verb — in under a minute total; hesitation here means the three-question pass is not yet automatic. Third, for your last ten errors, write the reason each distractor was tempting; if you cannot explain the trap, you have memorised answers rather than learned the distinctions.
For the final week, rework the entire error log as a corrected rules sheet, then complete one full timed set under exam conditions and review it against the rules sheet. Administrative details — assessment format, scheduling, registration, and any entry requirements — are set by the issuer, so confirm them directly on the IOB website rather than relying on secondary summaries; keep that check short and spend the recovered time on scenario drills.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.