A bank feed is a direct, automatic connection between a client's bank account and their accounting software that imports transactions daily without manual export or import steps. Bank feeds are the single most impactful automation available in bookkeeping — they eliminate a high-volume, error-prone manual task and provide near-real-time financial data in the accounting system.

This guide covers how bank feeds work, the Open Banking framework that underpins them in the UK, how to set them up across major accounting platforms, and best practice for managing them reliably.

How bank feeds work in the UK

Bank feeds in UK accounting software are powered by Open Banking — a regulatory framework implemented through the Payment Services Regulations 2017 (the UK's implementation of PSD2) and overseen by the Financial Conduct Authority. The Open Banking Implementation Entity maintains the technical standards and the list of providers authorised to access bank data.

When a client connects their bank account to their accounting software, the accounting software uses an Account Information Service Provider (AISP) — typically a specialist aggregator like TrueLayer, Yapily, or Plaid — to request access to the account's transaction data. The client authenticates this access directly with their bank using their normal online banking login (strong customer authentication). They do not share their banking credentials with the accounting software or the AISP — the authentication is handled entirely by the bank.

Once authorised, the AISP retrieves transaction data from the bank's API daily (or more frequently for some banks) and delivers it to the accounting software. The authorisation is read-only — the AISP and accounting software can see transaction data but cannot initiate payments.

Authorisations typically expire after 90 days, after which the client must re-authorise. This is an EU and UK regulatory requirement under PSD2 designed to ensure the client actively maintains consent rather than granting indefinite access.

Bank feed support across accounting platforms

Xero

Xero supports bank feeds from over 100 UK banks and financial institutions via Open Banking and through direct feed agreements with major banks. Feeds are set up within Xero under Bank Accounts and require the client to authenticate with their bank.

For some banks (including HSBC, Barclays, Lloyds, and NatWest), Xero has direct feed arrangements that may offer more stable connections than the AISP-aggregated Open Banking route. Direct feeds are preferable where available.

Xero's bank reconciliation interface is one of the most refined on the market, with intelligent bank rules and suggested matches significantly reducing the manual reconciliation effort once the feed is established.

QuickBooks Online

QuickBooks supports bank feeds from major UK banks and building societies. The connection uses Open Banking via Yodlee and other AISP providers. Setup is within the Banking section of QuickBooks Online.

QuickBooks' auto-categorisation uses machine learning to suggest coding for bank transactions, with accuracy improving over time as the system learns from corrections.

Sage Accounting (cloud)

Sage Accounting cloud supports Open Banking bank feeds for major UK banks. For Sage 50 desktop users, bank statement import (CSV or OFX format) remains the primary method, as the desktop product has more limited live feed integration.

FreeAgent

FreeAgent includes bank feed connectivity for major UK banks via Open Banking. It is particularly well-suited to sole traders and freelancers due to its simpler interface.

Setting up bank feeds: practical steps

  1. In the accounting software, navigate to the bank accounts section and select the client's bank
  2. The software initiates the Open Banking authorisation flow
  3. The client is redirected to their bank's authentication page and logs in using their normal online banking credentials (they do not share these with the accounting software)
  4. The client approves the data sharing request, specifying which accounts and the duration of access
  5. The authorisation returns to the accounting software, and the feed activates — historical transactions for the recent period are imported immediately
  6. Going forward, transactions import automatically, typically each day

For clients who are not tech-savvy, walking through the authorisation step together (in person, by screen share, or with a step-by-step written guide) reduces failed setups and re-authorisation confusion. For more on technology adoption across your practice, visit the AI tools and technology for UK accountants hub.

Managing bank feed re-authorisation

The 90-day re-authorisation requirement under PSD2 is one of the most common operational friction points in bank feed management. A feed that is not re-authorised expires silently — transactions stop importing, but there is often no obvious alert in the accounting software.

Best practice for managing re-authorisations:

  • Note the re-authorisation date when the feed is set up
  • Add a reminder in your practice management system two weeks before expiry
  • Send the client a brief notification before re-authorisation is due, with a one-click link to the re-authorisation flow if the software supports this
  • After re-authorisation, check that the feed resumes and import the missed transactions if there was any gap

Some accounting software providers are working to extend re-authorisation periods under the FCA's evolving guidance, which may reduce this friction over time.

Bank rules and reconciliation automation

Once the feed is live, the most powerful automation comes from well-configured bank rules. A bank rule is an instruction to the accounting software: "When you see a transaction from payee X for amount Y, code it to account Z." Rules can be as simple or complex as needed:

  • Simple rule: all transactions from "HMRC PAYE" code to the PAYE liability account
  • More complex rule: all transactions from "AMAZON" where the description contains "PRIME" code to subscriptions, but other Amazon transactions code to a holding account for review

Well-built bank rules mean that a large proportion of transactions are automatically suggested to the correct account, and reconciliation becomes a process of confirming correct suggestions rather than coding each transaction manually.

Invest time in building a comprehensive bank rule set when onboarding each client to the feed. This front-loaded effort pays back rapidly in reduced reconciliation time.

Handling problem connections

Some UK banks have less stable Open Banking implementations than others. Smaller banks, challenger banks, and credit unions may have intermittent feed issues. Problems to watch for:

Feed stops importing: check the authorisation has not expired and the bank's Open Banking service is operational. HMRC, major high street banks, and most challenger banks maintain status pages.

Duplicate transactions: occasionally a reconnection or re-authorisation imports transactions that are already in the accounting software. Check for duplicates after any re-authorisation event.

Missing transactions: some transactions may not appear in the feed for several days after the transaction date. Allow a few days before investigating gaps.

Authentication failures: some banks require specific authentication steps that clients find confusing. Provide step-by-step screenshots for the client's specific bank if the setup is failing.

For persistently unreliable bank connections, bank statement import (manual upload of CSV or OFX files exported from online banking) is a reliable fallback.

Key takeaways

  • Bank feeds import transactions automatically from client bank accounts to accounting software via Open Banking — the most impactful automation in bookkeeping for eliminating manual data entry.
  • Open Banking connections are read-only, use OAuth authorisation (no banking credentials shared), and are regulated by the FCA — they are secure by design.
  • UK PSD2 requires re-authorisation every 90 days; manage this proactively with reminders before expiry to avoid silent feed gaps.
  • Well-configured bank rules are the multiplier that makes bank feeds most efficient — invest time in rule building at client onboarding.
  • For unstable bank connections, manual bank statement import is a reliable fallback.

Frequently asked questions

Is it safe to connect a client's bank account to accounting software?

Yes. Open Banking connections are read-only — the accounting software cannot initiate payments or access your client's banking credentials. The connection uses OAuth authentication, which means the client authorises access directly through their bank's own secure login without sharing passwords with the software. The connection is overseen by the FCA and conforms to the Open Banking Implementation Entity's technical standards.

Which UK banks support Open Banking bank feeds?

All major UK high street banks — HSBC, Barclays, Lloyds, NatWest, Santander, Halifax, TSB — support Open Banking bank feeds. Most challenger banks (Starling, Monzo, Tide, Revolut Business) also support Open Banking. Credit unions and smaller building societies have more variable support. The Open Banking Implementation Entity maintains a directory of regulated providers.

What happens if a client's bank changes their Open Banking implementation?

Bank system updates can occasionally break existing feed connections. If a feed stops importing after a bank system update, reconnecting the feed through the accounting software's bank setup usually resolves the issue. Monitor feeds periodically (weekly at minimum) to catch breaks before they result in significant gaps.

Can I see all the client's bank accounts through one bank feed connection?

This depends on the bank and the scope of access the client authorises. Most Open Banking connections allow the client to specify which accounts to share. If a client has multiple accounts (current account, savings, credit card) they can typically connect them all, though each may require a separate authorisation.

Why does the bank feed sometimes miss transactions that appear in online banking?

Bank feeds typically update once a day, and there can be a lag of 24 to 48 hours between when a transaction appears in online banking and when it appears in the accounting software feed. Some transaction types — particularly pending transactions and some direct debits — may also be delayed or excluded by the bank's API. This is normal behaviour; wait two to three days before investigating a specific missing transaction.