Treadstone Associates
Article · Compilation

Can AI be used in a compilation engagement?

Yes, on the assembly. The standard's requirements for knowledge of the business, documentation and the practitioner's own stand-back are unchanged by the presence of a tool, and they are the whole engagement.

Treadstone Associates · Updated 2026

Key takeaways

  • • CSRS 4200 replaced Section 9200 and AuG-5 and took effect for compiled financial information for periods ending on or after 14 December 2021 — per the AASB's own project record.
  • • The standard added specific required work effort and documentation, engagement-acceptance considerations where a third party will use the information, and a required note describing the basis of accounting.
  • • A compilation is a related services engagement, so the firm's system of quality management under CSQM 1 already applies to it — including the technology requirement in paragraph 32(f).
  • • AI can assemble, reconcile and draft. It cannot hold knowledge of the client's business, and it cannot be the practitioner who declines to be associated with information that is misleading.

The short answer

AI can be used inside a compilation engagement, and the interesting question is where. A compilation is an assembly exercise: management's figures, arranged into financial information, with a report that says plainly what was and was not done. The assembly — pulling trial balances, mapping accounts, reconciling to source, drafting the note that describes the basis of accounting — is mechanical enough that a tool can carry a lot of it. The parts that are not mechanical are the parts the standard actually cares about.

Those parts are knowledge of the client's business and operations, the judgment about whether it is appropriate to accept or continue the engagement, and the practitioner's own stand-back at the end. None of those move to software, and each of them is where a compilation goes wrong when it goes wrong.

What CSRS 4200 actually changed

This matters because a lot of firms are still running a Notice to Reader mental model. The AASB approved Canadian Standard on Related Services (CSRS) 4200, Compilation Engagements in October 2019 to replace Section 9200 and Assurance and Related Services Guideline (AuG) 5, and it took effect for compiled financial information for periods ending on or after 14 December 2021, with early application permitted. The Board's own summary of what the new standard introduced lists the features that bear directly on whether a tool can help:

  • • A clarified scope that distinguishes a bookkeeping service from a compilation engagement — system-generated financial information is outside the standard if no communication is included or attached to it.
  • • Specific engagement-acceptance considerations that apply when the compiled financial information is intended to be used by a third party.
  • • Specific required work effort and documentation, where previously the lack of guidance produced variability in practice.
  • • A requirement that the compiled financial information include a note describing the basis of accounting applied.
  • • A compilation engagement report that is more informative than the old Notice to Reader, because users were unclear about the extent of the practitioner's work.

Two of those five are where AI is genuinely useful, and one is where it is genuinely dangerous. The documentation requirement and the basis-of-accounting note are drafting and consistency tasks. The third-party-user acceptance judgment is not.

The scope trap, sharpened by automation

The clarified scope creates a practical problem that automation makes worse rather than better. If a bookkeeping service produces system-generated financial information and nothing is attached to it, it is outside CSRS 4200. Attach a communication and it is not. A firm that has automated its month-end output and emails clients a tidy statement pack every quarter has, without anyone deciding to, moved a service across that boundary.

The fix is not technical. It is that someone in the firm has to own the question of what is being sent, with what attached, to whom. Build the automation so that anything leaving the firm passes a named person who knows which engagement it belongs to.

CSQM 1 already covers your tool

Practitioners sometimes assume quality management standards are an audit concern. They are not. The AASB's effective-dates record for Other Canadian Standards states that systems of quality management complying with CSQM 1 were required to be designed and implemented for related services engagements by 15 December 2023, with the evaluation of the system required within one year after that date, and that CSQM 2, Engagement Quality Reviews, is effective for related services engagements beginning on or after 15 December 2023. A compilation is a related services engagement.

What that means concretely is set out in the AASB's own summary of its Canadian Technology Quality Management roundtable, which quotes the operative requirement: CSQM 1 paragraph 32(f) requires a firm to establish the quality objective that “appropriate technological resources are obtained or developed, implemented, maintained, and used, to enable the operation of the firm's system of quality management and the performance of engagements”. That is not aspirational language. If you buy a tool that touches compilation files, the obligation to be able to say why it is appropriate, and to keep it appropriate as it changes, is already yours.

The same summary records how firms are meeting that obligation today: human involvement at critical points, centralised certification of firm-level tools, validation of inputs and outputs for engagement-level tools, risk-based testing with baseline testing for all tools and more for higher-risk ones, limits on how tools can be used in engagement files, and mandatory training before staff may use them. For a small practice, the scalable version of that list is short but it is not empty.

Where AI fits, task by task

  • • Mapping and reconciliation. Matching a client trial balance to the firm's standard chart and flagging accounts that moved category since last period. Output is an exceptions list.
  • • Prior-period consistency. Comparing this period's compiled information against last period's and listing what changed in presentation rather than in substance.
  • • Drafting the basis of accounting note. The note is required; its wording is largely stable between periods and between similar clients. A draft, then a practitioner who confirms it is true of this client.
  • • Documentation completeness. Checking the file contains the items the firm's own programme says a CSRS 4200 file must contain, before it reaches review.

Where it does not fit

Knowledge of the entity's business and operations is a person's knowledge. So is the decision about whether to accept or continue an engagement whose output a lender will rely on. And so is the moment at the end where a practitioner considers whether the information is misleading and declines to be associated with it. A model has no standing to decline anything; the firm's name is on the report.

That last point has a legal edge worth knowing about. Treadstone Law's note on what it means when financial statements were never reviewed by an accountant sets out how a buyer's counsel reads a compiled statement pack, and its explanation of what a claimant must prove in a professional negligence claim against an accountant in Ontario is the other half of the picture.

Worked example (illustrative)

A two-partner firm in Manitoba compiles roughly 140 owner-managed year-ends. It introduces a tool that maps client trial balances to its standard chart and drafts the basis-of-accounting note. In the first quarter the tool produces clean mappings on files where the client uses a mainstream bookkeeping package and poor mappings on files where the client has invented account names.

The firm's response is the right one: it does not turn the tool off, and it does not trust it evenly. It records which client files it certified the tool for, requires a mapping sign-off on the others, and adds the tool to its quality management documentation so that the ‘appropriate technological resources’ objective has an answer behind it. The countable measure is the number of mapping corrections at review, per file, before and after.

Questions we get asked

Does a compilation need a quality management system at all?
Yes. The AASB's effective-dates record puts related services engagements inside CSQM 1 and CSQM 2, on the dates set out above.

Do I have to tell the client I used AI?
CSRS 4200 does not require it. Your engagement letter and your own confidentiality obligations may, particularly if client data leaves your tenancy. Decide it at the firm level rather than per file.

Is a compilation report an assurance report?
No, and that distinction is precisely what the redesigned report was meant to make clearer to users, per the AASB's summary of the change.

See where AI pays off first in your firm.

A 30-minute call is enough to tell you whether AI pays for itself here.