Topic 11 of 17 · Tables

Duplicates

Tables can scan for duplicates. Duplicate entries appear in a separate duplicate section and are excluded from normal summaries and exports. Scans compare the calendar day, so an entry imported from a bank statement and the same purchase added by hand on that day are grouped.

Review tools also lists Possible duplicates to review: one purchase recorded twice, once from its invoice or receipt and once from the bank statement — often on different dates, because the invoice was paid later. Choose Same purchase to move one entry to the duplicates section, or Not the same so the pair is not suggested again. The entry you keep gets a copy of the other's receipt and bank reference if it has none, and a refund recorded on the other moves to it; the entry set aside keeps everything it had. Nothing is deleted. Two entries from different bank transactions, or with a refund on each, cannot be confirmed as one purchase, and an entry that another copy was already set aside for cannot itself be set aside (keep it instead). The Master Table has the same review across every Table.

If an entry was incorrectly marked duplicate, move it back to the main table. For a confirmed pair the duplicates section shows the Kept Entry (naming its Table if it is in another) next to the one Set Aside; choose Keep (Not Duplicate) on the one set aside and whatever was copied or moved to the kept entry goes back. The kept entry cannot be deleted or set aside from there. If you delete a kept entry anywhere else, the entry set aside for it returns to its Table, so the purchase still counts once, and takes over the kept entry's refund (and its receipts, if it has none of its own). Entries you marked or confirmed by hand are left alone by later scans, and a scan never sets aside a kept entry. In other duplicate groups the original is the entry that stands for the group, wherever it is; when that is in another Table, the card names it.