Bank feeds can bring transactions into accounting software without someone typing every line of a statement. Matching rules can suggest categories or connect receipts with unpaid invoices. These functions reduce repetitive work, but they do not establish what a payment was for, whether a document is valid or whether the accounts are complete.
In this article
- Check imported bank transactions
- Review suggested matches and categories
- Resolve duplicates and missing evidence
- Reconcile balances with bank statements
The useful question is therefore not whether to automate bookkeeping. It is which decisions can safely follow an agreed rule, which need evidence and who checks exceptions. A short review routine can make automation substantially more dependable.
A bank transaction is one piece of the evidence
Money leaving the bank might be a supplier payment, loan repayment, deposit, purchase of equipment or personal withdrawal. Those transactions need different accounting treatment even when the bank description looks similar.
Likewise, a receipt might settle an existing invoice rather than create new sales income. Posting the receipt as a fresh sale would duplicate income already recorded. A transfer between business accounts is movement of cash, not another sale.
Bank feeds also cannot show everything that matters. Unpaid customer invoices, supplier bills awaiting payment, stock changes and transactions paid personally can sit outside the feed. Review the wider records before treating the bank screen as the business's financial position.
Give each automation rule a narrow job
Start with repeatable transactions whose treatment is understood. A rule for a particular bank charge is generally easier to control than a rule categorising every payment containing a supplier's name.
Document the rule's purpose, conditions, account code and approval arrangements. Where the software allows it, use a suggestion that someone reviews before posting until the rule has been tested. Features differ by product and subscription, so confirm what your package actually supports.
| Suggested automation | Human check that remains necessary |
|---|---|
| Match a receipt to an invoice | Correct customer, invoice, amount and any short payment |
| Categorise recurring payments | Whether the contract, purpose or tax treatment has changed |
| Extract details from a receipt | Supplier, date, total, VAT details and readable attachment |
| Import bank transactions | Missing days, duplicate imports and correct bank account |
| Match a payment processor payout | Gross sales, refunds, fees and timing differences |
Review rules after changes to suppliers, business activities or payment methods. Do not let an old rule silently determine the treatment of a new type of transaction.
VAT needs more than a bank description
For a VAT-registered business, the evidence and tax treatment matter independently of the cash movement. Do not infer that VAT can be reclaimed simply because a payment went to a familiar supplier. Check the invoice and whether the purchase qualifies under the relevant rules.
HMRC's VAT record-keeping guidance explains the records businesses must retain, including invoices and credit notes. A bank feed does not replace those documents.
Where Making Tax Digital for VAT applies, required records must be kept digitally. If several products form part of that record-keeping and submission process, required transfers between them need digital links. HMRC's Making Tax Digital notice explains the rules and permitted arrangements. Confirm the actual workflow rather than assuming that any connected app makes it compliant.
Build a weekly exception review
Assign one person to inspect unmatched transactions, missing documents and unusually large or unfamiliar entries. Keep a short query list with the transaction date, amount, question and person responsible for answering it.
For each exception, gather the underlying evidence before deciding the category. If an employee paid for something personally, obtain their expense details rather than pretending the payment came from the business bank. If a supplier refunded a purchase, connect the refund with the original bill and credit note.
Then check the bank reconciliation. Compare the accounting balance with the bank statement for the same date, allowing for genuine outstanding items. Investigate unexplained differences; an empty import queue does not prove reconciliation is complete.
An illustrative double-counting problem
Imagine a design business records a customer invoice in its accounts. When the customer pays, an automated rule recognises the customer's name and records the receipt as sales income. The bank balance looks plausible, but income has been counted twice and the original invoice still appears unpaid.
The reviewer spots the inconsistency in the overdue invoice list. They correct the receipt so it settles the invoice, document the change and amend the rule. They also check earlier receipts affected by that rule. This is an illustrative example, not an EPOS client result.
Finish the month with a wider review
Before relying on reports, review unpaid invoices and bills, bank and payment processor balances, duplicate entries, personal transactions and outstanding queries. Look for unexplained changes in margins or expense categories. A sharp fall in costs might be a missing import rather than improved performance.
Keep a record of significant corrections and restrict who can change completed periods where your software supports this. Agree how later adjustments will be approved, especially when figures have already supported a tax return or a management decision.
Useful automation should leave you with fewer routine tasks and clearer exceptions. It should not leave the business unable to explain its figures. If you would like help reviewing your workflow, discuss accounting software support with EPOS Accountancy. Agree the software, records, review responsibilities and available support before work starts; see pricing for the next step towards a scoped quote.