What happens when your only bookkeeper resigns — and what a handover cannot

IN SHORT

What leaves with a departing bookkeeper is not the bookkeeping. The ledger stays. What leaves is the undocumented layer — why an account is coded the way it is, which supplier invoices are always queried, what the three-year-old reconciling item actually represents. A two-week handover demonstrates that knowledge; it does not transfer it. The remedy is not a longer handover but holding the process in documents and system configuration rather than in a person.

SECTION 1

The pattern

The resignation is handed in on a Tuesday. Within the hour, the conversation has moved to replacement: who do we know, what will it cost, how quickly can we advertise. Everybody is now working on the wrong problem.

The replacement will be found. What will not be found is the reason the freight account is split the way it is, or which of the two customer records is the live one, or why the bank charges are posted a month in arrears. None of that is in the ledger. All of it was in one head, and the head has given four weeks’ notice.

There are three layers of knowledge in any finance function, and they behave completely differently when somebody leaves.

The recorded layer. The transactions themselves — what was posted, to which account, on which date. This layer is safe. It sits in the ledger and it does not walk out of the building.

The procedural layer. How the month actually gets done: the sequence, the workarounds, which report is run before which reconciliation, the spreadsheet that bridges the gap the package leaves. Rarely written down anywhere, because it was never designed — it accumulated, one fix at a time.

The contextual layer. Why. Why that account exists, why that customer is on different terms, why the suspense balance has not moved since 2023, why the payroll file is checked against a separate list before it is posted. Almost never written down, and the layer that costs the most to lose.

The handover is scheduled as two weeks, and two weeks is a demonstration rather than a transfer. The successor watches one month-end being performed. Watching something done once is not knowing how to do it, and it is certainly not knowing why it is done that way. The questions that matter do not arise during the demonstration. They arise in week three, when the leaver has gone.

THE HANDOVER TEST — name the ten things a successor would need in their first month, then answer each one from a document rather than from memory. Where does the payroll input come from and who checks it? Which customers are on non-standard terms, and on whose authority? What is in the suspense account? Which reconciling items are permanent and which are errors? Most businesses cannot answer a single one without asking the person who is leaving.

The test is uncomfortable precisely because the answers all exist. They are simply held in a form that cannot be inherited.

SECTION 2

The Caribbean variant

Key-person risk in finance is universal. Six regional conditions make the handover shorter, the knowledge deeper and the loss more complete.

Departures are often exits from the island, not just the job. A finance professional leaving for North America or the United Kingdom is not available for a follow-up call in week three. The informal safety net that most businesses quietly rely on — ringing the previous person — does not exist, and time zones and goodwill both expire quickly.

Very long tenure concentrates the undocumented layer. Fifteen or twenty years in the same seat produces an extraordinary depth of convention, almost none of it written. The longer the service, the more valuable the person and the more catastrophic the departure. Loyalty and risk grow together, which is an uncomfortable thing to say about someone who has served the business well.

The workarounds are the system. Where the accounting package does not do landed costing, or multi-currency, or job margin, somebody built a spreadsheet. That spreadsheet is now load-bearing, it has no documentation, and its logic is personal invention rather than accounting convention.

Relationships hold the ledger together. Which supplier will accept payment a week late, which customer responds to a call rather than a statement, which officer at the bank resolves a query the same day. This is real operational knowledge and it is entirely personal.

Written procedure reads as distrust. In smaller firms here, asking a long-serving employee to document their process is frequently received as an accusation. The request is deferred to avoid the awkwardness, and then it is never made again.

The recruitment cycle outruns the notice period. Notice is four weeks; replacement takes three to six months. In most departures there is no overlap at all, so even the demonstration does not happen.

SECTION 3

What it costs

The cost of a finance departure is rarely booked as such. It surfaces months later, in places that are not obviously connected to a resignation. The figures below are indicative, drawn from advisory experience across the region rather than from survey.

The close slips, and stays slipped. A monthly close that had settled into a rhythm typically slips by two to four months following an unplanned departure, and does not return to its previous timetable for six to twelve months — if it returns at all.

Unexplained balances become write-offs. Reconciling items nobody can now explain age quietly until somebody decides to clear them. The write-off is real money, and it is charged against a period that had nothing to do with the error.

