The most frequent cause is reconnecting a card (especially Amex). When you reconnect, the bank connection (Plaid) backfills from the last successful sync, so recent charges already in Vergo can come in again as second copies.

If a charge was entered manually in Vergo or your ERP and also came in through the automated import, you can end up with two records.

A split transaction shows its split portions, which can look like duplicates but aren't — see Split transactions.

A Pending charge that posts with a slightly different amount or date can create a second record instead of updating the original.

Vergo automatically detects likely duplicates — matching on the card, amount, merchant, and date — and flags them in your transaction list, so you don't have to hunt for them.

Once you've confirmed it's a true duplicate, remove the extra copy from the flagged duplicate in your transaction list. (Note: the general Actions → Delete option applies to saved views/filters, not to transactions — use the duplicate flag to clear the extra rather than a bulk delete.)

⚠️ Be careful: only remove after confirming it's a true duplicate — deleting a legitimate posted charge creates a discrepancy. When in doubt, contact support.

If a duplicate has already been Approved and you don't want it to export to your ERP, an Admin can Mark it as Reported (Approved tab → Actions → Mark as Reported). It moves to the Reported tab without syncing to the ERP. This option is enabled per account by support, so contact support if you don't see it.