Describe the correction before editing
A duplicate-import correction should explain which representation was wrong and which underlying payments remain unchanged. Write a concise problem statement before removing rows: for example, two overlapping downloads added the same completed debit twice to the spending list. This distinguishes an import problem from an incorrect merchant charge, a refund or a change to a purchase category.
Record the affected account and file intervals. Avoid a broad instruction to delete all repeated values. A precise scope protects unrelated accounts and legitimate purchases that happen to share an amount. If the review later reveals more overlap, expand the scope explicitly rather than allowing a local repair to become an unexplained rewrite of the whole account history.
Keep a stable before-and-after reference
Save a copy of the working record before correction, alongside the original downloads. Identify the version used for the earlier report and the version containing the resolved matches. Preserve any category decisions, receipt links or comments that would otherwise disappear with an excluded row.
A useful correction log connects each removed representation to the event retained. It can contain a source filename, source row identifier, transaction reference and reason. Do not rely exclusively on a spreadsheet row number, since sorting changes row positions. The log should still make sense after the corrected record has been rearranged for reporting.
Build an illustrative correction bridge
Suppose the original spending report totals 2,430 units. Review confirms that a 320 grocery payment and a 210 household payment each appeared twice. Removing those two duplicate representations reduces the total by 530, producing 1,900. The bridge is 2,430 minus 320 minus 210 equals 1,900.
No credit of 530 has arrived in the account. The correction changes the report, while the real payments remain 320 and 210 once each. If the corrected account balance also increases by 530, inspect the calculation: historical debits may have been deducted again from an opening balance that already included them. Keep report reconciliation separate from the observed account balance.
Distinguish separate kinds of changes
A category correction moves an event between categories without changing total spending. Removing a confirmed duplicate changes the total represented in the working list. Adding a previously omitted genuine debit increases that total. Record these changes separately so their effects can be checked rather than combining everything into one unexplained adjustment.
If a duplicate row contains a better description than the retained row, transfer the supported descriptive information without transferring another amount. A working label may change while the event identity remains stable. Note material allocation changes when they affect earlier comparisons, particularly if a report has already been shared with another person.
Preserve unresolved pairs
Some suspected duplicates will remain ambiguous. Put them in a review list with the evidence needed to decide, instead of removing them under a general cleanup label. Show how including or excluding the disputed amount affects the total when that distinction matters to the report being used.
Do not mark unresolved records as refunds or reversals merely to neutralise their financial effect. Those labels describe real events and require supporting evidence. A correction trail is more useful when it acknowledges a limited unresolved amount than when it presents an exact total built from unsupported assumptions about what happened to the money.
Verify the repair survives another import
After correction, repeat the relevant comparison against the source files and confirm that the retained events still match their evidence. Check both the changed subtotal and any reports that depend on it. A repair to one category can alter a household overview, a period comparison or a shared balance even when those screens were not where the duplicate was first noticed.
Before processing another overlapping download, retain the match decisions or define how they will be reapplied. A new import should not silently resurrect the rows that were just excluded. Close the correction with a dated summary of the total change, the events affected and the remaining uncertainties. The aim is a record that remains understandable after the immediate cleanup has been forgotten.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


