CPA Canada PEP Assurance Elective Quick Review

A concise Quick Review for CPA Canada PEP Assurance Elective candidates reviewing audit, review, reporting, evidence, risk, controls, and case-writing decisions before question-bank practice.

CPA Canada PEP Assurance Elective Quick Orientation

This Quick Review is for candidates preparing for the CPA Canada PEP Assurance Elective using the official exam code CPA Assurance. It is independent review support, not affiliated with CPA Canada, and is designed to help you refresh high-yield concepts before using topic drills, mock exams, original practice questions, and detailed explanations.

The Assurance elective rewards candidates who can:

  • Identify the correct engagement type and reporting implications.
  • Link risk, materiality, assertions, controls, and procedures.
  • Write practical, case-specific audit or review procedures.
  • Recognize independence, ethical, governance, and acceptance issues.
  • Explain reporting options clearly when evidence, scope, or misstatement issues exist.
  • Manage case time by prioritizing the most significant assurance matters.

High-Yield Assurance Framework

The Core Assurance Logic

Most assurance case issues can be handled with this sequence:

  1. What is the user asking for?

    • Audit opinion?
    • Review conclusion?
    • No-assurance compilation?
    • Specific agreed procedures?
    • Internal control or special-purpose reporting?
  2. What level of assurance is appropriate?

    • Reasonable assurance: positive opinion.
    • Limited assurance: negative-form conclusion.
    • No assurance: compilation or advisory support.
  3. What are the risks?

    • Financial statement risk.
    • Engagement risk.
    • Independence risk.
    • Reporting risk.
    • User expectation risk.
  4. What evidence is needed?

    • Inspection, observation, inquiry, confirmation, recalculation, reperformance, analytical procedures.
  5. What is the reporting consequence?

    • Clean/unmodified report?
    • Modified opinion/conclusion?
    • Emphasis or other matter?
    • Withdrawal or decline engagement?
    flowchart TD
	A[Client request or case issue] --> B{Is assurance required?}
	B -->|Yes| C{Reasonable or limited assurance?}
	B -->|No| D[Compilation/advisory/no assurance]
	C -->|Reasonable| E[Audit: assess risks, controls, substantive evidence]
	C -->|Limited| F[Review: inquiry + analytics + targeted follow-up]
	E --> G{Sufficient appropriate evidence?}
	F --> G
	G -->|Yes| H{Material misstatement?}
	G -->|No| I[Scope limitation: consider qualified/disclaimer]
	H -->|No| J[Unmodified opinion/conclusion]
	H -->|Yes| K{Material and pervasive?}
	K -->|Material not pervasive| L[Qualified opinion/conclusion]
	K -->|Material and pervasive| M[Adverse opinion/conclusion]

Engagement Type Decision Table

Engagement / ServiceAssurance LevelTypical Work EffortReport Wording LogicCommon Exam Trap
Audit of financial statementsReasonable assuranceRisk assessment, controls understanding, substantive procedures, sufficient appropriate evidencePositive opinion on whether financial statements are fairly presented / prepared in accordance with applicable frameworkWriting only review-level procedures for an audit
Review engagementLimited assurancePrimarily inquiry, analytical procedures, discussion, follow-up on unusual itemsNegative-form conclusion: nothing has come to attention causing belief statements are misstatedTreating a review like a full audit
Compilation engagementNo assuranceCompile information based on management-provided data; consider whether information appears misleadingNo assurance expressedSaying the practitioner “verifies” or “provides assurance”
Agreed-upon proceduresNo assurance opinion; factual findingsPerform only procedures agreed with specified partiesReport factual findings, not conclusionRecommending broad assurance language
Special-purpose financial statementsVaries by engagementProcedures depend on framework and user needsMay require specific reporting references to special-purpose frameworkIgnoring basis of accounting and restricted users
Internal control reportingVariesAssess design and/or operating effectiveness depending on scopeConclusion depends on criteria and engagement termsConfusing design effectiveness with operating effectiveness

Audit Risk, Materiality, and Assertions

Audit Risk Model

Audit risk is the risk that the auditor expresses an inappropriate opinion when the financial statements are materially misstated.

\[ \text{Audit Risk} = \text{Inherent Risk} \times \text{Control Risk} \times \text{Detection Risk} \]

