A duplicate is the same real-world payment appearing twice in Finthy. Marking one as a duplicate keeps it in your history but takes it out of every total.
How duplicates happen
- Importing a statement that overlaps data you already have. The common case: a statement covering a period your bank already synced, or two statements whose date ranges overlap.
- Two connections to the same bank. Finthy warns you before you create a second one, because both will report the same payments.
- The bank reporting the same payment twice, which does happen, often around a pending payment that later settles.
Finthy already filters duplicates on import
You do not have to catch import duplicates by hand. When a statement is read, Finthy compares each row against what the account already holds on four things: the date, the amount, the description and the running balance.
The running balance is what makes this safe. Two genuine payments on the same day, for the same amount, with the same description, are a real pattern (two identical coffees, two transfers of the same round number). Their running balances differ, so Finthy keeps both rather than silently dropping one.
In the review screen before you import, a row Finthy considers a repeat is labelled Duplicate, with the note “Already in the suggested account, so it is left out. Select it to import it anyway.” So the decision stays yours: select it to import it anyway. After the import, the history line tells you how many duplicates were skipped.
Marking a duplicate yourself
- On the Transactions page, open the transaction’s actions menu and choose Mark as Duplicate. To do several at once, select them and choose Mark Multiple as Duplicates, or Mark All as Duplicates for everything matching your current view.
- Finthy suggests the transactions it looks most like, each with a match score shown as “{score} match”. Pick the one it duplicates, or search for it yourself.
- Confirm. For one transaction Finthy asks “Are you sure you want to mark this transaction as a duplicate?”; for several it tells you how many you are about to mark and reports the outcome per transaction afterwards.
What marking one changes
- The transaction gets a Duplicate badge.
- It is left out of your totals, budgets and reports. Nothing is deleted.
- It disappears from the default Transactions list. To see duplicates again, turn on the Show Duplicates filter.
- It is left out of a transaction export too, unless Show Duplicates is on when you export. With that filter on it is included, and the Is Duplicate column tells you which rows they are, so a reconciliation can account for them.
Undoing it
Click the Duplicate badge to open Duplicate Transaction. It shows the Original Transaction beside it, with View Original to jump to it, and Unmark as Duplicate to reverse the marking. Finthy confirms first, because unmarking puts the transaction back into your totals.
If the original was deleted in the meantime, the panel says so: “The original transaction was deleted. It is no longer here to compare against. Unmark this one as a duplicate to bring it back.” The duplicate is not stranded, you can always recover it.
Edge cases
- A duplicate cannot be split. Unmark it first, split it, then mark whichever part is the duplicate.
- Marking is per transaction, not per rule. Finthy does not learn a pattern from it, so a bank that repeats a payment every month needs each one marked.
- Prevention beats cleanup. Keep one connection per account. If you are reconnecting a bank you already have, use the existing connection rather than adding a second.