Every licensed real estate agency in Australia runs a trust account, and every trust account is a compliance test waiting to happen. The money belongs to buyers, sellers, landlords and tenants, so the rules around it are unforgiving. A single unreconciled month, a receipt applied to the wrong ledger, or one client balance quietly slipping into deficit can trigger a please-explain from the regulator, a qualified audit, or the loss of a licence. Most agencies still check their trust accounts by hand, which means the quality of the check depends on how much time the bookkeeper has on the last Friday of the month.
What trust account compliance actually requires
The detail varies by state, but the shape is consistent. In New South Wales the Property and Stock Agents Act sets the trust account rules; in Victoria it is the Estate Agents Act and Consumer Affairs Victoria; in Queensland it is the Agents Financial Administration Act. Across all of them, an agency has to reconcile its trust account every month and submit to an annual audit. The recurring checks that matter are:
Monthly reconciliation: the trust ledger, the cash book and the bank statement have to agree to the cent, usually within a set number of business days after month end.
Receipting discipline: every deposit recorded promptly, against the correct trust account and the correct client ledger, with no funds parked in the wrong place.
No overdrawn ledgers: an individual client ledger can never go into deficit, even when the account as a whole is in surplus.
Retention and audit trail: records kept for the period your state requires, often seven years, and ready for the annual auditor.
Authorised disbursements: money only leaves the account for a permitted purpose, with the right authority behind it.
Where the manual process breaks down
None of these checks is hard on its own. The problem is volume and timing. A busy rent roll can generate hundreds of receipts and disbursements a month, and the reconciliation has to be finished in a tight window while the same people are also settling sales and chasing arrears. That is exactly when a transposed figure, a receipt keyed to the wrong ledger, or a duplicated receipt number slips through. The error is usually small. The consequence, if the auditor finds it before you do, is not.
What Claude can check, and what it can't
Claude is well suited to the reading-and-flagging part of this work. Give it the month-end reconciliation report, the trust ledger export and the bank statement, and it can compare them line by line far faster than a person, without getting tired at entry four hundred. Concretely, it can:
Compare the closing trust ledger balance against the reconciled bank balance and flag any variance.
Scan every individual client ledger for a negative balance.
Confirm each receipt has a matching ledger entry, and catch duplicated or missing receipt numbers.
Flag disbursements that fall outside your normal pattern for a human to look at twice.
Draft a plain-English exception note that your bookkeeper or auditor can act on directly.
What it does not do is sign the audit, make the legal call, or touch your banking. The licensed agent remains responsible for the account, and the registered auditor still does the audit. Claude is a fast, consistent first pass that catches the obvious before it reaches the person whose judgement actually carries the weight.
A worked example
Take a mid-sized agency in Parramatta running roughly 600 managements. In one month-end review, Claude compared the ledger export against the bank reconciliation and flagged two things a rushed manual check had missed: a $4,200 rental bond receipt applied to the wrong owner ledger, and one client ledger sitting $180 in deficit after a disbursement went out a day before the matching funds cleared. Both were fixed before the month was locked. Neither was fraud. But an overdrawn client ledger is precisely the kind of finding that turns a clean annual audit into a qualified one, and serious breaches of the trust account rules can carry penalties of $45,000 or more, plus the reputational cost of a Fair Trading investigation.
Setting this up without creating a new privacy problem
Trust account data is sensitive, so the way you run these checks matters as much as the checks themselves. The goal is a review that never widens your privacy exposure. In practice that means:
Work from read-only exports, never a live banking connection.
Mask or strip the client personal details the check does not actually need.
Keep the review inside tooling your agency controls, consistent with your obligations under the Privacy Act.
Log every check that runs, so the auditor can see what was examined and when.
Set up this way, the AI layer sees numbers and reference codes, not a pile of identifiable client files, and every run leaves its own audit trail.
What this is worth
For a mid-sized agency, a careful monthly reconciliation review can absorb the better part of a senior bookkeeper's day. Across a year that is easily $18,000 in salary time spent on a task that is mostly comparison and pattern-matching. Shifting the first pass to Claude does not remove the bookkeeper, it gives them a checked starting point and their afternoon back. The larger saving is quieter: fewer qualified audits, fewer nervous conversations with the regulator, and a trust account you can defend on any given day rather than only at audit time.
If you run trust accounts and want a consistent second set of eyes on every reconciliation, we help Australian agencies design AI-assisted checks that respect both the audit and the Privacy Act. You can book a short call to talk through what a safe setup looks like for your agency.
