Duplicate DetectionBank exports overlap. You download January–March, then February–April; or you re-download a file you already imported. RockSolid Money is built for that: importing an overlapping statement does not create duplicates.
How it works
Instead of asking “does this row look like one already in the ledger?” one row at a time, the application counts. If the file contains two identical $4.50 coffee purchases on the same day and your ledger already holds one, exactly one is new — and that is what gets imported. Genuine same-day, same-amount repeats (two coffees) are preserved; re-imports of the same row are not doubled.
Where the file carries bank-assigned transaction IDs (OFX/QFX), those strengthen the matching further.
What you'll see
The import commit summary reports it plainly: how many transactions were created, how many were skipped as duplicates, and how many were linked to existing entries. The same numbers are visible later in Import History.
Ambiguity is surfaced, not resolved silently
When the arithmetic genuinely cannot decide — the file and ledger disagree in a way counting can't settle — the rows are shown for your review rather than quietly resolved either way.
Your edits are never collateral damage
Re-importing never overwrites what you've added to a transaction: categories, memos, tags, payee overrides, and reconciliation status are yours. If a bank restates a transaction, the change is shown as a proposed revision for approval.
Still need help?
If you're still stuck, contact us or email support@rockriverresearch.com — you will reach the people who build RockSolid Money.