CPA Canada Core 1 common mistakes
CPA Canada Core 1 · Understand the traps and how to avoid them.
Spending the full time budget drafting a technically perfect answer to the first case requirement, then leaving the final requirement (often the highest-value integrative or 'advise the client' ask) with 10 minutes or unanswered.
Candidates treat case writing like university exams, where thoroughness on one question is rewarded. CPA cases are marked holistically across all requirements (often using a rubric with assessment opportunities spread evenly), so an unfinished requirement scores near zero regardless of quality elsewhere. Time pressure and the urge to 'get it right' cause front-loading.
What to do instead
Before writing, allocate minutes per requirement based on the marks allocated (a common rule: roughly 1 minute per mark, reserving 10–15 minutes for planning and review). Write the plan (issue, analysis, recommendation) as bullet points for every requirement first, then flesh out. If time runs short, write a structured skeleton with the key conclusion and 2–3 supporting points for each remaining requirement rather than a polished answer to one.
Identifying the accounting issue but never stating the applicable Handbook standard or the specific recognition/measurement criterion, then jumping straight to a number.
Candidates know the 'right answer' intuitively from practice and skip the authoritative support, or they are unsure which standard applies and avoid committing. Rubrics award assessment opportunities for identifying the issue and applying the relevant guidance, so an unsupported number captures only partial credit.
What to do instead
Use a fixed template for every issues-based requirement: (1) issue, (2) relevant standard and criterion (e.g., ASPE Section 3064 for internally generated intangibles, IFRS 15 five-step model, IAS 36 impairment indicators), (3) analysis against the criteria, (4) conclusion and recommended treatment/journal entry. Practise writing this template until it is automatic.
Answering the 'required' as a technical memo with no user focus-no quantification of the impact on the financial statements, covenants, or tax-and no clear recommendation.
Candidates default to describing the accounting treatment and stop there. Cases are written for a specified audience (CFO, board, client) and the rubric rewards analysis of consequences and a decision. The habit comes from textbook problems that end at 'record the entry'.
What to do instead
After the technical conclusion, always add an 'impact and implications' paragraph: dollar effect on profit, assets, or ratios; effect on debt covenants or lending agreements; tax or cash flow consequences; and a one-sentence recommendation addressed to the named user. Rehearse the phrase 'the impact on X is $Y, which means Z' for each issue.
Treating the strategy and governance requirement as generic commentary-listing SWOT items or 'the company should improve controls'-without linking to the case facts, the entity's objectives, or a decision criterion.
Candidates lack a structured framework for strategy analysis and fall back on buzzwords. They also underestimate how much of the rubric rewards using the specific facts (competitive position, stakeholder pressures, board composition) rather than general business advice.
What to do instead
Use a consistent framework: identify the strategic objective, analyse the external environment (Porter's Five Forces or PESTEL) and internal capabilities (value chain, resources), then evaluate the specific alternatives with explicit criteria (feasibility, risk, alignment with mission, financial impact) and recommend one. Tie every point to a named fact from the case and to a governance consideration (e.g., board independence, conflict of interest, tone at the top).
Ignoring the governance/ethical dimension when a case contains a conflict of interest, related-party transaction, pressure to meet a covenant, or a controller being asked to book an unsupported entry.
Candidates focus on the numbers and treat ethics as a separate topic. In integrated cases, ethical and governance issues are embedded in the facts and are explicitly assessed; missing them forfeits assessment opportunities and can undermine an otherwise correct recommendation.
What to do instead
Scan the case for red flags during planning: pressure from owners or lenders, related parties, unusual journal entries, auditor independence, board composition. For each, apply a professional-judgment framework-identify the threat, evaluate materiality and intent, consider the CPA Code of Professional Conduct and applicable securities/company law, then recommend a course of action (escalate to audit committee, disclose, refuse, consult).
In management accounting requirements, producing a variance or cost analysis that stops at the numbers without explaining the cause or the operational decision it implies.
Candidates are trained to compute variances but not to interpret them. Rubrics reward explaining why a variance arose (price vs. efficiency, mix vs. volume, standard-setting error) and what management should do, not just the arithmetic.
What to do instead
For every quantitative management accounting answer, add a 'so what' layer: decompose the variance into its components, identify plausible operational causes, distinguish controllable from uncontrollable factors, and state a specific action (renegotiate the supplier contract, revise the standard, investigate the production process). Show the calculation in a small table so the marker can follow it.
Making a recommendation on a capital budgeting or pricing decision without considering qualitative factors, sensitivity, or the assumptions behind the discount rate and cash flow estimates.
Candidates present a single NPV or break-even number as if it were certain. Cases often deliberately include uncertainty (a new market, a competitor response, a regulatory change) that the rubric expects to be addressed. Over-reliance on one point estimate signals weak decision analysis.
What to do instead
Present the base-case calculation, then a brief sensitivity or scenario analysis (e.g., what happens if volume falls 10% or the discount rate rises 2 points), state the break-even threshold, and weigh qualitative factors (strategic fit, risk, capacity, reputational and environmental impacts). Conclude with a clear recommendation conditional on the key assumption.
In audit and assurance requirements, listing audit procedures generically ('obtain a management representation', 'perform analytical procedures') without specifying the assertion, population, timing, and evidence expected.
Candidates memorise procedure categories but not how to operationalise them. Rubrics reward procedures that are specific enough to be performed-naming the document, the assertion addressed, and the source of evidence-and penalise vague lists.
What to do instead
Write every procedure in a four-part format: assertion/risk addressed, specific action (inspect, confirm, recalculate, vouch), population/sample and source document, and the evidence or conclusion expected. For example, instead of 'test revenue', write 'for a sample of sales invoices around year-end, vouch to shipping documents and the sales contract to test occurrence and cut-off, and investigate any unmatched invoices'.
Failing to adjust the audit approach to the assessed risk of material misstatement-applying the same substantive procedures regardless of whether the area is high-risk (revenue recognition, estimates, related parties) or routine.
Candidates treat audit planning as a checklist and do not connect risk assessment to the nature, timing, and extent of procedures. In cases with fraud risk or significant estimates, the rubric expects a response that is responsive to the specific risk.
What to do instead
For each significant risk identified, state the risk (what could go wrong, which assertion), then design a tailored response: more experienced staff, increased sample sizes, external confirmations, involvement of a specialist, testing of controls, or a review of management's assumptions against external data. Explicitly link each procedure back to the risk it addresses.
Writing answers in long narrative paragraphs without headings, tables, or a clear structure, so the marker cannot locate the assessment opportunities.
Candidates write as they think, and under time pressure prose sprawls. Markers score against a rubric and must find each point; buried conclusions and unstructured text cause valid points to be missed and reduce readability scores.
What to do instead
Adopt a consistent format for every response: a short issue heading, bulleted analysis, a clearly labelled conclusion or recommendation, and tables for any calculations. Use the case's own terminology and signpost with phrases like 'Issue:', 'Analysis:', 'Recommendation:'. Practise under timed conditions and review your own answers against a rubric to confirm each point is visible.