Every finance office has one. She (or he) is the person who knows that the supplier export has to be opened in a text editor before it will import, that the month-end journal only balances if the credit note from the second branch is entered first, and that one customer's statement must be adjusted by hand because the system rounds it differently. None of this is written anywhere. It lives in a head, and the business runs on it.
This piece looks at what it costs a skilled bookkeeper to be the keeper of every workaround, and what a business can do to turn private tricks into shared, supported process. It is a hypothesis drawn from general research on job design and on how work is documented, not a finding about any particular South African firm, and the scenarios below are illustrative.
Expertise that looks like patching
There are two kinds of knowledge in a bookkeeping role. One is professional: understanding how revenue is recognised, what a reconciliation proves, when an accrual is justified. The other is local: how to coax this particular accounting package, this bank file format and this spreadsheet into producing a correct answer. The second kind is real skill, and it takes years to build. But it is skill in compensating for tools that do not fit the work, not skill in the profession itself.
Because the workarounds work, they are rarely questioned. The month closes, the reports go out and the owner is pleased. The cost is invisible because it is paid in the bookkeeper's attention and evenings, not in an invoice. The note on software workarounds replacing professional discretion describes the same pattern from the side of judgement: when the tool dictates the steps, the person stops deciding and starts complying.
Why the knowledge stays private
Workarounds stay in one person's head for ordinary reasons, not sinister ones.
- They grow one fix at a time. Each trick was a small answer to a Tuesday problem. Nobody ever sat down and designed the whole.
- Writing them down feels like admitting the system is broken. A bookkeeper who documents the tricks is also documenting that the tools are inadequate, which can feel like criticising a purchase someone else made.
- There is no time. The person with the knowledge is the person with the least slack, because they are the one holding everything together.
The Job Demands-Resources model, a widely used framework in occupational research, offers a way to see this. It treats a job as a balance between demands that drain energy and resources, such as autonomy, support and clear processes, that restore it. A role that depends on undocumented workarounds is heavy on demand and light on support. Its holder carries a load that nobody else can share, because nobody else can see it.
The human tax: dignity and cognitive load
The first cost is dignity. A qualified bookkeeper is trusted with the money of the business, yet spends part of every week performing manual rituals that a better-fitted tool would not require. The work they are proudest of, accurate and timely books, is invisible when it goes right. The work that is visible is the fixing. The companion article on best work that is invisible because it is repair work explores why this is so corrosive: the person is seen as reliable, not as skilled.
The second cost is cognitive load. Holding a long list of exceptions in memory is tiring in a particular way. The bookkeeper must remember not only the rules but the exceptions to the rules and the order in which to apply them, and a single slip can unbalance a month. The UK Health and Safety Executive's management standards for work-related stress list demands, control and support among the conditions that shape whether pressure becomes harmful. A job where demands are high, control over the tools is low and support is thin sits in exactly the place those standards warn about. See the HSE explanation of demands in the management standards for how the standard frames this.
An illustrative case
Imagine, as a hypothetical example, a Durban distribution business with forty staff and one bookkeeper who has been there eleven years. Orders come in through a web form, are re-captured into the accounting package, and are then matched to bank deposits by hand. The bookkeeper has a private checklist of nineteen steps for month-end, kept on a sticky note and in her memory. When she is unwell for three days in the last week of the month, the owner discovers that nobody can produce the VAT figures, and the temp who is brought in cannot get past step four.
The fragility was not her fault. It was the natural result of a tool that never fitted the work and a business that never asked what the work actually was.
Turning private tricks into shared process
The aim is not to make the bookkeeper redundant. It is to lift the workarounds out of one head so they can be examined, shared and, where possible, retired. Notice that the first step is documentation, not technology. The article on understanding how the work actually moves before automating makes the same point: automating a process nobody has described simply speeds up the confusion.
Practical next actions
- Ask the bookkeeper to list the workarounds, with credit. Frame it as capturing expertise, not auditing weakness. A one-hour conversation, recorded as a plain list, is a good start.
- Sort each workaround into three piles. Some exist because of a real accounting rule and should stay. Some exist because of a tool limitation and can be fixed with a setting or a better import. Some exist because of habit and can simply stop.
- Have someone else follow the list. Ask a colleague to run one month-end step using only the written notes. Every place they stumble is a missing detail.
- Cost the workarounds. Estimate the hours each one takes per month. Putting a number next to the sticky note makes the case for a fix far easier to make to an owner.
- Choose one to retire this quarter. Pick the most time-consuming workaround and ask the vendor, or an adviser, whether the package can do it natively. The questions to ask before buying another tool are a sensible checklist before spending money.
- Protect the person's time off. Once the steps are written down, schedule a deliberate handover test while the bookkeeper is present, so that a real absence is no longer a crisis.
The business outcome
A business that has documented its workarounds can close its books on time when one person is away, onboard a new colleague in days instead of months, and see which tool limitations are costing the most. It also reduces a quiet risk: the concentration of financial knowledge in a single person. If the workaround was also the only control catching an error, as is often the case, writing it down lets the business decide on purpose whether that control should remain. For a related look at how small entry mistakes cascade, see how one typing error becomes a disputed invoice.
The human dividend
The dividend here is predictability together with the restoration of dignity. Predictability means a month-end that does not depend on one person's memory, and a holiday that stays a holiday. Dignity means the bookkeeper's professional judgement is the thing the business values and uses, not her ability to survive a clumsy tool. What she does with the recovered attention is her choice: deeper analysis, a qualification, a shorter week, or simply a calmer close.
The trade-offs
- Documenting takes time that is already scarce. The first hours spent writing steps down are hours not spent closing the books.
- Some indispensability is lost. Shared knowledge changes how the bookkeeper is positioned, and a business must show it values her for more than being the only one who knows.
- Not every workaround is waste. Some quietly catch real errors. Retiring them without replacing the control can make matters worse.
- A better tool is not guaranteed. The cost, migration effort and learning curve of a replacement may outweigh the gain for a small business.
Why it matters
The most knowledgeable person in the finance office is often the one most tightly bound to the business's worst habits. Giving that person's expertise a shared, documented home is a practical act of respect, and it gives the business something sturdier than one person's memory. For the opposite scenario, where skills are used on something worth doing, read the dignity of work that adds something new.
Sources and further reading
- Management Standards - Demands - HSE (last verified 10 October 2026)
- Job demands-resources model - Wikipedia
- Management Standards - Support - HSE (last verified 10 October 2026)
Related Mellorca reading
- Why Re-Keying Data Is Not a Career
- Why Respect Shows Up in the Tools You Give People
- The Customer Service Agent Apologising for a Broken System