Claude to reconcile medical reimbursement claims
An author who submitted out-of-network medical bills for themselves and their wife had lost track of what Aetna had received, allowed and paid. They gave Claude Cowork invoices, explanation-of-benefits documents and the plan's schedule of benefits, then developed a reimbursement workbook.
Original prompt
Shared by the source author. See source notes for context.
Read every invoice and EOB in this folder. Build a medical reimbursement tracker as an Excel workbook.
Reach people exploring AI agents
See placements →What happened
The author reports over $8,000 of possible claim errors flagged in a day, with recovery still pending rather than confirmed.
Reported by u/No_Zookeepergame8576How the agent did it
- Collect invoices, EOBs and plan benefits in the working folders.
- Build three-way matches and a formula-based reimbursement workbook.
- Review the weekly read-only action report and manually submit corrections or appeals.
Where a person stepped in
The author manually applied recommended changes and submitted documents through the insurer portal; ambiguous matches stayed pending.
An author who submitted out-of-network medical bills for themselves and their wife had lost track of what Aetna had received, allowed and paid. They gave Claude Cowork invoices, explanation-of-benefits documents and the plan's schedule of benefits, then developed a reimbursement workbook.
The workbook matched three sides of each claim: the provider invoice, the submitted claim and the insurer's response. Service dates and procedure codes helped connect records. Separate sheets held claims, invoices and an action dashboard, with live formulas rather than only a written summary. In-network records were separated, ambiguous matches remained in an inbox and duplicate records were excluded.
The author reports more than $8,000 in flagged errors within twenty-four hours. That is money questioned, not money recovered. Examples included a denial citing a daily visit limit for sessions a month apart, documentation already supplied, and conflicting statements about whether payment had gone to the provider.
The follow-up explains the operating boundary. A Friday report is read-only and distinguishes items waiting on the patient, insurer or provider. Changes require manual application, and the author submits material through the insurer portal. A claim marked acceptable can still have no reimbursement because of the deductible; the system therefore does not treat an apparently valid claim as proof of payment.
Prompt
Original prompt
Source: www.reddit.com · u/No_Zookeepergame8576
Frequently asked questions
Was the $8,000 recovered?
No. The author described errors to pursue, not a completed reimbursement.
Why can an acceptable claim still show no payment?
The author's tracker separated claim validity from payment, including valid claims absorbed by the deductible.
What happened to uncertain matches?
They remained in the inbox for review; the weekly report did not overwrite records automatically.
More details
About this account
Cowork read claim documents and built a matched Excel tracker and read-only action reports.
Firsthand post and same-author June 16 follow-up opened and read. Prompt is an excerpt of the author's published setup example.
Credit: u/No_Zookeepergame8576
Source published 13 Jun 2026
Source checked 14 Oct 2026
Tools and topics
Claude Cowork · Excel · Invoices · Explanation of benefits
Medical claims · EOB reconciliation · Appeal queue
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.