Compilation Engagement (CSRS 4200)

CSRS 4200 stands for Canadian Standard on Related Services 4200, “Compilation Engagements.” It is issued by the Auditing and Assurance Standards Board (AASB) at CPA Canada, and it replaced the old “Notice to Reader” standard (Section 9200) for compiled financial information covering periods ending on or after December 14, 2021.

The practitioner takes information the client provides, the trial balance, the general ledger, the supporting schedules, and presents it as a set of financial statements. Under CSRS 4200 we do not verify the numbers, test transactions, or confirm balances with third parties. What the standard does require is more than the old Notice to Reader ever did:

• A basis of accounting note on the statements, describing the accounting framework used to prepare them.
• Knowledge of the client’s business sufficient to compile the information.
• A judgment call: if the compiled information appears false or misleading, we cannot simply issue the report.

The output is a formal compilation engagement report attached to the statements, which is the document that replaced the Notice to Reader wording most lenders and business owners grew up with.

This is the point where compilations get confused with work that carries far more weight, so we say it plainly. A compilation provides no assurance. Here is how the three engagement levels compare:

Most compilations we see are driven by a specific reader. A lender wants clean year-end statements before renewing a credit facility. An owner wants a tidy balance sheet and income statement to support a tax filing or a management review. A private company simply wants its books presented properly without paying for an audit it is not required to obtain.

On one engagement we ran a CSRS 4200 compilation for an insurance underwriter, producing a balance sheet, an income statement, and a statement of retained earnings addressed to management and the company’s lenders. That is the classic fit: a private business, a defined set of readers, and a need for credible statements rather than an audited opinion.

The most common surprise for a first-time compilation client is the basis of accounting note. If a reader of the statements cannot come back and ask us for more detail, the standard makes us describe the accounting basis carefully enough that they are not misled. That one requirement shapes how we scope the whole file.

A compilation is generally not the right tool for a public company’s continuous disclosure. Reporting issuers on the TSX Venture Exchange, the CSE, and similar markets file audited annual statements and reviewed interim statements, not compilations. If that is your world, the public company reporting work matters more than a compilation, and pieces like IFRS financial statement preparation and MD&A preparation are the standards you actually need to clear.

We start by asking who will read the statements and whether they can request more information from you. That answer drives the basis of accounting disclosure the standard demands. Then we build the file the same way our controllership team builds any month-end or year-end close: reconcile the accounts, review the general ledger for consistency, and present the statements in a format the reader will trust.

Because compilation work usually sits next to bookkeeping, controllership, and Office of the CFO support, we can keep the underlying records clean year-round so the compilation itself is fast at period-end. When a company later graduates to an audit or a review, that same discipline shortens the process, since the auditor is starting from organized, reconciled statements rather than a raw ledger. For public filers we support the SEDAR+ filing and reporting workflow separately, and we keep the two streams clearly distinct so no one mistakes a compilation for an assurance product.