Practical exam use:

  • If inherent risk is high, plan more persuasive evidence.
  • If control risk is high, reduce reliance on controls and increase substantive testing.
  • If acceptable detection risk must be low, perform more effective substantive procedures, closer to year-end, with larger sample sizes or more reliable evidence.

Inherent Risk Indicators

IndicatorWhy It MattersLikely Audit Response
Complex estimatesMore judgment and bias riskTest assumptions, methods, data, sensitivity
Rapid growthRevenue cutoff, collectability, inventory, controls may lagExpand revenue, receivables, inventory testing
New accounting systemData migration and control failure riskTest conversion, access controls, reconciliations
Financing pressureIncentive to overstate assets/profits or understate liabilitiesIncrease fraud-focused procedures
Related-party transactionsNon-arm’s-length terms and disclosure riskInspect agreements, board minutes, confirmations
Management bonus targetsBias in estimates and revenue recognitionApply professional skepticism to judgment areas
Going concern pressureDisclosure and valuation issuesCash flow review, financing support, covenant analysis

Materiality: What to Say in a Case

Materiality affects planning, procedure extent, evaluating misstatements, and reporting. In a case response, do more than calculate a number.

Include:

  • Benchmark selected and why it is appropriate.
  • Percentage applied and why risk supports higher/lower end.
  • Performance materiality if relevant for planning testing.
  • Qualitative materiality items even if quantitatively small.
  • Reporting impact if misstatements are material.

Common qualitative materiality factors:

  • Turns profit into loss or affects trends.
  • Affects debt covenants, bonuses, financing, or regulatory compliance.
  • Involves fraud, illegal acts, related parties, or management integrity.
  • Changes key ratios or user decisions.
  • Affects disclosures important to users.

Assertion-to-Procedure Quick Map

A strong assurance answer links the risk to an assertion and then to a procedure.

Account / AreaCommon Assertion RiskStrong Procedure Examples
RevenueOccurrence, cutoff, accuracySelect sales near year-end and trace to shipping documents, contracts, invoices, and subsequent cash receipt
Accounts receivableExistence, valuationConfirm balances; review subsequent collections; assess allowance using aging and customer history
InventoryExistence, valuation, completenessAttend count; perform test counts; inspect obsolete items; compare cost to net realizable value
Purchases/payablesCompleteness, cutoffSearch for unrecorded liabilities using subsequent payments, unmatched receiving reports, supplier statements
PayrollOccurrence, accuracyReconcile payroll register to GL; test employee master file changes; inspect approvals
Fixed assetsExistence, valuation, rightsPhysically inspect additions; agree to invoices; assess capitalization vs expense; review impairment indicators
DebtCompleteness, classification, presentationConfirm with lenders; inspect agreements; test covenant compliance; review current/non-current classification
EstimatesValuation, disclosureEvaluate method, assumptions, source data, bias, subsequent events, expert reports
Related partiesCompleteness, disclosureReview minutes, confirmations, management representations, unusual transactions, ownership records
Provisions/contingenciesCompleteness, valuationLegal letter, board minutes, correspondence, subsequent payments, management assessment

Audit Evidence: Reliability Rules

Evidence Persuasiveness

Sufficient appropriate evidence depends on both quantity and quality.

Evidence TypeReliability NotesExam Use
External confirmationOften highly reliable if controlled by auditorStrong for receivables, cash, debt, legal claims
Auditor reperformanceHighly persuasive for calculations/controlsUse for depreciation, interest, reconciliations, control operation
Inspection of original documentsStronger than copies or verbal statementsGood for contracts, invoices, title documents
ObservationUseful but limited to point in timeInventory count, control performance
InquiryNecessary but weak alonePair with corroborating evidence
Analytical proceduresUseful for risk assessment and reviewsStronger when expectations are precise and data reliable
Management representationLowest standalone reliabilitySupportive only; not substitute for other evidence

Common Evidence Mistakes

Avoid writing:

  • “Discuss with management” as the only procedure for a material issue.
  • “Ensure revenue is correct” without saying how.
  • “Check invoices” without specifying direction of test.
  • “Review documents” without identifying documents and assertion.
  • “Compare to prior year” as sufficient evidence for a high-risk audit area.
  • “Obtain management representation” as the primary procedure.