Audit effort and audit cost rise. Auditors ask questions the new incumbent cannot answer from records. Explanation is replaced by testing, testing takes hours, and hours are billed. A departure in the financial year is one of the more reliable predictors of a higher audit fee.

Statutory deadlines are missed in the gap. Filings that ran automatically because one person remembered them stop running when that person stops. Penalties and interest accrue against dates nobody was watching.

The comparatives break. The least visible cost. A successor with no written convention invents their own — reasonably, and often better — with the result that this year is no longer comparable to last year. Variance analysis becomes unreliable at exactly the moment management most needs it.

The business does not lose an employee. It loses a specification — and it only discovers the specification existed once it is gone.

SECTION 4

What the capability actually does

The instinct is to solve this by writing a procedures manual. Manuals are written once, become inaccurate within a quarter and are consulted by nobody. The durable answer is different, and it rests on a single principle: documentation should be a by-product of doing the work, not a separate task competing with it. Nine mechanisms do that.

A chart of accounts with written definitions. Each account carries a note stating what belongs in it and what does not. This takes an afternoon to write and settles the largest single category of successor error — coding drift, where the same transaction is treated differently after a change of staff.

Coding rules held in the platform. Where a recurring supplier is coded by rule rather than by judgement, the rule is the documentation. It is visible, editable and auditable, and it does not depend on anybody remembering what was decided two years ago.

The supporting document attached to the entry. The invoice, the contract, the correspondence — held against the transaction permanently. This is what converts “why is this here?” from an interview question into a click. It is the single most effective defence against loss of the contextual layer.

An approval matrix enforced by permissions. Authority is documented by being enforced. Who may approve what, to what limit, is a system configuration rather than an understanding, and a successor inherits it intact on their first morning.

The close as a task list, not a memory. Each step of the close is a task with an owner, a sequence and a date, ticked as it is completed. The checklist is simultaneously the procedure, the progress report and the evidence that the step was performed.

Standing journals on a schedule. Depreciation, prepayment releases and recurring accruals post because they are scheduled, not because somebody recalls that they are due. Nothing quietly stops when the person who remembered it stops.

Reconciliations with retained working papers. Every reconciliation kept for every period, with its supporting schedule. Long-standing reconciling items carry their own explanation and their own age, so no successor inherits a balance they cannot account for.

Master data with written conventions. Customer and supplier naming, payment terms, cost centre structure and non-standard arrangements recorded against the record itself rather than known informally. The customer on special terms says so on their own file.

A complete audit trail. Who created each entry, who approved it, when, and what changed afterwards. This is ordinarily discussed as a control, and it is one — but it is also the most detailed record of practice a business has, and it exists whether or not anybody set out to write it.

Taken together these do not describe a manual. They describe a finance function in which the procedure is inseparable from the performance of it, so that keeping the documentation current requires no discipline that the work itself does not already require.

SECTION 5

How the Accounting Services BPO Division delivers it

Continuity is the part of the service that is invisible until it is needed, which is why it belongs in the contract rather than in the relationship.

The written process comes before operation. The design stage produces the chart of accounts definitions, coding rules, approval matrix, close checklist and reporting calendar as documents, agreed and signed off, before the first transaction is processed. The documentation is not retrofitted; it is the specification the work is built from.

Two people current on the file at all times. A named engagement manager and a named reviewer, both familiar with the client. Neither is a single point of failure, and cover does not require a handover because there is nothing to hand over.

Continuity is contractual rather than personal. Illness, leave and resignation are absorbed inside the division. The client’s close does not slip because of an event in someone else’s employment.

A departure is the best moment to capture the knowledge, not the worst. Where a long-serving employee is leaving, transition includes structured capture of exactly the conventions that would otherwise walk out: the workarounds, the non-standard arrangements, the unexplained balances. That knowledge is written into the configuration while its owner is still available to confirm it — which is why the notice period is the right time to begin, not the wrong one.

Quarterly review keeps the documentation true. Process documents are revisited as part of the scope review rather than left to decay, which is what happens to every manual ever written.

The documented process is yours on exit. Exit terms cover the process as well as the data. The definitions, rules, checklists and working papers leave with you in usable form. A provider who returns your ledger but keeps the method has recreated the original problem at a larger scale.

