A data event wearing an admin costume
A bank switch gets planned like a change of address. Tell the people who need to know, move the payments, update the details. That framing is not wrong and it is incomplete, because the parts that cause trouble months later are all in the records rather than in the logistics.
By the end of it you have two accounts where you used to have one, a month that belongs half to each, a large movement between them that is not income or expense, and a set of recurring payments whose true state is knowable only from the old account's statements.
Most of that is easy to handle if you know it is coming. One item is not, and it is the reason to read this before rather than after: the moment the old account closes, self-service access to its history goes with it.
The deadline nobody sets
Everything else in this article can be fixed later with effort. Getting statements out of the old bank is the one that gets structurally harder, and there is a specific moment after which it changes character.
While the account is open you can log in and download. Once it is closed you can request, which means writing to the bank, possibly proving identity, possibly paying a fee, and waiting — sometimes for weeks. That is a completely different proposition when a filing deadline is a fortnight away.
So the first task in any switch is not administrative. Download the statements for the current financial year and the one before it, before anything else happens. If the account has been open longer and nobody has been collecting statements as they were issued, take everything the bank will give you.
The order that matters
The transfer that gets counted as income
The single most common accounting error in a bank switch. A balance of, say, 40,000 moves from the old account to the new one. In the old account's statement it is a payment out. In the new account's statement it is a receipt in.
Recorded naively, that becomes an expense of 40,000 and income of 40,000. Turnover is overstated, costs are overstated, and profit is unchanged — which is exactly why nobody notices. The bottom line looks right, so the error survives.
It is a transfer: an internal movement between two accounts you own. It belongs on the balance sheet, moving money from one asset to another, and it does not touch the profit and loss at all.
Notice why reconciliation cannot help here. The money genuinely left the old account and genuinely arrived in the new one, so both statements agree with the ledger perfectly. Nothing in the arithmetic knows the two entries describe the same money — a limitation covered in what "reconciled" actually proves.
The consequences show up where turnover matters rather than where profit does: registration thresholds, covenants, ratios, and any figure a reader compares year on year.
The split month
A switch rarely happens on the first of a month. So one period has activity on two accounts, and the instinct to treat it as one bank position is the second common mistake.
Each account has its own balance chain. The old one runs from its opening balance to whatever it held when it stopped; the new one runs from zero or its opening deposit to its month-end figure. Neither chain continues into the other, and adding them together produces a number with no arithmetic meaning.
So reconcile twice. Old account, on its own terms. New account, on its own terms. The combined cash position for reporting is the sum of the two closing balances — but the reconciliation is two separate exercises, and treating it as one is how the transition month becomes unreconcilable.
This is the same principle as a statement covering multiple accounts, where one opening and closing pair cannot span several chains. Two accounts, two chains, two checks.
Two accounts, both live
Keep both bank accounts open in the ledger for as long as either has activity. This sounds obvious and is regularly got wrong, because closing the old one feels like completing the task.
Close it too early and late transactions have nowhere to go. They end up forced into the new account, where they will never reconcile because the bank has no such entry, or into a suspense account, where they become somebody's problem at year end. Both are harder to unpick than simply leaving the account open.
The right closing moment is when three things are true: the balance is zero, you hold the final statement, and nothing has arrived for a reasonable period afterwards. Then close it deliberately and note the date, so a later reader knows the account ended rather than wondering where it went.
What did not move
Recurring payments are the part everyone believes is handled and frequently is not. Some transfer automatically, some require the counterparty to act, and some are simply forgotten because nobody remembered they existed.
The failure has two flavours. A payment still drawing from the old account creates transactions on an account nobody is watching any more. A payment that stopped entirely — because the mandate did not move and the old account closed — means a supplier, subscription or obligation is now unpaid, and you find out when someone chases.
The reliable way to find them is to work from the statements rather than from a list. Take twelve months of the old account, extract every recurring payment and receipt, and check each one against the new account. A list of what you believe is set up will always be shorter than what the statements show, because the statements include the ones you forgot.
Twelve months matters. Annual charges — insurance, licences, subscriptions, professional fees — appear once, and a three-month sample will miss every one of them.
Arrivals after you thought it was over
An account that has been emptied is not necessarily finished. Interest can be credited for the final period. Fees can be applied in arrears. A refund can arrive from a supplier who still had the old details. A customer can pay into the account months later.
Each of those creates entries after the point where most people consider the switch complete, which is precisely why they get missed. The ledger account has been closed, nobody is reconciling, and the transaction lands in a place no one is looking at.
Obtain the final statement after the last movement rather than on the day you empty the account. And keep the ledger account open until the tail genuinely stops — in practice a couple of months, longer if annual charges are involved.
Where the account has already closed and something arrives afterwards, the bank will usually return or forward it. Find out which, because the two produce very different entries.
The account you can no longer download
Once closed, an account has no login, no download and no feed. This is worth stating plainly because it defeats a whole category of tooling that people assume will cover them.
An automatic bank connection cannot be established retrospectively to an account that no longer exists. Whatever your accounting system does with live feeds, the period before the switch has to come from documents — which is a structural limit rather than a gap in any particular product.
So the PDF statements you downloaded become the only machine-readable route to that period. Converting them is straightforward; obtaining them after the fact is the part that takes weeks. That asymmetry is the entire argument for doing it first.
If you are reading this having already closed the account with nothing saved: request statements from the bank in writing now rather than at the deadline, and search your own archives in parallel. Statements attached to old emails, saved to a shared drive, or sent to an accountant are usually faster than the bank, and a PDF from an archive is exactly as usable as one downloaded today.
Cards, and moving more than one account
Most switches are not a single account. There is usually a card, often a deposit or savings account, sometimes a currency account or one opened for a specific project. Each is a separate balance chain with its own statements and its own closure.
Cards deserve particular attention because they behave differently. A card statement runs on its own cycle, which is rarely the calendar month, and it settles from the current account — so closing the current account while a card balance is outstanding creates a settlement with nowhere to draw from. Sequence matters: settle and close cards before the account that funds them.
There is also a timing quirk worth expecting. Card transactions authorised before the switch can settle after it, so a purchase made on the old card can appear on a statement dated after you believed everything had moved. Those are real transactions belonging to the old account, and they need capturing.
Handle each account as its own project: its own history download, its own final statement, its own closure date, its own ledger account kept open until its tail stops. The temptation is to treat the switch as one event with one checklist, and the accounts do not close at the same time or in the same way.
One practical consequence: when you later gather the year's statements, you have several series rather than one. Each series needs its own continuity check, because a gap in the card statements is just as invisible as a gap in the current account's.
What to collect before anything closes
One pass, while access still exists. Everything here becomes materially harder afterwards.
| Collect | Why | How hard afterwards |
|---|---|---|
| Statements, current financial year | The period you will be reporting on | Requestable, slow |
| Statements, prior year | Comparatives and any late adjustment | Requestable, slow |
| Everything older the bank offers | Last easy chance at the archive | Often much harder |
| The final closing statement | Proves the account ended at zero | Only issued after closure |
| Twelve months of transactions as data | To find every recurring item | Derivable from statements |
| List of mandates and standing orders | To check what moved | Not always available later |
| Account and sort details on file | For matching historic entries | Easy to lose track of |
Download statements as the bank's own PDF rather than a screen export where you have the choice. The PDF is the document of record, it carries the printed opening and closing balances that make completeness checkable, and it is what an auditor or lender will expect to see.
Reconciling the transition
Do the old account first and finish it completely. It has a defined end, which makes it the easier of the two, and closing it out properly means the remaining work only concerns one account.
Reconcile it from its opening balance at the start of the period through to its final closing figure. The last reconciliation of a closing account should end at zero, and if it does not, something has not been captured — that is a useful, unambiguous test you only get once.
Then the new account, from zero or its opening deposit forward. Its first month often contains a handful of oddities as mandates arrive at different times, so expect the transition month to be untidy and the following one to look normal.
Confirm the transfer appears on both sides — as a payment out of the old and a receipt into the new, for the same amount, on dates a day or two apart — and that it is booked once, as a transfer.
Proving the records are complete
A bank switch is one of the most common places for a gap in a statement series, because responsibility for collecting statements is exactly what gets dropped while everything is changing.
Test each account's series independently: within one account, every statement's closing balance should equal the next statement's opening balance, exactly. The switch does not join the two chains — it ends one and begins another — so you are proving two unbroken series rather than one.
Then test each document on its own: opening balance plus every transaction should equal the printed closing balance. Together those two checks establish that no statement is missing from either account and no rows are missing from any statement.
Both tests, and why they have different blind spots, are covered in the missing month problem. The switch is the single most likely moment for the failure they catch.
Errors specific to a switch
Every one of these produces books that look fine. That is the theme.
| Error | What it does | How to catch it |
|---|---|---|
| Transfer booked as income and expense | Inflates turnover and costs equally | Look for a large matched pair around the switch date |
| Transfer booked only once | Cash position wrong by the amount | Both accounts fail to reconcile |
| Two accounts reconciled as one | Meaningless combined position | Reconcile each chain separately |
| Old ledger account closed early | Late items forced elsewhere or into suspense | Keep it open until the tail stops |
| Missing statement across the switch | A period absent from both records | Continuity check within each account |
| Mandate still drawing on the old account | Transactions nobody is watching | Twelve-month recurring-item comparison |
| Mandate stopped entirely | An obligation silently unpaid | Same comparison, opposite direction |
| Final interest or fees missed | The account never truly closes at zero | Obtain the final statement after the last movement |
A worked example
A company moves banks on 18 September. The balance of 41,300 transfers on the 19th. The old account is emptied and left open; the new one starts taking receipts immediately.
September is reconciled as two exercises. The old account runs from its 1 September opening balance to 0 on the 30th, and it balances. The new account runs from 0 to its month-end figure, and it balances. Combining them would have produced nothing usable.
The transfer is booked once, as a movement between two asset accounts. Had it been recorded as a payment and a receipt, September turnover would have been overstated by 41,300 with profit entirely unaffected — invisible in the numbers most people check.
A twelve-month extract of the old account shows twenty-three recurring items. Twenty had moved. Two were annual — an insurance premium and a professional subscription, neither due for months, neither in anyone's list. One was a small monthly charge still drawing on the old account, found only because the account was still open and still being reconciled.
In November, interest of 4.12 and a supplier refund of 380.00 arrive on the old account. Both are captured because the ledger account is still open. It is closed in January, at zero, with the final statement on file.
| Step | What was done | What it prevented |
|---|---|---|
| Before switching | Downloaded two years of statements | Weeks of waiting on a closed-account request |
| Transfer | Booked once as an internal movement | Turnover overstated by 41,300 |
| September | Reconciled both accounts separately | An unreconcilable combined position |
| Recurring items | Compared twelve months against the new account | Three missed mandates, two of them annual |
| Nov–Jan | Kept the old ledger account open | Late interest and a refund lost to suspense |
| January | Closed at zero with the final statement | An account that never formally ended |
What happens at year end
A switch draws attention. Whoever reviews the year — an accountant, an auditor, a lender — will look at the transition, because it is a known weak point for completeness and cut-off.
Expect three questions. Is the old account's record complete up to closure? Was the transfer treated as an internal movement rather than as trading? Does anything fall between the two accounts — a period, a transaction, a mandate?
All three are short conversations if the documents are in hand and both series are provably unbroken. All three are expensive if the answer involves requesting statements from a bank you no longer have a relationship with.
Keep the final statement of the closed account somewhere obvious. It is the single document that proves the account ended at zero, and it is the one nobody can reissue conveniently.
The checklist
In order. The first item is the only one that becomes irreversible.
| When | Do | Why |
|---|---|---|
| Before anything | Download all available statements | Access ends with the account |
| Before switching | Extract twelve months of recurring items | Annual charges hide in a short sample |
| At switch | Open the new account in the ledger | Both accounts must coexist |
| At transfer | Book it as an internal movement | Prevents overstated turnover |
| Transition month | Reconcile each account separately | The chains do not join |
| Following month | Check every recurring item arrived | Finds mandates that did not move |
| Two months on | Check for late interest, fees, refunds | The tail is real |
| Before closing | Obtain the final statement | Proves the account ended at zero |
| At year end | Verify continuity within each account | The switch is the likeliest gap |
Key takeaways
Download the old account's history before anything else happens. Every other problem here is fixable later; a closed account turns self-service into a written request with a waiting time you do not control.
Book the transfer as an internal movement, not as income and expense — the error leaves profit unchanged, which is why it survives every check that looks at the bottom line. And reconcile the two accounts separately through the transition, because their balance chains do not join.
Then find what did not move, using twelve months of statements rather than a list, and keep the old ledger account open until the tail of interest, fees and late arrivals genuinely stops. A switch is finished later than it feels.
Frequently asked questions
Turn the closed account into usable data
No feed can reach an account that no longer exists. Convert the statements you downloaded into a single sheet, with every document checked against its own arithmetic and the whole series tested for gaps.