Sequence matters: catch up first, clean up second. Cleaning a file that's still missing six months of transactions means doing the same diagnosis twice, because the missing data changes what the existing data means. The one exception is a structurally broken chart of accounts — if the coding structure itself is wrong, fix it before importing thousands of transactions into it.

Find the last known-good date

Work backwards through bank statements comparing each month-end balance to what Xero shows for that date. The most recent month where they agree is your starting line. Everything after it is in scope; everything before it, you can provisionally trust. This single step reframes most cleanups from "the whole file is broken" to "fourteen months need work," which is both more accurate and considerably less daunting.

Size the gap

Check the Trial Balance and Balance Sheet for the tells: a suspense or clearing account carrying a balance, an "Ask My Accountant" account with anything in it, aged payables and receivables that don't tie to their control accounts, negative balances where they shouldn't be, and accounts holding round-number amounts that look like plugs.

Check what was done manually

If you have advisor access, the assurance dashboard is the fastest diagnostic in Xero. It shows statement lines that were manually deleted and transactions manually marked as reconciled — the two actions most likely to make a file look reconciled when it isn't. It also shows backdated entries and user activity, which tells you who did what and when.

Confirm your bank feed reaches back far enough

Bank feeds generally only import a limited window of history when first connected, and a feed that dropped out won't backfill the gap on its own. Before planning a catch-up, check the earliest transaction actually present for each account. Where the feed doesn't reach, you'll need to import statement files directly from the bank — and if the period is old enough that the bank portal no longer offers downloads, request the records early, because that lead time often sets the whole project timeline.

POWER TOOL
Cash coding
The job it does: codes and reconciles hundreds of bank statement lines at once.

Cash coding presents your unreconciled statement lines in a fast, spreadsheet-like grid where you can select accounts and tax rates for multiple lines simultaneously. When you save, Xero creates the matching spend or receive money transactions and reconciles them in one action.

This is the single biggest time saver in a catch-up. Work that takes days in the standard reconcile screen — clicking through one line at a time — takes an afternoon here. Sort by description or amount, select every instance of a recurring payee, code them together, move on. Accuracy improves too, because coding identical transactions as a group is more consistent than coding them individually across several sittings.

Cash coding is available on Standard and Premium Xero plans.

Important limitation: don't use cash coding to reconcile statement lines that relate to invoices, credit notes, expense claims or transfers between your own accounts. Doing so creates a new spend or receive money transaction and leaves the original invoice or bill sitting unpaid — so you end up with the expense recorded twice and a payables balance that never clears. Cash coding is for transactions you didn't otherwise enter.

ADVISOR  ROLE REQUIRED
Find & Recode
The job it does: bulk-corrects miscoded transactions after the fact.

The clean-up counterpart to cash coding, and the reason a competent advisor can fix in twenty minutes what would otherwise take a full day. Find & Recode uses a query builder to locate transaction lines matching your criteria, then changes them in bulk. You can update the account, tax rate, contact and tracking category — up to four fields in a single operation.

It works at the level of individual transaction lines rather than whole transactions, which matters for multi-line bills where only one line was coded wrongly.

Two features make it safe enough to use at scale. First, you choose whether to edit the source transactions directly or post a journal reflecting the change — the journal route preserves the original entries, which is often what you want when correcting a prior period. Second, Xero keeps a full history of every recode, showing what was changed and which transactions were affected, with a link to re-run the same search.

Typical uses in a cleanup: splitting one overloaded expense account into several, applying tracking categories retrospectively, correcting a tax rate applied wrongly for months, and consolidating duplicate contact records.

What it can't touch: tracked inventory lines, payroll transactions, bank transfers, and anything in a locked period. Those need manual journals or unlocking first — plan for them separately rather than discovering them halfway through.

CORE
Bank statement import
The job it does: fills the periods your feed doesn't cover.

Where the bank feed doesn't reach back far enough, or dropped out for a period, you import statement files from the bank directly. Xero accepts the standard export formats banks provide.

The critical discipline is at the join. Feeds commonly re-deliver a few days either side of a gap, so importing a file that overlaps produces duplicates that look entirely legitimate. Note the exact first and last dates present before importing, trim the import file to match precisely, and check the boundary dates afterwards rather than assuming.

CORE
Bank rules
The job it does: auto-codes recurring transactions as they're imported.

Before processing a large backlog, set up rules for your genuinely predictable recurring transactions — the monthly subscriptions, the utility direct debits, the regular suppliers. Every rule you write before the bulk work is coding you don't do by hand across however many months you're catching up.

Write them narrowly. A rule broad enough to catch unintended transactions will code them silently and correctly-looking, and because the automation worked, nothing flags it for review.

