Re-import the Same Bank File Without Creating Duplicates
Import a file PennyBolt has seen before and it skips what it recognizes — matching on date, amount and payee, and showing you every match in the preview before anything is written.
Switching to PennyBolt › Importing › Re-importing safely
Yes — you can import the same file twice. PennyBolt checks every incoming transaction against what’s already in your file and skips anything it has seen before, so overlapping bank downloads don’t double your history. This matters most when you’re catching up: download January to June, then March to August, and the overlap takes care of itself. Re-importing is safe by default.
What duplicate detection catches and what it does not
| Situation | Caught? | Notes |
|---|---|---|
| The same transaction in two overlapping downloads | Yes | Matched on date, amount and payee together. |
| A genuine second charge that looks identical | Flagged — sometimes wrongly | Rare, and you can override it in the preview. See below. |
| A transaction whose payee you renamed after importing | No | The payee names no longer match, so a re-import may not recognize it. |
| Anything written without your seeing it | Never happens | Every match appears in the preview labeled Duplicate before you commit. |
How duplicate detection works
When you import a file, PennyBolt compares each incoming transaction against existing transactions in the destination account. A transaction is considered a duplicate if it matches on all of: date, amount, and payee.
Duplicates appear in the import preview with a Duplicate label. They’re shown so you can see what was detected, but they won’t be imported unless you explicitly override the detection (see below).
When detection can be wrong
Duplicate detection errs on the side of caution. Two cases where it can give a false positive:
- Recurring identical charges. If you pay the same amount to the same payee on the same day of two different months, and the earlier one is already imported, PennyBolt may flag the new one as a duplicate. This is rare, but it happens with charges like subscription renewals that fall on predictable dates.
- Edited payees. If you imported a transaction and later renamed the payee manually, a re-import of the same file may not detect the duplicate because the payee names no longer match.
In both cases, review the flagged transactions in the preview before deciding to override.
Force an import when you know better
If PennyBolt marks a transaction as a duplicate but you know it’s genuinely new, uncheck the Skip checkbox next to it in the import preview. That transaction will be imported even though it matched an existing one.
Use this when you’ve confirmed — by checking your bank’s website — that the transaction really did happen twice.
Don’t have PennyBolt yet?
Duplicate detection is what makes switching survivable: you don’t have to plan your downloads perfectly, because overlapping files are cheap. PennyBolt isn’t available to download yet — see what it costs and get the download link on day one . It’s $79 once, with a 60-day trial.
See also
- Bank downloads (OFX / QFX) — the most common source of re-imported files.
- Import your Quicken history (QIF) — QIF imports also support safe re-importing.
- Reconciling with your bank — the right way to confirm your file matches your bank after any import.