Quickbooky

Accounting News

Banking & Feeds

QuickBooks Online users report duplicate transactions in bank feeds

An accepted community fix explains why QuickBooks Online bank feeds show duplicate transactions and how to match, exclude, or void the extras safely.

COMMUNITY ISSUESQUICKBOOKY

QuickBooks Online users keep reporting the same irritation: a charge that appears twice in the bank feed. A formally accepted community fix now covers the problem from diagnosis to prevention, and we have broken it down below. Its first rule is one many people skip.

Is it a duplicate or a real repeated charge?

Before touching the books, check the statement. A charge that appears twice on the statement happened twice, and the software is simply reporting reality. In that case the correction belongs with the bank or the payment processor, not in your records. A charge that appears once on the statement but twice in QuickBooks is a genuine duplicate. That is when the cleanup steps begin.

The bookkeeping patterns behind the doubles

Several ordinary habits create doubles that no feed caused. One is receiving an invoice payment and then adding the bank deposit as fresh income, which records the sale twice. The remedy is to undo the added deposit and match it to the payment instead. Another is creating an invoice and a sales receipt for the same sale. Keep whichever entry has the payment attached and delete the other.

A third pattern involves Undeposited Funds. A payment reaches the bank directly while also sitting in that holding account. Open the payment, set its deposit field back to Undeposited Funds, and save. Then open the bank deposit that matches the statement, select the payment inside it, and save. The deposit that no longer matches gets deleted.

Recurring templates and duplicate connections

Automation can double-record quietly. The fix directs users to a report that lists recurring templates. Look there for two templates carrying the same payee and the same amount. If a pair exists, open recurring transactions in settings and delete the extra template.

A duplicate bank connection produces the same symptom at scale. Review the connected accounts under banking and confirm the affected account appears only once. An account connected twice by mistake should be disconnected, and the spare entry made inactive in the chart of accounts. The original account, with its full history, stays.

A register check that lines the amounts up

The register gives you a fast visual audit. From the chart of accounts, open the register for the account, set a date range, and sort by the amount column so identical values sit together. One caution applies. If the register filter reads All plus deposits, switch it to All, because that combined view can show some transactions twice on its own.

The register also settles a common false alarm. A payment and the deposit it belongs to are one pair, not two records. Open either one; if it links to the other, you are seeing two halves of a single transaction, and nothing needs cleaning.

Cleaning up the review tabs

Duplicates still waiting in the queue are handled by exclusion. Open the For review tab, which some account views label Pending, select the checkbox on each extra copy, and keep one to match or add. Then choose Exclude.

When the duplicate has already been categorized, open the Categorized tab, sometimes labeled Posted, and select the link in the Added or Matched column. Undo sends the transaction back to the review queue. There you can match it to a record you already hold, or exclude it. If the software does not propose the right match, the Find match option lets you locate it yourself.

Should you delete or void the extra entry?

Entries already recorded in the register get a different treatment. Open the register, find the duplicate, and choose More. Delete removes it outright. Void is the conservative choice, because a voided transaction stays in the books at zero. Deleted transactions cannot be restored, although the audit log keeps their details for roughly two years.

Prevention beats cleanup

The accepted fix closes with the habit that avoids all of the above. Match downloaded transactions to records already in your books instead of adding them as new entries. Matching is what stops a bank line from becoming a second copy of a sale you already recorded. Turning off automatic addition on bank rules helps as well, since a rule that adds on its own can double a charge before you ever see it. A few minutes of matching discipline spares you the register work described above.

← Back to Community Issues