QuickBooks Bank Feeds: Match, Post and Reconcile

QuickBooks Online (QBO) is cloud accounting software used by business owners, office teams and accountants to record transactions, invoice customers and review financial reports. Reconciling means comparing the accounting records with the bank statement for the same period and explaining differences.

A bank feed brings bank and card transactions into QuickBooks for review. Match links a bank item to a transaction already in the books. Add creates a new entry. Before adding an item, check whether an invoice payment, payroll entry or expense already records it. Otherwise the same cash movement can be counted twice.

If the feed and the books disagree, start with the bank statement, the existing accounting entry and the feed item for the same account and dates. The detailed checks below explain payroll, duplicate-looking amounts and other cases where a quick match can be misleading.

Payroll clearing and duplicate posting: trace one pay run first

Trace the existing posting before accepting a feed item

A payroll journal is the accounting entry for a pay run. It can already record expense and a funding liability, an amount still to be paid or cleared through payroll funding. The later bank debit may settle that liability, rather than create another wage expense. Payroll approval, the days employees worked, funding and bank settlement have different dates and evidence. Settlement here means the money actually moving through the bank. The correct mapping depends on the actual authorized posting route. The same applies to card settlement and transfers: inspect both accounts before assigning another expense.

After reconnecting a bank, verify which account is actually selected in the software and compare the downloaded period against an independent statement. Keep main card programs, checking and loans separate. A legitimate monthly subscription can repeat at the same price. A suggested journal can contain an earlier transaction date beside a different bank-reported feed date. Never infer duplicate identity from amount alone. If an approved correction replaces one lump-sum month-end journal with supported individual entries, first prove that the replacement changes each account by the same net amount. Then review individual bank matches. Moving entry dates can still change balances within the month, which need a fresh statement-cycle check.

Review a clearing account according to its purpose

A clearing account temporarily holds amounts while related entries move between systems. Its remaining balance needs an explanation; it does not always have to be zero at month end. An account holding unsettled transfers, a customer-deposit liability and an expense account awaiting allocation require different checks. A customer-deposit liability records money received for work still owed. Expense allocation assigns a recorded cost to the job, department or other reporting category it belongs to. A supported deposit or unsettled transfer may remain at the cutoff, the final date covered by the review. Intuit's deposit guidance describes a liability workflow for customer money received before services are performed. Retain a schedule explaining the remaining obligations. Identify the underlying customers, obligations or settlement items before deciding whether a balance is unexplained.

For an expense account intended to clear during the monthly close, inspect the completed month's accrual profit-and-loss statement (P&L) and recorded transaction detail. Accrual reporting records revenue when earned and expenses when incurred, which can differ from when cash moves. A lifetime account balance or unfinished current month answers a different question. Ask for the missing support and record the exception. Do not create a plug entry, an unsupported adjustment chosen only to make the total match, merely to make an account zero; any correction needs the actual error, accounting basis and authorized posting route.

Chase card control: one parent total, several possible mappings

A parent card account can contain several individual employee cards, or subcards. A statement can prove the parent’s total without proving which accounting accounts should receive each subcard’s purchases. Separate those questions. First identify checking versus credit card, the selected accounting account and statement period. Check the debit/credit sign convention: whether each source shows purchases, payments and credits as positive or negative amounts. Then compare the statement total with the sum of the retained transactions. Only after that should you allocate records to child accounts or cardholders.

Last-four digits help find a candidate account; they do not establish the whole identity. As a collection precaution, check whether a saved account list still matches the active accounts. Confirm the active account and parent/subcard structure before changing a bank connection. Check whether a newly linked account would download purchases already collected through the parent. See the Chase playbook for the source collection and account-selection questions.

What a "no deposit found" result actually establishes

A search box returning no result is weaker than reviewing a saved, ordered transaction list. Check the requested dates, opening and closing balances and row order. Running-balance continuity means each transaction explains the change to the next balance, and the full list explains the closing balance. Record exactly which account and period were examined. A bounded window does not exclude a batched receipt, split settlement, different account or transaction outside the window. Preserve those alternatives before concluding that a payment recorded in QBO had no cash component.

The same caution applies when card charges resemble supplier bills in accounts payable (AP), the amounts the business owes suppliers. A card charge resembling a supplier bill is an investigation candidate. Determine whether the bill, expense and payment record different stages: what is owed, when the cost is recorded and when cash pays it. Excluding one from a spreadsheet may make that spreadsheet balance while leaving the ledger unchanged. The review output should name the proposed accounting treatment and the reports to rerun after a change to verify the result (read-back evidence), not just mark the pair "duplicate."

{
  "fictional": true,
  "unit": "USD cents",
  "id": "bank-identity",
  "totalsTie": true,
  "matchedIds": [
    "A"
  ],
  "unmatchedBank": [
    "B"
  ],
  "unmatchedLedger": [
    "C"
  ],
  "decision": "Same amount and equal totals do not prove occurrence identity",
  "limitation": "This is teaching arithmetic from supplied invented inputs, not source authenticity, financial assurance or authority to post."
}

Collect the native report needed to resolve the exception

Keep the bank statement and accounting transaction detail for the same account and period. Compare them with the selected bank-feed items; for payroll, also retain the register and the existing pay-run journal. Read how to collect missing original reports with an authorized browser when the existing connection does not provide that evidence. The Financial Systems Field Guide holds the named-system collection notes, pitfalls and bounded prompts.

Recheck the statement cycle after changing posting dates

A correction can preserve month-end totals while changing a balance inside the month. For example, replacing a month-end aggregate with supported entries on their individual transaction dates changes the intermediate path even if the final account total agrees. That requires a fresh check against the actual statement cycle.

Retain the original entries, the approved replacement and the dates that explain the movement. Recheck the affected cycle after the change, keeping later clearing activity separate. An older passing reconciliation does not establish that the newly dated accounting records still match the statement.

Use the QBO example of equal totals hiding unmatched transactions to see how equal totals can hide unmatched records, and the Chase liability example to distinguish purchases from a card payment. Then apply the close investigation steps to the actual affected controls.

Sources and method

Field Guide. Level guidance explains how to check whether records support a financial conclusion. The worked examples linked above use visibly labelled fictional inputs. The financial-evidence section supplies a separate downloadable teaching calculation. No private customer documents or measured customer outcomes are included. Current account eligibility and report definitions must be checked before operational use.