Treat each banking concept as a decision rule, not a sentence to recite. For every term you study, write down the cue in a scenario that should make you reach for it, and the first action it requires. Then drill the order: in lending, purpose and capacity come before security; in financial crime, internal escalation comes before any customer contact; in every answer, the record comes last but is never optional. Use the comparison table to settle adjacent-term confusion, rehearse the two worked scenarios and the documentation habit, and finish with the readiness rubric so your revision produces observable evidence, not a feeling of familiarity.
Why banking definitions collide when a scenario replaces the definition
Banking terms overlap in ordinary description but differ on one axis — initiation, control, access, or security. The study skill is matching scenario cues to the concept that governs the next action.
Learned as standalone sentences, banking definitions blur. A standing order and a direct debit both 'move money regularly'; an overdraft and a term loan both 'provide credit'. The overlap lives in the summary sentence; the difference lives on a single axis: who initiates the instruction, whether the amount can vary, when funds can be accessed, or what secures the position. If you can name the axis, two near-identical terms stop competing for the same answer.
Convert every definition you meet into a trigger-action pair: 'If the scenario says the customer wants the supplier to pull variable amounts, that is a direct debit resting on a mandate; the first action is confirming the mandate is in place.' Then test the pair by swapping cues between adjacent terms. If your answer survives the swap, your pairing is wrong and you have found the exact boundary you were missing. This discrimination habit is worth building deliberately for scenario-style practice, because a scenario presents a situation, not a named term — and the habit is what turns your flashcard knowledge into decisions.
- Trigger: payer wants a fixed recurring payment → standing order; first action: confirm payer-set details.
- Trigger: payee wants variable recurring collection → direct debit; first action: verify the payer mandate.
- Trigger: customer needs flexible short-term borrowing → overdraft; first action: match the facility to the cash-flow pattern, not to habit.
Products and payments: the three axes that change the answer
Product and payment terms separate cleanly on three axes: who initiates, what is varied, and what is secured or when funds are accessible. A cue-lookup table resolves most mix-ups.
On the lending side, an overdraft is a short-term, typically revolving facility repayable on demand; a term loan is a fixed sum on an agreed schedule for a stated purpose. The distinction matters because the facility must match the customer's cash-flow shape: a seasonal working-capital gap points to an overdraft, while a defined purchase with predictable repayment points to a term loan. On the deposit side, demand, notice, and fixed-term accounts differ on access conditions — when and under what constraints money can be withdrawn — not merely on the headline rate.
Payments follow the same logic. A credit transfer is payer-initiated and can be one-off or recurring; a standing order is payer-initiated, fixed-amount, recurring; a direct debit is payee-initiated, variable, and rests on a payer mandate. Because Irish retail payments run largely on SEPA instruments in euro, the payment-type choice is a practical one your module materials will illustrate. Use the table below as a cue-lookup: cover the right-hand columns, read only the cue, and reproduce the rest from memory. Any column you cannot reconstruct shows which distinction needs another pass.
| Scenario cue | Overlapping terms | The distinction that settles it | First correct action |
|---|---|---|---|
| Payer instructs the bank to pay a fixed amount regularly | Standing order vs direct debit | Payer initiates and fixes the amount; no payee mandate involved | Confirm the payer-set details before setup |
| Payee collects variable amounts with the payer's consent | Direct debit vs standing order | Payee initiates under a payer mandate; amounts can vary | Verify the mandate is in place |
| One-off euro payment to another account within SEPA | Credit transfer vs direct debit | Payer-initiated single instruction, not a recurring collection | Execute against available funds and keep the record |
| Flexible short-term borrowing on a current account | Overdraft vs term loan | Revolving and repayable on demand vs fixed sum on a schedule | Match the facility to the cash-flow pattern |
| Fixed sum for a stated purpose repaid on a schedule | Term loan vs overdraft | Defined amount, duration, and purpose vs on-demand flexibility | Document purpose and repayment capacity |
| Money withdrawable at any time without penalty | Demand deposit vs notice account | Immediate access vs access only after an agreed notice period | Confirm access terms before recommending |
| Withdrawal only after an agreed notice period | Notice account vs fixed-term deposit | Notice condition vs money locked for a set term | State the notice requirement clearly to the customer |
| Funds committed for a set term at a fixed rate | Fixed-term deposit vs notice account | Fixed maturity date governs, not a notice condition | Confirm maturity and consequences of early access |
| Account activity inconsistent with the customer profile | CDD vs EDD | Risk tiering decides the depth of due diligence | Record the facts and escalate internally |
| Higher-risk situation such as a PEP or complex structure | EDD vs standard CDD | Enhanced measures apply on top of the baseline checks | Apply the firm's enhanced-check procedure |
| Impulse to tell the customer an account is under review | Tipping off vs internal escalation | Disclosing suspicion is prohibited; escalation is the protected route | Escalate internally; disclose nothing to the customer |
| Property with equity offered to support weak cash flow | Security vs capacity | Security mitigates loss given default; it does not create ability to pay | Assess purpose and capacity before collateral |
| Colleague asks to backdate a file note | Documentation integrity vs convenience | Records must reflect true dates and true events | Refuse and report through the appropriate channel |
Credit judgement: why collateral is not the first question
A lending decision runs purpose → capacity → security. Security limits the lender's loss if repayment fails; it does not demonstrate that repayment will succeed.
Worked scenario 1: a self-employed printer applies for a term loan to buy equipment and owns a property with equity in it. The plausible mistake in a practice answer is 'approve — the property covers the exposure.' That treats collateral as evidence of repayment. The better decision sequence: establish the purpose and whether it is legitimate and specific; assess capacity from business cash flow, existing commitments, and whether repayments survive a dip in revenue; only then consider whether security is appropriate. If capacity is weak, the property changes the lender's loss given default, not the customer's ability to pay — so the sound outcome is decline or restructure, not approval on the back of equity.
This ordering matters because it is how the judgement is reasoned, not a stylistic preference. In the Irish context, consumer credit frameworks place affordability assessment at the centre of the lending decision, so leaning on security in a consumer scenario is not just weak practice — it points in the wrong regulatory direction. Drill the same applicant with a second cue: same business, same property, but contracts secured for the coming year. Capacity now looks different, and so should your recommendation. That contrast shows you the decision turns on cash flow, and the collateral was never the answer.
The Irish layer: same product, different rules of engagement
Irish assessment items turn on setting: the Central Bank of Ireland as regulator, consumer protection requirements for regulated firms, and the euro/SEPA payment environment. Anchor every scenario in that setting.
A payments question reads differently once you place it: retail payments in Ireland operate in euro largely through SEPA credit transfers and direct debits, which is why the payment-type distinctions above are practical rather than academic. A conduct question reads differently once you know the Central Bank of Ireland supervises regulated financial services firms and maintains consumer protection requirements shaping how firms treat customers — including areas such as complaint handling and the recognition of customers in vulnerable circumstances. None of this needs to be memorised as a free-floating list; it needs to be placed, like a map reference, so the scenario lands on the right part of the map.
The working method is a one-line 'Irish anchor' per syllabus topic: who regulates this activity, which customer protections apply, and what documentation the process leaves behind. Write it in one sentence and keep it beside your trigger-action cards. When a scenario mentions a vulnerable customer, a complaint, or a charge over assets, the anchor tells you which obligations are in play before you reason about the product. Where a precise timeline, threshold, or form is involved, take it from your module materials rather than from recall — anchors tell you where to look; the materials give you the exact figure.
Financial crime checks: knowing what you are permitted to do next
Customer due diligence is tiered by risk, and the operational rule in a suspicious situation is internal escalation plus a factual record — never disclosing suspicion to the customer.
Name the tiers precisely: customer due diligence (CDD) means identifying and verifying the customer and understanding the purpose of the relationship; enhanced due diligence (EDD) adds measures for higher-risk situations, such as politically exposed persons or unusually complex structures; and 'tipping off' describes disclosing to a customer that a suspicion has been formed or a report considered, which is prohibited. The plausible mistake is procedural: a candidate who, shown an inconsistency, recommends 'informing the customer that the account is under review.' That confuses customer-service instincts with the duty structure and steers directly toward tipping off.
Worked scenario 2: a long-standing retail customer with a modest stated income suddenly begins routing large third-party payments through the account. The wrong move is confronting the customer or closing the account on your own initiative. The better decision: record the observations factually — amounts, counterparties, dates, and the inconsistency with the profile — and escalate internally to the firm's designated function (the MLRO or compliance equivalent) so the firm's reporting process can operate. Why it matters: the internal escalation is what creates the protected channel, the factual record is what the process depends on, and disclosing suspicion to the customer can itself be an offence. The correct sequence is record → escalate → let the process run.
Ethics and documentation: the four-part sentence for every case answer
For professional standards scenarios, a documented decision path — duty, facts, action, record — is the structure to use in your practice answers, rather than a confident verdict with nothing behind it.
When you build or work through ethics practice scenarios, focus on knowing the procedure for the moment integrity and convenience diverge, rather than rehearsing dramatic choices. Take a colleague who asks you to backdate a file note 'to keep things tidy.' The professional response is not a private objection but a refusal plus reporting through the appropriate channel, because documentation integrity is what audit trails, regulatory engagement, and customer trust all rest on. The same shape appears in conflict-of-interest, gift, and confidentiality situations: the answer to reach for is the declared, recorded, escalated route, so use your practice time to make that route habitual rather than improvised.
Build this into a four-part sentence and use it in every practice answer: 'The relevant duty is X; the facts show Y; the correct next step is Z; this is recorded in W.' It forces you to name the duty before the judgement, to separate observed facts from inference, and to close the loop with the record. It also has a self-diagnostic function: if you cannot fill in the 'duty' slot, you have not yet identified which concept governs the scenario — which sends you back to the trigger-action card for that topic rather than to more reading.
- Name the duty first; if the duty is unnamed, the answer is not yet answerable.
- Keep observed facts (amounts, dates, documents) visibly separate from conclusions.
- Choose the procedural action — record, escalate, decline, refer — over improvised fixes.
- Close with the record: what was documented, where, and who was informed.
A preparation sequence and readiness checks you can actually observe
Sequence the syllabus as products → credit → Irish anchors → financial crime → integrated ethics cases, then test readiness with a scenario-mapping drill scored against an observable rubric.
An adaptable sequence: in the first phase, build trigger-action cards for products, deposits, and payment types, using the three axes to force the boundary between adjacent terms. In the second, drill credit scenarios with the purpose-capacity-security order until the order is automatic. Third, write the one-line Irish anchor for each topic and attach the CDD/EDD/tipping-off structure to the financial crime material. In the final phase, run integrated case practice under time, answering with the four-part documentation sentence. Adjust the weighting to your own module syllabus, and for the current programme structure, assessment format, and scheduling, check the IOB website directly (iob.ie) — administrative details change and belong to the issuer.
Exercise — the scenario-mapping drill: take five short scenarios, either from your module materials or ones you write yourself. For each, in this order: (1) label the governing concept in one term; (2) state the first correct action; (3) write the four-part duty-facts-action-record sentence; (4) swap one cue between two scenarios and check your labels still hold. Expected observations: in early runs you will hesitate between adjacent terms — overdraft versus term loan, CDD versus EDD — and your 'first action' will sometimes appear after your analysis instead of before it. By the third run, labelling should quicken and the first action should consistently come first. That shift is the observable signal that definitions have become decisions.
- You can name the axis (initiation, access, or security) separating two confused terms within a minute of reading the cue.
- In a lending scenario, you state purpose and capacity before collateral, unprompted.
- In a suspicion scenario, your first move is a factual record and internal escalation, with no customer disclosure.
- Every practice answer contains all four parts: duty, facts, action, record.
- Consistently scoring 4 out of 5 on the drill is a study milestone — evidence you are ready to move to full case practice, not a prediction of your result.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.