ICAB CL Business & Finance study materials
ICAB CL Business & Finance study resources

ICAB CL Business & Finance common mistakes

ICAB CL Business & Finance · Understand the traps and how to avoid them.

Mistake 1

When asked to identify the most appropriate source of finance for a stated scenario, the candidate names a single instrument (for example 'issue ordinary shares') without matching it to the firm's life stage, asset base, cash-flow profile and the purpose/duration of the funding need.

Candidates memorise lists of sources and treat the question as a recall test, so they retrieve a familiar term rather than running the matching logic the question is actually testing. Under time pressure the first plausible term wins.

What to do instead

Before answering, write three tags for the scenario: purpose (asset purchase, working capital, expansion), duration (short/medium/long), and risk position (existing gearing, security available, dilution tolerance). Then eliminate any source that fails any tag and justify the survivor in one sentence. Practise by taking ten past scenarios and producing the tag set before looking at options.

Mistake 2

In investment appraisal questions the candidate computes NPV or payback correctly but then ignores or mis-handles the treatment of depreciation, sunk costs, allocated fixed overheads, interest costs and working capital release, so the cash-flow schedule itself is wrong.

Candidates conflate accounting profit with cash flow because the two are taught side by side, and they treat any figure printed in the question as relevant. The distractor figures are deliberately included to test relevance, not arithmetic.

What to do instead

Adopt a fixed two-column ritual: list every figure in the question, mark each as relevant or excluded with a one-word reason (non-cash, sunk, committed, financing), and only then build the timeline. Rehearse the exclusion list until it is automatic: depreciation, sunk R&D, apportioned head office cost, interest, and the recovery of working capital at the end.

Mistake 3

The candidate calculates a ratio or variance accurately but offers no interpretation, or interprets it in isolation without a comparator, so the answer states 'the current ratio is 1.4' and stops.

Numeric confidence displaces analytical confidence: candidates feel the calculation is the answer and run out of time or words for the commentary. Without a benchmark (prior year, industry, budget, covenant) they do not know what to say.

What to do instead

Structure every interpretation as three moves: direction and size of change, the plausible operational cause, and the consequence for a named stakeholder or decision. Always state the comparator explicitly. Practise by writing the interpretation sentence first and the calculation second, so the habit is analysis-led.

Mistake 4

On market structure and pricing questions the candidate answers from intuition about 'competition being good' rather than applying the defining conditions (number of firms, barriers to entry, product differentiation, information, price-setting power) to the specific market described.

The models are learned as definitions rather than as diagnostic tools, and everyday usage of words like 'competitive' or 'monopoly' pulls the answer away from the technical meaning in the question stem.

What to do instead

Build a one-page grid of the four structures against the five conditions and, in the exam, tick the conditions the stem actually evidences before naming the structure. Where the stem is ambiguous, state which condition is decisive. Then link to the pricing implication (price taker versus price maker, kinked demand, limit pricing).

Mistake 5

The candidate treats legal forms of business as a vocabulary list, describing a partnership or private limited company generically instead of addressing liability, continuity, taxation, governance obligations and capital-raising capacity as separate dimensions.

Textbook descriptions blur the dimensions together, and candidates reproduce the description rather than comparing on the axis the question asks about, so a question about liability gets an answer about ownership and control.

What to do instead

Answer in a fixed five-row frame: liability, legal personality and continuity, taxation, decision-making and governance, access to capital. Read the question to identify which row is being tested and lead with it. Where the question asks for a recommendation, state the trade-off the founder is accepting.

Mistake 6

In governance and compliance questions the candidate lists statutory duties or regulatory bodies without identifying who owes the duty to whom, which mechanism enforces it, and what the consequence of breach is.

Codes and statutes are revised as lists, so recall is triggered without the relational structure that makes the answer a governance answer rather than a naming exercise.

What to do instead

For each duty, rehearse a three-part chain: duty-holder, beneficiary, enforcement mechanism and sanction. In the exam, write the chain in the margin before composing the answer. Where a scenario is given, name the specific breach and the specific remedy rather than describing the framework in general.

Mistake 7

The candidate answers strategy questions by listing generic frameworks (SWOT, PESTLE, Porter's five forces) and populating them with restated facts from the case, without reaching a recommendation or ranking the options.

Frameworks are taught as answer templates, and candidates believe filling the template earns marks. They also avoid commitment because a recommendation can be marked wrong, whereas a list feels safe.

What to do instead

Use the framework only as a checklist in rough work, then write the answer as: the decisive issue, two or three options with the criterion used to rank them, the recommended option, and the main implementation risk. Ban yourself from reproducing framework headings in the answer text. Practise converting a populated SWOT into a single sentence of strategic implication.

Mistake 8

On working capital and cash-flow questions the candidate computes the operating cycle or a cash budget but fails to connect the number to the financing consequence, such as the overdraft requirement, the cost of the funding gap, or the effect of a change in credit terms.

The mechanics of the cycle are taught separately from the treasury decision, so the candidate stops at the ratio. Sign errors in the cycle (payables subtracted rather than added) compound the problem.

What to do instead

Always finish with a 'so what' line quantifying the cash effect: for example, reducing receivables days by ten releases a stated amount. Memorise the cycle as inventory days plus receivable days minus payable days and sanity-check the sign by asking whether slower payment to suppliers shortens or lengthens the cycle.

Mistake 9

The candidate uses data and IT questions to describe technology in general terms ('use of big data improves decisions') without addressing data quality, controls, security, privacy obligations or the specific risk being mitigated.

The domain feels non-technical to candidates from a finance background, so they substitute general assertion for the control-and-risk vocabulary the examiner is looking for.

What to do instead

Prepare a short risk register template: asset, threat, vulnerability, control, residual risk, owner. Apply it to any IT scenario in the exam. Learn the distinction between accuracy, completeness, timeliness and validity as data-quality dimensions, and name the specific control rather than the benefit.

Mistake 10

The candidate allocates time evenly across the paper or over-invests in the first long calculation, leaving short high-yield discursive questions unanswered or answered in note form.

Calculations feel productive and give a false sense of progress, and candidates do not rehearse the paper under timed conditions, so they have no calibrated sense of minutes per mark.

What to do instead

Before starting, compute minutes per mark from total time and total marks, and write the target finish time for each section on the script. Do two full timed mocks, logging actual versus target time per question, and enforce a hard stop by moving on when a calculation exceeds its allocation and returning only if time remains.