On this page Jump to section
Question and scope
When a bank feed transaction has already been matched to an existing entry or categorized into a new one, does choosing Exclude in QuickBooks Online reverse the posted ledger entry, or does it only remove the bank line from the review queue? A bookkeeping VA meets this question after a duplicate download, a transfer that should not be booked, or a client instruction that arrives after the transaction was coded. The answer decides whether the next step is a deletion, a reversal, a reclassification, or no ledger work at all. A wrong assumption can leave a real expense in the profit and loss report while the feed looks clean.
The scope is one QuickBooks Online company file, one bank or card account, and one feed transaction that has a visible posted counterpart. It includes transactions matched to an existing entry, transactions categorized into a new entry, and transfers between two accounts in the same file. It excludes excluded transactions that were never posted, bank errors that require a statement correction, and account merges, because each of those questions has a different evidence path. The audit tests the visible bookkeeping result rather than the internal database write.
Why exclusion could affect a posted entry
A bank feed line and a ledger entry are two different records that can be linked. The feed line arrives from the financial institution, while the ledger entry carries the account, amount, date, name, and class that appear in reports. Matching or categorizing creates a relationship between them, and that relationship is what the Exclude action may break or preserve. The audit has to observe both records before and after the action rather than infer the result from the feed label.
The date of the action adds a second variable. If the posted entry sits in a closed period, a reversal could change a report that has already been reviewed, while a feed-only exclusion would leave the closed period untouched. If the entry sits in the current period, the ledger may still change without affecting a filed return. The test must record the transaction date, the posting date, and the accounting period status before it changes anything.
Population and baseline
Build the population from feed transactions that were matched or categorized during a defined window and still have a posted counterpart. Record the bank account, feed date, posted date, amount, transaction type, match status, and the ledger entry number. Include at least one matched transaction, one categorized transaction, and one transfer, so the test compares more than one relationship. Exclude lines that are still unreviewed, because they have no posted entry to reverse.
Freeze the baseline before making any change. Export the profit and loss report, the balance sheet, and the transaction list for the affected account with the same date range and accounting method. Save the bank reconciliation status and the audit log view for the transaction. Capture the exact report run time, because a later rerun can differ for reasons unrelated to the exclusion.
Test setup
Work in a copy of the company file when the subscription and the client permit it. A live exclusion can change a reconciliation, a report, and a client-facing balance in ways that are difficult to undo without a clear baseline. If a copy is not possible, schedule the test outside the close window, obtain written approval, and record every setting before the edit. The test must be reversible without guessing which values were original.
Change one relationship at a time. First test a matched transaction, because the match connects the feed line to an existing ledger entry. Then test a categorized transaction, because the category action created a new entry. Finally test a transfer, because both sides of the transfer may be affected. A test that excludes several transaction types at once cannot show which relationship produced the result.
Procedure
Run the baseline comparison before touching the transaction. Reopen the saved reports and confirm that they still match the exports from the test start. This step catches ordinary drift from later activity, so the audit does not blame the exclusion for a change that came from another user. Record the current balances and the report run time for each account involved.
Next, open the matched transaction in the bank feed and choose Exclude. Do not delete the posted entry first, because that would remove the relationship the test is meant to observe. After the action, check the feed tab, the transaction list, the account register, and the same reports. Compare the amount, date, name, and account of the posted entry line by line. Repeat the process for the categorized transaction and the transfer, reversing the state between tests.
Definitions and measures
A ledger reversal means the posted entry disappears or is offset so the account balance and the reports no longer include it. A feed-only exclusion means the bank line leaves the review queue while the posted entry remains in the register and reports. A broken link means the posted entry remains but is no longer matched to any feed line, which can leave the reconciliation in a different state from either of the first two outcomes. Name the observed category before writing the memo.
Measure the result at three levels. The first is the feed, where the transaction either remains visible in an excluded view or disappears from the review queue. The second is the register, where the posted entry either remains, changes, or disappears. The third is the report, where the account balance, the profit and loss line, and the reconciliation status either move or hold. Report all three, because a stable feed can hide a changed ledger and a stable ledger can hide a broken match.
Worked example
Suppose a client has a 240 dollar office supply purchase that was downloaded twice. The first feed line was categorized to Office Supplies, and the second line was matched to the same posted entry by mistake. A VA who excludes the second line may expect the duplicate to disappear from the expense total. If the exclusion only removes the feed line, the original 240 dollar expense remains correctly posted and the duplicate match is gone.
The VA reruns the profit and loss report and the account register after the exclusion. If the expense still shows once, the result is a feed-only exclusion with the desired ledger outcome. If the expense disappears entirely, the exclusion reversed the posted entry and the VA must restore it. If the entry remains but the reconciliation shows an unmatched line, the VA documents the broken link and rematches it. The test identifies the state; the client's accountant decides whether any further correction is appropriate.
Evidence standard
The evidence set includes the baseline reports, the feed screenshot before and after, the register detail, the reconciliation status, and the audit log entry for the action. Each claim in the memo should point to a specific artifact with a timestamp and the user who performed the step. A statement that the ledger did not change is credible only when the same report, date range, and accounting method are shown before and after with identical figures. Add at least two transaction examples so the conclusion rests on more than one line.
Keep the raw exports rather than only a summary table. A summary can omit the account, the match status, or the transaction type that actually determined the result. If the report cannot be reproduced because the period is locked, the transaction was deleted by another user, or the bank connection changed, say so and lower the confidence of the conclusion. Do not fill the gap with an assumption about how the product should behave.
Interpretation limits
A result in one company file does not prove that every QuickBooks Online edition or every bank connection behaves the same way. The outcome can depend on the transaction type, the match state, the account type, the period status, and whether the feed line was manually added. Record the product edition, the bank connection, and the test date so a later reviewer can judge whether the result still applies. A second account with a different connection is a useful follow-up test.
The audit also cannot see every internal state that the interface hides. A feed line may be removed from the review queue while a related record remains in a background table, and the visible reports may not expose that difference. A clean result means no visible change in the fields examined, not proof that no database write occurred. The memo should state that boundary and identify the fields that were not observable.
Review cadence
Repeat the test after a bank connection change, after a QuickBooks Online release that alters the bank feed, and before a close in which a VA plans to exclude matched transactions at scale. A quarterly spot check is reasonable for a client with a high volume of duplicate downloads, while a low-volume client can review once a year. Put the next review date in the client's close calendar rather than in a personal reminder. Record the previous result beside the new one so a change in behavior is visible immediately.
Close the review with a named owner, the exact report settings, and a date for the next check. Link the result to the bank feed exception review workflow and the bank reconciliation exception log so the next reviewer starts from the same evidence. If the exclusion changes the ledger, convert the finding into a documented correction with an approval step. The test explains the state; the accountant decides what belongs in the close.
