Product guides

The duplicates screen: judging a pair

Spendix pairs up transactions that look like copies and asks you to decide. Learn what the cards show and how to choose between keeping both, merging or deleting.

Editorial illustration for The duplicates screen: judging a pair

Duplicates sneak in from overlapping imports, double manual entries and the same payment appearing in two sources. Left alone, they inflate spending and break reconciliation. The duplicates screen collects likely pairs and lets you resolve them one at a time, in a swipe-through style that is quick when you know what to look for.

What a pair card shows

Each card shows two transactions: the one that was added earlier, labelled as the kept one, and the newer one, labelled as the flagged copy. The card states why they were paired, for example that amount, date and account all match. That statement is the reason for suspicion, not proof of guilt.

The screen is headed possible duplicates, and when there are none it says nothing looks duplicated right now. Only owners, admins and accountants may review duplicates, so the screen may show no access for other roles.

Three choices

For each pair you have three options.

  • **Merge.** Keeps the earlier transaction and moves the newer one's useful information into it, then removes the extra. Use this when both are the same real payment.
  • **Delete newer.** Removes the flagged copy. Use it when the newer one adds nothing.
  • **Keep both.** Records that the two are genuinely separate, so they will not be flagged again.

The deleted copy is not gone at once. The screen notes that deleted copies stay in the recycle bin for 30 days, which allows a second thought.

How to judge

The matching fields prove similarity but not duplication. Ask what else you know. Two identical fares on the same morning may be an outbound and a return trip. Two payments of the same amount to a landlord in one day probably are not both rent. Consider whether the merchant naturally produces repeats.

Look at supporting details: notes, receipts, tags and the source of each entry. If one came from an import and the other was typed by hand, a duplicate is likely. If both came from the same import and the statement lists two lines, keep both.

Decide faster with a habit

When unsure, check the statement. It is the authority on whether two lines exist. If the statement shows only one payment, one of your entries is extra. If it shows two, keep both.

Prevention

Most duplicates come from overlapping statement periods. Check the dates of each file before importing, and review flagged rows before committing. Preventing duplicates at the staging step is far easier than resolving them afterwards.

SituationAction
Same amount, date, account; one typed by hand, one importedMerge
Statement shows only one paymentMerge or delete newer
Statement shows two paymentsKeep both
Cannot tellCheck the statement before deciding

Notes and receipts help judgement

Cards that carry receipts or notes make decisions easier. If one entry has a receipt and the other does not, the one with the receipt is probably the genuine record, and the other the copy. Adding notes as you enter transactions pays off here, because the evidence you need to judge a pair is already in place.

Do it regularly

Open the screen after every import and once a month otherwise. A short queue clears in a minute, whereas a long one invites guesswork. Regular passes also keep reports and balances accurate between reconciliations.

Wrapping up

Clearing the duplicates screen takes a few minutes and has an immediate effect on your totals. When it shows all cleared, you can trust that spending is not being counted twice.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports