Avoid duplicate bank transactions in QuickBooks Online uploads

Find the overlap before making another upload

Intuit documents a common cause of duplicates: a bank feed brings in transactions that were already uploaded manually. Before preparing another file, identify the selected account, the dates already present and the exact gap you need to fill.

Write a short handoff note with the file name, account identifier, date range and transaction count. Keep that note with the reviewed source data. If another person manages the feed, confirm the coverage with them before treating a blank-looking view as proof that transactions are absent.

Compare the transaction, not just its amount

In a fictional account, a $60 fuel purchase on September 8 appears in both a manual file and a bank feed with the same reference and source detail. That is evidence to investigate as a duplicate. Two different $60 fuel purchases on September 8 are not duplicates merely because their dates and amounts match.

Check description, reference, source statement and the state of the existing QuickBooks row. A pending item and its later posted record also need context. Preserve the original records until you know which entry represents the actual transaction and which is the extra copy.

Use the review controls for a confirmed extra copy

Intuit’s current instructions place exclusion under Bank transactions, in the For review tab. Select the confirmed extra transaction and choose Exclude. A mistaken exclusion can be reversed with Undo in the Excluded tab.

Those instructions concern transactions awaiting review. Do not assume the same action is appropriate for an entry already added, matched or reconciled. Inspect its current state and use the applicable QuickBooks guidance before changing accounting records. The linked Intuit source is the authority for current navigation.

Check the result without deleting a whole period

After handling a confirmed extra copy, compare the remaining transaction list with the source period. Check both the row count and the total movement. A count that drops by one is not sufficient if the removed row belonged to a different real transaction.

For an overlapping upload, resolve the identified overlap rather than clearing the whole period and starting again. Broad removal can affect rows that were already reviewed. Keep a note of which copy was excluded and why so a later feed update or reviewer can follow the decision.

• The selected QuickBooks account matches the statement account.
• Every retained transaction has source support.
• Every excluded row has a confirmed corresponding transaction.
• The revised list still covers the required dates without a new gap.

Keep conversion and duplicate review separate

Fulla prepares exports from an approved statement revision; it does not inspect your QuickBooks account or provide a direct bank feed. An OFX transaction ID can help a receiving importer identify repeat rows, but it does not guarantee that a separate upload or bank-feed entry will match.

Use the existing QuickBooks handoff guide for accepted file types and upload preparation. For duplicate prevention, the critical work is comparing the destination’s existing coverage with the rows you intend to add.