Bank Feed Reconciliation: Why 'Matched' Isn't 'Reconciled'

Introduction

Every transaction in the feed shows a green checkmark. The client's books still don't tie to the bank statement. Off by $1,240. If you run bank feed reconciliation for 15 or 20 clients, you've hit this exact moment. The feed says done. The statement says otherwise.

Here's the claim this article stands on: matching transactions in a bank feed is not reconciliation. They're different jobs. One pairs transactions. The other proves your books are complete.

Definition Box: Bank feed reconciliation is a two-part discipline. Part one: match imported feed transactions to entries in your books. Part two: tie the account's cleared activity to the bank statement's closing balance. Only part two proves the books are right. A feed with every transaction matched can still hide duplicates, gaps, and missing entries.

By the end you'll have a month-end checklist that catches what the feed misses. It takes about 15 minutes per account once it's a habit.

Key Takeaways

• Matched is not reconciled: bank feeds pair transactions; reconciliation proves the account ties to the statement balance.
• Feeds fail silently: duplicates, dropped transactions, and month-boundary timing all hide behind green checkmarks.
• QBO: the Banking screen is feed matching; the Reconcile module is where the real tie-out happens. Audit auto-add rules quarterly.
• Xero: the "Reconcile" tab is matching too. The Reconciliation report against the statement balance is the proof.
• Monthly discipline: 8 steps, about 15 minutes per account, with the bank statement as the truth source every time.

Body

The bank feeds vs reconciliation confusion is the most common bookkeeping gap we see in QBO and Xero files. Here's how it happens, where it bites, and how to close it.

What bank feeds actually do (and don't)

A bank feed pulls transactions from the bank and suggests matches. That's it. It's a data pipe with a matching assistant on top.

The feed does three things well. It imports transactions so you don't key them by hand. It suggests matches against existing entries. It remembers your categorization patterns.

Here's what it doesn't do. It doesn't prove completeness. A feed can drop transactions during an outage and never tell you. It doesn't catch duplicates from a reconnected connection. And it doesn't compare your book balance to the bank's closing balance. Matching is per-transaction. Reconciliation is account-level proof. We've broken down the automated vs manual payment reconciliation trade-off separately; this article is about what neither mode can skip.

Think of it like counting cars in a parking lot by checking tickets. Every ticket can match a car. You still haven't counted the cars without tickets.

The distinction matters because the two jobs fail differently. A bad match is visible: you can click it, review it, and fix it. A missing transaction is invisible until you compare totals against the bank's own record. Feeds make the visible work faster. They do nothing for the invisible work. That's not a flaw in QBO or Xero. It's the design: feeds were built to cut data entry, not to audit completeness.

Where "matched" goes wrong

Four failure modes show up over and over.

Duplicate entries. A bank connection breaks and gets reconnected. The feed re-imports two weeks of transactions. Now there are 3 duplicate deposits sitting in the books, and revenue is overstated by $4,800. Every one of them shows as matched or added.

Missing transactions. Feed outages leave silent holes. The bank posted 212 transactions in March. The feed delivered 207. Nothing in QBO or Xero flags the missing 5. Only the statement tie-out finds them.

Bank-initiated items that never hit the feed. Adjustments, reversed fees, and some wire corrections post at the bank but arrive late or never. Your books drift without a single unmatched transaction.

Month-boundary timing. A deposit posts on the 31st at the bank and the 1st in the feed. Matched? Yes. In the right month? No. That's a clean-looking feed and a wrong P&L. Lump-sum processor deposits make this worse: see how to reconcile lump-sum deposits from payment processors, and why Stripe bookkeeping deserves its own workflow.

QBO bank feed matching: what to check

QBO bank feed matching runs through the Banking screen. Green checkmarks, Match buttons, and auto-add rules. It feels like progress. Three traps to check.

First, auto-add rules create entries without review. A rule that says "anything from Amazon goes to Office Supplies" will happily file a $2,100 equipment purchase as supplies. Rules add speed and remove eyeballs. Audit your rules quarterly.

Second, QBO's suggested matches run about 50% accurate in real client files. The other half need a human call. Accepting suggestions in bulk is how a client's loan payment ends up matched to a vendor bill.

Third, the Banking screen is not the Reconcile module. Clearing the feed queue does not reconcile the account. Open Accounting, then Reconcile. Enter the statement ending balance and ending date. Work to a $0.00 difference. That screen, not the feed, is where reconciliation happens in QBO.

Two QBO details trip people up in that module. Undeposited Funds can make a clean feed look wrong: payments sit in the holding account while the bank shows one combined deposit, so match deposits to grouped payments before you start the tie-out. Our payment reconciliation guide walks that matching flow step by step. And QBO lets you finish a reconciliation with a difference by forcing an adjustment entry. Don't. A forced adjustment is an unknown error with a journal entry on top. Find the gap or leave the reconciliation open with a note.

Xero bank reconciliation: same trap, different UI

Xero bank reconciliation has a sharper naming problem. Xero's main screen literally says "Reconcile" on the feed-matching tab. You can click OK on every line and Xero calls the account reconciled. It isn't. That tab is feed matching.

The real check in Xero is the statement balance comparison. Open the bank account, then Reconciliation report. Compare the statement balance to the balance in Xero as of the statement date. If the feed dropped transactions, this report is where the gap shows.

Two Xero-specific checks. Watch for manually added statement lines, which can double up against feed imports. And run the Bank Reconciliation Summary monthly. Unreconciled statement lines older than 30 days are a red flag, not a backlog item.

Xero's cash coding screen deserves the same caution as QBO's rules. Bulk-coding 80 lines in one pass feels great on a Friday afternoon. It also files 80 judgment calls in 4 minutes. Keep bulk coding for true repeaters like bank fees and card processor payouts, and slow down on anything with a varying amount or a new payee.

The month-end tie-out: reconcile to the statement, not the feed

The discipline is one equation. Opening balance plus cleared activity equals the statement closing balance. Every account, every month. If the mechanics are new, our bank reconciliation guide covers the full walkthrough; this section is the bank-feed-specific layer.

The feed is an input. The statement is the truth source. When you reconcile bank feed transactions, you're checking the feed's work against the bank's record, not the other way around. The bank's PDF wins every dispute.

This matters most when you carry a full client list. A bookkeeper with 14 clients and 3 accounts each has 42 tie-outs a month. Skip them for a quarter and you're not behind on a chore. You're carrying unknown errors in 42 accounts, and clean-up billing conversations are no fun.

One more habit worth building: reconcile in the same week the statement drops. Most banks post statements within 3 business days of month close. A tie-out done on the 5th catches a feed gap while the bank's support team can still explain it. A tie-out done in October for a March statement turns a 15-minute fix into a forensic project.

A month-end bank-feed reconciliation checklist

Run this per account. Budget 15 minutes once it's routine.

1. Pull the bank statement PDF for the month. Not the feed export. The statement.
2. Clear the feed queue first. Match or add every imported transaction so the queue is empty.
3. Open the reconcile screen (QBO: Reconcile module; Xero: Reconciliation report) and enter the statement ending balance and date.
4. Tie out to $0.00. Opening balance plus cleared activity must equal the statement close.
5. Investigate every gap by type: duplicates first, then missing transactions, then timing items.
6. Count transactions. Statement count vs feed count. A mismatch means a silent feed gap.
7. Check for stale uncleared items. Anything uncleared over 60 days needs a decision, not another month of waiting.
8. Save the reconciliation report to the client file. The report is your proof when the feed misbehaves later.

Print it, pin it, or build it into your close template. The order matters: a noisy feed queue makes step 4 impossible to read. If you close full sets of books monthly, fold these steps into the month-end close checklist so reconciliation lands in sequence with billing and accruals.

Conclusion

The feed queue at zero feels like a finished job. It's half the job. The statement tie-out is the half that protects you, because it's the half that catches what the feed never shows.

If you run books for 10, 20, or 30 clients, the math is simple. The matching half is hours of clicking. The proving half is minutes per account. Automation should eat the clicking so your time goes to the proof, the review, and the judgment calls clients actually pay for.

That's the model we're building toward: software handles automated expense categorization and the matching grunt work, you review and approve, and the tie-out is waiting instead of buried. Get early access to Growthy and put your hours into the half of reconciliation that needs a professional. Get Early Access.