Home › Blog › Cleanup & Catch-Up Bookkeeping › Bookkeeping Cleanup Engagement Checklist
Scope a bookkeeping cleanup before you start: the period, the last filed year, every account, transaction volume, and a snapshot of the file as found.
By StatementVerified Editorial · November 5, 2026 · 6 min read · Filed under Cleanup & Catch-Up Bookkeeping
Most cleanup engagements go wrong before any bookkeeping happens, at the scoping stage. The client says the books are a bit behind, the bookkeeper hears a few months of categorization, and three weeks later both are staring at two years, five accounts, a loan nobody mentioned, and a file whose last filed year does not match its balances. Neither party acted in bad faith. The scope was simply never established in writing, so each side priced and planned a different job.
A proper scoping pass takes an hour or two and saves weeks. You establish the exact period, the last year a return was filed from these books, every account in play, the rough transaction volume, and the condition of the existing file, and you snapshot that file before changing a single entry. This checklist walks through each element, why it matters, and the questions that surface the surprises while they are still cheap.
Name the first month and the last month of the cleanup, in writing, and identify what sits just before the first month: the last month that is known to be reconciled and correct. A cleanup that starts mid-stream needs that preceding month as its anchor, so include obtaining its statement in the scope. Vague periods such as since last year or from when it got messy drift as the work proceeds, because messy has no date. If the client wants additional months once work starts, that is a scope change to agree explicitly, not a silent extension absorbed into the original fee and timeline.
Also define the end condition. Does the engagement end at the last complete month, at a quarter end, or at a date chosen because a tax filing, loan application, or sale depends on it? The end condition drives sequencing when time is short: a filing deadline may mean completing the most recent year first in draft while still rebuilding chronologically underneath. Write the priority down, because under deadline pressure everyone remembers the conversation differently.
Ask which tax year was most recently filed using these books, and get a copy of that return or at least its key totals: revenue, major expense categories, and ending balances where the return reports them. The filed year is protected territory. Its numbers have been reported to a tax authority, so the cleanup should not casually change them. If the rebuild shows the filed year was wrong, that is a separate, deliberate conversation about amending, involving the tax preparer, not a quiet edit during cleanup.
The last filed year also tells you where reliable ground probably is. Books for filed years were at least assembled into a return, however imperfectly, while unfiled years may never have been reviewed at all. Scope the verification effort accordingly: agree the filed year balances to the return as a starting check, then rebuild forward from there. If the file balances do not match the filed return, finding out during scoping, rather than mid-engagement, changes the price and the plan honestly for everyone.
Clients reliably forget accounts: the card used only for travel, the savings account that holds tax money, the payment processor that settles into the bank net of fees, the business account at a second bank opened for a loan. Each forgotten account is unrecorded activity and a reconciliation that cannot tie. Prompt systematically: ask where sales settle, what cards are in the owner wallet, whether any account was opened or closed during the period, and whether personal accounts were ever used for business. Then compare the list against the statements and the existing chart of accounts for orphans on both sides.
For loans, scope beyond the statement. You need the loan documents or at least the payment breakdown between principal and interest, because a year of loan payments recorded entirely as expense overstates costs and understates the liability. For processors, decide whether the books will record gross sales with fees as expenses, which is the informative approach, or net deposits, and note the decision in the scope so the rebuild applies it consistently from the first month.
Count roughly: transactions per account per month, months in scope, and the share that are likely to need client answers. Volume drives everything: conversion effort, categorization rules versus manual review, and how many question passes the client must commit to. A client with a handful of large transactions needs a different plan from a retailer with thousands of small ones, even over the same period. Also assess the file condition: are bank feeds connected and duplicated against manual entries, are prior reconciliations present, are there suspense balances, negative accounts, or equity accounts used as dumping grounds?
Record your findings as a short scoping memo, even for a small engagement. It should state the period, the accounts, the filed-year position, the expected volume, the known problems, what the client must provide and by when, and what is explicitly out of scope, such as payroll reconstruction or sales tax filings. That memo becomes the engagement agreement backbone. Cleanups expand; the memo is what lets you expand them fairly, with a conversation and an adjusted fee, instead of resentfully and for free.
Before the first correction, export or back up the bookkeeping file exactly as received, and save key reports: trial balance, profit and loss for the affected years, balance sheet at the anchor date, and any existing reconciliation reports. Date the snapshot and store it outside the live file. This before picture protects everyone. It proves the state you inherited if a prior preparer or the client questions a change, and it gives you a genuine fallback if a rebuild approach needs to be abandoned and restarted.
Repeat the snapshot habit at milestones: after the filed year is verified, after each major account is rebuilt, and at completion, when the after reports pair with the before reports to show exactly what the cleanup changed. Clients understand before and after reports better than any narrative summary, and tax preparers trust a cleanup more when they can see the bridge from what was filed and recorded to what now stands. Scoping feels like paperwork. In truth it is the engagement, because the bookkeeping that follows can only ever be as good as the boundaries and baselines set here.
Because those numbers were reported to a tax authority and should not change casually during cleanup. Knowing the filed year tells you where to anchor the rebuild, what to verify against the return, and when a discovered error becomes an amendment conversation instead.
Reconstruct the list from evidence: the chart of accounts, statements they do have, deposits whose source is another account, and card payments leaving the main bank account. Every unexplained transfer points at an account that belongs on the inventory.
Yes, in short form. Even a one page note covering period, accounts, filed year, volume, client responsibilities, and exclusions prevents the misunderstanding that turns a small job into an unpaid large one.
Cleanup & Catch-Up Bookkeeping · November 2, 2026
Why a bookkeeping rebuild must run in chronological order: solid ground, balance continuity, and reconciling each month before the next one starts.
Cleanup & Catch-Up Bookkeeping · November 4, 2026
A complete workflow for a business a year behind on its books: gather every statement, convert, import oldest first, and reconcile month by month.
Cleanup & Catch-Up Bookkeeping · November 3, 2026
Collect statements from clients in one complete request: every account, the month before the period, credit cards, loans, and processor reports.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.