I can tell you whether a new client's books have been done properly in about five minutes. I skip the P&L, skip the balance sheet, and go straight to the bank reconciliation screen.
Disclosure up front: I work at Xero. Read this as field notes from someone who uses the platform daily, not a neutral review.
TL;DR: Three quick checks on the bank reconciliation - age of unreconciled items, orphaned transfers, and manual journals hitting the bank account - tell me more about a client file's health than a full set of management accounts. I learned this in audit, and I use it every week in cloud practice.
Why Does the Bank Rec Tell You More Than the Accounts?
A trial balance is a summary. It hides problems behind round numbers. But the bank reconciliation is where every transaction has to land, and when things go wrong, they leave traces.
In my first year of audit at a mid-tier firm, a senior once glanced at a bank reconciliation and said "that file has been bodged." I asked how she knew. She pointed at three things. Those three things became my default check for every new Xero, QuickBooks, or FreeAgent file I open - and they catch problems about 70% of the time.
The AAT found that 40% of UK entrepreneurs have lost money because of poor accounting. In my experience, most of those losses trace back to reconciliation gaps that nobody checked.
What Are the Three Things I Check?
I run this in order. Each check takes about 90 seconds.
Check 1: How old are the unreconciled items? Open the bank reconciliation report. If there are items sitting unreconciled for more than 30 days, something is wrong. It might be a bounced payment nobody followed up. It might be a bank feed that imported a transfer as a standalone transaction. Either way, stale items mean nobody is reviewing regularly. Research from FinSheet AI suggests 68% of small businesses reconcile monthly or less - and that gap is where errors compound.
Check 2: How many orphaned transfers are floating? Transfers between accounts should always have a matched pair - money out of one account, money into another. When I see transfer entries sitting alone, it usually means someone coded a transfer as an expense or created a bank rule that catches one side but not the other. In Xero, the "Account Transactions" report filtered to the transfer code shows these fast. In QuickBooks, the bank transfers register does the same job.
Check 3: Has anyone posted manual journals directly to the bank account? This is the one that makes me nervous. In a well-run cloud file, the bank account balance should only move through bank feed reconciliation or properly matched payments. Manual journals hitting the bank account directly are either fixing a genuine error (fine, but should be rare) or papering over a reconciliation they could not figure out (not fine). More than two or three in a quarter and I want to see every one of them.
A Landlord File That Failed All Three
I onboarded a landlord client last year with three rental properties on a single Xero file. The previous bookkeeper had set up bank rules that auto-coded rental income - but the rules did not account for the agent splitting payments across two bank accounts. Result: six months of orphaned transfers, rental income double-counted in one file and missing in another, and a VAT return that was wrong by about £4,200.
The five-minute check would have caught the orphaned transfers on day one. The bookkeeper was coding transactions, but nobody was looking at the reconciliation as a diagnostic tool.
For comparison, a clean file looks boring. Unreconciled items are recent (last seven days at most). Transfers are matched. Manual journals to the bank account number fewer than two per quarter. When I see a file like that, I know I can trust the numbers downstream - and the year-end process is simpler because the source data is reliable.
The Gap Between Coding and Diagnosing
Yes, and that is the point. Most cloud-native practitioners go straight to coding transactions. They open the bank feed, match, suggest, approve, and move on. That workflow is efficient - but it skips the diagnostic step.
Audit teaches you to expect a number before you look at it. If monthly rental income should be around £1,800 and the bank feed shows £3,600, something has been imported twice. If direct debits are usually five per month and you see twelve, a feed reconnection has pulled historical data again. About 0.05% of all invoices are duplicate payments according to Docsumo's research - small in percentage terms, but in a high-volume file that adds up to real money.
I wrote about how six cloud platforms handle AI features recently. The AI tools are getting better at flagging anomalies automatically. But none of them replace this initial five-minute scan, because the scan is not about individual transactions - it is about the pattern of how the file has been maintained.
Can I Run This Check on My Own File?
Absolutely. If you use Xero, pull up the bank reconciliation report and filter for items older than 30 days. In QuickBooks, the reconciliation discrepancy report does a similar job. FreeAgent surfaces unreconciled items on the banking dashboard.
The three questions are the same regardless of platform: how stale are the unreconciled items, are there orphaned transfers, and has anyone journalled directly to the bank. If all three come back clean, your file is probably in good shape. If any one of them flags, dig into it before you run your next management report or VAT return.
UK accounting mistakes cost small businesses an average of £8,300 over their lifetime according to Intuit research cited by AAT. A five-minute check is cheap insurance against that.
FAQ
How often should I reconcile my bank feed in Xero or QuickBooks?
Weekly at minimum. Daily if your transaction volume is high. The longer you leave it, the harder it is to remember what a transaction was for - and the more likely that errors compound undetected. Xero recommends reconciling as frequently as transactions come in.
What causes orphaned transfers in cloud accounting software?
Usually a bank rule that catches one side of a transfer but not the other, or a manual payment entry where the corresponding receipt was never recorded. Feed disconnections can also cause it - one account reconnects and re-imports, creating duplicates on one side only.
Should I worry about manual journals to my bank account?
A few per year is normal - correcting a genuine posting error, for example. More than two or three per quarter is a flag. It often means someone could not reconcile a transaction and used a journal to force the balance. That hides the problem rather than fixing it.
If your bank reconciliation raises more flags than you expected, get in touch - I am happy to run through the file with you and show you exactly where the issues sit.