A bank feed stopping does not mean the business has stopped making transactions. It means one route into the bookkeeping software may be incomplete. Keep collecting the underlying records, identify the gap and agree how it will be filled before adding transactions by another route.
When asking for help with bookkeeping, Leicester business owners can describe the last period known to be complete and what has changed since. KKB Accounting provides paperless bookkeeping support centred on your current records or software, the frequency of support needed and when it should begin. There is no assumption that you must change software before making contact.
Find the last reliable point
Check which account is affected and the date of the most recent transaction present in the bookkeeping system. Compare it with the bank's own record. A feed can be delayed, disconnected or showing only part of an account's activity; the message on screen and the records available should guide the investigation.
Keep the distinction between the last imported transaction and the last completed reconciliation. Transactions appearing in a list does not necessarily mean they have all been matched and reviewed. If the last confirmed month is earlier than the apparent feed gap, say so.
Write down the account, dates and error message, without including passwords or security codes. A screenshot can help explain the issue, but check what personal or financial information it contains before sharing it through an agreed secure route.
Keep collecting invoices and receipts
The feed is only one part of the records. Continue saving sales invoices, supplier documents and expense evidence while the connection is being checked. Those documents may explain transactions that eventually arrive through the feed, or support an alternative import agreed with the bookkeeper.
Download complete statements for the affected period from the bank's normal secure service when available. Keep the original download intact. If the bank also offers transaction exports, preserve the date range and file format so the person handling the records knows exactly what the file contains.
Do not assume that a screenshot of a current balance shows all activity in the missing period. The task is to restore a complete transaction history, not simply to make the latest balance appear somewhere else.
Choose one recovery route before importing
Restoring the feed and importing a file independently can produce overlapping records. Before doing either, establish who is handling the recovery and which dates that action is intended to cover. Use the software provider's current instructions for the product and connection involved.
If an import is appropriate, compare its period with what is already present. Keep the original file and note what was imported. If the feed later supplies the same transactions, the overlap needs review; do not delete entries simply because the amounts look familiar.
Two genuine payments can have the same value. Check references, dates and the underlying documents before treating something as a duplicate. An uncertain transaction should remain a clear question for review, rather than being changed to make a screen look tidy.
Reconnect through the proper service
Use the recognised bank and accounting-software routes when reviewing a connection. Do not send a password, one-time code or a complete set of security answers to someone offering to reconnect it for you. If another person needs access, discuss the appropriate authorised access arrangement rather than sharing the owner's sign-in.
A working connection is useful, but it is not the end of the check. Confirm which missing dates have actually arrived and whether any remain outstanding. A success message about the connection does not establish that every older transaction has been recovered.
Close the gap against the statement
Once the missing activity has been brought in through the agreed route, compare the affected period with the bank statement and the supporting documents. Account for transfers, charges and other items that may need explanation. Keep a short record of the period checked and any remaining questions.
If a filing deadline depends on these records, tell the accountant early. Describe the affected period and what is available rather than waiting for the software issue to resolve itself. KKB Accounting's year-end accounts service considers the accounting period, current state of the records and filing date; its bookkeeping service covers the underlying day-to-day record support.
A feed interruption can be treated as a defined recovery task: one account, an identified period and a single agreed route for restoring it. Keep the current records moving while that task is completed, so a temporary connection problem does not become a larger administrative backlog.
A short handover for the person fixing the gap
Keep one note alongside the existing bookkeeping records with:
- The affected bank account and last reliable transaction date.
- The last period that was fully reconciled.
- The missing date range and original statements available.
- Any manual imports already made and the person responsible for recovery.
Questions customers ask
Does reconnecting the feed prove that the missing period is complete?
No. Check the transaction dates that actually arrived against the bank statement and review any overlap with manual entries. A successful connection and a complete, reconciled period are separate checks.
Can I ask KKB Accounting for help before every record is recovered?
Explain which records are available, the period affected and the software you currently use. Say how often you need bookkeeping support and when you would like support to begin. If year-end accounts are also due, include the financial year-end and filing deadline so the timing can be considered together.
