Use this guide when the app tells you something may be in twice: a receipt flagged Is this one we already have?, or a bank import that says payments look the same as ones from another file.
Prerequisites
- For receipts: both copies are in the app.
- For bank imports: the import opened the column editor, or the banner offered Import anyway. See Import a bank CSV.
Mark a receipt as a duplicate
The reader flags a receipt as a probable duplicate when another receipt has the same seller, receipt number, date, currency and total. You can also mark one yourself, for example after uploading a better copy of a scan.
Open the copy you want to drop
Open the receipt you do not want to keep, for example from Receipts To do. Keep the better copy (the clearer one, or the one already matched to a payment) as the original.
Pick the receipt it repeats
If it is flagged, the flag Is this one we already have? has the list beside it. Otherwise use Duplicate of under Other fields (Edit on a ready receipt). Choose the receipt it repeats. The list offers receipts with the same seller or the same total; if the one you want is missing, correct the seller first and save, then try again.
Save
Select Approve receipt, or Save on a ready receipt. Skip also keeps your changes.
A receipt cannot be a duplicate of itself, of a receipt that is itself a duplicate, or be marked as a duplicate while another receipt points at it. To undo, set Duplicate of back to Not a duplicate and save.
Check that it worked
The duplicate leaves Receipts To do and the month: it is no longer counted on Home, and it stays out of the CSV and the month package.
Uploading the exact same file twice never makes a duplicate: the app recognises the bytes and opens the receipt you already have.
Payments that look already imported
When you import a statement, payments are recognised in two ways:
- With a bank transaction ID column mapped: a payment with the same ID in the same account is skipped. If the ID matches but the date, amount or other facts differ, the import is blocked with “Stable bank ID has conflicting facts”. Check you picked the right account and file.
- Without a bank ID: the app cannot tell a repeated payment from a genuine second one, so it asks.
Open the mapping panel
In the column editor, open The columns look wrong? Adjust how we read the file if it is not open. A warning says how many payments without a bank ID look the same as ones from another file.
Choose what to do
Under If a payment was already imported, choose:
- Skip the ones already imported when the files overlap, for example two exports whose date ranges share a few days.
- Import them as extra payments when they really are separate payments with the same date, amount and payee.
Then select Check again and import.
Two identical rows inside one file are always kept as separate payments.
Payments in another account
If payments with the same date and amount already exist in a different account, the import asks you to confirm the account. Tick I checked the account. Similar payments in my other accounts are separate payments. if this is the right account. Nothing is merged between accounts. If those payments are money moved between your own accounts, pair them afterwards; see Pair an own-account transfer.
Check that it worked
The banner on Bank counts what was added and skipped. The To do count on Bank does not double.
Related
- The full dedupe rules: Bank CSV import.
- How a duplicate affects the flags on a receipt: Receipt fields and flags.