Why Client Accounting Systems Create Unnecessary Work
Client Accounting in Lettings: How It Actually Works
…and why most systems get it wrong
Most letting agents use a client accounting system every day.
They log in to the bank, their CRM, run bank receipts, payments, reconcile transactions, check statements and stay busy checking and double checking.
It works. It’s familiar. No one really questions it.
But here’s the problem.
Agents are too busy working around systems to question why.
Why so much of their daily workload exists in the first place.
Let’s start with the basics
When rent is paid, something very specific happens:
1. The tenant sends money to the client account
2. The bank receives the funds
At this point, the money is sitting in the bank… and your client accounting system doesn’t actually know about it yet.
So the next step is critical.
3. A person or system has to retrieve that transaction data from the bank
This might be a manual download
A file import
Or a scheduled sync
4. That data is then pulled into the client accounting system
This is where the link is created.
A person or process becomes the bridge between:
What’s happened in the bank
And what the system thinks has happened
From there:
5. The agent (or system) matches the transaction to a tenant
6. The agent reconciles it
7. Payments are then prepared and sent out
And then you wait for the bank to process…
That’s the standard flow across most platforms.
And on paper, it’s fine. You are coping. Just.
The bit no one really talks about
All of this happens after the money hits the bank.
That single detail is where most of the friction comes from.
Because once the funds have landed:
The system has to go and fetch them
The data has to be interpreted
Someone or something has to match it
And if anything doesn’t line up, it becomes a manual problem
This is why:
Reconciliation exists
Payment runs exist
Cut-off times exist
CSV uploads still exist in some cases
Payment delays still exist
None of these are “features”.
They’re workarounds.
Why reconciliation is still a thing
Reconciliation isn’t there because agents want it.
It exists because the system doesn’t know, with certainty, what the money is when it arrives.
So it has to:
Import
Try and make a match
Wait for confirmation
Then allow payments to be made
If something breaks in that chain, you end up:
Unreconciling
Reallocating
Double checking
Fixing mistakes after the fact
It’s not a user problem.
It’s a timing problem.
And as soon as you’ve finished, its all out of sync again!
The timing problem (this is the real issue)
Most systems sit on top of the bank, not inside it.
So they are always playing catch-up.
They only know about money sometime after it arrives.
Which means everything else happens later:
Allocation
Reconciliation
Payment preparation
Statement generation
Funds moving from bank to bank
That delay might be minutes, hours or days depending on the setup.
But traditionally - it’s always there.
What happens when you remove that delay
If you flip the model and process money at the point it hits the bank, everything changes.
Instead of:
Receiving money → then working out what it is
You get:
Money arrives → already identified, allocated and reconciled 24/7
Which means:
No reconciliation step
No payment runs
No waiting to “catch up”
Payments are ready immediately
Funds move instantly on your command
You’re not processing work after the event.
It’s already done.
The shift most agents haven’t seen yet
There is a different way of doing this.
One where:
The system is connected directly at bank level
Transactions are identified instantly
Allocation and reconciliation happen automatically
Payments are prepared in real time 24/7
So by the time you log in:
Everything is already done.
You’re not processing.
You’re approving.
The practical difference day to day
Instead of:
Logging in to start your accounting work
You log in to:
Review what’s already been prepared
Approve payments
Move on
No batching.
No chasing.
No end-of-day pressure to get payments out.
No system or bank enforced delays.
Just a clean, continuous flow.
So why isn’t everyone doing this?
Because almost all platforms were built around the older model.
They’ve layered automation on top of a process that still starts after the bank.
And once that foundation is in place, you can only ever get better at working around it.
So instead, the industry has accepted:
Reconciliation as normal
Payment runs as standard
Delays as unavoidable
Even though they’re not.
The simple way to sense check your current setup
Ask yourself:
Do we reconcile payments daily?
Do we run scheduled payment batches?
Do we ever have to fix or reallocate transactions?
Do landlords receive payments after the statements (or vice versa)?
Do you have to wait for the money to actually move?
If the answer is yes to any of these…
You’re working in a system that processes after the bank.
Final thought
Most client accounting systems aren’t broken.
They do what they were designed to do.
But they were designed around a model that creates work after money arrives.
Once you see that clearly, the question changes.
Ask yourself:
“Does our system work efficiently?”
Or
“Are we efficient at working around the system?”
Worth a quick sense check?
If you’re curious what client accounting looks like without reconciliation, payment runs or delays, it’s worth seeing how LettsPay handles it.
No overhaul. No disruption to your front office systems.
Just real time rent processing, working directly at bank level.
We process it. You approve it. Everyone gets paid instantly.
Book a demo and see the difference that embedded banking can make for you, your landlords and teams.
We do the processing, you do the approving.
