Review CPA Canada Common Final Examination Day 2 reminders for role depth, common issues, evidence quality, assumptions, time allocation, and recommendation support.
Use this CPA Canada Common Final Examination (CFE) Day 2 cheat sheet as a role-depth checklist before sample questions. Day 2 preparation should build the habit of deciding what deserves depth, what belongs to common competency coverage, and what evidence supports the recommendation. This page is companion practice support and does not reproduce or mirror official CFE cases.
| Item | CFE Day 2 cue |
|---|---|
| Provider | CPA Canada |
| Assessment | Common Final Examination Day 2 |
| Current Finance Prep status | sample questions available |
| Main practice behavior | role-depth triage, common issue coverage, quantitative support, evidence assessment, assumption control, and recommendation quality |
| Candidate risk | spending too much time on low-value issues while underdeveloping role-specific requirements |
Use this map to keep long-case reasoning organized. The selected role needs depth, but common issues still need appropriate coverage.
flowchart LR
Scan["Scan case facts"] --> Split["Split role and common issues"]
Split --> Rank["Rank material issues"]
Rank --> Evidence["Test evidence and assumptions"]
Evidence --> Analyze["Analyze at right depth"]
Analyze --> Conclude["Conclude and recommend"]
| Distinction | How to think in a question | Common trap |
|---|---|---|
| Role-depth issue vs common issue | Role-depth issues usually deserve more developed analysis; common issues still need coverage. | Ignoring common issues because they are not in the selected role. |
| Material issue vs background issue | Material issues affect the user’s decision, reporting, risk, or recommendation. | Writing equal detail on every fact in the case. |
| Calculation vs conclusion | Calculations support decisions; they do not replace them. | Producing a correct number without saying what to do. |
| Evidence vs management assertion | Case evidence may support, weaken, or contradict management’s preferred option. | Accepting a forecast or explanation without caveats. |
| Assumption vs fact | Assumptions must be stated and tested; facts should be used as support. | Treating optimistic assumptions as established evidence. |
| Depth vs perfection | Depth means enough issue-specific analysis, not perfect treatment of one calculation. | Overworking one section and sacrificing coverage. |
| Role answer vs generic answer | A role answer uses the lens of Assurance, Finance, Performance Management, Taxation, or another selected depth area. | Writing broad business advice that could apply to any case. |
| Recommendation vs observation | A recommendation tells the user what to do next and why. | Listing problems without a supported next step. |
Use this checklist before writing:
| Role lens | Look for | Avoid |
|---|---|---|
| Assurance | risk, assertions, materiality, evidence quality, procedures, reporting effect, independence | generic audit terms without procedures tied to the risk |
| Finance | cash flow, valuation, financing, sensitivity, working capital, downside risk, feasibility | a single base-case number with no risk analysis |
| Performance Management | strategy, KPIs, incentives, controls, bottlenecks, cost behavior, governance | KPI or variance comments that ignore behavior |
| Taxation | taxpayer, relationship, timing, documentation, compliance, owner-manager issues, risk wording | final tax advice from incomplete facts |
| Common issues | reporting, governance, cash pressure, going concern, controls, ethics, user needs | treating cross-competency issues as someone else’s problem |
| If the case gives… | Ask… |
|---|---|
| Management forecast | What supports the assumptions, and what sensitivity is needed? |
| Preferred option | Is the evidence balanced, or is management bias present? |
| Customer or supplier concentration | Does it change valuation, risk, financing, or strategy? |
| Weak controls | Does the issue affect reliability, fraud risk, operations, or reporting? |
| Cash pressure | Does it affect feasibility, covenants, going concern, or recommendation timing? |
| Related-party facts | Are conflict safeguards, fair value, disclosure, and approval needed? |
| Post-year-end event | Does it affect measurement, disclosure, risk, financing, or assurance work? |
| Technical detail | Does it support the decision, or is it a low-value distractor? |
| Trap | Better candidate habit |
|---|---|
| Writing in case order without prioritizing. | Rank issues by role relevance, materiality, and decision impact. |
| Spending too long on one calculation. | State assumptions, conclude, and move to the next material issue. |
| Ignoring role depth. | Give the selected role enough technical and case-specific development. |
| Ignoring common issues. | Cover decision-critical common issues at an appropriate depth. |
| Accepting management’s preferred option. | Test evidence, assumptions, constraints, and bias. |
| Ending with analysis but no recommendation. | Tell the user what to do, why, and under what caveats. |
| Giving generic advice. | Tie each conclusion to a case fact, constraint, or user need. |
| Treating uncertainty as a reason not to decide. | Recommend a path with assumptions, risk controls, or next-step evidence. |
This is a practical self-check, not an official timing rule:
Use the main CFE Day 2 page as a role-triage preview. After each miss, label the error: role focus, common issue, evidence quality, assumption, calculation support, or conclusion. If the miss is role focus, practise separating role-depth issues before reading answer choices. If the miss is conclusion quality, practise writing one sentence that includes the recommendation, evidence, and caveat.
When Finance Prep coverage expands, use mixed case-style prompts after you can explain which issues deserve depth and which should be handled briefly.