Your Accounts Person Isn't the Problem. Your Process Is.
Every growing business has one.
The person who knows how everything works. Which supplier needs the PO number in the reference field. Which client always disputes the first invoice. How the job numbers link to the payroll codes. Where the spreadsheet lives that reconciles the thing the software doesn't handle properly.
They're usually excellent. They're usually loyal. And they're usually the reason your business functions.
They're also, quietly, one of your biggest risks.
The Test
Here's a simple one. If that person resigned tomorrow, how long would it take to replace what they know?
Not their job description, their actual knowledge. The workarounds, the exceptions, the small decisions made a hundred times a month that keep everything moving.
For most businesses in the $2–20 million range, the honest answer is somewhere between three months and "I genuinely don't know."
And it's not just resignation. It's annual leave. It's illness. It's the week they're flat out and something slips, and nobody notices until the BAS is due.
How Businesses End Up Here
Nobody designs this deliberately. It's the natural result of growth.
In the early days, the owner does the books. Then it gets too big, so someone is hired to help. That person learns by doing, figuring out what works, building workarounds for the gaps, developing their own way of handling things.
It works. The business grows. More volume, more complexity, more exceptions. Each one gets solved individually, in the moment, by the person in front of it.
Five years later you have a functioning accounts process that exists almost entirely inside one person's head. Nobody wrote it down, because there was never a day when writing it down was more urgent than the work itself.
This isn't a hiring mistake. It's what happens when a business grows faster than its systems.
The signs it's happening to you
It's rarely dramatic. It shows up in small things:
The same questions come to you repeatedly, and you answer them the same way each time
When your accounts person is away, things simply wait
Onboarding a new team member takes months, and mostly happens by shadowing
There are spreadsheets outside the accounting system that are critical to the process
Nobody's confident why something is done a particular way, only that it's always been done that way
Month-end takes longer than it should, and the reason is hard to articulate
Individually, minor. Together, they mean your finance function can't scale, and can't be handed over.
Documentation isn't the whole answer
The instinctive fix is: write it all down. Build a procedures manual. Get everything out of their head and onto paper.
Half right.
Most procedure manuals fail for the same reasons. They're written once, in a burst of effort, then never updated, so within six months they describe a process that no longer exists. They're written in too much detail to be usable, or too little to be useful. And critically, they document the current process rather than questioning whether it's the right one.
That last point matters most. If your process has accumulated five years of workarounds, documenting it faithfully just preserves the workarounds. You've made the inefficiency official.
A better sequence
The businesses that get this right tend to work in a different order.
First, map what actually happens. Not what's supposed to happen, what genuinely does, including the exceptions and manual steps. This is usually revealing on its own. Most owners are surprised how many touchpoints a single invoice passes through.
Second, question each step. Why does this exist? Is it a control, a habit, or a workaround for a problem that's since been fixed? A meaningful proportion of steps in a mature process are solving problems that no longer exist. Removing work beats documenting work.
Third, simplify before you document. Redesign the process so it's straightforward enough to be described briefly. If a procedure needs four pages to explain, the procedure is the problem, not the documentation.
Fourth, document the simplified version, and train to it. A document nobody's been walked through is a document nobody follows. Training is what turns a procedure into an actual standard.
Fifth, build in review. Processes drift. A short quarterly check on what's changed keeps documentation alive rather than archaeological.
What you get back
Businesses that do this properly usually report the same handful of outcomes.
Leave stops being a problem. Someone else can pick up the work because it's defined, not inherited.
New starters become useful in weeks, not months. Onboarding follows a path instead of relying on osmosis.
Your accounts person gets better work. This is the part people miss. Most good accounts people are frustrated by how much time goes on repetitive manual tasks. Streamlining doesn't threaten them, it frees them up for work they'd rather be doing. Handled well, this is a retention measure, not a restructure.
Month-end gets shorter and more predictable. Fewer exceptions, fewer handoffs, fewer things waiting on one person.
And you stop being the escalation point for questions that should never have reached you.
Where to start
You don't need to fix everything. Pick the one process that causes the most friction, usually accounts payable, payroll, or month-end close, and work through it properly.
One process, mapped, simplified, documented and trained, is worth more than a manual covering everything at a level nobody reads.
At Rise Finance, we work with established businesses to streamline their internal accounts processes and train their teams to run them confidently. If your finance function depends on one person's memory, let's talk about what it would take to change that.