Your Clients Aren't Difficult But Your System Might Be

One of the most common things I hear from bookkeepers is some version of the same frustration.

"Why won't they just send what I've asked for?"

You've told them what you need. You've reminded them. You may have even written it all down in a checklist and sent it across. And still, every month, the same missing receipts, the same unanswered emails, the same last minute scramble to get what you need before the deadline.

It's exhausting. And it's easy, in those moments, to conclude that the client is the problem.

Usually, they're not.

The Curse of Knowledge

There's a concept worth understanding here, because once you see it you can't unsee it.

It's called the curse of knowledge. The idea is simple: once you understand something well, it becomes almost impossible to remember what it felt like not to understand it. You lose the ability to imagine the other person's experience, because your own knowledge has permanently replaced it.

As bookkeepers, we're swimming in this.

You know why you need that invoice. You know why the bank statement matters. You know what happens if a transaction is miscategorised or a submission is late. These things are so obvious to you that asking for them feels like the simplest request in the world.

To your client, it's admin. It's paperwork. It's something to deal with when they're less busy, which is never.

They're a plumber, a photographer, a driving instructor. Their real work isn't paperwork. If HMRC didn't require it, most of them wouldn't do any bookkeeping at all. That doesn't make them lazy or difficult. It makes them completely normal. And it means that if we want different behaviour, we have to build systems that account for who they actually are, not who we wish they were.

Tell Them Why, Not Just What

Most requests bookkeepers send to clients explain what is needed and nothing else.

"Can you send your bank statements by Friday?"

That lands as another task on a list that's already too long. It has no urgency, no context, no reason to be prioritised over everything else competing for attention that day.

A small change makes a significant difference.

"I need your bank statements so I can match every transaction and make sure everything reconciles. If anything's missing it could affect your tax return, which could mean paying more than you need to."

Same request. Same deadline. Completely different frame. Now it's not admin, it's protecting their money. Now there's a reason to act.

Adding the why to every request isn't about over-explaining yourself. It's about closing the gap between your knowledge and theirs. When clients understand why something matters, they treat it like it matters. When they don't, they treat it like it doesn't. That's not awkwardness. That's just how people work.

The System Problem

Here's the uncomfortable part.

If you're chasing the same clients for the same things every month, the system isn't working. Not because you don't have one, but because having a system and having one that delivers consistent outcomes are two different things.

A system that exists on paper but still leaves you firefighting every month isn't a system. It's a document.

The test of a system isn't whether it's written down. It's whether it changes behaviour. Whether clients know what's expected, when it's expected, and what happens if they don't deliver. Whether the friction is designed out rather than repeatedly absorbed.

Most bookkeeping practices have processes. Fewer have systems that actually enforce themselves.

The difference usually comes down to two things. First, whether expectations are set clearly enough at the start that clients know exactly how things work before the first piece of work is done. And second, whether there are real consequences when things go wrong, or whether the bookkeeper just absorbs the chaos and carries on.

If there are no consequences, there's no system. There's just hope.

What to Actually Fix

The things worth systemising are the ones you find yourself repeating. The same explanation sent to three different clients this month. The same reminder that goes out every quarter. The same conversation at onboarding that covers the same ground every time.

Turn the recurring explanation into a template that includes the why, not just the what. Record a short screen share showing clients how to get bank statements or upload documents to your portal. Build a welcome pack that sets out clearly what's needed, when, and why it matters. Use automated reminders so the prompt arrives before the deadline rather than after it.

None of this needs to be sophisticated. It just needs to exist and be used consistently.

But the most important thing to build in is a consequence. A submission deadline that actually means something. A policy that late paperwork moves to the next available slot. Something that makes the system real rather than advisory.

Because a system without a consequence is just a suggestion. And clients, like most people, respond to what's real.

The Actual Problem

The reason this matters is that the frustration most bookkeepers feel about client behaviour is largely self-inflicted. Not deliberately, but structurally.

When we ask without explaining, clients deprioritise. When we chase without consequence, clients learn that chasing is just part of the process. When we absorb the chaos every month without changing anything, we confirm that the chaos is acceptable.

The clients aren't broken.

But if the same problems keep arriving every month, something in the system is.

The good news is that unlike client personalities, which you can't change, systems are entirely within your control. Most of the friction that makes a bookkeeping practice feel harder than it should be isn't inevitable. It's designed in, usually by accident, and it can be designed out.

It just takes a decision to stop absorbing it and start fixing it.

Inside The Bookkeepers Alliance we help members build practices that run properly, from onboarding to client communication to the systems that make everything consistent. If you're ready to stop firefighting and start building, join us here.