Almost every number a brokerage wants in a monthly report already exists somewhere — in the trade record sheets, the trust ledger, the deal files and the registration records. What is missing is assembly, and assembly is the part software does well. The mistake is treating reporting as purely internal. A brokerage in Ontario also owes RECO a set of notices on fixed deadlines, and those are reports too. Build one dashboard that carries both, and the deadline-driven half stops depending on somebody remembering.
Key takeaways
Start by separating two things that get lumped together. The first is management reporting: listings taken, deals closed, average days on market for your own files, remuneration receivable, agent activity, trust balances. These are questions about data you already hold, and a script plus a language model will assemble them into a readable monthly pack faster than a person will. The second is regulatory reporting: the notices a brokerage is required to give the regulator, on the regulator’s clock. Those cannot be generated retrospectively at month end, because the deadline has usually already passed by then.
RECO’s notice bulletin sets out the events that start a clock. Every brokerage must, within five (5) days after the event, provide notice to RECO of any change in the brokerage’s address for service, and a brokerage must also notify RECO if the broker of record changes, within five days of the change. A brokerage that initiates the termination of an agent’s employment must give the agent written notice including the date the termination takes effect, and forward a copy of that notice to RECO within five days after the termination takes effect. Share movements run on a different clock: a corporate brokerage must notify RECO in writing within 30 days after the issue or transfer of any equity shares where the result is a person, or associated persons, acquiring or accumulating beneficial ownership or control of 10 per cent or more of the total number of equity shares.
None of that is analysis. It is event detection — something changed in a system you already run, and a notice is now due. That is precisely the kind of rule a workflow tool enforces reliably and a person enforces unreliably, because the person only sees it if they happen to be looking. The underlying duty is not negotiable: RECO’s conduct bulletin is blunt that a brokerage and its agents must comply with TRESA and its regulations, as well as other laws applicable to trading in real estate, and that not knowing what the legislation requires is not an answer.
Trust reporting has the shortest fuse in the whole set. If a brokerage determines there is a shortfall in its real estate trust account, RECO’s bulletin requires the brokerage to immediately notify RECO of the shortfall and deposit sufficient funds in the account to eliminate it. There is one narrow relief: where the shortfall results from financial institution service fees, the brokerage is not required to notify RECO as long as the shortfall is eliminated as soon as it is discovered. The same bulletin treats non-money property the same way — a brokerage must keep a written record of property received in trust, and if property goes missing must immediately notify RECO and replace it.
A daily reconciliation job that compares the bank position against the trust ledger and raises an exception the moment they diverge is not clever technology. It is a scheduled query. But it turns “immediately” from an aspiration into something the brokerage can actually meet, and it produces the evidence trail as a by-product.
The second trust report is slower but easier to forget. All unclaimed money held in trust for more than two years must be paid to RECO, though if the amount is less than $25.00 the brokerage is not required to forward the money. When it is forwarded, the brokerage sends the trade record sheet related to the transaction, a copy of the relevant trust account transaction records, and proof of unsuccessful attempts to contact the entitled person during the two-year period — postmarked returned envelopes being the example RECO gives. A report that ages unclaimed balances and starts collecting the contact-attempt evidence at month one, rather than month twenty-three, is worth building.
A monthly brokerage pack, split by who has to sign it
Assembled by software, reviewed by a person. Deal counts, remuneration receivable and aged, listings taken and expired, days on market across your own closed files, agent activity, commission splits, marketing spend against deals sourced.
Assembled by software, escalated immediately. Trust reconciliation exceptions, aged unclaimed trust balances approaching two years, deposits not yet reconciled.
Triggered by an event, not by the calendar. Broker of record change, address for service change, agent termination, equity share movements crossing the 10 per cent threshold.
Never generated. Any narrative claim about the brokerage’s performance that will be used in advertising. That is a separate regime with its own content requirements, and it needs a source for every figure.
A language model reading a well-structured ledger will write a competent commentary: what moved, by how much, and which files are the outliers. It should not be the thing that decides whether a number is right. BCFSA’s guideline for real estate licensees puts it plainly — AI tools are designed to “guess” answers to questions they do not have complete information on and may end up telling you something that is not correct, and using AI does not exempt you from your legal and ethical obligations. CREA reaches the same place nationally: a REALTOR® is generally responsible for inaccurate information generated by AI and should independently verify AI-generated information before relying on it or sharing it.
The practical control is provenance. Every figure in the pack carries the query or the record it came from, so a reviewer can trace it in one click. Anything the model wrote that is not traceable to a record is commentary and is labelled as such. BCFSA also expects the supervision layer to be real: it tells managing brokers to continuously monitor how AI tools are being used by your licensees and regularly review AI-generated content to ensure it aligns with brokerage policies and maintains accuracy.
The following is illustrative — a composite of how the workflow is usually assembled, not a measured result.
A twenty-agent Ontario brokerage runs its deals in one system and its trust accounting in another. Two scheduled jobs run nightly. The first pulls trust balances and bank positions and writes an exception row wherever they differ by more than rounding; the exception goes straight to the broker of record by email, because the shortfall duty is immediate. The second ages every unclaimed trust balance and flags anything past eighteen months, which is when the brokerage starts its documented attempts to locate the person entitled so the two-year evidence file is complete before it is needed.
A third job runs monthly. It assembles the management pack from the deal system, and an assistant drafts a page of commentary against it — which segments moved, which agents’ pipelines thinned, which listings expired without a price change. The broker of record reads the commentary, strikes the two sentences that overreach, and signs. Separately, a small watcher sits on the registration records: if the broker of record field, the address for service, or the shareholder register changes, it opens a task with the deadline already calculated. Nobody has to remember that five days is five days.
It can read the feed; it should not be the only thing that reconciles it. Keep the arithmetic in the accounting system, where it is auditable, and use the model for the narrative and the exception triage. A reconciliation that exists only inside a chat transcript is not a record you can hand to a regulator.
For tax purposes the federal floor is long. The Income Tax Act requires a person keeping records 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, and where they are kept electronically to retain them in an electronically readable format for that period. Our sister firm sets out the wider retention picture in its guide to how long an Ontario corporation must keep its records.
A person, always. The dashboard removes the excuse of not knowing; it does not remove the obligation, and it cannot exercise the judgment that a broker of record is registered to exercise. Treat it the way you would treat a smoke alarm: extremely useful, and not a fire plan.
Owner-facing reporting works the same way but answers to a different reader — see automating monthly owner reports. If the blocker is that your data sits in three systems that do not talk, start with adding AI to the software you already run.
A 30-minute call is enough to tell you whether AI pays for itself here.
