Key takeaways
- Compilation provides no assurance — appropriate for internal management and tax filing only.
- Review provides limited assurance — based on inquiry and analytical procedures; common for bank financing.
- Audit provides reasonable assurance — through risk-based testing, external confirmation and observation; required for larger financing and regulatory compliance.
- Confirm requirements with the end user first — before engaging an accountant, get written confirmation from lender, investor or regulator of what engagement is needed.
- Audit-ready is not audited — audit-ready describes records organized for audit; only an audit opinion means audited.
A business submits management-prepared financial statements to a lender as part of a financing application. The lender approves the loan in principle, then requests a review engagement. The year-end closes in two weeks, the records are archived, and reopening them will delay the application by months.
This scenario is common and entirely preventable. The problem is that "financial statements" in Canada can refer to several different deliverables, each with different assurance levels and cost implications. A compilation provides no assurance. A review provides limited assurance. An audit provides reasonable assurance. Audit-ready statements are records prepared for audit—they are not audited.
Which engagement you need depends on who will use the statements, why, and what assurance level the intended user requires. Before engaging an accountant, confirming requirements with the lender, investor, regulator or other intended user prevents costly delays and replaces guesswork with clarity.
For MSBs and PSPs: Financial reporting challenges are distinctive in money services businesses. See our MSB and PSP considerations section below, or contact us for AML program design support.
Financial Statement Preparation vs Compilation
Bookkeeping software produces trial balances and general ledger reports. An accountant may organize year-end records, correct posting errors, and prepare financial statements for internal management. These are management-prepared statements. If the accountant reviews the draft, corrects errors, and formats it professionally, that is still management-prepared statement preparation—not a formal compilation engagement.
A formal compilation engagement is performed under Canadian Standard on Related Services 4200 (CSRS 4200) and involves a defined professional engagement with specific responsibilities and a formal report. The key distinction is the engagement agreement, the intended users, the professional standard applied, and the report issued.
What Is a Compilation Engagement?
A compilation engagement under CSRS 4200 (Canadian Standard on Related Services 4200) involves the practitioner assisting management in presenting the entity's financial information. Importantly, management remains responsible for the accuracy and completeness of the underlying records and financial information. The practitioner compiles the information in accordance with the identified basis of accounting. No assurance is provided—the practitioner does not test transactions, verify balances with external parties, or perform procedures to detect errors or fraud.
The practitioner describes the basis of accounting applied and the compiled financial information must include a note clearly describing this basis. The practitioner issues a Compilation Engagement Report.
Understanding the Basis of Accounting
Compiled financial information must include a clear description of the basis of accounting applied. The basis may be a general-purpose framework such as ASPE (Accounting Standards for Private Enterprises) or IFRS (International Financial Reporting Standards) where appropriate for the entity's circumstances and intended use. However, a business may also select another basis of accounting suited to its particular needs—such as a modified cash basis for internal management reporting. See CPA Canada's professional standards guidance for framework selection and disclosure requirements.
The compiled statements should not be described as fully compliant with ASPE or IFRS unless the applicable recognition, measurement, presentation and disclosure requirements have actually been met. This transparency is essential to ensure users understand which framework was applied and what limitations may exist.
Is a Compilation the Same as a Notice to Reader?
"Notice to Reader" is the former Canadian term and remains commonly searched and used colloquially by business owners and stakeholders. However, CSRS 4200 represented more than a simple terminology update. The standard introduced clearer engagement acceptance requirements, more defined management and practitioner responsibilities, a mandatory basis-of-accounting note, and updated documentation and reporting standards. The new report is called a Compilation Engagement Report.
Many stakeholders still use the former term, and existing statements may still bear that title. Understanding both terms prevents confusion when communicating with lenders, investors or other users.
What Is a Review Engagement?
A review engagement under CSRE 2400 (Canadian Standard on Review Engagements 2400) provides limited assurance. The practitioner is required to be independent of the entity. The practitioner's primary procedures are inquiry (asking management detailed questions) and analytical procedures (comparing current results to prior years, identifying unusual trends).
If the practitioner's work suggests material misstatement, additional procedures are performed. A review does not ordinarily involve external confirmations, inventory observation, or detailed transaction testing. However, when unusual matters or possible material misstatements are identified, additional procedures may be necessary.
The review concludes with a Report on Review Engagement expressing limited assurance that the financial statements are presented fairly.
What Is a Financial Statement Audit?
A financial statement audit provides reasonable assurance—though not absolute assurance, as no audit can detect every error or instance of fraud. The auditor assesses risks, understands relevant internal controls, and determines materiality.
Based on this assessment, the auditor performs extensive work: inspecting documents and supporting evidence, confirming balances with external parties (banks, suppliers, customers), observing physical inventory, recalculating amounts, performing analytical procedures, and testing a risk-based sample of transactions throughout the year. The auditor is required to be independent.
At the conclusion, the auditor issues an Independent Auditor's Report expressing an opinion on whether the financial statements present fairly, in all material respects, in accordance with the applicable financial reporting framework.
Compilation vs Review vs Audit Comparison
| Feature | Compilation | Review | Audit |
|---|---|---|---|
| Assurance Level | None | Limited | Reasonable |
| Main Procedures | Compile information; describe basis of accounting | Inquiry and analytical procedures; investigate unusual matters | Risk assessment; testing; confirmation; observation; sampling |
| Independence Required | Not generally; disclosure may be needed | Yes | Yes |
| Report Issued | Compilation Engagement Report | Report on Review Engagement | Independent Auditor's Report with Opinion |
| Opinion Provided | No | Limited assurance conclusion | Yes |
| Common Uses | Internal management; tax filing; smaller financing | Bank financing; investor review; government programs | Large financing; regulatory compliance; public reporting |
Audit-Ready vs Audited Financial Statements
"Audit-ready" does not mean "audited." Audit-ready is not a level of assurance. Audit-ready describes financial records and supporting schedules organized and prepared so that an independent auditor can perform their audit work efficiently. Only an independent auditor who completes an audit and issues an audit opinion has audited the statements.
Audit-ready records typically include:
- Trial balance and general ledger
- Bank and credit card reconciliations
- Accounts receivable and payable schedules
- Fixed-asset continuity schedules
- Loan agreements and payment terms
- Payroll reconciliations
- GST/HST and tax filings
- Related-party transaction detail
- Supporting documentation for significant estimates and assumptions
Audit-ready describes the quality and organization of evidence—not the assurance level.
How to Choose the Right Engagement
The right engagement depends on the intended use and the requirements of the end user:
- Corporate tax filing: Management-prepared statements or a compilation may be sufficient for CRA purposes. For year-end compliance obligations and deadlines, see our guide to Canadian tax deadlines and penalties.
- Internal management: A compilation is common for internal reporting and board-level decision-making.
- Bank financing: Many banks set their own requirements based on loan size, risk profile and industry. Some accept management-prepared statements; others require a review. Always ask the lender before beginning work.
- Investor due diligence or business acquisition: A review or audit is typically requested.
- Shareholder agreements: The agreement itself may specify the required assurance level.
- Government grants or funding: Regulatory requirements for the specific program determine the engagement level.
- Regulatory compliance (FINTRAC examinations): The assurance level of your financial statements affects FINTRAC examination scope and procedures. Audited statements create different control testing expectations than reviewed or compiled statements. See our FINTRAC examination readiness checklist for guidance on preparing documentation for compliance examinations.
- Contractual covenants: A financing agreement may specify that reviewed or audited statements are required.
Before engaging an accountant, obtain written confirmation from the intended user—lender, investor, regulator or shareholder—of what engagement is required. This single step prevents delays and unnecessary rework.
Financial Statement Considerations for MSBs and PSPs
Money services businesses and payment service providers face distinctive financial reporting challenges. These challenges also intersect with FINTRAC compliance obligations—financial reporting accuracy is tested during FINTRAC compliance examinations:
- Transaction volume vs revenue: Transaction volume may not align with recognised revenue due to processing delays and settlement cycles; FINTRAC requires reconciliation of transaction volume to reported revenue
- Foreign-exchange impacts: FX gains and losses are common and require careful treatment; documentation must support FINTRAC reporting
- Agent commissions: Must be traced and reconciled; commission detail is often examined for beneficial ownership and related-party disclosure
- Customer/end-user funds: Funds held temporarily require careful analysis of rights and control to determine accounting treatment; FINTRAC safeguarding obligations overlap with financial reporting treatment
- Related-party balances: Must be identified and disclosed; see our beneficial ownership verification guide for identification and disclosure requirements
- Virtual currency holdings: Present measurement and classification challenges depending on asset nature and applicable framework; FINTRAC reporting obligations vary by asset type
- Settlement balances and chargebacks: Create timing differences requiring explanation
- Multiple currency accounts: Require translation and reconciliation
- End-user fund safeguarding: For PSPs, safeguarding records are maintained separately and subject to regulatory requirements; safeguarding does not apply universally to all MSBs; safeguarding compliance and financial reporting must align
The treatment of these items may depend on contractual rights and obligations, principal-versus-agent assessment, fund control, applicable accounting framework, materiality, asset nature, and regulatory arrangements. A qualified accountant familiar with your specific business model is essential. Our AML program design services and independent compliance audits address the intersection of financial reporting and FINTRAC obligations.
Common Mistakes When Choosing an Engagement
- ❌ Ordering a compilation when the lender requires a review (discovered only after statements are submitted)
- ❌ Assuming a review provides the same level of confidence as an audit
- ❌ Calling management-prepared statements "compiled" without a formal CSRS 4200 engagement
- ❌ Waiting until the financing deadline to confirm what report is required
- ❌ Treating audit-ready statements as audited statements when an audit opinion is actually required
- ❌ Providing incomplete or unreconciled schedules to the accountant, forcing rework
Note: For regulated entities (MSBs, PSPs, FINTRAC-reporting entities), financial statement quality is tested during FINTRAC compliance examinations. Incomplete or unreconciled statements create examination deficiencies.
Practical Decision Checklist
Before engaging an accountant, answer these questions:
- ☐ Who will use the financial statements (lender, investor, management, regulator, shareholder)?
- ☐ What engagement does that party require?
- ☐ Is assurance required?
- ☐ Is practitioner independence required?
- ☐ Is there a contractual, lending or regulatory requirement specifying the engagement level?
- ☐ What accounting framework or basis should be used?
- ☐ What is the submission deadline?
- ☐ Are the company's records reconciled and complete?
- ☐ Will comparative figures be needed?
Final Takeaway
The choice between compilation, review and audit engagements reflects the level of assurance the intended user requires from the financial statements. A compilation provides no assurance and is appropriate for internal management reporting and straightforward tax filing. A review provides limited assurance suitable for many lending scenarios, investor reviews and partnership arrangements. An audit provides reasonable assurance for larger financing arrangements, regulatory compliance and public company reporting.
Audit-ready statements are simply records organized for audit—they are not audited. The business that confirms requirements with the intended user before engagement, provides complete and reconciled records promptly, and chooses the correct engagement level avoids delays, cost overruns and the frustration of rejected statements.
Frequently Asked Questions
Is a Notice to Reader still used in Canada?
What assurance does a compilation engagement provide?
What is the difference between a review and an audit?
Are audit-ready statements the same as audited statements?
Can a bank require reviewed or audited financial statements?
Official Standards and Further Reading
- CPA Canada — Professional Standards — CSRS 4200 (Compilation), CSRE 2400 (Review), and Canadian Auditing Standards
- Canada Revenue Agency — Corporate Tax Information — CRA guidance on filing requirements and tax compliance
- FINTRAC — Compliance Guidance — For MSBs and PSPs, financial reporting accuracy is examined during compliance reviews
ComplyFactor advises Canadian MSBs, PSPs, fintechs and other regulated businesses on financial reporting, compliance and assurance. Our advisors help businesses select the right engagement level for their intended users, support year-end financial statement preparation and tax compliance, and ensure financial reporting aligns with FINTRAC obligations.
