CPA Canada PEP Assurance Elective Exam Blueprint
Practical exam blueprint for CPA Canada PEP Assurance Elective candidates reviewing audit planning, evidence, reporting, ethics, controls, and assurance case judgment.
How to Use This Exam Blueprint
Use this page as a practical readiness map for the CPA Canada PEP Assurance Elective exam, code CPA Assurance. It is designed to help you convert broad assurance study areas into actions you can perform under case conditions.
This is not a substitute for CPA Canada materials and does not assign official weights. Treat each area below as a readiness area: if a case fact points to the issue, you should know what to analyze, what standard or principle is relevant, what procedure or recommendation fits, and how to communicate it clearly.
A strong candidate can usually do four things:
- Identify the assurance issue from messy case facts.
- Explain why the issue matters to users, the engagement, or the report.
- Recommend procedures, documentation, or reporting action.
- Tie the response back to risk, materiality, evidence, independence, and professional judgment.
Exam identity
| Item | Details |
|---|---|
| Official vendor/provider | CPA Canada |
| Official exam title | CPA Canada PEP Assurance Elective |
| Official exam code | CPA Assurance |
| Page purpose | Independent Exam Blueprint for readiness review |
| Best use | Final review, gap-checking, case debriefing, and targeted practice |
Topic-area readiness map
| Readiness area | What to be ready for | You are ready when you can… |
|---|---|---|
| Engagement acceptance and continuance | Client integrity, independence, competence, scope, deadlines, preconditions, management responsibilities | Decide whether to accept or continue, identify threats, propose safeguards, and explain missing engagement prerequisites |
| Professional ethics and independence | Self-interest, self-review, advocacy, familiarity, intimidation, conflicts of interest, confidentiality | Spot threats from case facts and recommend specific safeguards or withdrawal/escalation where appropriate |
| Audit planning | Understanding the entity, users, reporting framework, engagement team planning, timing, specialists, group considerations if relevant | Build a focused plan that links business risks to financial statement risks and audit responses |
| Risk assessment | Inherent risk, control risk, fraud risk, significant risks, related parties, estimates, going concern, unusual transactions | Identify what could go wrong, which assertions are affected, and whether the risk requires stronger evidence |
| Materiality | Users, benchmark selection, qualitative factors, performance materiality, clearly trivial threshold, revision during the engagement | Calculate or discuss materiality without relying only on arithmetic; adjust for qualitative facts |
| Internal control | Control environment, process controls, segregation of duties, authorization, reconciliations, IT controls, control deficiencies | Describe the control, identify the weakness, explain the implication, and recommend a practical fix |
| Tests of controls | Walkthroughs, inquiry, observation, inspection, reperformance, timing and extent | Decide when controls can be relied on and what testing is needed before reducing substantive work |
| Substantive procedures | Inspection, confirmation, recalculation, reperformance, analytical procedures, inquiry, cut-off testing | Design procedures that directly address assertions and risks, not generic audit work |
| Audit evidence | Relevance, reliability, sufficiency, appropriateness, external vs internal evidence, contradictory evidence | Evaluate whether evidence supports the conclusion and identify what additional evidence is needed |
| Assertions | Existence, completeness, accuracy, valuation, rights and obligations, presentation, occurrence, cut-off | Map each risk to the right assertion and choose a procedure that tests that assertion |
| Analytical procedures | Planning analytics, substantive analytics, final review analytics, expectation setting, investigation thresholds | Explain when analytics are useful, what data is needed, and what unusual relationships imply |
| Sampling and testing approach | Sample design, population, sampling risk, tolerable misstatement/deviation, projected errors | Interpret sample results and decide whether more work is required |
| Revenue and receivables | Recognition, cut-off, collectability, returns, side agreements, contract terms, confirmations | Identify revenue risks and design procedures around occurrence, accuracy, cut-off, and valuation |
| Inventory | Existence, condition, costing, obsolescence, cut-off, count attendance, third-party locations | Plan count procedures and follow-up work for slow-moving, damaged, or consigned inventory |
| Purchases, payables, and accruals | Completeness, unrecorded liabilities, cut-off, expense classification, vendor terms | Design search-for-unrecorded-liabilities procedures and explain completeness risk |
| Payroll | Authorization, ghost employees, rates, deductions, cut-off, payroll system controls | Test payroll controls and substantive links between employees, hours, rates, and payments |
| Cash and financing | Bank confirmations, reconciliations, restrictions, debt covenants, interest, classification | Identify evidence needed for cash, debt, covenant compliance, and disclosure |
| Estimates and fair values | Management assumptions, bias, sensitivity, specialists, subsequent events, disclosure | Challenge assumptions and propose procedures to test reasonableness |
| Related parties | Identification, authorization, business purpose, measurement, disclosure | Recognize related-party indicators and recommend procedures beyond management inquiry |
| Fraud considerations | Incentives, opportunities, rationalization, management override, journal entries, unusual transactions | Link fraud risk factors to procedures and discuss professional skepticism |
| Going concern | Financial indicators, operating indicators, mitigating plans, disclosure, reporting implications | Assess management’s plans and evidence; explain possible reporting consequences |
| Subsequent events | Events requiring adjustment vs disclosure, date of report, procedures near completion | Classify events and identify required audit work before the report date |
| Written representations | Management responsibilities, completeness of information, specific representations | Know what representations support and what they do not replace |
| Audit completion | Misstatements, adjusted/unadjusted differences, final analytics, subsequent events, review of work | Conclude whether evidence is sufficient and whether misstatements affect the report |
| Reporting | Unmodified and modified opinions, scope limitations, material misstatements, emphasis-type communication where relevant | Select the reporting consequence and explain the reason in user-focused language |
| Review engagements | Limited assurance, inquiry and analytics, plausibility, engagement terms, reporting differences | Distinguish review work from audit work and avoid over-auditing or under-explaining |
| Compilation and related services | No assurance, management responsibility, use of financial information, practitioner involvement | Explain what is and is not provided, and avoid applying audit-level procedures unnecessarily |
| Special reports and other assurance work | Subject matter, criteria, responsible party, intended users, level of assurance, restricted use | Identify the engagement elements and tailor procedures to the subject matter |
| Communication with governance | Significant risks, independence, deficiencies, misstatements, disagreements, fraud, significant findings | Decide what must be communicated, to whom, and with what urgency |
| Documentation | Planning, risk assessment, evidence, conclusions, review notes, professional judgment | Prepare documentation that shows the link from issue to procedure to conclusion |
Can you do this?
Use this as a direct self-test. If you cannot confidently check an item, it belongs in your next practice session.
Core assurance judgment
- Identify the engagement type from case facts: audit, review, compilation, special assurance, agreed procedures, or advisory work.
- Explain the level of assurance provided, if any.
- Identify the users of the report and how their needs affect materiality, risk, and reporting.
- State management’s responsibilities separately from the practitioner’s responsibilities.
- Recognize when independence is required and when threats require safeguards.
- Identify scope limitations before and during the engagement.
- Distinguish a financial reporting issue from an assurance procedure issue.
- Recommend a practical next step when evidence is insufficient.
- Avoid giving a conclusion that is stronger than the work performed supports.
Audit planning and risk
- Build a planning memo from scattered facts.
- Identify business risks and translate them into financial statement risks.
- Connect each risk to the relevant assertion.
- Determine whether a risk may be significant based on judgment, complexity, fraud, estimates, or unusual transactions.
- Explain how assessed risk affects the nature, timing, and extent of procedures.
- Identify fraud risk factors and management override risks.
- Recognize when a specialist may be needed.
- Revise planning decisions when new facts appear during the engagement.
Materiality and misstatements
- Select a reasonable benchmark based on users and entity circumstances.
- Explain qualitative factors that may lower materiality.
- Distinguish overall materiality, performance materiality, and clearly trivial amounts.
- Reassess materiality when results or user needs change.
- Aggregate misstatements and assess their impact.
- Distinguish factual, judgmental, and projected misstatements.
- Explain reporting implications when uncorrected misstatements are material.
Internal controls
- Identify the control objective for a process.
- Identify the control weakness, not just the error.
- Explain the possible misstatement caused by the weakness.
- Recommend a control that is specific, practical, and segregates incompatible duties where possible.
- Decide whether a test of control or substantive procedure is more appropriate.
- Describe how to perform a walkthrough.
- Identify IT general control concerns such as access, change management, backups, and system-generated reports.
- Explain how control deficiencies affect the audit approach.
Evidence and procedures
- Design procedures that begin with an action verb: inspect, agree, trace, vouch, recalculate, confirm, observe, inquire, analyze, reperformance.
- Write procedures with source document, target document, direction of test, assertion, and purpose.
- Avoid vague procedures such as “check revenue” or “verify inventory.”
- Explain why external evidence is often more reliable than internal evidence.
- Identify when inquiry alone is insufficient.
- Know when confirmation is useful and when alternative procedures are required.
- Use subsequent cash receipts, shipping documents, receiving reports, bank statements, contracts, and board minutes appropriately.
- Evaluate contradictory evidence instead of ignoring it.
Reporting and completion
- Decide whether evidence is sufficient and appropriate.
- Identify whether a matter is a material misstatement or scope limitation.
- Determine whether the matter is pervasive enough to affect the type of report.
- Explain when additional disclosure is required.
- Identify matters to communicate to management or those charged with governance.
- Assess subsequent events and going-concern evidence before report issuance.
- Write concise conclusions supported by case facts.
Assurance engagement decision checks
Engagement type comparison
| Question | Audit | Review | Compilation / related service |
|---|---|---|---|
| Is assurance provided? | Yes, reasonable assurance | Yes, limited assurance | Generally no assurance |
| Typical work emphasis | Risk assessment, controls where relevant, substantive evidence, completion and reporting | Inquiry, analytics, plausibility, follow-up on unusual items | Assemble or present information based on management-provided data |
| Evidence expectation | Sufficient appropriate audit evidence | Evidence sufficient for limited assurance conclusion | Not designed to obtain assurance evidence |
| Common exam trap | Writing generic procedures without linking to assertions | Performing audit-level procedures without explaining why | Implying assurance when none is provided |
| Candidate focus | Risk, materiality, assertions, evidence, opinion impact | Plausibility, inquiry, analytics, limited assurance wording | Scope, responsibility, no assurance, user understanding |
Report consequence decision path
flowchart TD
A[Issue identified] --> B{Is it a financial statement misstatement?}
B -->|Yes| C{Is it material?}
B -->|No| D{Is it a scope limitation or evidence issue?}
C -->|No| E[Accumulate and communicate as appropriate]
C -->|Yes| F{Is it pervasive?}
F -->|No| G[Modified opinion may be needed]
F -->|Yes| H[More severe modification may be needed]
D -->|Yes| I{Can additional procedures obtain evidence?}
I -->|Yes| J[Perform additional procedures]
I -->|No| K[Assess reporting impact]
D -->|No| L[Consider disclosure, communication, or documentation]
Use this flow to discipline your case writing. First classify the issue. Then decide whether the response is more work, correction, disclosure, communication, or reporting modification.
Planning, risk, and materiality checklist
Planning questions to answer in every audit-style case
| Planning question | What to look for in the case | Why it matters |
|---|---|---|
| Who are the users? | Lenders, investors, board, regulator, buyer, parent company, owner-manager | Drives materiality and reporting sensitivity |
| What changed this year? | New systems, financing, growth, losses, acquisitions, staff turnover, new contracts | Changes often create risk |
| Where is management under pressure? | Covenants, bonuses, sale of business, cash shortage, performance targets | Increases fraud or bias risk |
| Which balances are large or judgmental? | Revenue, receivables, inventory, impairment, provisions, estimates | Larger or subjective balances need focused work |
| What controls are weak? | Lack of segregation, owner override, no reconciliations, weak access controls | Affects risk assessment and audit strategy |
| What evidence may be hard to obtain? | Third-party records, estimates, related parties, old balances, missing documents | May create scope or completion issues |
| What deadlines exist? | Financing date, board meeting, transaction close | May affect staffing, timing, and acceptance risk |
Materiality readiness
You do not need to memorize one universal benchmark. You need to justify the basis selected and respond to case facts.
Common materiality thinking:
\[ \text{Planning materiality} = \text{chosen benchmark} \times \text{selected percentage} \]\[ \text{Performance materiality} < \text{planning materiality} \]| Materiality decision | Readiness check |
|---|---|
| Benchmark selection | Can you explain why profit, revenue, assets, equity, or another basis fits the users? |
| Normalization | Can you adjust for unusual one-time items before applying judgment? |
| Qualitative factors | Can you identify covenant breaches, fraud, related parties, regulatory sensitivity, or management compensation issues? |
| Performance materiality | Can you explain why it is set below overall materiality to reduce aggregation risk? |
| Clearly trivial threshold | Can you explain why very small differences may not need accumulation? |
| Revision | Can you update materiality when actual results differ from planning assumptions? |
| Evaluation | Can you aggregate uncorrected differences and conclude on their effect? |
Audit risk model
Use the audit risk model conceptually, not mechanically.
\[ \text{Audit Risk} = \text{Risk of Material Misstatement} \times \text{Detection Risk} \]\[ \text{Risk of Material Misstatement} = \text{Inherent Risk} \times \text{Control Risk} \]| If this increases… | Then be ready to explain… |
|---|---|
| Inherent risk | Why the account or transaction is naturally risky |
| Control risk | Why controls may not prevent or detect misstatement |
| Risk of material misstatement | Why stronger evidence or more procedures are needed |
| Detection risk allowed | Why less work may be acceptable only when assessed risk is lower |
| Detection risk required | Why nature, timing, or extent must be strengthened when assessed risk is higher |
Assertions and procedure design
Assertion map
| Assertion | Typical concern | Procedure cue |
|---|---|---|
| Existence | Recorded asset or balance may not exist | Vouch from accounting records to external evidence or physical item |
| Completeness | Items may be omitted | Trace from source documents to accounting records |
| Accuracy | Amounts may be mathematically or clerically wrong | Recalculate, agree details, inspect pricing or rates |
| Valuation | Asset, liability, or estimate may be misstated | Test assumptions, compare to subsequent events, inspect market or support |
| Rights and obligations | Entity may not own asset or owe liability | Inspect contracts, title, loan agreements, lease terms |
| Occurrence | Recorded transaction may not have occurred | Vouch to contract, shipment, receipt, approval, or cash movement |
| Cut-off | Transaction recorded in wrong period | Test documents immediately before and after period end |
| Classification | Item recorded in wrong account | Inspect nature of transaction and account coding |
| Presentation and disclosure | Financial statements may not describe matter properly | Compare disclosures to framework and supporting documents |
Strong procedure-writing formula
A useful exam procedure usually includes:
- Action: inspect, trace, vouch, recalculate, confirm, observe, inquire, analyze.
- Source: invoice, contract, bank statement, shipping log, board minutes, subledger.
- Direction: from records to support, or from source documents to records.
- Assertion: existence, completeness, valuation, cut-off, etc.
- Purpose: what the procedure proves or challenges.
| Weak procedure | Stronger procedure |
|---|---|
| Check revenue. | Select recorded sales near year-end and agree to signed contracts, shipping documents, and subsequent cash receipts to test occurrence, cut-off, and collectability. |
| Verify inventory. | Attend the year-end count, perform test counts from floor to count sheets and count sheets to floor, inspect for obsolete items, and reconcile final count sheets to the inventory listing. |
| Review expenses. | Select payments made after year-end and trace to receiving reports and invoices dated before year-end to identify unrecorded liabilities. |
| Test payroll. | Select employees from the payroll register and agree to HR authorization, approved pay rates, hours worked, and bank payment details. |
| Confirm receivables. | Send confirmations to selected customers and perform alternative procedures, such as inspecting subsequent receipts and shipping documents, for non-responses. |
High-yield account and cycle checks
Revenue and receivables
| Risk cue | Likely assertion | Procedures to be ready to propose |
|---|---|---|
| Aggressive sales targets | Occurrence, cut-off | Vouch sales to contracts, shipping documents, delivery evidence, and customer acceptance |
| New revenue stream | Accuracy, presentation | Inspect contracts and evaluate recognition pattern and disclosure |
| Large year-end sales | Cut-off, occurrence | Test sales before and after year-end using shipping and delivery records |
| High receivables growth | Valuation, existence | Confirm balances, inspect subsequent receipts, review aged receivables |
| Side agreements or returns | Valuation, occurrence | Inspect credit notes, returns after year-end, correspondence, and sales terms |
| Related-party customer | Occurrence, measurement, disclosure | Inspect approvals, business purpose, pricing support, and disclosure |
Inventory
| Risk cue | Likely assertion | Procedures to be ready to propose |
|---|---|---|
| Inventory stored at multiple locations | Existence, completeness | Attend selected counts, confirm third-party-held inventory, reconcile location listings |
| Slow-moving goods | Valuation | Review aging, subsequent sales, write-down history, and obsolescence reports |
| Complex costing | Accuracy, valuation | Test cost build-up, overhead allocation, standard cost updates, and variance treatment |
| Goods in transit | Cut-off, rights | Inspect shipping terms, receiving reports, supplier invoices, and freight documents |
| Count weaknesses | Existence, completeness | Observe count instructions, perform test counts, evaluate control over count sheets |
| Consignment arrangements | Rights and obligations | Inspect agreements and exclude goods not owned by the entity |
Purchases, payables, and expenses
| Risk cue | Likely assertion | Procedures to be ready to propose |
|---|---|---|
| Understatement pressure | Completeness | Search for unrecorded liabilities using subsequent payments and unmatched receiving reports |
| Manual accruals | Accuracy, completeness | Recalculate accruals and compare to contracts, invoices, and subsequent payments |
| Capitalization judgment | Classification, valuation | Inspect invoices and evaluate whether costs meet capitalization criteria |
| Vendor disputes | Completeness, valuation | Inspect correspondence, legal letters, and settlement documents |
| Cut-off issues | Cut-off, completeness | Match receiving reports before and after year-end to invoices and ledger entries |
Cash, debt, and financing
| Risk cue | Likely assertion | Procedures to be ready to propose |
|---|---|---|
| New loan or covenant | Classification, disclosure, completeness | Inspect loan agreement, recalculate covenant ratios, confirm balance with lender |
| Restricted cash | Presentation, rights | Inspect agreements and bank confirmations for restrictions |
| Bank reconciliation issues | Existence, completeness | Reperform reconciliation, inspect subsequent clearing of outstanding items |
| Cash shortages | Going concern, fraud | Review forecasts, financing agreements, board minutes, and subsequent cash flows |
| Unusual transfers | Occurrence, classification | Trace transfers between bank accounts and inspect authorization |
Estimates, provisions, and fair values
| Risk cue | Likely assertion | Procedures to be ready to propose |
|---|---|---|
| Management bias | Valuation | Compare prior estimates to actual results and challenge assumptions |
| Complex model | Accuracy, valuation | Test mathematical accuracy, inputs, assumptions, and sensitivity |
| Legal claim | Completeness, valuation | Inspect legal correspondence and obtain legal confirmation where appropriate |
| Impairment indicator | Valuation | Review cash-flow forecasts, market evidence, assumptions, and subsequent performance |
| Environmental or warranty obligation | Completeness, valuation | Inspect contracts, claims history, expert reports, and subsequent payments |
Internal control checklist
Control weakness response format
For each weakness, write your response in four parts:
| Part | What to include |
|---|---|
| Weakness | The exact missing or ineffective control |
| Implication | The error, fraud, or misstatement that could occur |
| Recommendation | A practical control improvement |
| Assurance impact | How the weakness affects risk assessment or testing |
Common control areas
| Process | Controls to know | Common weaknesses |
|---|---|---|
| Sales | Credit approval, order authorization, shipping match, invoice sequence, price approval, receivables review | Sales recorded before shipment, unauthorized discounts, poor credit review |
| Purchases | Purchase orders, receiving reports, invoice matching, approval limits, vendor master controls | Fictitious vendors, duplicate payments, unrecorded liabilities |
| Payroll | HR authorization, approved rates, timesheet approval, segregation of HR/payroll/payment | Ghost employees, unauthorized raises, inaccurate hours |
| Inventory | Count instructions, count sheet control, restricted access, cycle counts, review of obsolescence | Missing count control, theft, obsolete inventory not written down |
| Cash | Bank reconciliations, dual approvals, restricted access, independent review | Unauthorized payments, unreconciled differences |
| IT | User access, password controls, change approval, backups, system report integrity | Excessive access, untested changes, unreliable reports |
| Financial close | Journal entry approval, reconciliations, review of estimates, disclosure checklist | Management override, late adjustments, unsupported accruals |
Controls vs substantive testing decision
| Case fact | Likely response |
|---|---|
| Controls are well designed and expected to operate effectively | Consider testing controls if efficient and relevant |
| Controls are weak or absent | Increase substantive procedures and communicate deficiencies |
| System-generated reports are used as evidence | Test report completeness and accuracy or underlying IT controls |
| Small owner-managed entity with limited segregation | Consider compensating owner review controls, but remain alert to override |
| One-time complex transaction | Substantive testing may be more effective than relying on routine controls |
| Fraud risk identified | Do not rely only on controls; add unpredictable and targeted procedures |
Review engagement and related-service readiness
| Topic | Readiness questions |
|---|---|
| Engagement acceptance | Are management responsibilities clear? Is the practitioner competent and independent where required? Is the scope appropriate? |
| Level of assurance | Can you explain limited assurance without using audit language? |
| Work effort | Can you design inquiry and analytical procedures tailored to the entity? |
| Plausibility | Can you identify balances or relationships that appear inconsistent with expectations? |
| Follow-up | Can you explain what to do when inquiry or analytics reveal unusual items? |
| Reporting | Can you avoid implying an audit opinion when only limited assurance work was performed? |
| Compilation | Can you explain that compilation-type work does not provide assurance? |
| Special assurance | Can you identify subject matter, criteria, responsible party, users, evidence, and form of conclusion? |
Ethics, independence, and professional behavior
Threat identification table
| Threat | Case cue | Candidate response |
|---|---|---|
| Self-interest | Fees, financial interest, loan, employment opportunity, client pressure | Identify threat, assess significance, propose safeguard or decline/withdraw |
| Self-review | Practitioner prepared information being assured | Separate teams, independent review, decline if safeguard insufficient |
| Advocacy | Promoting client position, financing, or transaction | Avoid acting as advocate when assurance objectivity is impaired |
| Familiarity | Long relationship, family connection, former employee | Rotate staff, independent review, remove person from engagement |
| Intimidation | Management threatens dismissal, fee pressure, deadline pressure | Escalate, document, involve governance, consider withdrawal |
| Conflict of interest | Serving parties with opposing interests | Obtain consent where appropriate, use safeguards, decline if conflict cannot be managed |
| Confidentiality | Request for client information by unauthorized party | Do not disclose unless permitted or required; seek guidance if uncertain |
Ethics readiness prompts
- Can you separate an independence issue from a general business risk?
- Can you name the threat category and connect it to the case fact?
- Can you recommend a safeguard that actually addresses the threat?
- Can you explain when a safeguard is not enough?
- Can you identify when communication with those charged with governance is needed?
- Can you document the reasoning rather than only stating a conclusion?
Scenario and decision-point checks
| Scenario cue | What the exam may be testing | Strong response pattern |
|---|---|---|
| Management refuses access to records | Scope limitation, evidence sufficiency, reporting impact | Explain why evidence is needed, request access, perform alternatives if possible, assess report effect |
| Client wants audit completed very quickly | Acceptance, competence, due care, staffing, scope risk | Identify deadline risk and recommend realistic planning or decline if quality is compromised |
| Material error found after work is nearly complete | Misstatement evaluation, communication, reporting | Quantify, aggregate, ask management to correct, assess effect if uncorrected |
| New system implemented mid-year | IT controls, data reliability, change management | Test conversion, access, change controls, and report reliability |
| Owner approves all transactions | Segregation, override, small entity controls | Identify compensating controls and increase substantive work for override risk |
| Revenue contract has unusual terms | Accounting and assurance integration | Analyze recognition issue first, then design procedures around contract terms |
| Inventory count not attended | Scope limitation, alternative procedures | Perform roll-forward/roll-back, inspect subsequent sales/purchases, evaluate whether evidence is enough |
| Significant uncertainty about financing | Going concern, disclosure, reporting | Assess forecasts, lender support, covenant status, management plans, and disclosure |
| Related-party transaction not disclosed | Completeness, transparency, ethics | Inspect records, inquire, review minutes, assess measurement and disclosure |
| Management estimate appears optimistic | Bias, valuation, professional skepticism | Test assumptions, compare external data, perform sensitivity analysis, review subsequent events |
| Lawyer letter notes possible claim | Provision or disclosure, evidence | Assess likelihood and amount, obtain management/legal evidence, evaluate reporting impact |
| Control deficiency caused errors | Control communication, substantive response | Explain deficiency, recommend control, expand substantive testing |
Calculations and quantitative checks
CPA Assurance cases may not be calculation-heavy, but assurance conclusions often depend on interpreting numbers. Be ready to calculate and explain the result.
| Calculation area | What to practice | Interpretation check |
|---|---|---|
| Materiality | Benchmark times selected percentage | Does the basis fit the users and entity? |
| Performance materiality | Amount below overall materiality | Does it reduce aggregation risk? |
| Misstatement aggregation | Sum known and projected misstatements | Are uncorrected differences material individually or in aggregate? |
| Ratio analysis | Gross margin, current ratio, debt-to-equity, inventory turnover, days sales outstanding | Does the trend indicate risk or need for further work? |
| Covenant testing | Recalculate ratios from agreement definitions | Is there breach risk or disclosure concern? |
| Sample projection | Project sample error to population | Does projected misstatement exceed tolerable misstatement? |
| Aging analysis | Receivables or inventory aging percentages | Is valuation or allowance reasonable? |
| Analytical expectation | Expected amount based on non-financial data or prior relationship | Are differences explainable and supported? |
Useful formulas to know conceptually:
\[ \text{Days Sales Outstanding} = \frac{\text{Average Accounts Receivable}}{\text{Revenue}} \times 365 \]\[ \text{Inventory Turnover} = \frac{\text{Cost of Sales}}{\text{Average Inventory}} \]\[ \text{Current Ratio} = \frac{\text{Current Assets}}{\text{Current Liabilities}} \]\[ \text{Debt-to-Equity Ratio} = \frac{\text{Total Debt}}{\text{Total Equity}} \]When using ratios in a case, do not stop at the calculation. State what changed, why it matters, which assertion is affected, and what procedure follows.
Common weak areas and traps
| Trap | Why it hurts performance | Better approach |
|---|---|---|
| Listing generic procedures | Does not show judgment or linkage to risk | Tie each procedure to a risk and assertion |
| Ignoring the engagement type | Audit, review, and compilation require different work and conclusions | Identify engagement type before recommending procedures |
| Treating inquiry as enough | Inquiry alone is usually weak evidence | Corroborate with documents, external evidence, recalculation, or subsequent events |
| Confusing completeness and existence | Testing direction matters | Trace for completeness; vouch for existence or occurrence |
| Calculating materiality mechanically | Case users and qualitative factors may change the answer | Justify the benchmark and adjust for sensitive facts |
| Missing independence issues | Ethics facts are often embedded in client relationships or fees | Scan for threats before starting technical analysis |
| Overlooking reporting impact | Procedures are not enough when evidence or misstatements affect the report | Conclude on correction, disclosure, or modification |
| Forgetting communication with governance | Significant matters may need escalation | Identify who should be informed and why |
| Not following up contradictory evidence | Professional skepticism requires resolving inconsistencies | Explain additional procedures or revised conclusion |
| Writing accounting advice only | The elective requires assurance implications | Link accounting issue to audit risk, evidence, and reporting |
| Over-auditing review engagements | Review work has a different level of assurance | Use inquiry, analytics, plausibility, and follow-up procedures |
| Under-documenting judgment | Conclusions need support | State facts, criteria, analysis, and conclusion clearly |
Case-writing checklist
Before writing
- Identify the requireds and rank them by importance.
- Note the engagement type and reporting deadline.
- List users and their decision needs.
- Scan for independence and acceptance issues.
- Identify high-risk accounts and unusual transactions.
- Calculate key materiality or ratio figures if relevant.
- Mark evidence gaps and scope limitations.
- Decide which issues need procedures, controls, reporting, or ethics analysis.
While writing
- Use headings that match the issue.
- Start each issue with the risk or problem.
- Use case facts, not generic statements.
- State the assertion affected.
- Recommend specific procedures.
- Explain implications for the engagement or report.
- Include a clear conclusion or next step.
- Avoid long textbook explanations unless needed for the case.
After writing
- Did every recommendation respond to a case fact?
- Did you separate audit, review, and compilation logic?
- Did you address independence or ethics if facts indicated it?
- Did you quantify materiality or misstatements where useful?
- Did you consider communication with management or governance?
- Did you conclude on reporting implications?
- Did you avoid unsupported certainty?
Final-week review checklist
Technical refresh
- Review audit risk, materiality, assertions, and procedure design.
- Refresh engagement acceptance and continuance considerations.
- Review independence threat categories and safeguards.
- Practice writing specific procedures for revenue, inventory, payables, cash, debt, estimates, and payroll.
- Review internal control weakness format: weakness, implication, recommendation, assurance impact.
- Refresh audit completion topics: misstatements, subsequent events, going concern, representations, reporting.
- Review differences among audit, review, compilation, and special assurance work.
- Review common reporting consequences for misstatements and scope limitations.
Case practice
- Complete at least one timed assurance-focused case.
- Debrief by mapping missed points to this checklist.
- Rewrite weak procedures to include action, evidence source, direction, assertion, and purpose.
- Practice identifying issues from exhibits rather than from the requireds only.
- Practice concise conclusions instead of open-ended discussion.
- Redo one prior weak case under time pressure.
- Build a one-page personal error log.
Exam execution
- Read the requireds before reading exhibits in detail.
- Allocate time by required, then move on.
- Use case facts in every major paragraph.
- Prioritize high-risk and decision-useful issues.
- Do not spend excessive time on low-value calculations.
- If uncertain, state a reasonable assumption and proceed.
- Leave time to add missing conclusions and reporting implications.
Personal readiness scorecard
Use this table to decide where to spend your next study block.
| Area | Green: ready | Yellow: needs review | Red: urgent |
|---|---|---|---|
| Engagement acceptance and independence | Can identify threats and safeguards quickly | Can identify threats but safeguards are vague | Misses ethics facts or gives unsafe conclusions |
| Risk assessment | Links facts to risks and assertions | Identifies risks but not assertions | Lists facts without audit impact |
| Materiality | Justifies benchmark and qualitative factors | Can calculate but weak explanation | Uses one formula mechanically |
| Procedure design | Procedures are specific and assertion-based | Procedures are partly generic | Procedures are vague or unsupported |
| Internal controls | Explains weakness, implication, recommendation | Finds weakness but weak implication | Gives generic control advice |
| Evidence evaluation | Identifies sufficiency and reliability issues | Knows evidence types but weak conclusions | Accepts weak evidence without challenge |
| Reporting | Connects issue to report impact | Knows terms but hesitates on application | Does not conclude on reporting |
| Review/compilation distinctions | Clearly separates levels of assurance | Some confusion in wording | Implies wrong assurance level |
| Case writing | Organized, fact-based, concise | Good knowledge but timing issues | Unstructured or incomplete responses |
Practical next step
Pick your weakest two red or yellow areas from the scorecard. For each one, complete a short targeted practice set or case debrief focused only on that skill: one for procedure design, one for reporting judgment, one for controls, or one for ethics and independence. Then redo the same issue under time pressure until your response links case fact → risk → assertion → procedure or recommendation → conclusion without prompting.