Canonical page: https://bokeping.com/help/banking/duplicate-transactions/

Markdown page: https://bokeping.com/help/banking/duplicate-transactions.md

Source updated: 2026-09-28

Text version of the public page. Check the canonical page for current terms and interactive features.

# What to do when a bank transaction appears twice

Separate duplicate feed rows from an existing accounting record before excluding or correcting anything.

**In Bokeping** Banking → Bank transactions

Two rows with the same amount are not automatically duplicates. A bank-feed row and the payment already recorded in your books may be two views of one real event.

## Identify which kind of duplicate you have

| What you see | Next step |
| --- | --- |
| One bank row and one existing payment or expense. | Match the bank row to the record. |
| The same statement transaction imported twice. | Identify the extra feed row before excluding it. |
| Two posted expenses for one purchase. | Review the source records; excluding a feed row alone is not a complete correction. |
| A pending authorization and a settled card charge. | Compare their status with the bank before deciding either is extra. |

## Compare the evidence

1.  Open **Banking → Bank transactions** and select the affected account.
2.  Compare amount, direction, date, reference, and bank description against the statement. Check **Pending**, **Posted**, and **Excluded**.
3.  Look for an existing invoice payment, bill payment, expense, or transfer representing the same event.
4.  If that record exists, use **Match** instead of categorizing new income or expense.
5.  If two imported rows represent one statement transaction, keep the correct row and use **Exclude** for the confirmed extra row that does not belong in the books.

For example, a $75 expense you entered manually and a $75 imported card row usually need matching. Two separate $75 purchases at the same store need two records.

## If both copies have already been posted

Trace each row to its accounting record and check payment links, bank matches, and reconciliation status. Review the permitted correction action on the duplicate record; do not delete both records or change a completed reconciliation to hide the difference.

If the correct reversal is unclear, [contact support](<https://bokeping.com/resources/contact/>) with the record references and your accountant with the proposed accounting correction.

## Prevent a repeat

When using a file to fill a gap in a connected feed, import only the missing dates and review overlaps. Keep the import results and statement range. See [import bank transactions](<https://bokeping.com/help/banking/import-bank-transactions/>).

## Related walkthrough

The [illustrated matching walkthrough](<https://bokeping.com/help/banking/review-transactions/#example-match-an-existing-350-receipt>) shows a bank row being linked to its existing receipt, with no second receipt added.

## Frequently asked questions

### Why does the same bank transaction show up twice in Bokeping?

Two rows with the same amount are not automatically duplicates. Often one is the bank-feed row and the other is the payment or expense already recorded in your books, two views of one real event, and the fix is to match the bank row to that record. A pending authorization and a settled card charge also need checking against the bank before you treat either as extra.

### How do I get rid of a bank transaction that was imported twice?

Identify the extra feed row first. In Banking > Bank transactions, compare amount, direction, date, reference, and bank description against the statement, and check the Pending, Posted, and Excluded tabs. Keep the correct row and use Exclude only for the confirmed extra row that does not belong in the books.

### I have two charges for the same amount at the same store. Are they duplicates?

Not necessarily. Two separate $75 purchases at the same store need two records. By contrast, a $75 expense you entered manually and a $75 imported card row usually need matching rather than a second expense. Compare each row with the statement before excluding or correcting anything.

### What if both copies of a duplicate have already been posted?

Trace each row to its accounting record and check payment links, bank matches, and reconciliation status, because excluding a feed row alone is not a complete correction. Review the permitted correction action on the duplicate record. Don’t delete both records or change a completed reconciliation to hide the difference. If the correct reversal is unclear, contact support and your accountant.

### How do I avoid duplicates when I import a file into a connected bank account?

Import only the missing dates. When using a file to fill a gap in a connected feed, identify the missing range and review overlaps before posting anything. Keep the import results and the statement range so you can later check which activity has already been brought in.
