When Having a Bookkeeper Isn't Enough

A bookkeeper handles transactions. That's enough when the business is small enough that transactions are the back-office. By around 10–15 staff, most Australian SMEs cross a threshold where the back-office becomes much more than transactions — and what's needed is no longer one role but a coordinated set of capabilities. The question isn't whether to keep the bookkeeper. It's what to add around them, and how to keep it from turning into the fragmented stack that costs more than it saves.

The point where one role stops being enough

For a 5-staff business, a competent bookkeeper covers the bulk of what "back-office" means: bank reconciliation, accounts payable, accounts receivable, basic reporting, BAS preparation. The owner handles HR because there's barely any. IT is a laptop and a Google Workspace subscription. Marketing is the owner's LinkedIn account and word-of-mouth.

This works. It works because the business is small enough that each function is genuinely small. The bookkeeper isn't doing the work of three people; they're doing the only work there is.

The threshold where it breaks is gradual rather than sudden, but the shape of the breaking is consistent:

• First staff member on a Modern Award introduces real payroll complexity the bookkeeper isn't trained for. Penalty rates. Allowance interpretation. Classification reviews.
• First difficult HR conversation — a performance issue, a casual conversion request, a termination — surfaces the fact that there's no HR competency in-house, and the bookkeeper isn't qualified to weigh in.
• First IT incident — a phishing attempt, a device theft, a backup failure — surfaces the absence of IT systems and security thinking that nobody's been doing.
• First time the cash flow becomes a strategic question rather than a counting exercise — usually around the time the business starts thinking about a hire that requires confidence in 90-day cash position — the bookkeeper's transaction-level view isn't enough; what's needed is a forecast, a model, a CFO conversation.
• First marketing decision that has to compound — a website redesign, a CRM implementation, a paid-acquisition channel — needs a competency the bookkeeper has never had.

Most owners hit two or three of these in the same six-month window. That's the threshold.

The default answer: add another provider

When the bookkeeper-only model breaks, the default answer in the Australian SME market is to add another provider. The HR question goes to an employment-law subscription. The IT incident gets a managed-services contract. The cash flow question goes to a fractional CFO. The marketing decision goes to an agency.

Within twelve months, the business has gone from one provider to five or six. Each was added in response to a specific need; none of them know about the others. The fragmented stack we've covered in the previous articles is what most growing Australian SMEs end up with — not because anyone chose it, but because each individual addition seemed like the obvious next step.

The default answer is the trap. It solves the immediate problem (the HR question gets answered) while creating a larger one (now there are five providers nobody is coordinating).

The other default: stretch the bookkeeper into roles they aren't

The second default is to ask the bookkeeper to absorb more of the back-office than the role is built for. "Can you handle the payroll setup?" — yes, but without award expertise. "Can you book the casual conversion paperwork?" — yes, but without HR judgement. "Can you do basic IT setup for the new hire?" — yes, but without security thinking.

Each of these stretches the bookkeeper into work they can technically execute but aren't trained for. It usually shows up later as a Fair Work investigation, an underpayment, a security incident, or an audit finding. The bookkeeper isn't at fault — they were doing what they were asked. The architecture was wrong.

What "enough" actually looks like at 15–30 staff

The honest answer to "what does an Australian SME's back-office need once it's outgrown the bookkeeper-only model" is something like this:

Seven capabilities — and the bookkeeper does only one of them well.

The wrong question is "which of these can we make the bookkeeper do?" The right question is "how do we get all of these capabilities to a fit-for-purpose standard, without ending up with seven separate vendors who don't talk to each other?"

Three structurally different answers

There are exactly three structural answers to that question, and which one is right depends on the business.

Answer 1 — In-house build. Hire a finance manager, an HR specialist, an IT admin, eventually a CFO. Build the team yourself. Works at scale; expensive at SME-sized scale; brutal to manage during ramp-up. Most relevant for businesses on a clear trajectory past 75–100 staff, where the costs are amortised across a larger base.

Answer 2 — Multi-vendor stack. What most businesses default into. Pick a best-of-breed provider for each function. Manage the coordination yourself. The pattern we've spent four articles documenting. Works in principle; in practice produces the fragmented stack with its 50–70% hidden cost.

Answer 3 — Integrated outsourced team. One team that delivers all seven capabilities under a single relationship, with the coordination already inside the team. Doesn't fit every business — there's a band (roughly 8–80 staff) where it's the structurally best answer; below 8 the integrated team is over-resourced for the need, above 80 the economics start favouring an in-house build.

There isn't a single right answer; there's a right answer per business. But the default — the multi-vendor stack — is rarely the right one, and is usually adopted by accident.

How to know which side you're on

Three signals that you've crossed the bookkeeper-only threshold (and are about to default into the multi-vendor stack if you don't actively choose otherwise):

1. Your bookkeeper has asked an HR / IT / cash flow / payroll-compliance question in the last 60 days that they couldn't answer themselves. The role has reached its functional limit.
2. You've added — or are about to add — at least one new provider that isn't the bookkeeper. The fragmentation is already starting.
3. You're the one answering cross-functional questions — the payroll question that needs HR input, the IT question that needs finance input. You've become the integration layer.

If two or three of those apply, you're at the inflection point. The decision that needs making isn't "should we add another provider" — it's "what shape of back-office do we want for the next stage of the business."

What this article is and isn't

This isn't an argument that bookkeepers should be replaced. A good bookkeeper is one of the highest-leverage relationships an SME has. The argument is that the bookkeeper alone is no longer enough past a certain stage — and the answer to what comes next is a structural decision, not a vendor-shopping exercise.

The wrong move is to keep adding providers reactively. The right move is to choose, deliberately, which of the three structural answers fits the business — and then build (or engage) for that answer.

What to do next

The fastest way to know which structural answer fits your business: the Business Health Check. Five minutes, no sales call. The output identifies which of the seven capabilities your business is meaningfully exposed on, and which structural answer is most likely the right fit at your stage.

If you want a longer conversation: book 20 minutes with a Trusted Advisor. They'll walk through your current structure honestly and tell you which model fits — including telling you when it isn't Valont.