Better procedure wording:

Select a sample of sales recorded in the final two weeks of the year and the first two weeks after year-end. Trace each sale to the sales invoice, shipping document, customer contract, and subsequent cash receipt to determine whether revenue was recorded in the correct period and only when performance obligations were satisfied.

Internal Controls Quick Review

Control Categories

Control TypePurposeExamples
PreventiveStop errors/fraud before they occurCredit approval, purchase order authorization, segregation of duties
DetectiveIdentify errors/fraud after occurrenceBank reconciliations, exception reports, inventory variance review
IT general controlsSupport reliable systemsAccess controls, change management, backups, operations controls
Application controlsProcess-level automated controlsThree-way match, edit checks, automated pricing
Monitoring controlsOngoing oversightManagement review, internal audit, board/committee review

Segregation of Duties

Separate these functions where possible:

FunctionShould Be Separated From
AuthorizationCustody and recording
Custody of assetsRecording and reconciliation
Recording transactionsReconciliation and review
System administrationTransaction processing
Vendor/customer master file changesPayment/receipt processing

How to Write a Control Weakness Response

Use a 4-part structure:

  1. Weakness: What is wrong?
  2. Implication: What could go wrong?
  3. Recommendation: What should management implement?
  4. Audit impact: How does this affect risk/procedures?

Example:

ElementExample
WeaknessThe accounts payable clerk can create vendors and process payments.
ImplicationFictitious vendors or unauthorized payments could be processed and concealed.
RecommendationVendor creation should require independent approval, and payment runs should be reviewed by someone outside AP.
Audit ImpactIncrease fraud risk in purchases/cash disbursements; test vendor master changes and subsequent payments.

Substantive Procedures by Major Cycle

Revenue and Receivables

High-risk areas:

  • Premature revenue recognition.
  • Side agreements or return rights.
  • Cutoff errors.
  • Collectability issues.
  • Related-party sales.
  • Bill-and-hold or consignment arrangements.

Useful procedures:

  • Test sales before and after year-end for cutoff.
  • Trace recorded sales to contracts, shipping, invoices, and cash receipts.
  • Confirm receivables with customers.
  • Review subsequent collections.
  • Analyze credit notes after year-end.
  • Review aged receivables and allowance assumptions.
  • Investigate unusual margins, manual journal entries, and sales spikes.

Inventory and Cost of Sales

High-risk areas:

  • Existence at year-end.
  • Obsolescence or net realizable value.
  • Count errors.
  • Consigned goods.
  • Standard costing and overhead allocation.
  • Cutoff of purchases and sales.

Useful procedures:

  • Attend inventory count and perform test counts floor-to-sheet and sheet-to-floor.
  • Inspect damaged or slow-moving inventory.
  • Test pricing to invoices or cost records.
  • Compare cost to selling price less costs to sell.
  • Review post-year-end sales of inventory.
  • Test cutoff using receiving and shipping documents.
  • Reconcile count sheets to final inventory listing.

Purchases, Payables, and Accruals

High-risk areas:

  • Unrecorded liabilities.
  • Expense cutoff.
  • Unauthorized purchases.
  • Related-party suppliers.
  • Capitalization of expenses.

Useful procedures:

  • Search subsequent disbursements for liabilities existing at year-end.
  • Review unmatched receiving reports and supplier statements.
  • Inspect invoices received after year-end.
  • Test cutoff around year-end receiving dates.
  • Review board minutes and contracts for obligations.
  • Analyze expense trends and investigate unusual decreases.

Cash and Debt

High-risk areas:

  • Restrictions on cash.
  • Unrecorded debt.
  • Covenant breaches.
  • Incorrect classification.
  • Interest accrual errors.

Useful procedures:

  • Confirm bank balances and debt directly.
  • Review bank reconciliations and outstanding items.
  • Inspect loan agreements.
  • Recalculate interest.
  • Test covenant calculations.
  • Review classification of current vs long-term debt.
  • Inspect correspondence with lenders.

Payroll

High-risk areas:

  • Ghost employees.
  • Unauthorized rate changes.
  • Incorrect vacation/bonus accruals.
  • Terminated employees still paid.

