Stop Missing Three Weeks: Bank Feeds Explained for UK Trades

A bank feed is an automated link that pulls your transactions straight into your accounting software, so you stop typing figures from paper statements. The main payoff is speed and accuracy: fewer manual entries mean fewer mistakes, and reconciliation that once took an evening can take minutes. Most modern feeds run on Open Banking, the UK’s regulated standard for secure data sharing, and some bookkeeping tools build around that same principle of automated, tax-ready records.

TL;DR:

Most bank feeds rely on Open Banking APIs, which provide secure, regulated data sharing that removes the need to share login credentials directly.

Routine checks and reauthorization every 90 days are essential to prevent feed disruptions caused by expired consent or unaddressed technical issues.

Building categorization rules for common transactions early streamlines ongoing bookkeeping tasks and reduces errors during reconciliation.

Reliability depends on consistent maintenance, such as weekly reviews of import dates and merging duplicates, rather than a one-time setup.

If transactions do not update in several days, a manual refresh usually solves the issue, but unsupported banks may require fallback methods like CSV imports.

Tradetally

Simplify Your Trades Finances

TradeTally helps UK sole traders create invoices, capture receipts, and organise tax-ready records in one mobile app.

Explore TradeTally

What is a bank feed, exactly?
How do bank feeds actually work?
What are the practical benefits for small businesses and accountants?
Is it safe to connect my bank account to accounting software?
How do you set up and maintain a bank feed?
What common bank feed problems should you expect?
How does this look in a real trades workflow?
Is the industry overselling bank feeds?
Sources
FAQ

What is a bank feed, exactly?

A bank feed is the automated import of your bank transactions into accounting software, replacing the old routine of downloading a statement and typing each line by hand. Once connected, your software pulls in new transactions on a set schedule, usually daily, so your books stay current without you lifting a finger.

Each imported transaction typically carries a handful of fields:

The transaction date
The amount and whether it’s money in or out
A reference or description (often the same messy text you see on your bank statement)
The running account balance at that point

Feeds fit into a simple three-step cycle. First, the software imports the raw data. Second, you or the software match and categorise each line, whether that’s a fuel purchase, a customer payment, or a card fee. Third, you reconcile, confirming the books match what the bank actually shows. Get that cycle running smoothly and bookkeeping stops being a monthly ordeal.

How do bank feeds actually work?

Not all feeds are built the same way, and understanding the difference helps you judge how reliable yours will be. There are four common routes into your accounting software.

Open Banking / API feeds: You’re redirected to your bank’s own login screen, you approve the request, and the bank sends data directly to your software through a regulated interface. No passwords are ever shared with the accounting app itself.
Direct bank partnerships: Some banks and software providers build closer integrations using OAuth-based connections, often delivering richer transaction detail and steadier uptime than older methods.
Aggregator or credential-shared feeds: Older technology that sometimes required you to hand over your online banking login to a third party so it could “read” your account. Standards bodies now actively discourage this in favour of dedicated APIs.
Payment-platform feeds: PayPal, Stripe, and card processors run separate feeds from your bank account feed, showing gross sales, fees, and payouts rather than the net amount that eventually lands in your current account.

Open Banking has become the dominant route for good reason. Over six million people in the UK were using Open Banking services as of June 2022, and that scale reflects a shift away from credential sharing towards regulated, revocable consent.

What are the practical benefits for small businesses and accountants?

Ask any accountant what eats their time and manual data entry sits near the top of the list. Bank feeds attack that problem directly by integrating with suitable accounting software solutions; for more on software selection and capabilities, see this bookkeeping software features and adoption guide.

Time saved: Reconciliations that involved typing dozens of transactions line by line now take minutes once rules are set up.
Fewer posting errors: Removing manual re-typing removes the most common source of misposted amounts, which matters when those figures feed into VAT returns or Self Assessment.
Real-time cashflow visibility: You can see what’s actually landed in your account today, not what you think landed three weeks ago, which makes chasing a late-paying customer far less guesswork.
Cleaner accountant handoff: Categorised, reconciled data exports cleanly at year end, so your accountant spends less time chasing missing receipts and more time on the numbers that matter.

Experts studying Open Banking adoption point to exactly this shift: moving from error-prone manual bookkeeping to a real-time and accurate financial picture frees business owners for higher-value work instead of admin.

Pro Tip: *Set up bank rules for your five or six most common transaction types (fuel, materials suppliers, bank charges) first.

Is it safe to connect my bank account to accounting software?

Yes, provided the connection uses Open Banking rather than sharing your login credentials directly. The framework runs under PSD2 and UK secondary legislation, which requires account information services to get your explicit consent and limit requests to necessary data only. The CMA has also confirmed that the Open Banking Roadmap implementation phase is substantially complete, meaning the UK’s biggest banks now have firm obligations to support these connections reliably.

A few things worth checking before you connect anything:

