When should you use it?
- You are dealing with an estate, a divorce, a renovation or a long legal or accounting matter billed over many months
- Invoices arrive by email and earlier ones are buried in long threads
- A large bill arrives and you cannot remember which items were already settled
Not for: One-off purchases with a single receipt; Disputes that already involve lawyers, where you should follow their advice on what to raise; Documents you are not allowed to upload to an AI service under your firm's or family's agreements
What do you need, and what do you get?
You need
- All invoices, statements, engagement letters and payment confirmations in one folder
- A list of payments you made, with dates and amounts
- The new invoice you want checked
You get
- A running ledger of agreed work, billed items and payments
- A line-by-line comparison of the new invoice against that ledger
- A short list of possible repeats or mismatches, each with the earlier document cited
- A polite question you can send the firm
How does it work, step by step?
- Gather everythingSave all correspondence, statements and bills to a single project folder, named with the date, and add your own payment confirmations.
- Build the ledger onceHave the assistant read the folder and produce a table of agreed fees, billed items and payments, citing the file for each row.
- Check each new invoiceWhen a bill arrives, add it and run our prompt, which compares every line with the ledger.
- Verify before you writeOpen the cited earlier documents yourself and confirm the match before contacting anyone.
- Ask, do not accuseSend the firm a short question listing the items and dates, and update the ledger with their answer.
The prompt
Our own prompt, inspired by u/m_x_a on r/claude and written to work in Claude, ChatGPT, Claude Cowork and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are helping me track billing from {firm_type} on {matter}. First, from the documents in this folder, build a ledger table: date, document, item description, period covered, amount, and whether I have paid it (cite the payment record). Then compare the new invoice {new_invoice} line by line against the ledger. For each line, say: new, possible repeat (cite the earlier document and payment), or unclear. Treat items as repeats only when description, period and amount line up; explain any partial match. Finish with a short, polite question I could send the firm about the possible repeats. Do not suggest withholding payment.
Inspired by u/m_x_a on r/claude: Reddit post: Claude spotted a duplicate charge on my family's estate. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Similar descriptions are not always the same work. Periods, quantities and dates decide whether an item is a true repeat.
- Assistants can misread scanned PDFs. Check every flagged amount against the original document.
- Estate and tax papers contain sensitive personal data. Use an account and settings you trust, and remove what the check does not need.
- Do not withhold a payment on the assistant's word alone. Raise the question first.
Our take
This is a modest use of an assistant with an outsized payoff. Long engagements with professional firms generate dozens of documents, and the person paying is usually the one least able to keep track, especially during something as draining as settling a parent's estate. The poster's approach works because the assistant is not asked to judge the firm; it is asked to keep a record and compare against it. That framing produces specific, checkable findings (this item, billed on this date, paid on that date) rather than vague suspicion. We like that the follow-up was a polite question and the firm fixed it within hours, which is how most billing errors end. Our main caution is reading quality: scanned statements trip up every model, so every flagged amount needs a human look at the source document before anything is sent. In our dry run with a fictional estate file of nine invoices, the prompt flagged one repeated tax-preparation line and correctly ignored a similarly named item from a different period.
Where the time goes back: Instead of rereading months of email whenever a bill arrives, you check it against one ledger in minutes, and a single caught repeat can be worth far more than the setup time.
FAQ
How much did this save the poster?
Which assistant works best?
Is this only for estates?
Source and credit
Inspired by u/m_x_a on r/claude. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Reddit post: Claude spotted a duplicate charge on my family's estate
- Creator
- u/m_x_a on r/claude
- Published on
- Original date
- Nov 6, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- AI dry run
- Nov 7, 2026: passed. Dry-run tested by our AI test agent on sample input. One true repeat flagged with citations, similar item from another period not flagged, polite question drafted, no advice to withhold payment.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 8, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.