Useful procedures:

  • Reconcile payroll register to general ledger.
  • Test new hires and terminations to HR approvals.
  • Review master file changes.
  • Recalculate gross-to-net pay.
  • Compare payroll expense trends to headcount.
  • Test bonus/vacation accrual assumptions.

Special Topics Candidates Often Miss

Fraud Risk

Fraud risk is not solved by asking management whether fraud occurred. Address incentives, opportunities, and rationalization.

Common fraud-focused procedures:

  • Test manual journal entries, especially late, unusual, round-dollar, or posted by senior staff.
  • Review accounting estimates for management bias.
  • Investigate significant unusual transactions.
  • Perform unpredictable procedures.
  • Evaluate revenue recognition risk.
  • Consider management override of controls.

Related-party risks include incomplete disclosure, non-arm’s-length pricing, hidden obligations, and earnings manipulation.

Procedures:

  • Review board minutes and shareholder records.
  • Ask management and governance bodies about relationships.
  • Inspect unusual transactions and contracts.
  • Confirm terms directly where appropriate.
  • Compare terms to market terms if possible.
  • Ensure disclosures are complete and understandable.

Accounting Estimates

For estimates, focus on method, data, assumptions, and bias.

Estimate AreaAudit Focus
Allowance for doubtful accountsAging, subsequent collections, customer credit risk
Warranty provisionHistorical claims, current sales, product changes
Inventory obsolescenceSlow-moving items, post-year-end sales, write-down history
Fair valueValuation model, assumptions, external data, expert competence
ImpairmentCash flow forecasts, discount rates, sensitivity analysis
Legal provisionLegal letters, probability assessment, range of outcomes

Going Concern

Going concern issues often combine audit, financial reporting, and disclosure.

Indicators:

  • Recurring losses or negative cash flows.
  • Loan covenant breaches.
  • Expiring financing with no renewal.
  • Loss of major customer or supplier.
  • Inability to pay debts when due.
  • Significant legal claims.

Procedures:

  • Review cash flow forecasts and assumptions.
  • Compare forecasts to historical accuracy.
  • Inspect financing agreements and renewals.
  • Confirm support from lenders or owners where relevant.
  • Review covenant compliance.
  • Inspect subsequent cash receipts/disbursements.
  • Assess disclosure adequacy.

Reporting Quick Review

Audit Opinion Decision Table

SituationReporting Result
Sufficient appropriate evidence; no material misstatementUnmodified opinion
Material misstatement, not pervasiveQualified opinion
Material misstatement, pervasiveAdverse opinion
Scope limitation, material but not pervasiveQualified opinion
Scope limitation, material and pervasiveDisclaimer of opinion
Important matter properly presented/disclosedConsider emphasis of matter
Matter relevant to users’ understanding of audit/reportConsider other matter

Material vs Pervasive

ConceptMeaning
MaterialCould influence user decisions
PervasiveNot confined to specific elements, represents substantial portion of statements, or fundamental to users’ understanding

Quick decision rule:

  • Material but isolated → usually qualified.
  • Material and widespread/fundamental → adverse or disclaimer, depending on whether the issue is misstatement or lack of evidence.
  • Properly disclosed but important → consider emphasis, not modification.

Emphasis of Matter vs Other Matter

ParagraphUsed ForKey Condition
Emphasis of matterMatter presented/disclosed in the financial statementsAuditor wants to draw attention; opinion not modified
Other matterMatter not presented/disclosed in the financial statementsRelevant to users’ understanding of audit, responsibilities, or report

Common trap: Do not use emphasis of matter to “fix” inadequate disclosure. If disclosure is materially inadequate, consider modification.

Review Engagement Quick Review

A review provides limited assurance, so the work is narrower than an audit.

Review Engagement Procedures

Typical review procedures:

  • Inquiries of management and relevant personnel.
  • Analytical procedures.
  • Discussion of unexpected fluctuations.
  • Reading financial statements for plausibility.
  • Follow-up procedures when information appears inconsistent or misstated.

A review answer should not default to audit-level testing unless the case facts require follow-up on suspicious or inconsistent information.

IssueReview-Level Response
Revenue increased sharplyAsk management for explanation; compare to sales records/trends; perform analytics by month/customer/product; follow up unusual items
Receivables aging worsenedDiscuss collectability; compare subsequent collections; assess allowance reasonableness
Inventory margins changedAnalyze gross margin; discuss obsolete inventory; compare to post-year-end sales if needed
New debtInquire about terms; inspect agreement if necessary; assess classification/disclosure
Inconsistent explanationPerform additional procedures to resolve inconsistency

