Your accountant just quit and they were the only one who understood the books

At a glance

The resignation letter is on your desk, and you are discovering that your accounting system was never QuickBooks. It was one person. This post does two things in the order you need them: first, a 30-day stabilization plan you can start today to keep payroll and filings safe; second, how to rebuild so that no single departure can ever put your books at risk again. Secure access, baseline the books, stabilize, then fix the structure that made one person irreplaceable in the first place.

What should I do first when my accountant quits?

First, secure access: change passwords on accounting software, banking, and payroll, and confirm admin ownership of every account. Second, schedule a structured handover covering recurring deadlines like payroll, sales tax, and loan covenants. Third, export a trial balance and reconciliation status as a baseline. Only then decide between a replacement hire, a fractional accountant, or both.

That sequence matters. Most owners jump straight to posting the job ad, but a replacement hired into an undocumented system inherits the same black box, three weeks slower. Secure, extract, baseline. Then hire.

The 30-day stabilization checklist

This checklist is designed to be run by someone who is not an accountant: an owner, GM, or office manager holding the fort. The goal for the next month is survival, not elegance. Keep payroll and filings safe, get the books baselined, and buy yourself time to hire well instead of fast.

Days 1 to 3: access, passwords, admin rights, bank contacts

The first 72 hours are about control. You do not need to understand the files yet. You need to have them, and you need to be the one who owns every account.

• Change every password the departing employee held: accounting software, online banking, payroll provider, state tax portals, payment processors, and any shared email accounts such as ap@ or invoices@.
• Verify admin ownership. Log into each system and confirm that you, not the departing employee, are the account owner or master admin. QuickBooks files in particular are often registered to the person who set them up. If the departing accountant is the Primary Admin, transfer that role now, while they are still cooperative.
• Call your bank. Confirm who has signing authority, wire approval, and online banking tokens. Remove access you cannot account for.
• Inventory the machines. If they worked from a personal laptop or kept files in a personal Dropbox or Google Drive, get copies onto company storage before the last day.
• Export backups. A full QuickBooks backup, a trial balance, and copies of every spreadsheet they touch regularly.

Week 1: the handover interview, questions to ask before they walk

Book two sessions of 90 minutes each, recorded with their consent, and work through the questions that capture what only they know. Cover the recurring deadlines each month and their dates, what is due in the next 30 days specifically, which spreadsheets they maintain and what feeds what, and a step-by-step walkthrough of month-end close as if you had to run it tomorrow.

Then capture the exceptions: the recurring journal entries they post and why, which accounts they reconcile and when each was last reconciled, the weird workarounds done differently from how the software intends, which customers are on non-standard terms, and which vendors require special handling such as prepayment, portal invoicing, or manual checks.

Finally, map the people and the risks: who the external contacts are (CPA firm, banker, payroll rep, insurance broker) and what each handles, any pending notices from the IRS or state agencies, where the passwords live and how each account is registered for two-factor, and one open question people always skip: what is currently broken, behind, or never got done.

That last question is the one people skip and regret. Every departing accountant has a behind pile. You want it named before the last day, not discovered by a penalty notice.

Weeks 2 to 4: baseline the books and fill the gaps

With access secured and the handover captured, spend the rest of the month getting to a known-good baseline. Unreconciled accounts are where surprises hide, so this is where you find them on your terms.

• Reconcile or verify reconciliations on every bank and credit-card account.
• Pull open AR and AP. Know what is owed to you, what you owe, and what is overdue in each direction.
• Confirm the filing calendar. Map the next 90 days of payroll tax deposits, sales tax returns, and estimated taxes against who will execute each one.
• Bring in fractional help if gaps appear. A fractional accountant or your CPA firm can run payroll and the next close while you hire. This costs money; it costs far less than a missed payroll tax deposit.
• Do not rush the hire. A stabilized, baselined book buys you time to hire well instead of fast.

What is key-person risk in accounting?

Key-person risk is when critical financial knowledge, such as how reports are built, which spreadsheets feed which numbers, and undocumented workarounds, lives in one employee's head rather than in documented systems. Warning signs: reports stall when they are out sick, nobody else can close the month, and processes exist only as personal habit.

If you are living this right now, you already know the warning signs were there. The close that only happened when one person was in the building. The report nobody else could regenerate. The vacation that quietly delayed everything.

How you got here: it is the system, not the person

Resist the urge to blame the departing accountant for hoarding knowledge. In most businesses between $2M and $20M, nobody hoarded anything. The tooling made one person the system.

