What Your Accountant Fixes at Year-End (And Why)

Every March, UK accountants open client Xero files and find the same things. Not once in a while — reliably, predictably, every year. Mis-coded transactions dumped into General Expenses. Bank charges posted nowhere. Payments matched to the wrong invoice. A suspense account with £4,000 sitting in it that nobody can explain.

This work is not complicated. It is not interesting. It is billable at £150–£400 per hour because someone has to do it, and that someone is the accountant preparing your accounts. If your books are clean when they arrive, none of this happens. If they are not, you are paying your accountant to be a bookkeeper — at accountant rates.

Here is what they actually fix, and why it keeps happening.

The Named Problem: What the March Cleanup Actually Looks Like

A typical small UK limited company — trading company, professional services, e-commerce — might have 200–600 bank transactions a month. Over twelve months, that is up to 7,000 lines passing through Xero’s bank feed.

Xero’s automatic matching gets most of them right. The remainder — edge cases, unusual amounts, new suppliers, transactions that don’t map to a single invoice — get parked. Sometimes by the owner clicking “OK” without thinking. Sometimes by a bookkeeper choosing a wrong account because the right one isn’t obvious. Sometimes by Xero’s auto-suggestion that is technically accepted but contextually wrong.

By March, the accumulation looks like this:

Mis-coded transactions

Mis-coded transactions cost you more than you think. A £1,200 software subscription posted to “Office Supplies” instead of “Software.” A contractor invoice coded to “Materials.” A client entertainment dinner in “Travel.” None of these are catastrophic individually. Together, they corrupt your P&L categories, make your management accounts meaningless, and — when the miscoding affects VAT-rated items — create a VAT return problem that HMRC can query. HMRC estimates the UK VAT gap at £11.9 billion for 2024–25, with poor record-keeping cited as the primary cause for small businesses.

Unposted bank fees and charges

Bank charges, card payment terminal fees, Stripe processing costs, PayPal fees — these appear in the bank feed as small deductions and are routinely never posted to the correct expense account. They sit as unreconciled lines, or get buried in a catch-all account. By year-end, a business doing £60k in card-processed revenue might have £900–£1,800 of processing fees that are unaccounted for in the accounts.

Mismatched payments. A customer pays £2,340 but the invoice was for £2,400. The owner clicks “reconcile” in Xero and accepts the suggested match anyway. Now Xero thinks the invoice is settled — but there is a £60 shortfall that is either a short payment, a bank charge deduction, or a miskeyed invoice. The accountant has to find it.

Suspense account dumping

Xero does not have a native suspense account, but many businesses (and some bookkeepers) create one — a catch-all account for transactions they could not categorise at the time. The intention is always to come back and fix it. The reality is that suspense balances accumulate throughout the year. Suspense accounts should clear to zero at month-end; in practice, year-end reviews routinely find substantial unexplained balances.

Duplicate transactions

Bank feed resets, manual imports, or a misclick during reconciliation can introduce duplicate entries. A duplicated £3,500 supplier payment doubles the expense, understates your profit, and distorts the creditor balance. These are surprisingly common and seriously distort your financial picture — and they typically go unnoticed until a year-end review or an alert accountant spots an unexpected account balance.

Why The Conventional Approach Breaks

Xero’s bank feed and JAX

Xero’s automatic reconciliation handles clean, predictable transactions well: a standing order, a recurring direct debit, a single payment matched to a single invoice. JAX, Xero’s Anthropic-powered reconciliation layer, extends this to around 80% of typical transaction lines. The 20% it cannot confidently categorise — partial payments, fees, split transactions, new payees — gets left in the queue. Nothing forces a resolution. The queue grows. (For a direct comparison of Xero’s built-in rules against AI-driven approaches, see Xero Bank Rules vs AI: Which Should You Trust?.)

Manual coding by the owner

Most small business owners open Xero once a month, click through the reconciliation queue, and accept Xero’s suggestions. This is fast but imprecise. Xero’s suggestion is based on the payee name and amount; it does not know whether the £240 payment to “Amazon Business” is office supplies, IT hardware, or a book you bought for personal use and accidentally put on the company card. The suggestion lands somewhere. It may not be correct.

Periodic bookkeeper review

A bookkeeper on a monthly or quarterly cadence can keep things tidy — but only if they have the context to resolve ambiguous items. A transaction from two months ago with no reference, no invoice, and no email trail is hard to categorise correctly. Bookkeepers often make a best-guess on aged items. The best-guess is sometimes wrong.

The year-end accountant. The accountant receives the Xero file and starts from the assumption that the books are approximately correct. When they run a trial balance and find unexpected balances — a suspense account with £4,000, General Expenses three times higher than last year, bank charges unposted for twelve months — they start working backwards. That investigation is billable work on top of the standard fee. Year-end accounts for a small limited company typically cost £750–£1,500; messy books can push the final bill considerably higher.

How We’d Actually Solve It

TheBookkeeper.ai’s approach to this problem is not a better version of Xero’s bank feed suggestions. It is a different shape of thing entirely.

Each time a bank line lands in Xero, TheBookkeeper.ai reads it, reads your invoice and bill list, reads your chart of accounts, and reads your prior decisions on similar transactions. It does not suggest a category and wait for approval — it reasons about the correct posting and posts it, with a note explaining its reasoning in the transaction’s narration field.

