It's 10pm on a Wednesday. You've opened Xero to reconcile a client's accounts before the VAT deadline on Friday. You click into the bank transactions screen, expecting the usual stream of neatly imported entries.
Nothing. Last transaction imported: six days ago. The bank feed is down. Again.
You check the connection status — "Reauthorisation required." The client didn't click the renewal email. Or their online banking password changed. Or the bank updated its API and your accounting platform hasn't caught up yet. It doesn't matter why. What matters is you have 45 minutes of reconciliation to do and no data to do it with.
This is the moment every UK bookkeeper knows. The moment you realise that bank feeds — for all their convenience when they work — are a single point of failure. And when they fail, you're left with a choice: wait (and miss your deadline), or find another way.
This guide is about that other way. It's an honest comparison of bank feeds and bank statement conversion — not marketing fluff, but a practical framework for when to use each, what actually breaks, and how to build a workflow that keeps you productive no matter what the bank's API is doing tonight.
If you're currently staring at a broken feed and need a fix right now, skip to What to Do When Your Bank Feed Breaks — it covers your immediate next steps.
What Bank Feeds Actually Are (And What They Aren't)
Let's start with the basics, because there's a surprising amount of confusion about what a bank feed actually does — and what it doesn't.
How Bank Feeds Work
A bank feed is a direct data connection between your accounting software (Xero, QuickBooks, Sage, FreeAgent) and your client's bank account. It uses Open Banking APIs — the same regulated framework that powers everything from Monzo's app to your mortgage broker's affordability check. Once authorised, the feed pulls new transactions automatically, usually once a day, and drops them into your accounting platform's reconciliation screen.
When it works, it's brilliant. Transactions appear without anyone lifting a finger. You reconcile by matching imported entries against invoices and receipts. The whole system feels frictionless — right up until it doesn't.
What Bank Feeds Don't Do
This is the part that catches people out. Bank feeds do not:
- Go back more than 90 days — Open Banking regulations typically limit historical data access to the last 90 days of transactions. Need last year's statements for a tax return? The feed can't help.
- Work with every bank — Only the CMA9 (the UK's nine largest banks) are required to offer Open Banking. Building societies, specialist banks, and many business account providers either don't participate or offer limited access.
- Work with every account type — Joint accounts, trust accounts, and some business accounts have restricted or no feed support even at banks that otherwise offer it.
- Stay connected forever — FCA regulations require reauthorisation every 90 days. Miss the renewal and the feed stops silently.
- Handle PDF statements from clients — When a new client hands you two years of PDF bank statements at onboarding, the feed can't touch them.
Why Bank Feeds Break (And Why You're Googling This at 10pm)
If you're reading this at an unsociable hour, you've probably just discovered that a bank feed has stopped working. You're not alone — broken bank feeds are one of the most common complaints on AccountingWEB forums, in bookkeeping Facebook groups, and in the Xero and QuickBooks community boards. Here's exactly what's going wrong:
1. The 90-Day Reauthorisation Cliff
Under FCA Open Banking regulations, bank feed access must be reconfirmed every 90 days. The bank sends a renewal prompt — usually an email or an in-app notification — to the account holder. If the account holder is your client and they either miss the email or don't understand what it's for, the feed disconnects. Your accounting software won't always alert you proactively — the transactions just stop appearing. You discover it when you sit down to reconcile, which is why it's always 10pm on a deadline night.
2. Bank-Side API Changes
Banks update their online banking platforms and APIs regularly. When they do, the feed provider (Xero's Yodlee integration, QuickBooks' Open Banking connector, etc.) needs to update their integration to match. This lag can be hours, days, or — in the worst cases — weeks. During that window, your feed is dead and there is nothing you can do to fix it from your end.
3. Authentication Drift
If a client changes their online banking password, resets their MFA method, or their bank introduces a new security step (which happens frequently in the UK as banks tighten fraud controls), the stored authentication token becomes invalid. The feed breaks. And unlike a password reset on a website, there's no "click here to update" button — you often have to disconnect and reconnect the entire feed, which can trigger a fresh 90-day countdown.
4. Banks That Simply Don't Play Ball
Some UK banks offer Open Banking in theory but deliver a frustrating experience in practice. Nationwide business accounts are a notorious example — they don't offer CSV downloads through online banking, and their Open Banking feed can be intermittent. Virgin Money and Metro Bank have API implementations that some accounting platforms struggle with. And many smaller providers (Unity Trust, Cater Allen, Al Rayan) have no feed at all.
Every hour your bank feed is broken is an hour of manual data entry. Or it would be, if you didn't have a backup strategy. Let's look at what that strategy looks like.
What to Do When Your Bank Feed Breaks — The 10-Minute Recovery Plan
Before we dive into the broader comparison, here's your immediate action plan for right now, at 10pm, with a dead feed:
- Don't wait for the feed to fix itself. Feed outages can last hours or days. If you have a deadline, waiting is not a strategy — it's procrastination dressed as patience.
- Log into the client's online banking directly. You have authority to do this (you're their bookkeeper). Navigate to the statement or transaction history view for the period you need to reconcile.
- Download the statement. Look for an export or download option. CSV is ideal. PDF is more common — especially for business accounts and older statements. If neither is available, take a screenshot of the transaction list (last resort).
- Convert the statement to Excel or CSV. Upload the downloaded file to a bank statement converter that understands UK bank formats. BankScan AI handles all 16+ major UK banks and outputs a clean spreadsheet in under 30 seconds.
- Import into your accounting software and reconcile. Most platforms accept CSV imports directly. Xero, QuickBooks, Sage, and FreeAgent all have manual import options. Get the reconciliation done now, and sort out the feed reconnection when you're not under time pressure.
Bank Feeds vs Statement Conversion: The Honest Comparison
Now that we've covered why feeds break and what to do about it, let's compare the two approaches on their actual merits — not marketing promises, but real-world behaviour.
| Criteria | Bank Feeds | Statement Conversion |
|---|---|---|
| How it works | Direct API connection to bank servers via Open Banking | Upload a statement file (PDF/CSV/scan), AI extracts transactions into structured format |
| Speed (per statement) | Automatic — transactions appear daily without any action | Under 30 seconds upload-to-Excel with a purpose-built converter |
| Reliability | Depends on client reauthorising every 90 days, bank API stability, and platform integration | Always works — if you have the statement file, you can convert it |
| Historical access | Limited to ~90 days of transactions under Open Banking regulations | Unlimited — works with statements from any date, including archived and scanned paper statements |
| Bank coverage | CMA9 banks only (9 largest UK banks). Building societies and specialist banks often excluded. | Any bank, any account type — if a statement exists, it can be converted |
| Client onboarding | Requires client to authorise access — can take days if client is slow to respond | Immediate — client hands you PDFs at the first meeting, you convert them same day |
| Ongoing maintenance | Reauthorisation every 90 days. Breaks on password changes, MFA updates, bank API changes | Zero maintenance — statement files don't expire or disconnect |
| Data independence | Cannot access transaction data if feed is disconnected | Works with any statement file you have — downloaded, emailed, or scanned |
| Best for | Day-to-day transaction flow on supported accounts with attentive clients who reauthorise on time | Historical data, unsupported banks, onboarding, feed failures, year-end verification, and any situation where "waiting" isn't an option |
When Bank Feeds Win — And You Should Absolutely Use Them
This isn't an anti-feed argument. Bank feeds are the right tool for a specific job, and when that job lines up with what feeds are good at, they're the best option available.
Use Bank Feeds When:
- You're managing day-to-day transaction flow — For ongoing bookkeeping where transactions trickle in daily, feeds eliminate the need to download and convert statements every day. This is their sweet spot.
- The client's bank is well-supported — Barclays, HSBC, Lloyds, NatWest, and Santander all have mature Open Banking APIs that work reliably with major accounting platforms. If your client banks with a CMA9 institution, feeds are likely stable.
- The client is responsive — If your client clicks reauthorisation emails within 24 hours, the 90-day renewal is a minor inconvenience, not a workflow blocker.
- You're doing high-frequency reconciliation — Practices that reconcile weekly or daily benefit enormously from feeds because the transaction volume per session is small and manageable.
Where Feeds Excel
- Zero manual effort for daily transaction import
- Near-real-time visibility of client cash positions
- Automatic categorisation rules in most platforms
- Seamless when everything is configured correctly
Where Feeds Fall Short
- Silent failures — you discover the problem when you reconcile
- No historical data beyond 90 days
- Unsupported banks and account types
- Dependency on client action (reauthorisation)
When Statement Conversion Wins — The Safety Net Every Practice Needs
Statement conversion is not a competitor to bank feeds — it's the backup that catches everything feeds drop. Here's when it's not just useful, but essential.
Use Statement Conversion When:
- A bank feed has broken and you have a deadline — This is the scenario that drives bookkeepers to Google at 10pm. Statement conversion means you download the PDF from online banking, convert it in 30 seconds, and reconcile tonight — instead of waiting days for a feed to reconnect.
- You're onboarding a new client — New clients bring historical statements — often two years' worth, in PDF format, from multiple banks, some scanned from paper. Feeds can't touch any of this. A statement converter processes the entire batch while you work on something else.
- The bank doesn't offer Open Banking feeds — Nationwide (no CSV export), Virgin Money (limited API), Metro Bank (inconsistent), building societies, and specialist banks. If there's no feed, conversion is the only automated option. The alternative is manual data entry.
- You need historical data for tax returns or MTD — Making Tax Digital requires accurate transaction-level data going back further than 90 days. Bank feeds can't provide this. Statement conversion can — for any year, any bank, any format.
- You're verifying feed data at year-end — Smart practices cross-reference feed-imported transactions against original bank statements at year-end. It's a professional scepticism step that catches missing transactions and feed gaps before they become problems.
The Hidden Cost of Not Having a Backup
Every bookkeeping practice has moments when bank feeds fail. The practices that handle these smoothly have a conversion workflow ready. The practices that don't have a conversion workflow spend those hours doing manual data entry — typing transaction after transaction from a PDF into Excel, one line at a time. At 20–45 minutes per statement, a single broken feed on a monthly client can cost hours. Across a practice with 20 clients, the annual cost of not having a backup is measured in days, not hours.
UK Bank Feed Pitfalls: Bank by Bank
Not all bank feeds are created equal. Here's what to expect from the major UK banks — based on real bookkeeper experiences, forum discussions, and our own testing across 16+ UK bank formats.
CMA9 Banks — Feed Support Overview
| Bank | Feed Reliability | CSV Export Available? | Common Pain Points |
|---|---|---|---|
| Barclays | Generally stable | Yes — personal and business | Business account MFA can interfere with feed reconnection. CSV formatting is clean but dates are sometimes US-formatted. |
| HSBC | Moderate — feed works but requires frequent reauthorisation | Personal: yes. Business: PDF-only | Multi-line transaction descriptions break CSV structure. Business accounts are PDF-only — the feed is the only automated path, making failures more painful. |
| Lloyds | Generally stable | Yes — most account types | Business account CSV export uses non-standard column ordering that some platforms misinterpret. |
| NatWest | Generally stable | Yes — most account types | Feed reconnection sometimes requires full disconnect/reconnect rather than simple renewal. |
| Santander | Moderate — platform-dependent | Yes — personal and business | Feed integration varies by accounting platform. Xero support is solid; QuickBooks can be intermittent. |
| Nationwide | Intermittent — business accounts particularly problematic | No CSV export from online banking | No CSV download option at all. Open Banking feed is unreliable for business accounts. This is the bank that drives the most conversion need. |
| Virgin Money | Limited — API coverage is patchy | Limited — account-dependent | API implementation is newer and less mature than other CMA9 banks. Not all accounting platforms fully support it. |
| Metro Bank | Inconsistent — platform-dependent | Yes — most account types | Feed connection stability varies. Some bookkeepers report it works flawlessly; others have persistent disconnection issues. |
Non-CMA9 Banks — No Feed, No Problem
Banks outside the CMA9 — including building societies (Coventry, Yorkshire, Skipton), specialist banks (Cater Allen, Unity Trust, Al Rayan, Cashplus), and some digital-only providers — typically have no Open Banking feed at all. For these accounts, statement conversion isn't a backup — it's the primary workflow. The good news: because there's no feed to maintain, there's nothing to break. Download the statement, convert it, import it, done.
The Hybrid Approach That Actually Works
The most efficient UK bookkeeping practices don't choose between bank feeds and statement conversion. They use both as complementary tools in a single workflow:
- Bank feeds for day-to-day flow — Connect every supported account to your accounting platform's feed. This handles 80% of your transaction volume with zero manual effort.
- Statement conversion for everything feeds can't reach — Unsupported banks. Historical statements. Client onboarding. Broken feeds. Year-end verification. Keep a converter like BankScan AI bookmarked for these moments.
- Monthly feed health check — Once a month, spend 5 minutes checking that all client feeds are still connected and importing. Catch disconnections before they become deadline-night emergencies.
- Year-end cross-reference — At year-end, download the original bank statements for each client and spot-check a sample against your feed-imported data. This catches feed gaps, duplicates, and data corruption before they become compliance issues.
This hybrid approach means you get the automation of feeds when they work, the reliability of conversion when they don't, and you never tell a client "I can't reconcile your accounts because your bank feed is down."
Real-World Scenarios: What Would You Do?
Scenario 1: The 10pm VAT Deadline Emergency
It's Wednesday night. VAT return due Friday. One client's HSBC business feed has been silent for six days. Reauthorisation email went to the client, who hasn't opened it. You need the last week of transactions now.
The feed-only approach: Call the client (unlikely to answer at 10pm), explain how to reauthorise, wait. Return tomorrow, hope it's fixed, rush the reconciliation. Risk: it's not fixed, and you're doing a Thursday night panic instead of a Wednesday night one.
The hybrid approach: Log into HSBC online banking, download the last week's statement as a PDF, upload to BankScan AI, get a clean CSV in under 30 seconds, import into your accounting software, reconcile. Done by 10:30pm. Sort out the feed reconnection tomorrow morning when the client is awake.
Scenario 2: New Client Onboarding
New client signs. Hands you two years of statements — 24 PDFs from three different banks including Nationwide (no CSV export) and a building society savings account (no feed at all). First meeting is tomorrow and you want to show them you're on top of things.
The feed-only approach: Set up feeds for the two banks that support them. Wait for 90-day history to populate. For Nationwide and the building society, there is no feed path — you'll be doing manual data entry for these accounts regardless. Client waits a week for you to be "set up."
The hybrid approach: Upload all 24 PDFs to BankScan AI as a batch. Get clean Excel files for every statement in minutes. Import the data into your platform. Walk into the first meeting with their full transaction history already loaded. Set up feeds for the supported accounts afterwards, as a nice-to-have, not a blocker.
Scenario 3: Year-End Verification
It's December year-end for a limited company client. You've been using feeds all year, but you need to be certain the data is complete before finalising the accounts and submitting to HMRC.
The feed-only approach: Trust the feed data. Hope nothing was missed. Submit. This is what most practices do — and it's a compliance risk. If a feed gap went unnoticed in March, you won't discover it now.
The hybrid approach: Download the original bank statements for the full year. Convert them all to Excel with BankScan AI. Run a quick reconciliation between the feed data and the statement data. Any discrepancies surface immediately. Fix them before submission. Sleep better.
When Your Bank Feed Breaks, Don't Wait — Convert
BankScan AI handles all 16+ major UK bank formats — including the tricky ones like HSBC, Nationwide, and First Direct that other converters struggle with. Upload any statement PDF or CSV and get a clean Excel file in under 30 seconds. Free first conversion, no credit card needed.
Try BankScan AI Free →Frequently Asked Questions
Why do bank feeds keep disconnecting in the UK?
UK bank feeds disconnect for three main reasons: (1) Open Banking 90-day reauthorisation — FCA regulations require you to re-consent every 90 days, and missing the renewal email or in-app prompt breaks the connection silently. (2) Bank-side changes — when a bank updates its online banking platform or API, the feed provider's integration can break until they deploy a fix, which can take days or weeks. (3) Multi-factor authentication changes — if a client resets their password or changes their MFA method, the stored authentication token is invalidated. The result: transactions stop importing without warning, and you only discover it when you sit down to reconcile.
Which UK banks don't support Open Banking feeds?
While the CMA9 (the nine largest UK banks) are required to offer Open Banking access, the quality varies dramatically. Nationwide does not offer CSV exports through online banking and its Open Banking feed can be unreliable for business accounts. Virgin Money and Metro Bank have limited Open Banking APIs that some accounting platforms don't fully support. Many building societies and specialist banks (Cater Allen, Unity Trust, Al Rayan) have no Open Banking feed at all. Even among supported banks, features like historical transaction access (beyond 90 days) and joint account feeds remain inconsistent across providers. Always check your specific bank and account type before relying on a feed.
What's the difference between bank feeds and bank statement conversion?
Bank feeds connect directly to your bank's servers via Open Banking APIs and pull transactions automatically — usually daily — into your accounting software. Bank statement conversion takes a statement file (PDF, CSV, or scanned paper) and extracts the same transaction data into a structured format like Excel or CSV for manual import. Feeds are automatic but fragile — they break when connections fail or authorisation expires. Statement conversion is a manual trigger but works with any bank, any account type, and any time period — including historical statements a feed could never access. Most UK bookkeeping practices use both: feeds for day-to-day transaction flow on supported accounts, and statement conversion as the safety net when feeds fail or for unsupported banks.
How do I import bank statements when the bank feed is broken?
When your bank feed breaks, you have three immediate options: (1) Check reauthorisation — log into online banking, look for a 'renew access' or 'reauthorise' prompt, and reconnect the feed. This fixes most temporary disconnections. (2) Download a CSV or PDF statement from online banking and run it through a bank statement converter like BankScan AI to get clean Excel or CSV output, then import it manually into your accounting software. (3) For banks with no download option at all (some business accounts are PDF-only), use a converter that handles PDF extraction for your specific bank's format. The key insight: don't wait for the feed to fix itself while your reconciliation pile grows — convert the statement now, reconcile now, and sort out the feed connection afterwards.
Is statement conversion slower than bank feeds?
Per statement, yes — a bank feed imports transactions automatically while statement conversion requires downloading and uploading a file. But 'slower' assumes the feed is working. When a feed is broken, the alternative isn't 'feed vs conversion' — it's 'conversion vs manual data entry.' BankScan AI converts a bank statement PDF to Excel in under 30 seconds. Manual data entry of the same statement takes 20–45 minutes. In that comparison, conversion is dramatically faster. The productivity question isn't whether conversion is slower than a working feed — it's whether you have a reliable backup when the feed isn't working. Without one, every feed outage means hours of manual typing.
Can I use both bank feeds and statement conversion?
Yes, and this is exactly what most efficient UK bookkeeping practices do. Use bank feeds as your primary transaction pipeline for supported accounts — they handle the day-to-day flow automatically. But maintain statement conversion as your backup for: (1) clients whose bank feed has disconnected and won't reconnect quickly, (2) banks that don't offer feeds (Nationwide business, building societies, specialist banks), (3) historical statements beyond the feed's 90-day lookback, (4) client-provided PDFs when you're onboarding, and (5) year-end when you need to verify feed data against original statements. Having both tools means you never tell a client 'I can't reconcile your accounts because the feed is down.'
Does BankScan AI work when bank feeds fail?
Yes — BankScan AI is purpose-built for exactly this situation. When your client's bank feed disconnects, you can download their statement PDF or CSV from online banking, upload it to BankScan AI, and get a clean Excel or CSV file in under 30 seconds. It handles all 16+ major UK bank formats — including the tricky ones like HSBC (multi-line descriptions), Nationwide (no CSV export), and First Direct (abbreviated transaction codes). The output imports directly into Xero, QuickBooks, Sage, or FreeAgent. Rather than waiting for a feed to reconnect while your month-end deadline approaches, you keep moving — and handle the feed reconnection when you're not under time pressure. We've also published dedicated guides for Xero, QuickBooks, Sage, and FreeAgent imports if you need platform-specific help.
Last updated: 28 June 2026. BankScan AI supports 16+ UK bank formats — read our UK bank statement formats guide or browse all blog posts for UK accountants and bookkeepers.