Find duplicate charges on your statement
Paying twice for one thing happens more than people think: a retried checkout, two family plans, an old card still on file. Laying repeated payees side by side makes overlaps obvious.
Your file is never uploaded. The subscription finder runs in your browser and uploads nothing. Its results are estimates to check against your statement.
Steps
- Pull activity for every card and checking account you use for services.
- Load all of them into the tool together so overlapping payees meet in one list. Where exports cover the same dates, a charge found in two files on the same date for the same amount is counted once.
- Hunt for one payee appearing twice, or a cadence that feels wrong, like weekly where you expected monthly.
- Match each suspect against the original lines and dates before you raise it with anyone.
Good to know
Household overlap
Partners or flatmates sometimes each pay for an identical service. Combining everyone's files reveals that.
Identical lines on one date
That might be a real double bill, or a pending hold that later posted. Confirm with the merchant's receipt.
Who to contact
This page never reaches out on your behalf. Ask the seller for a refund first; your card issuer is the fallback.
Keep evidence handy
Before calling, note both posting dates, the exact amounts and any order reference printed beside them. Having that ready usually makes a refund conversation shorter and calmer.
Retried checkouts
A payment page that froze and was clicked again can leave two authorisations. One often drops off within days; if both settle, that is worth querying.
Questions
Can it combine several accounts?
Yes, several files load at once.
Is a flagged pair definitely a duplicate?
Not necessarily. Treat findings as estimates and confirm them.
The finder reads PDF, CSV, OFX, QFX, QBO and XLSX files. Drop in a text-based PDF statement or an export file. Scanned (image-only) PDFs can't be read; the tool will tell you if yours is one.
This guide was written with AI assistance and reviewed against the tool's behaviour. Always review your output before using it.