Review CPA Canada Common Final Examination Day 3 reminders for short-case triage, breadth, timeboxing, competency switching, evidence, and concise recommendations.
Use this CPA Canada Common Final Examination (CFE) Day 3 cheat sheet as a short-case triage checklist before sample questions. Day 3 preparation should build fast issue recognition, proportionate analysis, and concise recommendations across multiple competency areas. This page is companion practice support and does not reproduce or mirror official CFE cases.
| Item | CFE Day 3 cue |
|---|---|
| Provider | CPA Canada |
| Assessment | Common Final Examination Day 3 |
| Current Finance Prep status | sample questions available |
| Main practice behavior | short-case issue spotting, breadth coverage, timeboxing, cross-competency switching, and concise recommendation writing |
| Candidate risk | overworking one visible issue while missing other material accounting, assurance, tax, finance, or performance-management points |
Use this map to avoid spending all your time on the first issue you notice.
flowchart LR
Read["Read the ask"] --> Scan["Scan for issues"]
Scan --> Rank["Rank by materiality"]
Rank --> Timebox["Timebox depth"]
Timebox --> Answer["Answer concisely"]
Answer --> Move["Move to next issue"]
| Distinction | How to think in a short case | Common trap |
|---|---|---|
| Required ask vs background | The user’s request should control what you answer first. | Writing about interesting facts that were not requested. |
| Breadth vs depth | Day 3 often rewards identifying multiple material issues with enough analysis. | Giving Day 2-level depth to the first issue and missing the rest. |
| Technical issue vs business implication | Some prompts ask for both the accounting/tax issue and the operational consequence. | Stopping after the journal-entry or rule discussion. |
| Evidence vs assumption | Short cases still require support, even when time is tight. | Treating a management guess as reliable evidence. |
| Issue spotting vs recommendation | Identifying the issue is not enough if the user needs action. | Ending with “this is a concern” without next steps. |
| Time pressure vs careless answer | Timebox the response, but do not skip the core implication. | Writing vague one-word recommendations. |
| Single competency vs integrated issue | One fact can affect reporting, cash flow, controls, and tax. | Assigning the issue to one area and ignoring linked consequences. |
| Material issue vs low-value note | Not every fact deserves equal analysis. | Covering small issues while missing a major risk. |
On the first pass, scan for:
| If the issue is… | Write enough to cover… | Avoid… |
|---|---|---|
| Financial reporting | issue, relevant treatment, effect on statements, correction or disclosure | naming a standard without explaining the impact |
| Assurance | risk/assertion, evidence needed, procedure, conclusion effect | generic “do more audit work” language |
| Tax | taxpayer, treatment, documentation, compliance or risk consequence | giving final tax advice from incomplete facts |
| Finance | cash effect, assumption, risk, feasibility, recommendation | a number without a decision consequence |
| Performance management | measure, behavior, control, trade-off, recommendation | saying “improve controls” without naming the control |
| Governance | conflict, approval, disclosure, independence, oversight | assuming profitability cures a conflict |
| Trap | Better candidate habit |
|---|---|
| Starting to write before identifying all material issues. | Scan and rank first, then write. |
| Overanalyzing the first accounting issue. | Timebox depth and preserve breadth. |
| Missing a second competency in the same fact pattern. | Ask whether the fact also affects cash, tax, controls, or assurance. |
| Giving generic recommendations. | State the specific action, owner, control, or evidence needed. |
| Ignoring the user’s requested format or focus. | Let the ask determine the structure. |
| Treating management estimates as facts. | Mention evidence, trend data, assumptions, and uncertainty. |
| Leaving conclusions implied. | Add a short next step or recommendation for each material issue. |
| Writing too much setup. | Use direct issue-analysis-recommendation structure. |
This is a practical self-check, not an official timing rule:
Useful Day 3 wording often follows one of these patterns:
Avoid vague endings such as “management should monitor this” unless the answer says what to monitor, who should review it, and why it matters.
Use the main CFE Day 3 page as a breadth preview. For each missed question, label the failure as issue spotting, competency switch, evidence, time allocation, or recommendation wording. If you repeatedly identify the issue but miss the best answer, practise writing the action step. If you repeatedly miss second issues, practise scanning each prompt for accounting, assurance, tax, finance, performance management, and governance before reading choices.
When Finance Prep coverage expands, use short timed sets to train moving on. Day 3 improvement usually comes from cleaner triage and concise conclusions, not from making every answer longer.