A bank feed can run for a month without errors and still leave your books wrong at month-end. It imports transactions, but you or your bookkeeper still have to review every match and category before reconciliation. A banking tab full of unreviewed imports means the connection works, but the books behind it aren't ready for a payroll decision.
Connecting the bank to the software only starts the bookkeeping process. A bank feed imports cleared bank transactions into accounting software, but it doesn't review or reconcile them. To keep books clean, set up the accounts behind the feed and keep a review schedule in front of it. You also need a backup plan for the day the connection breaks.
What is a bank feed?
A bank feed automatically pulls cleared transactions from your business bank account into your accounting software. Payments and fees appear for review without a manual statement download. Deposits show up too.
In practice, the transactions land in a review queue inside the accounting software. Each line still needs a category, a match to an invoice or bill when one exists, and a later reconciliation against the bank statement.
Standard read-only bank feeds have one-way data flow and scheduled refreshes. Data moves from the bank into the software only, so the feed can't move money, initiate a payment, or change anything at the bank. The connection refreshes periodically, so your software may reflect earlier cleared activity from before this morning. A payment sent this morning usually won't appear until the next refresh.
Together, those settings explain why the feed can import transactions without giving you real-time books.
How bank feeds work
A bank feed connects through a direct integration or a third-party aggregator. In a direct integration, the banking platform and accounting software exchange data natively. With a third-party aggregator, a service sits between the bank and the software and passes transaction data along.
Either way, cleared bank activity syncs into the accounting software for review without a manual statement download or hand-keying line items. If you used to export a comma-separated values (CSV) file, the feed replaces that step too.
Cleared activity means the transaction has posted at the bank. Pending card charges and payments in motion may not appear until the bank clears them and the feed refreshes.
Does a bank feed reconcile your books automatically?
No. A synced bank feed only shows that cleared transactions arrived; reconciliation is the separate month-end check that compares the software balance with the bank statement and resolves discrepancies.
When you don't review the feed, duplicates and misclassified transfers start showing up in the books. A manually entered bill and its imported bank payment can both sit in the ledger. The ledger can overstate expenses, and deposits can overstate income. Transfers between your own accounts create another common problem. Move money from your operating account to a tax reserve, and an unreviewed feed can record the incoming transfer as income in one account. It can also record the outgoing transfer as spending in the other, when no money entered or left the business at all.
Those errors land in the reports you use to make decisions. An unreviewed bank feed can produce a profit and loss statement showing healthy profit while cash tells a different story. If a misclassified transfer inflates revenue, the reports can make the business look ready for a hire before the cash supports that decision. Because the reports still look complete, it's easy to make decisions from numbers that already have errors in them.
Clear account purposes reduce the judgment calls your reviewer has to make at month-end. Reconciliation software can flag duplicate transactions and mismatched transfers, but you still need to confirm how each item should be categorized.
How should you review what the bank feed brings in?
A clean feed review needs one assigned owner and a fixed cadence. Exceptions need their own rule so unclear items don't get buried.
Set the review cadence
When a few hundred imported transactions arrive each month, review weekly and assign the work to one person. If your bookkeeper handles the pass, give them read-only access to the accounts feeding the software.
The review itself runs the same four steps every time:
Hold a cadence matched to volume. A few hundred transactions a month calls for a weekly review. Weekly keeps the queue small; you still remember what Thursday's $412 charge was for.
Categorize and match. Assign each imported transaction to the right category, and match payments and deposits against the invoices and bills already in the software so nothing lands twice.
Confirm transfers are transfers. Book any movement between your own accounts as a transfer.
Reconcile against the bank statement. Compare the software balance to the statement balance and resolve every discrepancy, so the books and the bank agree on the same number.
A weekly pass prevents a larger month-end cleanup file from building up.
Hold unclear items in review
If a vendor is unknown, leave the transaction in review and add a short note about what needs confirming. Ask the person closest to the purchase or deposit before matching it. Keeping uncertainty visible prevents it from getting buried inside a report.
After a finished review, your banking tab shows zero unreviewed transactions, and the statement is reconciled.
How do categorization rules affect feed review?
Categorization rules speed the work: the software can auto-apply a category to a recurring vendor. Check those rules periodically, because a rule matched to the wrong vendor repeats the same mistake every week without anyone touching it.
If cleanup takes longer than expected, write down the single blocker before moving on. Over a few weeks, that note shows whether the issue is a rule, an account that mixes purposes, or a review handoff that needs to change.
What should you do when a bank feed breaks?
To recover from a broken bank feed, find the missing dates, reconnect the feed, import the gap, and remove duplicates before reconciling. Broken feeds usually go unnoticed at first because transactions stop importing or import inconsistently. The books drift away from the bank until someone catches it, often weeks later during reconciliation. Bank feeds usually break because credentials expire and need re-authentication, or because one connection method drops more often than another.
Recovery runs in order:
Confirm the gap. Compare the date of the last imported transaction against the bank statement to find exactly which window is missing.
Reconnect the feed. Re-authenticate the connection so new transactions resume importing from today forward.
Import the missing window manually. Download the gap period from the bank and bring it in as a CSV, Open Financial Exchange (OFX), or QuickBooks Online-compatible Web Connect file, whichever format your software accepts. These are bank export files; you download them from online banking and upload them into your accounting software for the missing dates. Before uploading the file, save the start and end dates of the gap and use those same dates for the bank download. Matching the dates ties the manual import to the missing window and makes overlap with the reconnected feed easier to spot.
Check for duplicates. Where the manual import overlaps the reconnected feed, the same transaction can arrive twice; remove one copy before reconciling.
Fold a last-import-date check into your weekly feed review; it only takes a few seconds. If the most recent imported transaction is older than your normal refresh window, the feed has probably dropped. You catch the gap in days and avoid finding it at quarter-end.
How does your banking setup affect bank feed quality?
Your bank feed is easier to review when the connection stays live, transaction names arrive clearly, and each account has its own feed. When imported descriptions arrive messy or accounts drop often, the bank side of the connection becomes a bookkeeping problem. Most owners pick a provider on fees and branch convenience and never evaluate the feed they'll use for years.
Before you choose an account, check how the feed will behave after the first month:
Connection method. Confirm whether the account connects directly to your accounting software or through an aggregator.
Re-authentication cadence. Ask how often you have to re-authenticate the connection.
Transaction descriptions. Check whether transaction descriptions arrive cleanly enough to categorize.
Per-account feeds. Confirm that each account can run as its own feed without extra per-account charges.
These setup problems slow reconciliation and push reviewers back to statements or screenshots.
How should account structure support bank feeds?
Account structure affects how much cleanup your reviewer has to do. Using one account for payroll, materials, tax reserve, and owner draws pushes more sorting and categorization into the accounting software after the fact. Multiple bank accounts separated by purpose can make transactions easier to review and reconcile because everything in the payroll account is expected to be payroll.
Relay accounts use that separation: each checking account runs as its own labeled feed into QuickBooks Online and Xero. Relay lets you create up to 20 checking accounts (50 on the Scale plan) and up to two savings accounts, so payroll, tax reserves, and operating cash can sync as distinct streams. Your reviewer starts each transaction already knowing which account it came from.
Put your bank feed on a review schedule
Separate payroll, tax reserves, and operating cash before the feed imports transactions. When payroll, taxes, and operating cash live in separate accounts before syncing, bookkeeping starts with cleaner inputs and a dependable close trail. Routine items move quickly, exceptions stay visible, and the final reconciliation leaves a trail a controller, accountant, or future hire can follow later.
If cleanup keeps slowing your close, opening a Relay account gives each purpose-built checking account its own labeled feed, so review starts with cleaner inputs instead of a mixed transaction pile. Separate your operating cash from reserves before the feed imports, then hand your reviewer a cleaner queue.
Frequently asked questions
Is a bank feed safe?
Yes, for the way standard feeds work. Standard bank feeds are read-only, so transaction data flows from the bank into the accounting software, and a feed can't move money or change settings at the bank. An application programming interface (API) is a direct data pipe between systems that lets the bank and software pass data without sharing your banking login. Older aggregator connections may store credentials so the service can collect transaction data.
How often does a bank feed update?
A bank feed updates on the connection's refresh schedule. The software shows cleared bank activity after the feed refreshes, so a payment sent this morning may appear later.
What's the difference between a bank feed and bank reconciliation?
A bank feed brings cleared bank activity into your software. Bank reconciliation checks the software balance against the bank statement and resolves any gaps.
Can I connect multiple bank accounts as bank feeds?
Yes. Each account can feed into the software on its own, which keeps the review tied to how the money is already organized. Keep each account's purpose clear so the reviewer can match payroll, tax, and operating activity without guessing.
