An owner statement is assembly, not analysis: rent charged, rent received, arrears, expenses, trust position, work completed, what is coming. Every one of those already exists in a system, which is why this is one of the easiest wins in property management. The two things to get right are provenance — every figure traceable to the record it came from — and retention, because the records behind the statement have a statutory life of six years.
Key takeaways
Owner reporting fails for boring reasons: the data lives in three systems, the person who assembles it does so by hand at month end, and the narrative gets written last and fastest. Automation fixes the first two directly. It also improves the third, because a language model reading a clean ledger writes a serviceable first draft of “what happened this month” — which is exactly the part a busy manager rushes.
The retention obligation is the reason to hold the underlying data properly rather than as spreadsheet exports. The Income Tax Act requires every person carrying on business to keep records and books of account at the person’s place of business or residence in Canada, in such form and containing such information as will enable the taxes payable to be determined, and to retain them until the expiration of six years from the end of the last taxation year to which the records and books of account relate. Where they are kept electronically, they must be retained in an electronically readable format for that period. The GST/HST side mirrors it: a person carrying on a commercial activity must keep all records that are necessary to enable the determination of the person’s liabilities and obligations and retain them until the expiration of six years after the end of the year to which they relate, again in an electronically readable format where kept electronically.
Six years of electronically readable records is a design constraint, not a filing habit. It rules out a reporting stack that depends on a chat transcript, a personal drive, or a report format that cannot be regenerated once the vendor changes their template. Our sister firm covers the wider picture in its guide to how long an Ontario corporation must keep its records, and the tax treatment the statement ultimately feeds in how rental income from an Ontario property is taxed.
If the manager is an Ontario real estate brokerage holding money in trust, the reporting question is not only monthly. RECO’s bulletin requires that where a brokerage determines there is a shortfall in its real estate trust account, it must immediately notify RECO of the shortfall and deposit sufficient funds in the account to eliminate it, with a narrow exception where the shortfall results from financial institution service fees and is eliminated as soon as it is discovered. Separately, all unclaimed money held in trust for more than two years must be paid to RECO, though amounts under $25.00 are not required to be forwarded.
A nightly reconciliation exception is therefore worth more than a prettier statement. Owners see the monthly pack; the regulator sees whether the trust position was right on the day it went wrong.
A monthly owner pack that assembles itself
Money in. Rent charged versus received per unit, arrears aged, deposits held, interest where applicable.
Money out. Expenses by category with the supplier invoice attached to each line, recoverable versus non-recoverable, capital versus repair.
Work. Work orders opened, closed, outstanding, with the ones that ran past target flagged and explained.
Position and outlook. Occupancy, upcoming lease events, planned works and their estimated cost, anything that will change next month’s number.
Commentary. Drafted from the above, reviewed line by line, signed by a named person.
The single control that makes generated reporting safe is that every figure carries its source. Practically: each number links to the query, the ledger account or the invoice behind it, and any sentence the model wrote that is not traceable to a record is labelled commentary. That is also the shape of the Privacy Commissioner’s expectation where automated systems feed decisions — organisations should maintain adequate records to allow for requests for access to information about that decision to be meaningfully fulfilled, and should ensure that system outputs that could have a significant impact on an individual or group are meaningfully identified as being created by a generative AI tool. Accountability sits with the organisation: parties should recognize that they are responsible for compliance with privacy legislation, and should be able to demonstrate this compliance.
It is worth being explicit about what nobody should automate: a recommendation to an owner about whether to sell, refinance, or spend capital. That is advice, and if it turns out badly the question asked afterwards is who gave it. Our sister firm covers the exposure directly in when a property manager can be sued for negligent management.
If the portfolio includes condominium management, the reporting audience is a board rather than an individual owner, the money is the corporation’s, and the manager is licensed. The differences run deeper than formatting — our sister firm explains how condominium manager licensing works in Ontario and what a condominium management company is responsible for. Build the reporting template against that reality rather than adapting a residential landlord pack.
The following is illustrative — a composite of how the workflow is usually assembled, not a measured result.
A manager with 180 units across 40 owners runs the pack on the second working day of the month. A scheduled job pulls the rent roll, the bank feed, the payables ledger and the work order system, reconciles them, and writes one row per unit with a source reference on every figure. Anything that fails to reconcile does not go into a report — it opens an exception and the pack for that owner is held.
An assistant then drafts a page per owner: what changed, which units are in arrears and for how long, which jobs are open past target and why, and what is scheduled next month. The manager reads all forty in about an hour, rewrites the three that involve a judgment call, and releases them. The invoices are attached to their own lines, so the owner asking “what was this $840?” clicks rather than emails.
The saving is not the writing. It is that the reconciliation happened before the report existed, so the manager spends her hour on the exceptions rather than on assembly.
Keep the arithmetic in the accounting system, where it is auditable and where the trail survives a software change. Use the model for narrative, variance explanation and exception triage. A statement that can only be reproduced by re-running a prompt is not a record.
Enough that the owner can answer their own questions without emailing, which usually means line-level expenses with documents attached and unit-level arrears. Summary-only reporting generates more work than it saves, because every summary produces a follow-up.
That is where automation earns its keep — once the data is structured, a second layout is configuration rather than a second month-end. It is also the reason to resist building the report as a hand-formatted spreadsheet in the first place.
The two inputs that most often hold up an owner pack are utility invoices and arrears — see processing utility bills across a portfolio and following up on rent arrears politely.
A 30-minute call is enough to tell you whether AI pays for itself here.
