Software collection playbook

QuickBooks Online: bank feed versus booked evidence

Booked reports versus pending bank feed.

By Sam Yang · Updated 2026-10-07

Is the missing transaction unbooked, unmatched or merely on another page?

Choose the next source from the transaction state. A Pending queue answers what needs review; it cannot answer whether the bank history or posted ledger is complete.

Evidence basis: Saved bank-feed and payment-review observations. This is a collection method, not a promise of every account menu. Some checks restate Level review safeguards (code rules, not observed vendor behavior).

Check supported booked entities and report scope first; collect native bank/feed evidence only for the specific missing population.

The item already names a matched or categorized posting

Inspect that existing entry and its source identity. Do not add a second entry because the amount resembles an expected charge.

The feed queue is empty but a bank movement remains unexplained

Use the selected bank account statement and posted ledger history. Reconnecting the feed is not the first diagnostic step.

Use supported API or native report access for the required scope. A permitted browser session can collect a specific gap. Neither route proves reconciliation or complete costs.

Put the evidence to work

The bank feed is empty and the bank balance agrees. Can we close the account?

Those are two useful controls, but they do not prove the transactions are right. A missing receipt and an extra receipt can offset. Review the statement period, opening balance and individual bank occurrences against the booked register before treating the account as reconciled. The feed queue describes work awaiting review, not the whole statement.

Trace one bank occurrence before considering a correction

Identify the QBO company, bank account ID, masked bank suffix and closed statement period. List any other ledger accounts that might contain that account's activity.
Locate the bank occurrence by statement or direct activity evidence. Keep its date, sign, amount and source reference; equal amounts are separate candidates until identity is established.
Collect the booked transaction and, where useful, the feed row. After a native account or tab switch, wait for the header and table to describe the same account and page.
Inspect any existing linked posting. Keep its transaction type, ID, account and party separate from the feed status. For receipts, distinguish cash received from invoice credit applied. For Bill Pay questions, keep the original remittance and current payment-history status together; an estimated refund date is not settled cash.
Record one of three findings: supported existing posting, source occurrence still unmatched, or conflicting evidence. Preserve both sides of any conflict.

Bring to the review: An occurrence worklist containing bank reference, booked ID if found, account, evidence link and unresolved difference.

Then decide: An accountant can review a specific correction only after this chain is complete. A similar name or amount is a candidate, not a decision to add, match or remove a transaction.

Find the first month a cash difference appears

Retain contiguous closed statements and their opening balances, closing balances and section totals. Validate any parsed detail against those controls.
Collect the same bank account's booked GL for each period, using the same cutoff. Keep the partial current month separate.
Calculate each monthly closing difference and activity difference. Compare the prior statement ending balance with the next opening balance.
Investigate the earliest unexplained difference, then carry its effect forward. Inspect activity in possible duplicate ledger accounts without silently combining them.
Check unmatched rows even when the final net balance is zero. Explain equal and opposite differences with source identities rather than a balancing journal.

Bring to the review: A monthly bridge plus a row-level exception list, with source gaps distinct from accounting differences.

Then decide: Resolve the first unsupported occurrence or scope difference before proposing a cleanup. A zero final difference can coexist with incorrect intermediate months or offsetting errors.

Which collection route answers this question?

Choose the route for the missing evidence and the access available in your account. The comparison below distinguishes documented coverage from coverage that still needs checking.

Accounting API

What it supplies: Intuit documents booked accounting entities and report workflows. These are useful for repeatable register and report collection.
What still needs proof: The documented accounting route does not by itself establish a complete native pending-bank-feed population. Validate the exact report, fields, accounting basis and account scope.

Choose it when: Use it for supported booked evidence. Investigate a specific missing source population before choosing another route.

Native reports and bank files

What it supplies: A native booked report and independent statement provide different sides of the review. Retain complete received files and original controls.
What still needs proof: An observed posted-feed CSV exported a selected page in the saved procedure. This is an observation about that workflow, not a universal current export limit.

Choose it when: Use files for statement controls and the particular detail not covered by the verified API.

Permitted browser inspection

What it supplies: Saved procedures support inspecting account headers, feed provenance and linked existing entries without changing them.
What still needs proof: Rendered rows may lag pagination indicators. Interface labels and collection scope need current verification; inspecting a row does not validate its accounting treatment.

