Bank Feeds in Accounting Software
How automatic bank feeds work, why UK businesses use them to save time and reduce errors, and how they integrate with bank reconciliation and Making Tax Digital compliance.
Bank feeds are automatic connections between a business bank account and its accounting software. Instead of manually entering every transaction, the software pulls in transaction data directly from the bank, typically on a daily basis. This automation has transformed bookkeeping for UK businesses of all sizes, reducing manual data entry and improving the accuracy of financial records.
How bank feeds work
The process follows a straightforward flow:
- The business authorises its accounting software to connect to its bank account
- The bank transmits transaction data to the software through a secure data feed
- Transactions appear in the software’s bank feed area, ready for review
- The bookkeeper or business owner matches, categorises and approves each transaction
- Approved transactions are posted to the general ledger
Most UK cloud accounting platforms refresh bank feeds daily, although some banks offer near real-time feeds. The transactions typically include the date, amount, payee or payer name, and a reference or description.
Connection methods
| Method | How it works | Security |
|---|---|---|
| Open Banking API | Direct, regulated connection via the bank’s API | Highest (FCA-regulated, read-only access) |
| Yodlee / screen scraping | Third-party service reads the bank’s online portal | Lower (uses login credentials) |
| File import (CSV/OFX) | Manual download and upload of bank statement files | No live connection |
Open Banking is the preferred method in the UK. Since the implementation of the Payment Services Directive 2 (PSD2) and the UK’s Open Banking initiative, the major UK banks are required to provide secure API access to authorised third-party providers. This gives accounting software direct, encrypted, read-only access to transaction data without requiring the user’s banking login credentials.
Benefits for UK businesses
Time savings
Manual transaction entry for a typical small business might take several hours per week. Bank feeds reduce this to a fraction of that time, as the data arrives automatically and the bookkeeper’s role shifts from data entry to data review.
| Task | Without bank feeds | With bank feeds |
|---|---|---|
| Recording bank transactions | Manual entry from statements | Automatic import |
| Time per month (typical SME) | 4-8 hours | 30-60 minutes |
| Risk of transcription error | High | Eliminated |
| Delay in recording | Days or weeks | Same day or next day |
Accuracy
Manual data entry is prone to transposition errors (entering £540 instead of £450), omissions (missing a transaction entirely) and duplicate entries (recording the same transaction twice). Bank feeds eliminate these risks because the data comes directly from the bank’s own records.
Real-time financial visibility
Because transactions flow into the software daily, the business has a near real-time view of its financial position. Directors can see their cash balance, outstanding payments and recent income without waiting for month-end processing.
Simplified bank reconciliation
Bank feeds make bank reconciliation significantly easier. The software can automatically match imported transactions against invoices, bills and other records, highlighting only the items that need manual attention. Many businesses find that reconciliation moves from a monthly chore to a quick daily check.
Setting up bank feeds
Step 1: Choose compatible software
Most UK cloud accounting platforms support bank feeds, including Xero, QuickBooks, FreeAgent, Sage and others. Check that your chosen software supports your specific bank before signing up.
Step 2: Connect your bank account
The connection process varies by software and bank:
- Open Banking connections typically involve clicking a link, selecting your bank, and authorising access through your bank’s own authentication process
- Some connections require re-authorisation every 90 days under PSD2 regulations
- Multiple bank accounts can usually be connected to a single accounting platform
Step 3: Set up matching rules
Most accounting software allows you to create rules that automatically categorise recurring transactions. For example:
| Transaction description | Category | VAT rate |
|---|---|---|
| BT GROUP PLC | Telephone expenses | 20% |
| BRITISH GAS | Utilities | 5% |
| TESCO STORES | Office supplies | 20% |
| HMRC PAYE | PAYE liability | N/A |
Well-configured rules can automatically categorise 60-80% of transactions, leaving only unusual or new transactions for manual review.
Step 4: Review and approve
Even with automation, every transaction should be reviewed before posting. The bookkeeper checks that:
- The suggested category is correct
- The VAT treatment is appropriate
- The transaction is matched to the right invoice or bill
- No duplicates have been created
Bank feeds and Making Tax Digital
Making Tax Digital (MTD) requires VAT-registered businesses to maintain digital records and file VAT returns using MTD-compatible software. Bank feeds support MTD compliance by ensuring that:
- All bank transactions are captured digitally from source
- Records are maintained in MTD-compatible software
- The digital links requirement is satisfied (no manual re-keying of data between systems)
When MTD for Income Tax Self Assessment rolls out for sole traders and landlords, bank feeds will become even more important as a means of maintaining real-time digital records.
Common issues and solutions
Missing transactions
Occasionally, a bank feed may miss transactions due to connection interruptions or timing differences. The solution is to perform a regular bank reconciliation that compares the software’s bank balance to the actual bank statement balance.
Duplicate transactions
If a user manually enters a transaction and the same transaction also arrives via the bank feed, a duplicate occurs. Most software flags potential duplicates for review, but the user must confirm whether to keep or delete the duplicate entry.
Connection dropouts
Bank feed connections can drop due to bank maintenance, security updates or the 90-day PSD2 re-authorisation requirement. If the feed stops working, the user typically needs to reconnect through the software’s bank feed settings.
Incorrect categorisation
Automatic rules are only as good as their configuration. Transactions with ambiguous descriptions may be miscategorised. Regular review of categorised transactions – particularly at VAT return time – catches and corrects these errors.
Security considerations
Bank feeds are read-only – they cannot be used to make payments or move money. Data flows in one direction only, from the bank to the accounting software.
| Security feature | Detail |
|---|---|
| Read-only access | Software can view transactions but cannot initiate payments |
| Encryption | Data transmitted using bank-grade TLS encryption |
| Authentication | Open Banking uses the bank’s own authentication |
| Regulation | Open Banking providers are authorised by the FCA |
| Re-authorisation | Required every 90 days under PSD2 |
Businesses should ensure their accounting software provider is a registered Account Information Service Provider (AISP) with the FCA, which guarantees compliance with data protection and security standards.