Compilation and No-Assurance Services

Compilation engagements are commonly tested because candidates may accidentally imply assurance.

Key points:

  • No assurance is expressed.
  • Management is responsible for information.
  • Practitioner compiles based on information provided.
  • Practitioner should consider whether information appears misleading.
  • Independence may need to be addressed depending on circumstances and reporting.

Common wording trap:

  • Weak: “We will audit the numbers for accuracy.”
  • Better: “A compilation does not provide assurance; users should understand that procedures are not designed to verify completeness or accuracy.”

Acceptance, Continuance, and Independence

Client Acceptance / Continuance Checklist

Before accepting or continuing, consider:

AreaQuestions to Ask
Management integrityAny history of fraud, aggressive reporting, unpaid fees, or pressure?
CompetenceDoes the firm have expertise, time, and resources?
IndependenceAny financial, employment, family, business, or advocacy threats?
PreconditionsIs the framework acceptable? Does management accept responsibility?
ScopeAre there restrictions that prevent sufficient evidence?
UsersWho will rely on the report? Are expectations clear?
FeesAre fees contingent or overdue in a way that creates threats?
Engagement termsIs there a clear engagement letter?

Independence Threats and Safeguards

ThreatExamplePossible Safeguards
Self-interestFinancial interest in client; significant overdue feesRemove interest, collect fees, independent review
Self-reviewAuditor prepared records being auditedSeparate teams, independent review, decline service
AdvocacyPromoting client financingLimit role, avoid advocacy, independent review
FamiliarityLong association or close relationshipRotate staff, independent quality review
IntimidationManagement threatens replacement or fee pressureEscalate, governance communication, consider withdrawal

Common exam mistake: identifying an independence threat without concluding whether it is significant and what safeguard or action is required.

Governance and Communication

Assurance cases may require recommendations to management, the board, audit committee, or owners.

Communicate:

  • Significant risks.
  • Fraud or suspected fraud.
  • Significant deficiencies in internal control.
  • Uncorrected misstatements.
  • Independence matters.
  • Scope limitations.
  • Significant accounting policy or estimate issues.
  • Going concern concerns.
  • Disagreements with management.

When governance is weak, recommend practical improvements:

  • Independent board or audit committee oversight.
  • Regular financial reporting package.
  • Approval limits.
  • Conflict-of-interest policy.
  • Whistleblower process.
  • Internal audit or periodic control review.
  • Formal budgeting and variance analysis.

Writing Strong Assurance Procedures

Procedure Formula

Use this structure:

Select / obtain / inspect / recalculate / confirm / observe + specific item + source document + purpose/assertion.

Examples:

Weak ProcedureStronger Procedure
Check revenue.Select revenue transactions recorded near year-end and trace to shipping documents and customer contracts to test cutoff and occurrence.
Review allowance.Compare the aged receivables listing to subsequent cash receipts and customer credit history to assess valuation of the allowance.
Test inventory.Perform floor-to-sheet and sheet-to-floor test counts during the inventory count to test existence and completeness.
Look at expenses.Search subsequent disbursements and unmatched receiving reports for liabilities existing at year-end to test completeness of payables.
Ask about debt.Confirm debt balances and terms with lenders and inspect loan agreements to test completeness, classification, and covenant disclosure.

Directional Testing

Direction matters.

ConcernStart FromTrace ToAssertion
Recorded sale may not existGeneral ledger / sales listingInvoice, shipping, contract, cash receiptOccurrence
Sale may be omittedShipping documents / ordersSales journal / GLCompleteness
Payable may be omittedSubsequent payments / receiving reportsPayables listing / GLCompleteness
Inventory may not existInventory listingPhysical inventoryExistence
Inventory may be incompletePhysical inventoryInventory listingCompleteness

Case-Writing Strategy for CPA Assurance

Practical Case Response Method

