BICA Qualification common mistakes
BICA Qualification · Understand the traps and how to avoid them.
Treating the ethics and compliance domain as a set of abstract principles and answering with the 'most virtuous-sounding' option rather than the one that reflects the actual regulatory obligation (for example, choosing broad client-loyalty language over the specific disclosure, escalation, or reporting duty the scenario is testing).
Candidates study ethics last, skim it as common sense, and never learn the hierarchy of duties, so they default to moral intuition instead of the prescribed rule. Scenario stems are deliberately written so the warmest-sounding answer is often the wrong one.
What to do instead
Before answering any ethics item, identify the concrete trigger in the stem (conflict of interest, inside information, gift, personal account dealing, confidentiality breach) and recall the specific obligation attached to it. Build a one-page table mapping each trigger to its required action and its escalation route, and practise sorting answer options by 'which rule is engaged' rather than by tone.
Performing customer due diligence as a box-ticking data-capture exercise and failing to apply enhanced measures when the risk indicators in the scenario call for them (foreign politically exposed person, unexplained source of wealth, complex ownership chain, high-risk jurisdiction).
Candidates memorise the standard identification checklist but never internalise that due diligence is risk-based, so they apply the baseline process to every client and miss the cue words that demand escalation, senior sign-off, or ongoing monitoring.
What to do instead
Learn a three-tier framework (simplified, standard, enhanced) with at least three concrete triggers per tier. For every onboarding scenario, explicitly state the risk rating, the evidence supporting it, and which tier of measures follows. Drill stems by underlining ownership, source-of-funds, and jurisdiction facts before choosing an answer.
Confusing the treatment, risk profile, and suitability of similar-sounding products, for example mixing up a money market instrument with a short-duration bond fund, or a structured note with a plain vanilla bond, and then selecting an answer that misstates the product's capital risk or liquidity.
Product knowledge is often learned as vocabulary lists rather than as a comparison of payoff structures, so candidates recognise a name but cannot reason about what happens to the investor under different market conditions.
What to do instead
Build comparison grids for each product family covering issuer, claim priority, maturity, interest or return mechanics, capital protection, liquidity, and main risks. For each product, write one sentence describing the worst realistic outcome for the investor. Test yourself by explaining the difference between two adjacent products aloud without notes.
Assessing suitability by checking only the client's stated risk tolerance or the product's label, while ignoring the interaction of time horizon, liquidity needs, existing concentration, and capacity for loss described in the scenario.
Candidates reduce suitability to a single matching step (tolerant client plus high-risk product equals suitable) because that is the simplest mental shortcut, and scenarios are built to punish exactly that shortcut with a hidden constraint such as a near-term cash need.
What to do instead
Adopt a fixed checklist for every advisory item: objective, time horizon, liquidity requirement, existing portfolio concentration, capacity for loss versus willingness to take risk, and cost. State the recommendation only after all six are addressed. When two options look plausible, choose the one that reconciles the conflict the scenario has planted rather than the one that matches the headline risk label.
Ignoring record-keeping and transaction-processing obligations embedded in operational scenarios, such as failing to recognise that a client instruction must be verified, that a trade error requires prompt escalation and allocation correction, or that certain communications must be retained for a defined period.
Operations content feels administrative, so candidates skim it and answer from general commercial instinct, missing that the exam tests specific sequencing (verify, authorise, execute, confirm, reconcile, retain) and specific retention and audit-trail requirements.
What to do instead
Memorise the end-to-end transaction lifecycle as an ordered sequence and the record types generated at each stage. For operational scenarios, ask three questions in order: who is authorised, what evidence must exist afterwards, and what is the escalation path if something breaks. Practise identifying the earliest control failure in a described process.
Missing the fraud and data-protection dimension of a scenario, for example treating an unusual payment request as a service problem to solve quickly rather than as a potential authorised push payment fraud or social engineering attempt, or agreeing to share client data without checking the lawful basis and minimum-necessary principle.
Candidates focus on the client-service narrative and the urgency cues written into the stem, which is precisely the pressure real fraudsters apply, so they mirror the victim's instinct to act fast and help.
What to do instead
Train a reflex: any change of bank details, unusual urgency, secrecy request, or deviation from established contact channels is a fraud indicator until independently verified through a known channel. For data items, run a three-part test (lawful basis, purpose limitation, minimum necessary) and prefer the option that verifies and escalates over the option that resolves fastest.
Answering 'what would you do' items with the outcome the client wants instead of the sequence the firm's procedures require, skipping the intermediate step of disclosure, documentation, or obtaining informed consent before acting.
Exam stems often present a sympathetic client under time pressure, and candidates conflate good client outcomes with correct process, forgetting that the exam marks the procedure, not the result.
What to do instead
For every conduct scenario, write the required sequence in order (identify conflict, disclose, obtain consent or decline, document, escalate if unresolved) and select the option that matches the earliest missing step. Rehearse that the correct answer frequently involves slowing down or refusing, not accommodating.
Misreading the scope of a question, for example answering which control is 'most effective' when the stem asks for the 'first' action, or selecting a true statement that does not answer the question asked.
Under time pressure candidates pattern-match a familiar phrase in the stem to a memorised fact and stop reading the qualifier, and many items include several factually correct options where only one satisfies the exact instruction.
What to do instead
Circle or mentally isolate the operative word (first, most, least, next, primary, except) before evaluating options. Eliminate options that are true but unresponsive. If two options survive, re-read the stem's final clause and choose the one that answers that clause specifically, not the one that is generally correct.
Applying a memorised numeric threshold or deadline to the wrong context, such as mixing up reporting timelines, retention periods, or thresholds that differ between client types or transaction categories.
Numbers are studied as isolated facts without the condition attached to them, so recall succeeds but application fails when the scenario changes the client category or the nature of the event.
What to do instead
Store every figure as a conditional statement rather than a bare number (trigger, actor, deadline, recipient). Build flashcards with the condition on the front and the figure plus its source rationale on the back, and review only the ones you have recently got wrong.
Leaving risk-assessment items at the level of naming a risk category instead of evaluating likelihood, impact, and the adequacy of the proposed control, so the chosen answer identifies the risk correctly but misjudges whether the mitigation actually reduces it.
Candidates learn risk terminology as labels and never practise the judgement step, and distractors are constructed as plausible-sounding controls that transfer or disclose risk without reducing it.
What to do instead
For each risk scenario, score likelihood and impact explicitly, then classify the proposed response as avoid, reduce, transfer, or accept, and check whether the stated control genuinely changes the likelihood or impact. Prefer answers that combine a specific control with a monitoring or review mechanism over answers that rely on a single one-off action.