Open Banking bank feeds: automate bookkeeping without giving up reconciliation

Open Banking bank feeds can import business-bank transactions directly into accounting software, reducing manual data entry and making daily reconciliation faster. The feed is still an import mechanism, not an accountant: transactions can be duplicated, uncategorised or matched incorrectly and need review.

A bank feed brings transaction data into accounting software

Open Banking listings describe accounting products such as Xero using direct bank feeds to bring account transactions into bookkeeping and reconciliation workflows.

The feed reduces manual statement entry but does not decide the commercial meaning of every line. Finance still needs invoices, receipts and account coding.

The business authorises access through the bank

Where the feed uses an AISP, the company gives explicit Open Banking consent to the accounting provider or its regulated partner. The bank authenticates the user.

Keep a list of who can establish and renew feeds. A junior bookkeeper should not automatically have permission to connect every group bank account if they do not need the data.

Automatic matching needs review

Accounting software can suggest matches between bank lines and invoices, bills or transfers. Accepting suggestions blindly can clear the wrong customer or supplier when amounts happen to match.

Review name, date, reference and amount. For material transactions, the bank line should connect to the underlying commercial evidence.

Feed reconnections can create duplicate or missing transactions

Changing consent, reconnecting an account or switching feed technology can create overlap or gaps depending on the provider. Reconcile opening and closing statement balances after any connection change.

Do not delete differences merely to make the software balance. Identify whether the problem is an imported duplicate, a missing line or a genuine accounting entry.

A bank feed does not decide VAT treatment

A £120 card transaction might be office supplies with VAT, client entertainment with restricted tax treatment, a personal director item or something else. The bank knows only that money moved.

Attach receipts and apply the correct tax code before filing VAT. Automated transaction rules should be reviewed periodically because one merchant can sell several kinds of goods or services.

Reconcile the software balance to the official bank record

At month-end, compare the ledger balance to the bank's statement or authoritative transaction record. The bank feed should help explain the balance, not replace the independent check.

Keep downloaded statements for record retention even where the software stores imported data. If the feed provider or software changes later, the company still needs its banking evidence.

Worked example: accounting software suggests matching a £5,000 customer receipt to Invoice 104 because the amount is identical. The payment reference actually belongs to Invoice 117 from another customer. Accepting the automatic match clears the wrong debtor and leaves the real payer apparently overdue. Automation should narrow the work, not remove verification.

Create feed rules only for genuinely repetitive transactions such as known bank fees or fixed subscriptions. Rules based only on merchant name can misclassify a supplier that sells both capital equipment and ordinary consumables. Review high-value rule-generated postings before month end.

When changing accounting systems, export official bank statements and the old reconciliation history before disconnecting. Open Banking consent can be recreated in the new platform, but historic matching logic and imported descriptions may not transfer. The company needs a clear cut-off so transactions are not imported into both systems.

Set a policy for feed outages. If a connection breaks for five days, decide whether bookkeeping waits, imports a statement file or posts urgent transactions manually. When the feed returns, reconcile the overlap so manual entries do not become duplicates.

Use reconciliation status as a control metric. A bank feed can make bookkeeping look current while dozens of transactions remain unmatched. Management should see the date each account was fully reconciled, not only the date data last downloaded.

For multi-currency accounts, check whether the feed supplies both original currency and sterling-equivalent data. Accounting software can otherwise create exchange differences simply because it imports a converted amount without the original transaction currency. Keep the bank's source-currency record available for material international items.

Set review thresholds for automatically posted entries. Low-value recurring bank fees may be safe for rules, while large transfers, tax payments and director transactions should remain visible to a human reviewer. The strongest bank feed automates repetitive evidence gathering but keeps judgement around transactions that can materially affect tax, ownership or reporting.

For audit and tax evidence, keep a link from each material feed transaction to the original invoice, receipt or statement even after it is reconciled automatically. A feed proves that money moved, not why it moved. Preserving the underlying document means the company can change accounting systems later without losing the evidence that supported VAT, Corporation Tax or management reporting.