What history is most likely to get lost?

Reconciliation notes, support schedules, open-item explanations, and document-location knowledge are the items most often lost in a poor handover. That matters because weak balance sheet review, management reporting, and clean schedules tends to resurface in the next monthly close, usually when the timing is worse.

Should the new bookkeeper start immediately?

Only once the handover has defined what the old provider owns and what the new provider inherits. That matters because weak balance sheet review, management reporting, and clean schedules tends to resurface in the next monthly close, usually when the timing is worse.

Can cloud software prevent history loss?

It helps, but only if the records, access, and working explanations are actually handed over cleanly. That matters because weak balance sheet review, management reporting, and clean schedules tends to resurface in the next monthly close, usually when the timing is worse.

How to Switch Bookkeepers Without Losing History

How to switch bookkeepers without losing history matters most when the owner needs a straight answer quickly and the file cannot provide one. We see this in South African SMEs when bank statements, supplier invoices, customer receipts, and support for unusual entries is still incomplete and the next month-end or SARS request is already close.

Businesses rarely lose bookkeeping history because of one dramatic event.

They lose it because nobody defined what had to be preserved before the switch happened.

What "history" actually means in a bookkeeping handover

History is not only the data in the accounting platform.

It also includes:

the last reconciled month
open-item explanations
support schedules
document locations
recurring journal logic
unresolved queries that still affect the live month

If those items are not transferred, the new provider can access the file but still not understand it.

The cutoff rule that protects the timeline

The cleanest switch starts with one question:

Which month belongs to the outgoing provider?

That answer should be written down.

Handover item	What should be defined
Final owned month	Last month the old provider closes
First inherited month	First month the new provider controls
Open issues	Items still unresolved at cutoff
Responsible party	Who owns each unresolved item

That one table prevents a lot of blame and confusion.

The records you must export before access changes

Before permissions are changed, export or verify:

general ledger and trial balance
bank reconciliations
supplier and customer age analysis
VAT schedules or control-account support
recurring journal explanations
document-folder structure

The platform data is only half the handover. The working records matter just as much.

The three places history usually disappears

1. Private inboxes

Support documents or explanations live in one person’s email instead of a shared system.

2. Verbal knowledge

The outgoing person knows why an old balance exists, but never wrote it down.

3. Incomplete reconciliation support

The file says the bank is reconciled, but the actual supporting logic is unclear.

These are the quiet failure points that force the new provider into accidental cleanup work.

The handover pack template

Every switch should have a short handover pack with:

Pack item	Status
System access confirmed
Last reconciled month confirmed
Open-item register attached
Document map attached
Reporting deadlines noted
First-month review scheduled

If that pack does not exist, the handover is not finished.

The first-month stabilization plan

The first month after the switch should not be treated as a normal month.

It should include:

extra review on the bank rec
confirmation of opening balances
testing the new document workflow
separate logging of inherited issues

This is how the business distinguishes old-process noise from current-process performance.

When a switch is really a cleanup project

Sometimes the business thinks it needs a provider change when it actually needs cleanup first.

That is usually true when:

the last clean month is unclear
old balances cannot be explained
the current provider cannot produce support schedules
the business cannot gather source records quickly

At that point, the safer move may be catch-up bookkeeping before the new monthly process is judged.

The pre-switch review owners should insist on

Before the outgoing provider's access changes, the owner should ask for a short review meeting that deals with facts, not feelings.

That meeting should confirm:

the last month where the bank, debtors, creditors, VAT, payroll, and loan accounts were reviewed
which balances still need explanation
which SARS or CIPC matters are open
whether any supplier, customer, or owner transactions are still parked in suspense
where the supporting documents are stored

The point is not to turn the handover into a blame exercise. The point is to prevent the new bookkeeper from inheriting unknown risk and then being judged on problems that were already present.

For a South African business, this matters most where bookkeeping feeds VAT returns, EMP201 checks, provisional-tax estimates, and year-end schedules. If the handover pack does not show how the last VAT period was supported, the new provider may spend the first month trying to reconstruct history instead of keeping the current month clean.

How to brief the incoming bookkeeper

The new bookkeeper needs more than login details.

