7 Finance Tasks That Should Not Live in One Person's Head

7 Finance Tasks That Should Not Live in One Person's Head

Ask an owner what happens to the books if their bookkeeper is out for a month, and most of them say it would be fine. Push a little and the answer changes to "well, we would figure it out."

Finance key person risk is not a trust problem. It usually attaches to the most loyal person in the building, which is exactly why nobody checks. Every year they have done the same work the same way added a piece of knowledge that exists in one place and is backed up nowhere.

The seven below are the ones that actually hurt. Each has the same failure mode: the task is documented somewhere, and the reasoning behind it is not.

1. Finance Key Person Risk Starts With the Access List

Start here, because it is the fastest to test and the most reliably wrong.

Write down every bank, card, payroll, tax portal, state registration, merchant processor, and vendor login the finance function touches. Then have someone else try to reproduce that list from the company's own records. The gap is the answer.

The limitation: an access list decays faster than anything else here, because every new vendor adds a row. Pin it to an event rather than a calendar. New accounts get added the day they are opened, and the list gets a full walkthrough whenever anyone with finance access joins or leaves.

2. The Close Sequence That Only Exists as One Person's Order of Operations

Most small businesses have a month-end close. Almost none have it written down as a sequence. What exists is a person who does the same eleven things in the same order because doing them out of order once caused a problem. The order is real knowledge, and it is invisible, because a checklist of eleven tasks does not tell you which three have to happen before the others. Ask for the sequence with dependencies, not just the list.

The limitation: a close sequence written once becomes fiction the first time you change a system. Rebuild it as part of any accounting software, payroll, or bank migration, and treat the rewrite as part of the project rather than cleanup after it.

3. Payroll, the One Task With Deadlines That Do Not Wait for a Learning Curve

Everything else on this list can absorb a bad week. Payroll cannot. Employees expect to be paid on a fixed day, tax deposits have external deadlines, and a new person learning the process in real time is learning it against a clock.

Document the run, not just the system. Who approves hours, what gets checked before submission, how a correction is handled mid-cycle, which states you are registered in and what each one expects. Those last two are where an unfamiliar person gets stuck.

The limitation: payroll documentation ages badly, because requirements change and so does your headcount footprint. Re-read it whenever you hire in a new state or change providers, and have someone other than the usual operator run one cycle a year.

4. The Chart of Accounts Logic, Which Is Not the Chart of Accounts

Anyone can export your account list. Nobody can export why a given expense lands where it does.

That reasoning is usually good. Software subscriptions here, contractor payments split that way, one recurring charge coded to cost of goods rather than overhead because of how you read margin. Lose it and the next person codes by best guess, and your year-over-year comparisons quietly stop comparing the same thing. Write a short coding guide: the twenty transactions you see most, where each goes, and one line on why.

The limitation: a coding guide nobody revisits becomes a rule with a forgotten reason, which is worse than no rule. Review it yearly with whoever reads the financial statements, and delete anything that no longer matches how you use the numbers.

5. Vendor Terms, Including the Ones That Were Never Written Down

The contract file tells you what you signed. It does not tell you that your main supplier has quietly allowed an extra two weeks for years, or that the landlord takes a late rent payment in January without comment.

Those handshake arrangements are working capital. They live entirely in the relationship between one vendor contact and one person in your office, and they do not transfer with a login. Keep a plain list of who you owe, on what terms, and what the actual practice is where it differs from the paper.

The limitation: informal terms can be withdrawn without notice, so documenting one does not make it reliable. Confirm the important ones in writing with the vendor, and re-check the list whenever your contact there changes.

6. The Recurring Entries Somebody Types From Memory

Every set of books has a handful of monthly journal entries keyed by hand: a prepaid amortization, a rent accrual, an allocation between entities, a loan split between principal and interest.

They are small and load-bearing. Nobody notices a missing one for a while, and by the time the numbers look wrong you are months away from the cause. Each recurring entry needs three things recorded: what it does, where the amount comes from, and when it ends. The third is the one people skip, and it is why businesses amortize a prepaid item for two years past the end of the contract.

The limitation: these go stale fastest, since amounts change and schedules end. Attach a review to the close itself, so whoever runs the month confirms each entry still has a live reason to exist.

7. The Filing Calendar, Especially the Local Items Nobody Remembers

Federal and state income filings are on everyone's radar. The damage usually comes from the other ones.

Business licenses, local registrations, annual reports, sales tax in a jurisdiction you entered two years ago, a personal property filing in one county. These rarely fail loudly. They fail with a notice, long after the fact, addressed to an office nobody checks. Build one calendar with every obligation, the jurisdiction, the due date, and who files it.

The limitation: a filing calendar reflects where you did business when you wrote it. Revisit it whenever you open a location, hire remotely in a new state, or start selling somewhere new, and have a tax professional confirm the list rather than treating your own reconstruction as complete.

Where Finance Key Person Risk Goes When an Outside Team Owns the Function

The uncomfortable version of this problem is that documentation written by the person who holds the knowledge tends to assume the knowledge. One reason businesses move day-to-day finance to an outside team is that a team cannot run on a single memory by design.

System Six is a Seattle firm founded in 2009 with 41 employees, serving clients nationwide. It does day-to-day finance work for small businesses generating between $1 million and $10 million in revenue: bookkeeping, payroll processing, bill pay, and invoicing. Its stated focus includes helping organizations modernize a finance function, which is roughly what this list describes.

The limitation: System Six lists a $1 million revenue minimum and prices from a monthly fixed fee starting at $800, so a smaller business is outside its scope and should build this documentation in-house. Outsourcing also moves the dependency rather than removing it. Ask any outside provider who specifically does your monthly work, what happens when that person is unavailable, and what you receive on day one if you end the engagement.

Frequently Asked Questions

How do I start this without insulting a loyal bookkeeper?

Frame it as coverage, not audit, and do it for every function rather than that one. The honest version works: you want the business to survive a vacation or a family emergency without landing on one person's phone. Most long-tenured bookkeepers already know they are the single point of failure and find it stressful rather than flattering.

What is the fastest test of how exposed we are?

Ask someone other than your bookkeeper to reproduce a month-end close from the written material alone, with the bookkeeper answering questions only in writing. Every question they have to ask is a gap. An afternoon of that usually tells you whether this is a small project or a real one.

Does accounting software solve this on its own?

Partly. Software holds transactions, recurring templates, and audit trails, which is real coverage. It does not hold reasoning, informal vendor terms, or the sequence someone follows for reasons the system never recorded. The gap between what your system stores and what your bookkeeper knows is the part to write down.

If you cannot say today which of these seven exists only in one person's head, that is the list to build before you need it. You can browse accountants and fractional CFOs on Sam's List who take on day-to-day finance work for small businesses.

---

About the author: Kimberly Green is the cofounder of Sam's List, where business owners and high earners find vetted CPAs, financial advisors, and fractional CFOs. She's met one-on-one with 400+ financial professionals and writes from the real data behind thousands of client-advisor matches. Ask her anything about finding an accountant - she's heard it all, including the questions people are afraid to ask.