Client money · Remittances · Period lock
You hold other people's money, and you have to prove what happened to it.
Rent in, fees out, deductions applied, remittance sent. Every step of that is somebody else's money passing through your account, and every step has to be reconstructable years later.
Beat 1 · Your week now
Money moves, and the explanation lives in three places.
Rent lands in a client account. Some of it is yours, most of it is not. Fees come off, recurring deductions apply, a remittance goes to the landlord, and a statement gets produced — usually with a spreadsheet doing the part the accounting package won't.
It reconciles. It reconciles because somebody knows how it reconciles, and that somebody is holding several conventions in their head that were never written down.
Beat 2 · What breaks
Client money, remittances, and an audit you can't reconstruct.
A client-money audit does not ask whether the maths worked. It asks you to show, for a specific date, which funds were whose, what was deducted and why, what was remitted and when — and to show the same figures again from a different direction.
The spreadsheet cannot do that, because it has been edited since. The accounting package cannot do it either, because it recorded the totals rather than the reasoning. And the person who knew the conventions has moved on.
- A deduction applied by a convention nobody documented
- A remittance whose supporting detail lives in a deleted email
- A closed period that somebody edited afterwards, in good faith
- Two systems that agree on the total and disagree on the composition
Beat 3 · Why your current tools can't fix it
General accounting isn't client accounting.
An accounting package is built for one entity's books. Client money is the opposite problem: many landlords' funds moving through one account, each with their own fees, deductions and statements, and a legal obligation to keep them separable at every moment.
Bolting that onto general ledger software means the separation lives in a naming convention and a spreadsheet — which is exactly the part an auditor will test, and exactly the part that cannot survive being tested.
Beat 4 · What changes
The reasoning is stored, not just the totals.
Remittances, fees and recurring deductions are modelled as what they are, so a statement can be produced from the underlying events rather than reconstructed from a balance. Bank transactions are matched against expected rent by a scoring engine, with anything uncertain queued for a human rather than guessed.
When a period closes it locks. If a property's ownership arrangement changes in a way that would split its accounting history, the system warns before it happens rather than after.
- Client money, remittances, fees and recurring deductions modelled explicitly
- Open banking feeds reconciled against expected rent, not just listed
- Period lock when the books close
- Accountant access by invitation, revocable, with SA105 and CT600 output
What ships today
The parts that do the work.
Client money, properly separated.
Landlord remittances, agency fees and recurring deductions handled as first-class objects, so statements come from events rather than from a balance.
Explore furtherReconciliation, not just a feed.
Transactions scored against expected rent periods — auto-matched above confidence, everything else queued with suggestions rather than guessed.
Explore furtherThe period locks.
When the books close they stay closed, and a change that would split a property's accounting history is flagged before it is made, not discovered later.
Explore furtherYour accountant, invited in.
Scoped access to the client's books, revocable at any time, with the SA105 pack and quarterly digital records ready to hand over.
Explore furtherFor managing agents across England — customer stories will appear here when there are real ones to tell
Show the auditor the trail, not the spreadsheet that survived.
See what it costs at your portfolio size.