Audit recurring charges from exported bank transactions
At a glance
AI for Mortals tests a Claude workflow that turns account CSVs into a checked spending summary and cancellation drafts. This workflow is listed under Money & Bills, Subscriptions, Spending Review.
- Agents / tools
- Claude, Claude Code, Bank CSV exports
SourceBuilding a tool for these workflows? See weekly rates.
What they did
1) Export a year of transactions from every spending account as CSVs, name files by account, and remove identifiers you do not want to share. Use Claude with code execution, or Claude Code with folder access. 2) Require code-based totals, coverage checks, transfer removal, and separate recurring charges by amount and billing day. 3) Ask for monthly totals and recurring charges, then have Claude pause for your answers about usage, unknown merchants, and prior cancellations. 4) Use those answers to classify charges and draft cancellation or refund messages. Check suspected duplicates against the original rows. 5) Keep the resulting action page; add next month's exports, deduplicate transactions, and check whether cancelled charges stop.
How it went
On synthetic household data, the test recovered the exact $47,617.61 spending total and found all 15 planted problems.
Worth knowing
This was a simulated audit. The test also produced a false duplicate suspicion and an unsupported future-charge claim; projected savings were not money recovered.