Choose it when: Inspect a small unresolved set or collect an authorized native source that has no adequate verified alternative.

Reproduce the diagnostic

A perfect net tie hiding two unsupported occurrences

All records and amounts below are fictional teaching inputs. This example demonstrates the calculation, not a customer outcome or a reproduced software defect.

Statement movement is 500 - 200 = 300. Book movement is -200 + 500 = 300. Both end at 2,300, but statement occurrence S-01 has no supported posting and B-02 has no supported statement occurrence.

What the CSV columns mean

All rows and identifiers are fictional teaching data in USD, not customer results or QBO-native exports.
amount is signed bank-account movement: receipts positive, payments negative. occurrence_id identifies the hypothetical bank event.
review_state is a supplied teaching classification after occurrence investigation, not an amount-only automated match. The account opens at USD 2,000 in both sources.

Statement movement: 300 USD; Net movement in the complete fictional statement.
Book movement: 300 USD; Net movement in the fictional register.
Net movement difference: 0 USD; Equality of totals does not resolve identities.
Unmatched statement occurrences: 1 rows; S-01 requires investigation.
Unmatched booked entries: 1 rows; B-02 requires investigation.

Inspect statement.csv

occurrence_id,date,amount,review_state
S-01,2026-09-04,500,unmatched
S-02,2026-09-08,-200,supported

Download this CSV

Inspect book.csv

book_id,date,amount,occurrence_id,review_state
B-01,2026-09-08,-200,S-02,supported
B-02,2026-09-12,500,UNKNOWN,unmatched

Download this CSV

Next decision: Investigate S-01 and B-02 separately. The example supplies no authority to remove B-02, create S-01 or classify either receipt as revenue.

Expected results and calculation checks Download the reproduction code

Run the example locally

Save the CSV files, expected-results.json and reproduce.mjs in one folder. With Node.js installed, run the command below. It calculates the checks from the CSV bytes and rejects a changed input or expected result.

node reproduce.mjs expected-results.json

No software login, customer records or API key is required.

When the result does not make sense

Closing balances match, but the owner disputes a receipt.

Check: Count and identify unmatched bank and book rows separately; test whether equal and opposite errors mask the net difference.

Resolve the question: Produce the offsetting occurrence chain with original references. Keep both findings open for review instead of declaring a clean tie.

A same-value suggestion names a different vendor.

Check: Compare exact party identity, bank description, account, date and the underlying bill/payment relationship.

Resolve the question: Reject the suggested identity as unproven and return the competing candidates. Do not choose the nearest amount automatically.

After changing accounts or pages, the table still looks familiar.

Check: Read the rendered account header, selected page and actual row dates after loading ends. Compare exported count with visible count and total.

Resolve the question: Recollect the affected page and mark earlier capture as stale. Do not count an unchanged old table as a new page.

Where automation earns its place

Good work for automation

Repeatable statement-control checks, account inventories, monthly bridges and exception worklists are valuable automation tasks. Retain source identities and the chosen cutoff with every run.

Keep a person on these decisions

A reviewer determines whether a bank occurrence represents a bill payment, new expense, transfer, refund or other event, and approves any accounting change. An AI should expose ambiguous candidates rather than convert similarity into a posting.

References behind these workflows

Product documentation supports the specific scope stated beside each source. Level's diagnostic methods and fictional calculations remain distinct from vendor capabilities.

Intuit Accounting API overview
Booked accounting API scope; not proof of bank-feed completeness. Reviewed 2026-10-07.
Intuit report workflow
Supported report workflow, with exact request scope to verify. Reviewed 2026-10-07.
Intuit duplicate transaction guidance
Reconnect/import overlap and existing-entry identity, not a license for automated deletion. Reviewed 2026-10-07.

Explore the financial diagnostic examples

Collect and verify the population

Native bank activity: Bind the intended account, actual occurrence and statement period, including reversals or later repeats.
Feed row and existing posting: Wait for the selected page and rendered rows to agree; retain the existing transaction identity if present.
Invoice, payment and credit graph: Keep cash received separate from credit applied. An invoice marked paid does not by itself identify the cash deposit.

