Quickbooky

Accounting News

QuickBooks

Duplicate Transactions in QuickBooks Online After an Issuer Switch

A card issuer switch can download the same charge twice in QuickBooks Online. Here is why it happens and how to sort the copies safely.

Duplicate Transactions in QuickBooks Online After an Issuer Switch

We see the same pattern each time a business card changes the bank behind it. One example from the community: holders of an Amazon business card reported duplicates after the program moved from American Express to US Bank. Charges and refunds began arriving in QuickBooks Online twice, once through each bank connection. Copies left sitting in review are harmless. Copies posted will double your expenses or your credits. Here is a calm way through it.

Why does one card turn into two feeds?

QuickBooks Online connects to the issuing bank, not to the card program. A new issuer means a new connection, a new account to map, and often a new card number as well. The old connection usually stays live until its final statement closes. During that overlap, the same purchase can download through both feeds. Refunds come through twice just as easily, and a doubled refund is as wrong as a doubled expense.

Should the duplicates sit in review while you decide?

Yes, and that instinct is correct. Nothing in the For review list touches your books until you add it or accept a match. A duplicate left in review costs you attention and nothing else. The one rule: never bulk-add the whole list just to clear it. Work the overlap dates by hand.

Which copy should you keep?

The charge cleared once, at the bank that held the card that day. Keep the copy that appears on that bank’s statement and exclude the other. Pull the final statement from the old issuer and the first statement from the new one. Together they should cover every transaction exactly once. If a charge appears on neither statement, pause and investigate before touching either copy.

Is excluding the same as deleting?

Prefer exclude. In the For review list, tick the row and choose Exclude from the action menu. The copy leaves the queue without ever reaching your books, and it moves to the Excluded tab rather than vanishing. That tab is your audit trail if anyone asks questions later. Excluded items are not pulled back in on the next sync, so the fix holds.

What if copies were already posted?

Search both card accounts for entries that share an amount and date near the switch. A register search or the Transaction List by Date report both work. Remove one copy of each pair, and keep the side whose statement shows the charge. Check refunds the same way, since a doubled refund quietly inflates money due back to you. If you reconcile, an account holding posted duplicates will not tie out, which is often how the problem first surfaces.

Can you prevent this at the next cutover?

When a card program announces a new issuer, note the switch date. Connect the new bank only once its first charges post, and map it to the existing card account or a new one as your books require. Check the old feed’s most recent transaction date. Reconcile the old account to its final statement, then disconnect that feed. An overlap of a few days is normal; silent double-posting is not.

Reconciliation is the safety net throughout. Reconcile the old account to its final statement and the new account to its first one. Every charge should land on exactly one side. Your next step today: pull both statements, mark every charge that appears in both review lists, and exclude one copy in the account whose statement does not show it.

← Back to News