Open Banking has transformed UK bookkeeping. What used to be a CSV download and manual import is now a live, near-real-time feed of every transaction from your bank into your accounting software. The time savings are real — but live feeds also introduce failure modes that didn't exist before. This post walks through best practices and the pitfalls we see most often.
What Open Banking actually is
Open Banking is the UK regulatory framework that lets you authorise a third party (your accounting software) to read your bank transactions directly from your bank's systems, with bank-grade security and a 90-day re-authentication cycle. It's different from the older "scraping" feeds that relied on shared credentials. Today, every major UK bank — Lloyds, HSBC, Barclays, NatWest, Santander, Starling, Monzo, Revolut Business, Tide — supports Open Banking with Xero, QuickBooks, and FreeAgent.
Why live feeds matter
- Transactions appear within hours, not days.
- No manual CSV imports means no duplicate rows or date-format errors.
- Reconciliation becomes a daily five-minute job instead of a quarterly slog.
- Cash flow forecasting becomes credible, because the data is current.
Combined with bank rules, live feeds are the single biggest productivity gain in modern bookkeeping.
Pitfall 1: the 90-day re-authentication trap
Open Banking regulation requires you to re-authenticate the feed every 90 days. If you miss it, the feed stops, and transactions stop appearing. Worse, you might not notice for weeks. We've seen clients reconcile a "complete" month only to discover later that no transactions came in after day 91.
Best practice: set a calendar reminder for day 85, and have your bookkeeper monitor feed status weekly. Xero and QuickBooks both show a banner when re-auth is needed.
Pitfall 2: missing transactions on bank holidays
Some banks batch transactions over bank holidays and weekends. A Friday card payment might not appear until Tuesday. This isn't a feed failure, it's how the bank reports. Don't reconcile to "today's" balance — reconcile to the statement, which is the source of truth.
Pitfall 3: duplicate feeds
If you migrate from one accounting platform to another and don't disconnect the old feed, you can end up with two systems reading the same account. Less common with Open Banking than the old scraping feeds, but still worth a check. We always disconnect the old feed as the first step of any migration we run as part of our bookkeeping setup.
Pitfall 4: multiple accounts, single connection
Some banks let you authorise multiple accounts under one Open Banking connection — others require a separate connection per account. If you have, say, a current account and two savings accounts at HSBC, double-check all three are flowing. We've seen savings interest income missed for an entire year because only the current account feed was active.
Pitfall 5: FX accounts and multi-currency
Wise, Revolut, and Airwallex feeds need careful setup. Each currency is usually a separate account in your bookkeeping software, and you'll need to decide how to handle FX gains and losses at month-end. Get this wrong and your P&L misstates margin. Our team configures multi-currency bookkeeping for international clients — read about our approach to cross-border setups.
Pitfall 6: feed lag during disputes
If a card transaction is disputed, the bank may pull it back and reissue it later. The feed will show two postings for what's effectively one transaction. Match them as a transfer or use a clearing account.
Pitfall 7: trusting the feed over the statement
The bank statement is the legal record. The feed is a convenience. If they disagree, the statement wins. Don't reconcile to the cloud dashboard balance — reconcile to the downloaded statement.
Setup checklist for a clean feed
- One feed per bank account, all under the same connection if your bank allows.
- Connection authorised by a director with permanent banking access (not a bookkeeper who might leave).
- Re-auth reminder set for day 85 of every cycle.
- Bank rules built for top recurring transactions in month one.
- First reconciliation done against a real statement to confirm the feed is complete.
- Monthly "feed health" check by your bookkeeper.
What about credit cards?
Credit card feeds work the same way under Open Banking. Treat each card as a separate "account" in your books, reconcile to the credit card statement, and pay attention to the statement date — not the calendar month — for cut-off.
Security: should you worry?
Open Banking is more secure than CSV exports. You're not sharing passwords, you're authorising read-only access through your bank's own authentication. The risk is lower than emailing statements around. The bigger security concern is who in your business can see the feed and what permissions they have inside your accounting software — review user roles annually.
Where live feeds end and bookkeeping starts
A live feed is plumbing. It delivers raw data. Bookkeeping is the discipline of classifying that data, matching it to invoices and bills, applying VAT correctly, and producing reliable accounts. The two are not the same. If you've connected a feed and assumed your books are done, look again — most likely 30–40% of transactions need human review every week. That's the work our team does for clients via our cloud bookkeeping service.
Open Banking is brilliant, and we'd never go back to the CSV days. But like any automation, it shifts the work, it doesn't eliminate it. Set it up properly, watch for the seven pitfalls above, and your reconciliation week becomes a reconciliation Monday morning.