Read the selected account and exact period; retain complete native statement/report bytes or every observed feed page, with transaction identifiers. Compare feed coverage separately from booked balances. Wait for final account header, selected page and table population to agree, including after switching to Categorized. If a row already shows a matched or categorized entry, record its existing identity and amounts; inspect that entry without changing it.

Evidence acceptance checklist

Confirm the bank account header after each account or tab switch.
Keep uncategorized feed occurrences separate from posted transactions.
Inspect an existing matched or categorized entry by identity without changing it.

Fictional collection example

A fictional checking account has an empty uncategorized queue, but the statement contains a transaction outside the collected date range. Return the missing period as an exception. Do not label the account reconciled because the queue is empty.

Invented teaching scenario, not a customer result or a reproduced vendor defect.

Capture the setup with the evidence

Company, legal entity or account, report name, period, basis, currency and timezone.
Selected filters, status, page count, original record identifiers and control totals.
Collection time, source route and authorized role. Record browser and automation versions when using a browser.
Original files and exceptions. Keep credentials, customer identifiers and financial artifacts private.

A browser version helps reproduce an interface issue. It does not validate the financial conclusion.

Pitfalls and stop conditions

A downloaded first page, uncategorized feed item or connected bank is not a complete posted ledger. Reconnect can map to the wrong account. Same-value suggestions can name different vendors. Genuine repeated charges are not duplicate downloads. An existing posting may already represent a feed occurrence; inspect its identity instead of adding or matching. An empty feed queue is not statement reconciliation.

How a plausible answer can go wrong

A nearby deposit of the same amount can be a different occurrence. Similarity is a lead for investigation, not permission to match or change the books.

Stop if account identity, permission, cutoff or population is uncertain. Return the missing evidence for review. Do not fill the gap with an invented record, a balancing entry or an assumed zero.

Read-only AI collection prompt

Replace the bracketed scope before use. This prompt collects evidence; it does not permit edits, approvals or accounting execution. Requesting an emailed report is a separate account action and requires explicit authorization.

Collect read-only evidence for QuickBooks Online to answer [financial question]. Confirm [company], [account/entity], [period], [basis], [currency] and [allowed reports]. Read the selected account and exact period; retain complete native statement/report bytes or every observed feed page, with transaction identifiers. Compare feed coverage separately from booked balances. Wait for final account header, selected page and table population to agree, including after switching to Categorized. If a row already shows a matched or categorized entry, record its identity and amounts without changing it. Retain original files, complete record IDs, counts, filters, collection timestamp and exceptions. A downloaded first page, uncategorized feed item or connected bank is not a complete posted ledger. A reconnection can map to the wrong account. Same-value suggestions can name different vendors. Genuine repeated charges are not duplicate downloads. Record any existing posting that may represent the feed occurrence for financial review. Do not match, add or categorize. An empty feed queue is not statement reconciliation. Stop if the source or scope is uncertain. Do not post, match, reconnect, delete or change settings. Return the evidence for financial review; do not claim the books are correct. Do not approve, submit payroll, pay, transfer, refund, send messages, invite users or accept terms. Stop at any login, MFA or credential prompt and hand back to the account owner. Store files only in [approved private location]. Do not paste customer artifacts into public tools. Use only preauthorized collection actions. Request an emailed report only when its delivery is explicitly authorized; otherwise ask the account owner to supply the file.

Next decision

What does the evidence support?

Can the owner identify one bank occurrence, its existing posting if any, and the unresolved difference? If that chain is incomplete, hold the proposed correction instead of creating a balancing entry.

Compare the same population, identities and cutoff. Keep unsupported costs or settlements visible before using the result for pricing, cash or close.

Open the financial acceptance guide →

Review documented API and capability scope

Sources and scope

Base product-reference scopes were reviewed 2026-10-06. No end-to-end dated native UI walkthrough is published for this software. Individual source rechecks are dated with their citations. Operator decision guidance was reviewed 2026-10-07. The references below support their stated product scope, not every observed interface detail. It is not a vendor capability certification, a measured customer result or an independently reconciled account. Verify current features and entitlement in the account you use.

QuickBooks Online Accounting API overview
Accounting API reference, not native bank-feed completeness.

Content revision history