A transaction appeared twice after import

A transaction appeared twice after import

Satsuma uses a deduplication fingerprint (account + date + amount + description + type) to skip rows it's already seen. Under normal conditions, re-importing the same CSV or re-receiving the same bank alert will not create a duplicate.

If you see a true duplicate, the most likely causes are:

• The description or amount was slightly different between two imports (e.g. one file had a trailing space, or a rounding difference)
• The transaction came from two different sources (a CSV import and a bank-alert email on the same day for the same amount)

If the duplicate is genuine, delete one of the transactions from the transaction detail page. If you believe there's a bug, contact support with both transaction IDs.