Confirm the provider is registered and follows Open Banking standards rather than asking for your online banking password.
Expect a redirect to your bank’s own secure login screen. If a service asks you to type your bank password directly into its own page, that’s a red flag.
You’ll typically need to reconsent every 90 days under standard Open Banking consent practice, which sounds like a hassle but exists precisely so you stay in control of who can see your data.
You can revoke access at any time, either through your bank or the connected software.

How do you set up and maintain a bank feed?

Getting a feed running is straightforward, but keeping it healthy is where most people slip up. Follow this order:

Prepare: Confirm your account type is supported (business current accounts are almost always fine; some niche accounts aren’t) and that you have your online banking login to hand.
Connect: Follow your software’s connect flow, select your bank, and complete the redirect consent screen. This takes two or three minutes.
Check the first import: Look at the last import date shown in your software and resolve any unmatched opening transactions before you build on top of them.
Establish a routine: Review new imports weekly at minimum, apply categorisation rules as patterns emerge, and reconcile monthly so nothing drifts unnoticed.
Set a consent reminder: Put a note in your calendar roughly every 90 days, since that’s the typical window before reconsent is required.
Know where re-authentication happens: Some banks require you to approve access again in the bank’s own app rather than inside your accounting software.

Pro Tip: Do your weekly feed review at the same time you check your diary for the week ahead. Pairing an admin task with one you already do daily is the easiest way to stop it slipping.

What common bank feed problems should you expect?

Most feed issues fall into four familiar categories, and none of them need a lengthy support call if you know what to check first.

Missing or delayed transactions: Check the last import date shown in your software. Most feeds refresh daily, so a short delay is normal, but if it’s been several days, try a manual refresh before contacting your bank.
Expired consent: If imports simply stop, consent has likely lapsed. Providers often work on a 90-day cycle and some require re-authentication directly in the bank’s own app rather than the accounting software.
Duplicates or miscategorising: Build matching rules based on payee or reference text, and merge duplicates manually rather than deleting, so your reconciliation trail stays intact.
Unsupported bank or account: Fall back to CSV import from your online banking portal, and flag it with your software provider, since bank support lists change regularly.

How does this look in a real trades workflow?

Picture a plumber who invoices on-site with Tradetally, snaps a photo of the materials receipt in the van, and lets the bank feed match that receipt to the payment automatically. By the time the job’s finished, the expense is categorised and sitting in a tax-ready record heading towards an SA103F export. That’s the whole point of a mobile-first setup: less evening admin, more evidence collected the moment it happens. One realistic caveat worth setting expectations on: some banks still insist on re-authentication happening in their own app rather than inside any accounting software, no matter how good that software is.

Is the industry overselling bank feeds?

The conventional pitch treats feed setup as a one-off task: connect once, forget forever. That’s the part worth pushing back on. The research on Open Banking adoption is genuinely reassuring, with over six million users and firm CMA obligations on the major banks behind it, but adoption figures say nothing about whether your feed still works properly in month four.

Is the industry overselling bank feeds? — overview diagram

What actually determines reliability is routine, not setup. A feed reconnected once and never checked again is the one that quietly stops importing after a 90-day consent window lapses, leaving three weeks of missing transactions nobody notices until reconciliation day. The fix isn’t more sophisticated software. It’s a five-minute weekly habit: check the last import date, clear unmatched items, and put a reminder in the calendar for reconsent.

If you prioritise one thing after reading this, make it the calendar reminder. Everything else, from Open Banking’s security model to the categorisation rules, works exactly as intended provided somebody’s actually looking at the feed on a schedule.

— Simon

Sources

FAQ

What is a bank feed and how does it work?

A bank feed automatically imports your bank transactions into accounting software, usually through Open Banking, which lets you authorise the connection securely without sharing your login details. Once connected, new transactions appear on a regular schedule, ready to be categorised and reconciled.

How do bank feeds speed up bank reconciliation?

Bank feeds remove the need to manually type transactions from statements, so matching and reconciling happens against live data rather than a stack of paper. Combined with categorisation rules, reconciliations that once took hours can shrink to a few minutes.

When should you use the categorise option in the bank feed?

Use categorising as soon as a transaction appears, ideally in a weekly review, so patterns like recurring suppliers or fuel purchases can become automatic rules. Leaving categorisation to pile up increases the risk of misposted or duplicated entries at reconciliation time.

What do bank feeds mean in accounting software like QuickBooks?

In platforms such as QuickBooks, a bank feed refers to the same underlying concept: an automated connection, typically via Open Banking, that pulls transactions into the software for review and matching. The mechanics (import, categorise, reconcile) are consistent across most UK accounting software.

Why do bank feeds need reconnecting every so often?

Providers commonly apply a 90-day reconsent window as part of Open Banking’s consent rules, meaning you’ll periodically need to reapprove access. Some banks also require that reauthorisation to happen inside their own banking app rather than the accounting software itself.