When Your Bank Drops Direct Connect: A Bookkeeper's Close Checklist

When a bank ends its direct connection with your accounting platform, the feed simply stops arriving. Nothing in the ledger is broken. The books are fine. What you have lost is the automated pipe that carried transactions into the banking centre, and the close now has a manual step in it until a replacement is sorted.

This is a workflow problem, not a data problem. That distinction shapes everything below.

What the loss of a feed does to the close

The first sign is usually silence. Expected transactions stop appearing in the review queue, and the bank balance shown in the software goes stale. If nobody notices, the danger is a reconciliation that looks complete because there is nothing left to match, not because everything has been matched.

The month-end close itself does not change. You still need the bank statement, you still reconcile to it, and you still clear cut-off. What changes is the entry path: someone has to bring the transactions in by hand.

Manual import is the bridge, not the fix

Most platforms, QuickBooks Online included, accept a file upload when a live feed is unavailable. The mechanics matter less than the discipline around them:

• Download the statement in the format your software accepts, and check the date range before importing. Overlapping imports create duplicates that surface weeks later.
• Import before matching, and match before adding. Resist the urge to bulk-add.
• Keep the downloaded files with the working papers for that month, so the audit trail shows where the figures came from.

A useful habit: note on the reconciliation working paper that the period was fed manually, and why. Six months later, nobody will remember, and the note saves the dig.

How this differs from a data problem

A dropped connection and a damaged file can look similar at first glance, because both show up as missing or stale bank activity. The tell is scope and consistency.

A connection loss is clean and total: no transactions arrive, the balance freezes at a fixed date, and everything already in the ledger remains intact. Data damage is usually ragged: reports that disagree with each other, balances that shift between runs, or history that will not reconcile to itself.

If the ledger itself is misbehaving, that is beyond bookkeeping. Preserve a backup before anyone touches the file, and hand it to a specialist in QuickBooks data repair rather than attempting fixes in place.

Getting the connection restored

Feeds come back through two routes. The bank may return to the supported list after an agreement is renewed, and the software vendor typically accepts requests for banks to be added. Both take time, and neither is under your control.

File the request, but plan the manual import as if it will last for months. Some outages do.

What to tell the client

Say it plainly: the bank changed how it shares data, the books are unaffected, and the reconciliation is current as of the last statement. Then show the reconciliation. A client who sees a clean tie-out to the bank statement will not panic about the plumbing.

The bookkeeper's job here is the same as always. Keep the evidence, keep the sequence, and keep the ledger honest while the pipe is rebuilt.