The numbers come from the ledger. The exceptions are what the client is actually paying for. The narrative is what makes them read it. Only two of the three are worth automating.
Key takeaways
Build it in three layers and be strict about which is which. Layer one is the numbers, and they come from the accounting system unaltered — a reporting pack whose figures were produced by a language model is not a reporting pack, it is a liability. Layer two is exceptions: the things that changed, crossed a line or stopped happening. Layer three is the narrative that says what the exceptions mean and what to do about them.
Almost every firm builds layer one well and layers two and three inconsistently, because two and three take judgment and time. That is precisely the shape of work worth automating the assembly of — a model can produce the exception list and a first narrative draft in the time it takes to export the trial balance, and the accountant spends their hour on the part that needed them.
Pull them, do not generate them. Canadian cloud ledgers are built for this; Xero’s Canadian product page describes running customised reports for insight into the business and generating reports to file GST/HST or provincial sales tax — their own description of the capability is the right reference point for what the software does, as distinct from what anyone claims it saves.
The rule to write into your process is that no figure in the pack may originate outside the ledger. If a number needs a calculation, the calculation lives in a spreadsheet or a report definition that a person can inspect, not in a prompt.
Exception detection is where the pack earns its fee, and two of the most valuable monitors are set out numerically in federal law, which makes them easy to encode and hard to argue with.
The small supplier threshold. Subsection 148(1) of the Excise Tax Act makes a person a small supplier throughout a particular calendar quarter and the first month following it where the total consideration for taxable supplies that became due, or was paid without having become due, in the four calendar quarters immediately preceding does not exceed $30,000 — or $50,000 where the person is a public service body — subject to the exclusions the subsection sets out. That is a rolling four-quarter measure, not a calendar-year one, which is exactly the sort of thing a monthly automated check should be watching and a busy client will not be.
The registration that follows. Subsection 240(1) of the same Act requires every person who makes a taxable supply in Canada in the course of a commercial activity to be registered, except where the person is a small supplier, where their only commercial activity is making supplies of real property by way of sale otherwise than in the course of a business, or where they are a non-resident not carrying on business in Canada. So the threshold monitor is not trivia: crossing it changes what the client is legally required to do.
Tax shown on documents. Section 223 of the Act requires a registrant making a taxable supply other than a zero-rated supply to indicate to the recipient, in the prescribed manner or in the invoice, receipt or written agreement, either the consideration and the tax payable in a manner clearly indicating the amount of the tax, or that the amount payable includes the tax. A monthly sample of the client’s outgoing invoices against that requirement is a small check that prevents an expensive conversation.
Other exceptions are firm-specific and equally automatable: a customer who has stopped ordering, a supplier price that moved, a payroll remittance that changed shape, a bank balance trending toward a covenant. Write the rule once, run it every month, and let the model explain what it found rather than decide whether it matters.
This one catches out otherwise careful packs. Subsection 165(1) of the Excise Tax Act imposes tax on a taxable supply made in Canada at the rate of 5% on the value of the consideration — that number is in the Act and you can quote it. Subsection 165(2) imposes the additional tax in a participating province “at the tax rate for that province”, and that rate is not stated in the section; it is prescribed elsewhere. Subsection 165(3) sets the rate for a zero-rated supply at 0%.
The practical rule: quote 5% federally with the citation, and for any participating-province rate direct the reader to confirm the current rate with the Canada Revenue Agency for the province in question rather than printing a number from memory into a client document. Where a client is already in dispute, Treadstone Law’s note on whether CRA can reassess HST/GST separately from income tax is a useful primer on why the two streams need separate attention in the pack.
The narrative is where a model is genuinely good: turning an exception list into three paragraphs a business owner will read. Give it the exceptions, the prior month’s narrative and the client’s sector, and require it to write only about exceptions on the list.
Then take two things off it. It does not decide which exceptions make the pack, and it does not give advice. An observation takes the form "receivables over 90 days rose for the third month". Advice is what you do about it, and that is the accountant’s to give and to sign.
A reporting pack is a management report. The moment it starts to look like financial statements you prepared for the client, you are into different territory: the AASB’s Other Canadian Standards are where the Canadian Standards on Related Services live, and what you may attach to a set of figures depends on which engagement you are in. Decide that deliberately before you design the template, not after a client forwards the pack to a lender.
The pack becomes part of the client’s record and of yours. Section 230 of the Income Tax Act requires every person carrying on business to keep records and books of account in a form that enables the taxes payable to be determined, with a general retention floor of six years from the end of the last taxation year to which they relate under paragraph 230(4)(b), and subsection 230(4.1) requiring electronic records to be retained in an electronically readable format. Treadstone Law’s note on corporate record retention in Ontario covers the broader corporate obligations that sit alongside it.
A bookkeeping and advisory practice serving forty owner-managed businesses replaces a hand-written commentary with a fixed exception ruleset and a drafted narrative. The rules include the rolling four-quarter revenue test above, receivables ageing, gross margin movement by more than a set band, and any month with no payroll remittance where there was one previously.
In the first quarter two clients trip the four-quarter test. Both are approaching the threshold rather than past it, which is the useful moment to raise it — the conversation happens before registration is required rather than after a CRA letter. Neither would have been caught by a human reading a monthly profit and loss.
Count packs delivered by the fifth working day, exceptions raised per client, and client questions arriving after the pack rather than before. All three are in the practice management system already.
Everything above is about delivering to a book of clients. Tightening your own firm’s month-end, reconciliations and payables is a separate job and it lives on the accounting automation page and the bookkeeping automation page.
How long should the pack be?
Short enough to read on a phone, with the detail attached rather than embedded. Most packs fail by being complete rather than by being wrong.
Can the client get it automatically?
The assembly can be automatic; the send should not be, until an accountant has cleared the exception list. An unreviewed exception sent to a client is a question you will answer twice.
What if the client’s bookkeeping is behind?
Then the pack reports that, as an exception, in the first line. A pack built on incomplete data and presented as complete is the one real failure mode of this whole process.
Does this work for a client on a desktop ledger?
Yes, with more friction — the exception rules need an export rather than a live connection. The rules themselves do not change, which is the point of writing them independently of the software.
A 30-minute call is enough to tell you whether AI pays for itself here.