SECTION 6

Where to start

In the next thirty days. Run the handover test while nobody is leaving. Write the ten questions a successor would ask in their first month and try to answer each one from a document. Do not ask the incumbent — the point of the exercise is to find out what only exists in their head. The list of unanswerable questions is your risk register, and it usually takes an hour to produce.

In thirty to ninety days. Capture the top ten conventions in writing, one page each at most, with the incumbent’s help and framed as protecting them rather than replacing them — nobody should have to be reachable on leave. Start with account definitions, the close sequence, non-standard customer and supplier arrangements, and every long-standing reconciling item.

Beyond ninety days. Move the conventions into the system so they stop depending on anyone’s discipline: coding rules configured, documents attached at entry, approvals as permissions, the close as a task list. At that point documentation stops being a project and becomes a consequence.

The closing test: could a competent stranger close your month using only what is written down? If the answer requires a phone call to someone who no longer works for you, the system is still a person.

REFERENCE

Frequently asked questions

What happens when your only bookkeeper leaves?

The ledger stays; the procedural and contextual knowledge goes. Typically the monthly close slips by two to four months, unexplained balances accumulate, statutory filings are missed in the gap and audit effort rises. The severity depends almost entirely on how much of the process was written down beforehand, and hardly at all on the length of the notice period.

How long should a finance handover be?

Length is the wrong variable. A four-week handover transfers little more than a two-week one, because both are demonstrations rather than transfers. What determines the outcome is whether account definitions, coding rules, the close checklist and non-standard arrangements exist as documents before the handover begins.

What should a finance handover file contain?

Account definitions; the close sequence with owners and dates; coding rules for recurring transactions; the approval matrix; non-standard customer and supplier arrangements; every long-standing reconciling item with its explanation; the statutory filing calendar; and the location of supporting documents. If each of those exists, the handover is a formality.

Is a procedures manual the answer?

Rarely. Manuals are written once, are inaccurate within a quarter and are consulted by nobody. Documentation holds only when it is a by-product of doing the work — rules configured in the system, documents attached at entry, approvals enforced by permissions, the close performed against a task list.

How do I ask a long-serving employee to document their process without causing offence?

Frame it as cover rather than as scrutiny: nobody should have to be reachable while on leave, and nobody should carry the whole month alone. Beginning with account definitions and the close sequence — technical, impersonal and obviously useful — tends to make the rest of the conversation easier.

Does outsourcing eliminate key-person risk?

It transfers it to a party structured to absorb it. Two named people are current on the file, cover is contractual rather than personal, and the process exists as documents and configuration. The risk worth testing then is provider risk, which is why exit terms should cover the documented process and not only the data.

NEXT STEP

Request the Finance Function Diagnostic

A 45-minute scoping conversation covering volumes, systems, entities, close cycle and reporting needs; a written recommendation on tier, scope, division of labour and transition plan; and a fixed-scope service proposal priced by process, with service levels and exit terms stated.

Contact us : Dawgen Global · Accounting Services BPO Division: [email protected] · dawgen.global/contact-us

Continue reading: “You are not hiring an accountant. You are buying a finance function.” · “Approval is not a signature. It is a permission setting.” · “If we disappeared tomorrow, could you still trade?”

About Dawgen Global

Dawgen Global is an independent, integrated multidisciplinary professional services firm headquartered at 47 Trinidad Terrace, New Kingston, Jamaica, serving more than 15 territories across the Caribbean. Founded and led by Dr. Dawkins Brown, Executive Chairman, the firm is independent and not affiliated with any international network. It delivers a full suite of professional services under one roof: audit and assurance; tax advisory; IT and digital transformation; risk management; cybersecurity; actuarial and insurance regulatory advisory; HR advisory; mergers and acquisitions; corporate recovery; business advisory and strategy; accounting BPO and virtual CFO services; and legal process outsourcing.

The proposition is simple: big-firm capability without the big-firm price. Dawgen Global’s integrated approach is built for the specific complexities and opportunities of the Caribbean market, helping organizations make sharper, better-informed decisions that drive measurable progress.

To explore a partnership, reach out: