Bank feed matching and bank statement reconciliation prove different things. Matching a feed shows that each imported transaction has a ledger entry. Reconciling to the statement shows that the ledger agrees with the bank's own closing balance for the period, which catches transactions the feed dropped or doubled. A clean feed does not replace the statement.
What bank feed matching actually checks
Bank feed matching pairs each transaction imported through a bank connection with an entry in the accounting software, or creates one. It checks that every line the feed delivered has a home in the ledger. It does not check that the feed delivered every line the bank posted, or delivered each one only once.
A bank feed is an automated connection that pulls transactions from a bank into accounting software such as QuickBooks Online or Xero. The software then suggests a match for each line: an existing invoice payment, a bill payment or a rule-based category. A bookkeeper accepts, changes or adds an entry, and the line leaves the review queue.
When the review queue is empty, three things are true:
- Every transaction the feed imported has been looked at.
- Each one is tied to a ledger entry or a new categorized transaction.
- The categorization reflects whatever rules and judgment were applied.
What an empty queue does not prove is the part that matters most for the account's balance. If the feed skipped a week of transactions, there is nothing in the queue to match, so nothing looks wrong. If a reconnection imported a week twice, both copies can be matched or added. The queue measures the work done on what arrived, not whether what arrived was complete.
A categorized feed is still useful. It speeds up data entry, it applies rules consistently, and it gives a near-daily view of activity. The comparison below is about what each method proves, not about which one saves more typing.
Why is the bank statement the source of truth for reconciliation?
A bank statement is the bank's formal record of an account for a period: opening balance, every posted transaction and closing balance. Reconciling to it tests the ledger against a figure the bank stands behind. A feed is a copy delivered through a connection, and a copy can be incomplete without anything announcing it.
The reconciliation tools in accounting software are built around the statement. Intuit's article Reconcile an account in QuickBooks Online tells the user to "Enter the Ending balance and Ending date from your account statement," then compare the transactions in the reconciliation window with the statement until the difference is $0.00. The anchor is the printed closing balance.
The IRS describes the same habit for small businesses. IRS Publication 583 says that when the bank statement arrives, the statement, the checkbook and the books should agree, and that the checking account should be reconciled each month.
Three properties make the statement the better anchor:
- It has a fixed period. A statement covers set dates, so its opening balance must equal the prior statement's closing balance. A gap or overlap is visible.
- It carries totals. Total deposits and total withdrawals are printed, so the sum of the lines can be checked.
- It is a document. It can be filed, sent to a reviewer and produced later, which a list of feed lines on a screen cannot always do.
Firms working in Xero make the same comparison between two figures: the statement balance and the balance in Xero. How to read that pair, and what to do when they differ, is covered in statement balance versus balance in Xero.
Bank feed failures: dropped, doubled and late transactions
Bank feed failures come in three kinds. Dropped transactions never arrive, so the ledger understates activity. Doubled transactions arrive twice, so the ledger overstates it. Late transactions arrive after the period closes and land in the wrong month. Matching alone hides all three, because each one leaves the review queue looking normal.
Doubled transactions
Intuit's help article Fix duplicate transactions in QuickBooks Online bank feeds says duplicates can happen if you "reconnect an account, import a file that overlaps with your bank feed," add a downloaded transaction instead of matching it, or record the same sale in two ways. It also warns that deleting a downloaded duplicate does not stop it: "QuickBooks will download it again from the bank." Excluding it is the route the article gives.
Every one of those causes is a normal event in a bookkeeping year. Banks change connection providers. A bookkeeper uploads a CSV to fill a gap and the date range overlaps. A new staff member adds a line instead of matching it to an invoice already entered.
Dropped transactions
A dropped transaction is one the bank posted and the feed never delivered. It might be a connection that stopped for several days, an account the connection never covered, or a transaction type the import skipped. Nothing appears in the queue, so nothing is matched or flagged. The only place the transaction exists is the statement.
Intuit's article on fixing issues at the end of a reconciliation in QuickBooks Online lists "missing or duplicate transactions in QuickBooks" among the causes of an ending balance that will not tie, and tells the user to compare the bank statement with the reconciliation window to find them.
Late transactions
A late transaction is one that posts at the bank in one month and arrives in the ledger dated in another, or arrives after someone has already closed the month. The feed's totals for the month then differ from the statement's. Matching each line still succeeds, so the error only shows when the month's ledger balance is compared with the statement's closing balance.
Bank feed and statement reconciliation side by side
Bank feed matching and statement reconciliation can be compared on four points: the evidence each rests on, the gaps each catches, the duplicates each catches and the audit trail each leaves. Feed matching is fast and continuous. Statement reconciliation is periodic and slower, but it is the only one that tests completeness against the bank's own figure.
The table below compares them for one fictional account, Juniper Row Bakery's operating account ending XXXX-4821, for an example month of March. Values are examples.
| Point of comparison | Bank feed matching | Statement reconciliation |
|---|---|---|
| Evidence it rests on | Lines delivered by the connection | The bank's statement, with a printed opening and closing balance |
| Example result for March | 212 lines imported, 212 matched, queue empty | Statement closing balance $14,906.15, ledger $14,426.15, difference $480.00 |
| Gaps caught | None; a missing line never enters the queue | A dropped $480.00 card deposit shows as an unexplained difference |
| Duplicates caught | Only if a person notices two similar lines | A doubled line inflates the ledger and leaves a difference to explain |
| Wrong-month items | Not visible; each line still matches | Visible as a difference between the month's ledger and the statement |
| Audit trail | A record of who matched what, inside the software | A dated report tied to a statement that can be filed with the workpapers |
| How often | Daily or weekly | Monthly, after the statement closes |
In the example, the feed said March was finished. The statement showed a $480.00 difference, traced to a card processor deposit the feed never imported, and the dropped deposit only came to light because someone compared the ledger to the printed balance.
Tracing a difference like that $480.00 follows a short routine:
- Confirm the opening balance in the ledger equals the statement's opening balance. If not, the problem is in an earlier month.
- Compare the statement's total deposits with the ledger's total deposits for the month, then do the same for withdrawals. The side that differs narrows the search by half.
- On that side, look for the exact amount first. A single dropped or doubled line usually shows up as one amount equal to the difference.
- If no single line matches, sort both lists by date and compare them week by week until the missing or extra lines appear.
The same routine finds doubled lines. A doubled deposit leaves the ledger higher than the statement, and a doubled payment leaves it lower. Either way, step 3 usually finds one line whose amount equals the difference, sitting next to an identical line on the same date.
The two methods work best together. The feed does the daily entry, and the monthly statement reconciliation checks the feed's work. Comparing the kinds of software that do each job is the subject of tools for bank account reconciliation, and the guides in QuickBooks, Xero and Excel cover each product's screens.
When can bank feed matching stand in for a statement reconciliation?
Bank feed matching can stand in for a statement reconciliation only when something else proves the feed was complete for the period, such as the ledger balance agreeing with the bank's balance on the period's last day. Without that comparison, matching proves activity was entered, not that every transaction is there.
Firms weigh a few factors when deciding how often to reconcile to the statement:
- What the numbers feed into. Figures going into a tax return, a loan application or a financial statement a third party relies on usually call for a statement reconciliation of the period.
- Volume and complexity. An account with a few dozen transactions a month and no reconnections is lower risk than one with thousands of card deposits and frequent manual imports.
- History of the connection. An account whose feed was reconnected, migrated or supplemented with CSV uploads during the year has exactly the risks Intuit lists for duplicates.
- Who reviews the work. A reviewer who did not do the matching needs a document to review. A reconciliation report tied to a statement is easier to check than a feed history.
One middle path is to match the feed through the year and reconcile to the statement each month-end or quarter-end, plus the final month of the year. Whatever the schedule, the statements have to be in hand. A client who never sends statements leaves the firm relying on the feed by default, which is the case this post argues against.
Collecting statements is often the slow part. Schema CPA takes the statements a client uploads, checks that each month opens on the last one's closing balance and names any month that is missing, so a gap shows up before reconciliation starts; the document categories it reads are listed on the homepage. What to require from software built for statement reconciliation is covered in bank statement reconciliation software.