Updated: July 2026
Why one field is not enough
Two legitimate transactions can share the same date or amount. Treating one matching field as proof of duplication can delete real activity. A stronger key combines date, amount, description and a bank reference when available.
Normalize before comparing
Trim spaces, use consistent capitalization and standardize dates and amount formats. Without normalization, visually identical records may be treated as different because one contains extra spaces or a currency symbol.
Use references carefully
A unique transaction reference is extremely useful, but some banks leave it blank or reuse generic values. Combine it with other fields rather than relying on it blindly.
Review repeated subscriptions
Recurring subscriptions can look nearly identical each month. The date should normally distinguish them. Same-day repeated charges may be genuine, so compare the source statement before removing them.
Keep an audit copy
Preserve the original export and save a separate deduplicated file. Record how many rows were removed and which fields were used for matching so the process can be repeated consistently.
Useful tools
Bank Statement Converter · QuickBooks CSV Formatter · Xero CSV Formatter