Claude to audit recurring receipts every Monday
Erich Archer set up a recurring Claude task to inspect subscription receipts each Monday morning. His Gmail Receipts label held invoices from services such as Stripe, the App Store and PayPal, giving the task a defined collection to search rather than the entire mailbox.
app.therundown.ai
Original prompt
Shared by the source author. See source notes for context.
Search label:Receipts newer_than:8d.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- Erich Archer
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A Monday task maintained a deduplicated receipt ledger and flagged new vendors, changed prices, duplicate services and paused project charges.
- Human involvement
- Archer reviewed the digest and handled any subscription cancellations himself.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Label relevant receipt and invoice emails in Gmail.
- Run the Monday search and append extracted billing details with message identifiers.
- Read the monthly spending digest and decide which flagged subscriptions to cancel.
Erich Archer set up a recurring Claude task to inspect subscription receipts each Monday morning. His Gmail Receipts label held invoices from services such as Stripe, the App Store and PayPal, giving the task a defined collection to search rather than the entire mailbox.
The agent extracted the vendor, receipt date, amount and billing cycle into a persistent ledger. It kept Gmail message identifiers with the rows so another weekly run would not count the same receipt twice. The workflow created the ledger initially and appended later records, making the results usable across repeated scheduled checks.
The digest calculated monthly spending and highlighted changes that needed attention. Those included newly appearing vendors, price changes, duplicate subscriptions and charges associated with projects that had been paused. The output was therefore a short set of decisions tied back to receipts, rather than an isolated summary of an email search.
Archer remained responsible for reading the digest and canceling services he no longer wanted. The task did not automatically cancel subscriptions, and the source does not report a recovered amount or a measured reduction in spending. Its concrete result is a recurring, deduplicated receipt ledger with exception flags that the author could use to decide which continuing charges deserved a closer look.
Prompt
Original prompt
Source: app.therundown.ai · Erich Archer
Frequently asked questions
How were repeated receipts avoided?
The ledger retained Gmail message identifiers so later runs could avoid adding the same email again.
What did the digest flag?
New vendors, price changes, duplicate subscriptions and charges for paused projects were highlighted.
Did Claude cancel subscriptions?
No. Archer read the digest and remained responsible for cancellation decisions.
More details
About this account
Claude searched labeled receipt emails, updated a persistent ledger and generated recurring subscription spending and change flags.
Firsthand source opened and read. Prompt is a verbatim excerpt of the published original instruction.
Credit: Erich Archer
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude scheduled tasks · Gmail
Receipt ledger · Gmail labels · Subscription flags · Weekly digest
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.