QuickBooks handles the general ledger. Everything else, from inventory valuation to job costing to commission calculations to the report your bank wants, lives in spreadsheets, because that is where QuickBooks runs out. Those spreadsheets do not connect themselves to the ledger. A person connects them: exporting, pasting, adjusting, remembering why one cell is hardcoded. That person was the integration layer. Of course the system fails when they leave; you just lost a load-bearing component. We priced this dependency, alongside the other hidden costs of the stack, in The Real Cost of Staying on QuickBooks and Spreadsheets.

Here is a one-question diagnostic worth running even after you have stabilized: could a competent outside accountant run your month-end close from your written documentation alone, with no phone calls allowed? If the answer is no, you do not have an accounting process. You have an accounting person. And you will be back in this exact crisis at the next resignation, retirement, or extended sick leave; the only variable is the date.

If you want that question answered rigorously rather than rhetorically, our free expert audit is built for this moment: a structured review of your books and processes that maps out what only the departed person knew, before it is lost for good, and what it would take to make the whole thing run from documentation.

How does an ERP reduce key-person risk?

An ERP embeds process into the system itself: approval workflows, recurring entries, role-based permissions, and a single ledger replace the private spreadsheet web. Any competent accountant can step into a documented, standardized system in days, because the logic lives in software and written procedure, not one person's memory. Implementation includes documenting your processes as they are configured. Concretely, in a modern ERP like ERPNext:

• Recurring entries are configured, not remembered. The monthly accruals post because the system is set to post them, not because someone's calendar reminder fired.
• Workflows are explicit. An invoice over a threshold routes to approval automatically. The rule is visible to anyone with access, not encoded in how one person always did it.
• Inventory, orders, and accounting share one database. The spreadsheet web existed to bridge systems that did not talk. One system, no bridges, no bridge-keeper.
• Permissions define roles. Who can post, approve, and close is configured by role, which forces you to define the roles in the first place.

Rebuilding so this never happens again

One honest caveat, because it matters: an ERP does not eliminate the need for a competent accountant. You still need someone who understands debits, credits, and your business. What it eliminates is irreplaceability, the gap between losing a good accountant (a normal hiring problem) and losing the only person who knows how your finances work (an existential one).

One more note on sequencing: do not start an ERP implementation in week one of this crisis. Stabilize first, run the 30-day plan, get payroll and filings safe, get the books baselined. The structural fix comes after the fire is out, typically a few weeks later, when you can give it attention. Anyone who pitches you a software project while your payroll is at risk is selling, not advising.

A properly run ERP implementation is a process-documentation exercise. In our 6 to 8 week delivery, the first weeks are spent mapping exactly the things that just walked out your door: what the recurring entries are, how the close runs, who approves what, where every number comes from. Those mappings become the system configuration and the written procedure, so the documentation cannot drift from reality, because it is the reality.

Make redundancy a design requirement, not an afterthought. Our implementations train multiple staff per function, and the system's role-based permissions make cross-training practical: a second person can be given read-and-review access to the close long before they can post to it. The goal is simple: every critical process has at least two people who have actually executed it, plus documentation a third could follow.

What this looked like in practice

Two of our clients show what moving process from heads into systems does. Neither lost an accountant; both removed the dependency before it could bite.

Texas Stone Designs, a Texas stone manufacturer, had production scheduling that consumed 24 hours of one person's effort per cycle, a process that existed entirely as personal knowledge. After their ERPNext implementation, scheduling takes 5 minutes, inside a system the whole team can see. "VGTS turned production scheduling from a daily headache into something fast, simple, and visible to the whole team," says CEO Micah Grant. Visible to the whole team is the key-person-risk phrase: the process no longer depends on what one planner knows.

Mr Goli Soda runs 70 franchises supplied by 45 factories. Before ERPNext, onboarding a new franchise took 60 days of person-dependent effort; standardizing the process in the system cut it to 35 days, repeatable at scale, as MD Chandru describes it. You cannot standardize 70 locations on tribal knowledge; it only works when process lives in the system.

Neither story is about an accountant quitting. Both are about the same structural fix: when the process is in the software, people can leave without the process leaving with them. That is exactly what a CFO-grade finance function is built on.

Turn the crisis into the upgrade you have been postponing

Here is the contrarian truth about this terrible month: a key person leaving is the cheapest moment you will ever get to fix the structure. You are already paying the transition cost, the handover effort, the documentation scramble, the new hire's ramp-up. Those are the exact same costs an ERP migration incurs, and right now you are paying them anyway, for the privilege of rebuilding the same fragile system around a new person.

Rebuild it around a new person and you have reset the clock on the next crisis. Rebuild it around a documented system and you have ended the cycle.

Stabilize first, using the 30-day plan above. Then, before you let the new normal harden, get a second opinion on the structure. Get a free books-and-process audit: we will map what only they knew, test whether your month-end could survive another departure, and tell you plainly what a documented, system-based rebuild would involve, including when the honest answer is that your setup is simpler than you think and you should just document it and move on.