Begin with the account, not the total
An account imported twice can make a spending report look convincing while overstating the underlying payments. Start by identifying the account represented in each file, the covered dates and the source of the closing balance. Two downloads from the same account may overlap for several weeks without being identical files. Conversely, files covering the same dates may belong to different accounts and contain entirely legitimate separate purchases.
Preserve both original downloads before changing the working list. Name them so the account and reporting interval remain visible without exposing a complete account number. Keep the imported rows connected to their source file. A later reviewer should be able to establish which download supplied an entry even after the duplicate has been removed from the spending view.
Define one payment event carefully
A payment event needs more identifying information than its amount. Compare the account, debit or credit direction, transaction reference and dates provided by the source. Retain the merchant description as supporting context. Where one file shows a posting date and another shows a purchase date, record the distinction rather than changing both dates until they happen to match.
Do not assume a reference is universally unique across unrelated accounts or export formats. Establish how it is represented in these particular files. A missing reference leaves more uncertainty than a matching reference supported by the same account and debit direction. A sound match records the evidence used instead of declaring that every pair of identical amounts is redundant.
Reconstruct a small overlap
Consider an illustrative account with three actual purchases: 260 units for groceries, 90 for transport and 150 for a household item. The total is 500. The first download includes all three; the second includes the transport and household purchases again. Combining every row produces 740, because the 90 and 150 have each been included twice.
After the two matches are verified, retain one spending event for each actual purchase. The reconciled total becomes 500, and the removed duplicate contribution is 240. Preserve links from the retained events to both source rows. The second file is still useful evidence, even though its overlapping rows should not add another 240 to spending.
| Actual payment | Amount counted once |
|---|---|
| Groceries | 260 |
| Transport | 90 |
| Household item | 150 |
| Reconciled purchases | 500 |
| Duplicate contribution excluded | 240 |
Protect genuine repeated purchases
Suppose the account also contains a separate 90-unit transport purchase on another day. That event belongs in the record. Removing every row with an amount of 90 would erase real spending. Even purchases on the same day can be separate events, particularly where a household makes several small payments to the same merchant.
Mark uncertain pairs for review rather than forcing a match to obtain a desired total. A reference, receipt, transaction sequence or explicit source explanation may resolve the ambiguity. If no adequate evidence exists, leave the provisional decision visible and explain its effect on the report. Uncertainty should have a location and an amount, not disappear inside a balancing correction.
Reconcile the retained events
Compare the corrected list with the statement interval using the statement's actual opening and closing balances where available. Include credits, transfers and charges according to the question being checked. A spending subtotal does not necessarily equal the change in an account balance, because income and internal transfers also move money.
Use the balance comparison to discover unexplained gaps, rather than treating it as permission to remove whichever entries make the arithmetic fit. A duplicated credit can offset a duplicated debit and leave a misleadingly plausible net change. Check event identity independently even when the beginning and ending balances appear to reconcile.
Finish with a stable payment record
Record which source rows were matched, which event was retained and why. Keep a separate unresolved list for pairs requiring more evidence. If a manual category or receipt note existed on the removed row, preserve that useful information on the retained event without creating another cash movement.
Before the next import, note the latest covered date and how overlap will be reviewed. A repeated download should not silently recreate entries already resolved. The finished record should explain each genuine payment once, retain the source trail and distinguish a bookkeeping repair from a refund or other real change to cash.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


