Switching Bookkeepers
Switching Bookkeepers: A No-Drama Checklist to Protect Your Numbers and Avoid Another Mess
Switching bookkeepers should feel like changing service providers, not running an emergency rescue mission. The difference comes down to two things:
You control access and ownership of your accounting system.
You get a clean handoff package so the next team can pick up without guessing.
Below is a practical checklist you can follow to protect your numbers, keep operations moving, and avoid the “we’re switching again in six months” cycle.
Before you switch: confirm what you are actually switching
Not every situation is a replace-the-bookkeeper problem. Sometimes it is a cleanup-first problem.
Switching only works smoothly if:
Reconciliations exist and can be trusted, or
You agree that cleanup will be part of the transition plan
If you switch without acknowledging broken reconciliations, you often just transfer the mess to a new person.
The no-drama switching checklist
Step 1: Lock down ownership and admin access first
This is the most important protection step.
QuickBooks Online (QBO):
Confirm the business owner is the Primary Admin. If the outgoing firm is Primary Admin, you may need to transfer that role back to the client account.
Confirm you can add and remove users without relying on the outgoing bookkeeper.
Xero:
Confirm who the Subscriber is. If the outgoing firm is the Subscriber, transfer the subscription first because Xero warns you cannot delete a Subscriber without transferring.
Review user roles and permissions, and remove access you no longer need.
Why this matters: if you do not own admin control, you do not fully control the system.
Step 2: Export a snapshot of your books before anything changes
Even with cloud software, take a clean snapshot so you have a reference point.
Export and save:
Profit and Loss and Balance Sheet for the last 12 to 24 months
General Ledger for the last 12 to 24 months
Trial Balance as of the last closed month
Aged Receivables and Aged Payables, if applicable
Bank and credit card reconciliation reports, or equivalent
Sales tax / GST-HST and payroll summaries, if applicable
Backing up key reports before transitions is a common best practice to avoid losing context and to prevent disputes about what changed when.
Step 3: Collect the handoff package from the outgoing bookkeeper
Ask for these items in one folder, organized by month.
Core close support
Bank and credit card statements
Reconciliation reports and support schedules
Journal entries list with explanations for unusual entries
Notes on accounting policies they followed (revenue recognition approach, capitalization rules, etc.)
SaaS and tool-heavy support, if relevant
Stripe payout reconciliation reports or monthly Stripe settlement support
Subscription billing exports used for revenue tie-outs
Payroll reports and filings
Stripe specifically recommends reconciling using payout reconciliation reports for automatic payouts, and points manual payout users toward balance reporting methods. Having these reports in the handoff prevents clearing accounts from turning into mystery balances.
Step 4: Make a clean list of tools and integrations
Most recurring bookkeeping messes come from broken or duplicated integrations.
Create a one-page list:
Banking feeds connected (which bank, which account)
Payment processors (Stripe, PayPal, etc.)
Payroll system
Expense management
Billing and subscriptions
Any connector apps and automations
Then check for the classic duplication trap:
Stripe syncing through an app and also recorded through bank feeds
Multiple apps posting the same sales data
Manual entries competing with automation
Step 5: Decide the cutoff date and what done means
Pick a clean transition line.
A simple approach:
Outgoing bookkeeper closes through Month X
New bookkeeper starts Month X+1
If cleanup is needed, define which months are in scope and what clean means
Write it down so you do not end up with two people touching the same month.
Step 6: Change access safely, not abruptly
Once you have the snapshot and handoff package:
QBO
Invite the new accountant user properly through QBO’s accountant invite flow. Accountant users invited this way do not count toward your user limit.
Remove the outgoing user access only after the handoff is confirmed.
Xero
Transfer the subscription if needed, then remove or change roles. Xero’s process keeps roles and permissions until the new subscriber updates them.
Step 7: Run a transition review for the first month
Your first month with the new bookkeeper should include a quick stability check:
Do bank and card reconciliations tie out cleanly?
Do Stripe payouts reconcile using a consistent method?
Are payroll liabilities correct?
Does the balance sheet look plausible?
Can the bookkeeper explain variances without guessing?
If these are not true in Month 1, fix the system before you scale the cadence.
Red flags that usually mean cleanup first
If you see any of these, plan for cleanup as part of the switch:
Bank reconciliations have gaps or were forced
Stripe clearing account never goes to zero and has old items
Payroll liabilities drift month to month
Large amounts in Uncategorized or Suspense
Reports change after the month is closed without explanation
Recordkeeping: do not lose your evidence
Even if a bookkeeper is leaving, your business needs to retain records that support income, deductions, payroll, and sales-tax filings. Both CRA and IRS guidance make the same practical point: keep records as long as needed to support the amounts reported on returns and filings.
Practical takeaway: keep your monthly close support and key statements in a secure folder that is owned by the business, not a vendor.
FAQ
Should I remove the old bookkeeper immediately?
Not until you have the snapshot exports and the handoff package. Remove access after the transition is stable.
What is the single most important step?
Confirm you control admin ownership. In QBO, confirm the client is Primary Admin. In Xero, confirm the Subscriber and transfer if needed before removal.
How do we avoid another mess?
Use a close checklist, reconcile consistently, and keep one source of truth for each integration. Transitions go wrong when systems are undocumented and responsibility is unclear.