They need a short operating brief that explains how the business actually works. A retailer, contractor, medical practice, ecommerce store, and professional-services firm may all use the same accounting platform, but their bookkeeping pressure points are different.

A useful brief should cover:

Area	What to explain
Sales cycle	how invoices, receipts, card payments, deposits, or platform payouts flow
Supplier cycle	who approves costs, how credit terms work, and where invoices are stored
Payroll	who prepares payroll, how payroll journals are posted, and when EMP201 figures are checked
VAT	which transactions often create VAT questions
Owner movements	drawings, reimbursements, director loans, and private costs paid by the business
Reporting	what the owner expects to see every month

That brief does not need to be long. It needs to be accurate enough for the new provider to avoid guessing.

What to monitor for the first two closes

The first close after the switch should be treated as a controlled transition. The second close should prove whether the new rhythm is working.

During those two months, management should watch for three things.

First, unresolved items should reduce, not grow. A new provider may find inherited problems, but there should still be a visible list of what is being cleared and what is waiting for the owner.

Second, the document workflow should become easier to follow. If support is still moving through private WhatsApp messages, personal inboxes, or memory, the business has not really improved the control environment.

Third, reporting should become more stable. The owner should be able to see whether the bank reconciles, whether supplier balances make sense, whether customer receipts have been matched, and whether tax-related accounts look credible before the next deadline arrives.

If those things are not improving after two closes, the issue may not be the handover anymore. It may be the scope, the process, or the quality of monthly review.

How this page supports the bookkeeping cluster

Use this page with:

The aim is continuity. A provider change should not reset the finance memory of the business.

A clean handover timeline

A practical switch should have a short timeline with named owners.

Week one is for access, exports, and confirming the last clean month. Week two is for open-item review, document mapping, and agreeing what the outgoing provider will still answer. Week three is for the incoming bookkeeper to test the file, list inherited issues, and confirm the first month-end plan. Week four is for management to review the first close pack and decide which inherited issues need cleanup work.

That timeline matters because many handovers fail in the space between "we changed providers" and "the new provider owns everything." If nobody manages that gap, old questions become new confusion.

The owner should keep the handover tracker simple:

access confirmed
exports saved
open items listed
SARS and VAT periods checked
first close reviewed
unresolved inherited issues separated from current work

That is enough to protect continuity without turning the switch into a long project.

Separate inherited problems from new service problems

The first two months after a switch can be noisy because the incoming bookkeeper is working through old records while also trying to keep the current month clean. Management should separate inherited problems from new service problems so the wrong person is not blamed and the wrong fix is not chosen.

Inherited problems include unreconciled bank periods, missing supplier support, stale debtor balances, VAT periods with thin evidence, old payroll journals, and director loan movements that were never explained. New service problems include missed cutoffs, poor communication, late reconciliations, or unclear exception reporting after the new process has started.

This distinction helps the owner manage the transition fairly. Historical cleanup may need a once-off project plan. Weak current service needs a process correction. Treating both as the same issue usually creates frustration and makes the handover feel less controlled than it really is.

Lock down access without losing evidence

Access changes should be deliberate. The outgoing bookkeeper should not retain unnecessary access once the handover is complete, but the business should first export the evidence it may need later: accounting reports, reconciliations, VAT reports, payroll summaries, user history where available, and documents stored inside the accounting system.

For cloud accounting, also check bank feeds, app integrations, user roles, and email addresses used for document capture. A switch can fail quietly if the new bookkeeper receives the ledger but not the connected workflow around it.

The goal is simple: the business should leave the old relationship with a complete evidence trail and enter the new relationship with clean access, clear permissions, and no dependency on private inboxes or informal memory.

Keep the first management report separate

The first report after a switch should separate current performance from inherited cleanup. If old unreconciled items distort the month, management should be told directly. Otherwise the owner may think the new bookkeeper caused a problem that was already sitting in the file.

A separate first report can show the current month, the inherited issue list, and the cleanup plan. That gives the owner a fair view of operating performance while still acknowledging the historical work that must be completed. It also gives the incoming bookkeeper a cleaner way to prove progress without pretending the old records were better than they were.