For each issue:

  1. Identify the issue clearly.

    • “Revenue cutoff risk exists because sales increased significantly in the final week of the year.”
  2. Explain why it matters.

    • Link to users, materiality, assertion, risk, or reporting.
  3. Apply case facts.

    • Use the numbers, dates, incentives, controls, agreements, and constraints provided.
  4. Recommend procedures or actions.

    • Be specific and feasible.
  5. Conclude.

    • State impact on engagement, report, control recommendation, or next step.

Time Management Traps

Avoid spending too much time on:

  • Generic definitions.
  • Long standard summaries without application.
  • Perfect materiality calculations at the expense of procedures.
  • Rewriting case facts.
  • Listing every possible procedure instead of the best procedures.
  • Over-auditing a review or compilation engagement.

What Markers Usually Reward in Assurance Responses

Strong responses tend to be:

  • Case-specific.
  • Risk-based.
  • Linked to assertions.
  • Clear about assurance level.
  • Practical and professionally worded.
  • Conclusive when reporting or acceptance decisions are required.

Weak responses tend to be:

  • Generic.
  • Procedure lists with no risk link.
  • Missing the report impact.
  • Confusing audit, review, and compilation.
  • Ignoring independence.
  • Failing to explain materiality or pervasiveness.

Rapid Review Tables

Engagement Planning Checklist

Planning AreaAsk Yourself
UsersWho relies on the report and why?
FrameworkWhat reporting framework applies?
Engagement typeAudit, review, compilation, agreed procedures, special report?
IndependenceAre there threats and safeguards?
MaterialityWhat benchmark and qualitative factors apply?
RisksWhat could be materially misstated?
ControlsCan controls be relied on or are they weak?
EvidenceWhat procedures provide sufficient appropriate evidence?
SpecialistsAre valuation, tax, actuarial, IT, or legal experts needed?
ReportingWhat opinion/conclusion/modification may be required?

Common Assurance Issue → Likely Response

Case FactLikely IssueCandidate Response
Client wants financingHigher user reliance; possible biasLower materiality, heightened skepticism, test debt/covenants/forecast assumptions
Owner pressures accountant to “make numbers work”Integrity and fraud riskConsider acceptance, governance communication, expanded fraud procedures
New ERP systemIT/control and data migration riskTest access, change management, conversion reconciliations
Inventory count not attendedScope limitation or alternative proceduresPerform alternative existence procedures; assess report impact if insufficient
Major lawsuitContingency completeness/valuation/disclosureLegal letter, minutes, correspondence, subsequent events
Significant sales after year-end creditsRevenue occurrence/returns riskTest credit notes, returns policy, cutoff, collectability
Missing bank confirmationsEvidence limitationFollow up confirmations; alternative procedures; reporting impact
Management refuses adjustmentMisstatementEvaluate materiality/pervasiveness; modify if necessary

Common Candidate Mistakes to Fix Before Practice

  • Recommending an audit when the user only needs limited assurance or no assurance.
  • Forgetting that compilation provides no assurance.
  • Writing procedures that are too vague to perform.
  • Not linking procedures to assertions.
  • Ignoring independence threats because the issue “feels small.”
  • Treating all misstatements as qualified opinions without assessing pervasiveness.
  • Using emphasis of matter for an uncorrected misstatement.
  • Concluding on going concern without discussing disclosures.
  • Relying only on management inquiry for high-risk areas.
  • Missing qualitative materiality.
  • Failing to use case facts in the recommendation.
  • Spending too long calculating and too little explaining.

Quick Practice Plan

Use this review page first, then move immediately into independent companion practice:

  1. Do short topic drills on materiality, assertions, reporting, and engagement type.
  2. Write procedures from scratch, then compare to detailed explanations.
  3. Complete mixed original practice questions that force you to identify the engagement type before choosing procedures.
  4. Attempt timed mini-cases focused on risk, controls, and reporting.
  5. Review every missed question by asking:
    • Did I identify the right assurance level?
    • Did I link risk to assertion?
    • Did I write a procedure that would actually produce evidence?
    • Did I conclude on reporting or engagement impact?

Final Exam-Prep Reminder

For the CPA Canada PEP Assurance Elective under exam code CPA Assurance, the fastest improvement usually comes from practicing applied case responses, not memorizing isolated definitions. Use this Quick Review to refresh the decision rules, then move into a question bank with original practice questions, topic drills, mock cases, and detailed explanations so you can apply the concepts under exam-style time pressure.