Home › Blog › Cleanup & Catch-Up Bookkeeping › The Catch-Up Bookkeeping Workflow
A complete workflow for a business a year behind on its books: gather every statement, convert, import oldest first, and reconcile month by month.
By StatementVerified Editorial · November 4, 2026 · 6 min read · Filed under Cleanup & Catch-Up Bookkeeping
Being a year behind on the books feels chaotic, but the work itself is not mysterious. It is the same monthly bookkeeping you already know, done in strict order, twelve times, with tighter controls because errors compound across months. The businesses that stay stuck are usually not missing skill; they are missing sequence. They import whatever statements are at hand, categorize whatever looks familiar, and try to reconcile the newest month while the opening balance underneath it is still wrong.
This workflow restores order. Gather everything first, including the month before the catch-up period. Establish solid ground at the last point the books were right. Then convert, import, categorize, and reconcile one month at a time, oldest first, never moving forward on an unreconciled month. It is slower in week one and dramatically faster by month six, because each finished month becomes the verified foundation for the next.
List every account the business used during the period: checking, savings, credit cards, payment processors, and loans. For each one you need a complete run of statements covering the whole catch-up period plus the final month before it begins, because that earlier statement proves the opening balance you will start from. Gaps are the enemy. A missing month discovered at month nine forces you to stop, source it, and recheck everything built after it, so spend the effort up front comparing statement dates account by account until every period is covered with no holes.
While gathering, also collect the context documents that answer categorization questions later: loan statements showing payments and interest, payroll reports, sales tax filings, and any prior tax return for a year inside the period. Note accounts that were opened or closed mid-period, since a closed account still needs its final statement and its transactions still belong in the books. The deliverable of this phase is a simple inventory: account, period covered, format received, and anything missing, in writing, before conversion begins.
Find the last month that was ever properly reconciled, or, if none was, the last filed tax year end. That point is your solid ground: the last date at which the books and the bank can be shown to agree. Every balance after that point is suspect until rebuilt, and every balance at that point is your anchor. If the books contain a balance for that date, test it against the statement. If it disagrees, the rebuild starts earlier than you hoped, and it is far better to learn that now than after importing a year of data on a faulty base.
Record the anchor in the engagement notes: the date, the account balances proven, and the statements that prove them. Also take a backup or export of the bookkeeping file as it stands before you change anything. Catch-up work rewrites history, and the before snapshot is both your safety net if an approach fails and your evidence of what the file looked like when you received it, which matters when a client later asks why a prior period changed.
Convert statements account by account and month by month, verifying each converted file against its statement totals before it is imported. Then import in chronological order, oldest first, one month at a time. Order is not a preference here. Importing newest first creates balances that cannot be checked, invites duplicate imports when you later fill gaps, and makes the running story of the account impossible to follow. Chronological import means every month ends with a balance you can compare to a statement before the next month begins.
Resist batching the categorization across the whole year at this stage. Import the month, categorize that month using the rules and questions it raises, reconcile it, and close it. A question about a recurring vendor in month one, answered once, becomes a rule applied confidently in month two. The same question left open across twelve imported months multiplies into dozens of uncertain transactions that all need revisiting. Small finished loops beat one giant unfinished one, every time, in cleanup work.
Reconciliation is the quality gate of the whole workflow. For each account and month, the book balance must agree with the statement balance after accounting for items genuinely in transit, such as a deposit recorded on the last day that the bank shows in the next period. Investigate differences while the month is in front of you. A difference equal to a transaction usually means a missing or duplicated entry. A difference equal to twice a transaction suggests a sign error. A small round difference often traces to a transposed or mistyped amount in older manual entries.
When a month reconciles, lock it in the practical sense: note it as complete in the engagement tracker, save the reconciliation report with the statements, and do not casually edit transactions in that period afterward. Later discoveries do happen, a client produces a missing statement page in month ten that affects month three, and when they do, you reopen the affected month deliberately, fix it, re-reconcile it and every month after it for that account, and note why. Deliberate reopening is professional. Silent drift is how cleanups stay unfinished forever.
With all months reconciled, review the full period as a whole: scan the profit and loss for categories that swing oddly between months, confirm owner transfers and loan payments were not recorded as income or expenses, check that transfers between accounts match on both sides, and clear suspense or ask-my-accountant accounts to zero or to a short explained list. This whole-period pass catches the categorization inconsistencies that single-month reviews miss, such as the same vendor coded to three different accounts across the year.
Hand over with a summary the client and their tax preparer can use: periods reconciled per account, balances proven, open items and why they remain, and any source documents still missing. Then set the monthly routine that prevents a repeat: statements pulled on a schedule, transactions categorized monthly, and reconciliation treated as a non-negotiable monthly close step rather than a year-end event. A catch-up that does not end in a routine is just an appointment with the same problem next year.
Because each month builds on the balance of the month before it. Chronological import lets you prove every month-end balance against a statement as you go. Importing out of order removes that check and makes duplicates and gaps much harder to detect.
Stop for that account and source the missing statement from the bank or the client portal before continuing past it. Building later months over a gap means every subsequent balance is unverifiable, and the rework costs more than the wait.
You can apply established rules in bulk, but work month by month for review and reconciliation. Questions answered in the first month become rules for the rest of the year, while a single bulk pass leaves the same uncertainties repeated through every month.
Cleanup & Catch-Up Bookkeeping · November 4, 2026
Categorize a full year of bank transactions consistently: build rules from recurring vendors, separate owner transfers from income, and review in passes.
Cleanup & Catch-Up Bookkeeping · November 5, 2026
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.
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.
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.