Posting bank charges automatically

For a bank charge from your payment terminal provider:

• It identifies the payee as a known card processing service
• It checks your chart of accounts for an existing payment processing fees account (typically 7900 or similar in a standard Xero setup)
• It posts the charge to that account, with the transaction amount and date
• It marks the bank line reconciled

Resolving short payments in real time

For a customer payment that is £60 short of the invoice:

• It reads the invoice, reads the payment amount, and recognises the discrepancy
• It checks whether prior payments from this customer have a pattern of small deductions (a standing deduction, or a regular settlement convention)
• If the pattern is clear, it posts a credit note for the £60 difference and settles the invoice
• If there is no pattern, it flags the item: “Payment £60 short of Invoice 1047. Possible short payment or deduction. Proposed handling: raise credit note. Approve or override?”

The flag arrives as a notification, not a growing queue. The proposed resolution is already formed. One tap to approve.

What it writes to Xero:

• The bank line is reconciled against the invoice
• The narration records: “Settled INV-1047 in full. £60 credit note raised for short payment — confirmed by user 12 Jun 2026.”
• The suspense account is never touched, because the transaction never needed to go there

By the end of the month, there is no queue. There is no suspense balance. The chart of accounts holds transactions coded to the right place, with reasoning attached. When the accountant opens the Xero file in March, there is nothing to unpick.

Worked Example

The scenario

Scarlet Ibis Ltd is a twelve-person digital agency based in Bristol. They invoice clients monthly, pay a small roster of freelancers, and process around 180 bank transactions a month. They have been doing their own Xero reconciliation, spending roughly two hours a month working through the queue. Their accountant charges a standard £1,200 year-end fee.

In March of their first year, their accountant calls with a list:

• General Expenses is showing £8,400 — unusually high relative to prior years. On investigation: £2,100 of software subscriptions miscoded from “Software Licences,” two contractor invoices that should have gone to “Subcontractors,” and a laptop purchase that should have been capitalised as a fixed asset.
• A suspense account (improvised during a team handover) holds £3,840 across eleven transactions. Four are identifiable; the remaining seven require email archaeology.
• Bank charges and Stripe fees — £1,140 across the year — are sitting unreconciled in the bank feed. Nobody ever posted them anywhere.
• Two customer invoices show as “Awaiting payment” despite the customers paying months ago. The payments were matched to the wrong invoices. The actual outstanding invoices have since been chased unnecessarily.

The accountant spends roughly four extra hours sorting this. At their hourly rate, that is an additional £600–£800 on top of the standard fee.

What TheBookkeeper.ai would have done differently

Across the year:

Software subscriptions coded consistently to the correct account from the first transaction — the payee is known, the amount is consistent, and the chart of accounts has the right home. The laptop purchase is flagged immediately: “Single capital expenditure of £1,640 to John Lewis plc. Likely fixed asset — confirm capitalise or expense?” The owner approves. The asset is on the balance sheet from day one.

The suspense account is never needed because ambiguous transactions are flagged in real time, not parked. Each flag has a proposed resolution. The owner’s morning review takes three minutes.

Stripe fees post automatically each settlement, to the correct account, with the settlement date in the narration. Twelve months later, the bank feed is fully reconciled. The bank charges account shows £1,140 — correctly, cleanly, already in the right place.

The customer payment mismatches are caught on the day of receipt, not six months later when a chaser goes out unnecessarily.

The March call

The accountant opens the file. The trial balance is clean. The suspense account is zero. The bank feed is fully reconciled. The standard £1,200 fee stands. The extra £600–£800 does not apply.

Takeaway

• UK accountants spend a predictable portion of year-end preparation untangling the same categories of error: mis-coded spend, unposted fees, mismatched payments, and suspense account accumulation.
• These errors do not require bad intentions — they accumulate from Xero suggestions accepted without scrutiny, from ambiguous transactions parked and forgotten, and from bank charges that nobody ever thought to post.
• Poor in-year reconciliation is directly billable. Year-end accounts typically cost £750–£1,500 for a small limited company; messy books add hours on top.
• The solution is not a better year-end checklist. It is transactions coded correctly in the month they land, with the reasoning recorded, flags resolved in real time, and no suspense balance to explain. If you are still doing this yourself and wondering whether you should be, When to Stop Doing Your Own Bookkeeping sets out the threshold clearly.
• Clean books going into March are not a nice-to-have. They are the difference between a standard fee and an unexpected one.

Get on the list

If your accountant’s March call tends to start with “I found a few things,” your in-year reconciliation is doing the work your year-end bill should never have to cover. Get on the waitlist if you want your Xero to arrive at year-end already clean.

---

Sources:

• HMRC Measuring Tax Gaps 2024–25
• How Messy Xero Files Cost Accountants Time and Profit — Hill Bookkeepers
• Common Xero Bookkeeping Mistakes UK Businesses Make — Outbooks
• Xero Bookkeeping Clean Up: How to Fix Messy Accounts Properly — eCloud Experts
• Month-End in Xero: Closing Procedures — FHP Accounting
• How to Prepare for Your Financial Year-End in Xero — Linggard & Thomas
• How Much Do Accountants Charge for Year-End Accounts in the UK? — Eternity Accountants