Build in a safety net: after processing, run a transaction report for each account code that receives auto-applied transactions and scan for anything that looks wrong. A rule that miscodes one transaction a month creates twelve errors before anyone reviews the year.

CORE
Unreconcile vs Remove & Redo
The job it does: undoes a bad reconciliation — in two different ways.

These get confused constantly, and choosing wrong either leaves an orphaned transaction or destroys one you needed. The distinction is straightforward once stated:

Unreconcile breaks the match between the statement line and the transaction, leaving both in place. Use it when the transaction in Xero is correct but was matched to the wrong statement line — you're fixing the pairing, not the record.

Remove & Redo deletes the created spend or receive money transaction and returns the statement line to the reconcile queue. Use it when the transaction itself is wrong — a duplicate, or something coded so badly it's easier to redo than repair.

The test: is the Xero transaction correct? If yes, unreconcile. If no, remove and redo.

ADVISOR  ROLE REQUIRED
Assurance dashboard
The job it does: shows you what was done manually, and by whom.

Covered above as a diagnostic, but it earns a second mention because it's equally useful at the end. Re-run it after the cleanup to confirm nothing was manually marked as reconciled or manually deleted during the work itself — including by you. In a long cleanup it's easy to take a shortcut in week one and forget it by week three.

CORE
Manual journals and conversion balances
The job it does: corrects what transactional tools can't reach.

Some corrections have no transaction to edit — clearing a suspense balance to its proper accounts, writing off unreconcilable historical items, correcting opening balances that were wrong from the file's creation, or fixing anything Find & Recode won't touch.

Where the problem is the starting position rather than the transactions, conversion balances are the right tool: they set what the opening position should have been rather than layering corrections on top of a wrong foundation. Narrate every journal properly — a correcting journal with no explanation is a problem for whoever reads the file next, which may well be you.

CORE
Archiving accounts and contacts
The job it does: tidies the chart of accounts and contact list without breaking history.

Accounts and contacts with transaction history can't be deleted — they can only be archived, which removes them from selection lists while preserving the history behind them. That's the correct behavior, even though it frustrates people wanting a truly clean list.

The workflow for retiring a redundant account is: recode its transactions to the account you're keeping, confirm the balance is zero, then archive it. Same for duplicate contacts — recode first, then archive, so nothing is orphaned.

Establish the last known-good date

Compare bank statement balances to Xero month by month until they agree. That date is your scope boundary — and knowing it prevents you re-examining years that were always fine.

Fix the chart of accounts first

If the coding structure is wrong, fix it before importing anything. Coding thousands of transactions into a broken structure means recoding them all later — the one case where structural work precedes data work.

Get all the data in

Import statement files for periods the feed doesn't cover, checking the joins for duplicates. Enter missing bills and invoices. Completeness before correctness — you can't diagnose a file that's still missing data.

Set up bank rules

Write narrow rules for genuinely recurring transactions before the bulk processing run. Every rule written now is coding you don't repeat across every month in scope.

Bulk process with cash coding

Work through the unreconciled backlog in the cash coding grid, grouping identical transactions. Set aside anything relating to an invoice, bill or transfer — those go through the standard reconcile screen instead.

Bulk correct with Find & Recode

Now that the data is complete, diagnose properly and correct in bulk. Use the journal option rather than editing source transactions when correcting closed or previously reported periods.

Clear the residue

Suspense and holding accounts investigated and cleared to zero. Genuinely unresolvable items written off with documented reasoning and approval, not left to age into the next person's problem.

Agree, review, publish, lock

Every bank and card account agreed to its statement. Balance sheet reviewed line by line. Publish the corrected reports and set the lock date, so the work you just did can't quietly come undone.

What Xero won't do for you

Three limitations worth knowing before you plan: there is no native way to merge two accounts in the chart of accounts — you recode into the surviving account and archive the other. There is no bulk void for invoices, so those are handled individually. And inventory items can't be merged either; the approach is to retire the old item and use the new one.

  Every bank and card account agrees to its statement at each month end in the cleaned period.

  Suspense, clearing and "Ask My Accountant" accounts are all at zero.

  Aged payables and receivables tie to their control accounts in the general ledger.

  Every balance sheet line can be explained and evidenced.

  Transfers between your own accounts are coded as transfers, not as income and expense.

  The chart of accounts has no duplicate or near-duplicate accounts still in use.

  Contacts have been consolidated, with redundant records archived rather than orphaned.

  Write-offs are documented with reasoning and were approved by someone other than whoever posted them.

  Corrected reports are published and the period is locked.

  The reason the file drifted has been addressed — otherwise you'll be doing this again.

That last one matters most. Files don't fall behind because of a software problem. They fall behind because nobody owned the monthly routine, or because the person who did left, or because the work outgrew the arrangement. A cleanup that fixes the data without addressing the cause buys you a year at best.