The recovery bench

Every recovered dollar shows its math.

Recoup reads an itemized bill, finds the provable overcharges — each grounded in a specific line with the arithmetic shown — totals the recovery, and drafts the dispute letter. Suspected duplicates are flagged for confirmation, never asserted. And a clean bill recovers nothing: the engine never invents a finding to justify itself.

Request a live demo   The two non-negotiables
Itemized bill — sample dataSAMPLE
L1 · Lab panel, qty 2 × $75
Billed $250 — quantity × unit price is $150. Overcharge shown line-by-line.
+$100.00
L2 / L3 · Identical charge, same date
Flagged as a suspected duplicate — held for human confirmation, not asserted.
+$150.00
L4 · Office visit
Clean. Left alone.
$0.00
Recoverable (sample bill)$250.00
Grounded or it doesn't count. Every finding names a real bill line and carries integer-cents arithmetic computed from the bill — never invented.

Two non-negotiables, enforced in code

Money is integer cents

Intake fails closed on any amount that isn't exact integer cents — you cannot recover a dollar you cannot represent exactly. No floats, ever, on a money path.

Grounding, fail-closed

Every recovered dollar cites a specific bill line and shows the math. An ungrounded or non-integer finding is rejected by the guard, not rounded into existence.

Assert vs. confirm

An arithmetic overcharge is asserted. A suspected duplicate is a candidate for human confirmation — legitimate repeat services exist, and the engine knows it can't tell the difference from the bill alone.

Honest coverage

Checks that didn't run are listed in the report. The absence of a finding is never presented as a clean bill.

What it checks today — and what it honestly doesn't

Four detectors ship and are tested. The rest are declared as gaps in every report, so recovery is never overstated.

DetectorState
Quantity mismatch — billed above quantity × unit priceShipped + tested
Duplicate charge — identical line billed more than onceShipped (flagged for confirmation, not asserted)
Unbundling — panel and component billed togetherShipped (candidate vs a SAMPLE pair table; real quarterly ingestion is launch-gated)
Out-of-network balance bill (No Surprises Act, emergency)Shipped (context-gated candidate; plan-type confirmation required)
UpcodingDeclared gap — not deterministically detectable without clinical records
Expired contract rateDeclared gap — waits on contract ingestion

The rights annex: the door, not the key

Alongside the findings, Recoup surfaces cited patient rights the bill's context makes worth raising — No Surprises Act balance-billing protections, the good-faith-estimate dispute channel, hospital financial-assistance obligations, FDCPA validation, medical-debt credit-reporting policy. Each entry is cited and dated. None is a verdict: Recoup names the right and the channel; the decision stays with the payer, provider, or agency.

For billing-recovery operators

A deterministic audit bench under your service: grounded findings, drafted dispute letters, and a report that discloses exactly what was and wasn't checked.

For businesses auditing their own bills

Medical, vendor, and SaaS invoices run through the same discipline — recovery totaled only from provable, line-grounded arithmetic. Priced on recovery, not a subscription.

Honest status, in writing

Where this stands

  • The engine is deterministic and runs with no network and no secrets; the figures above come from the repo's sample bill, not a customer.
  • The unbundling pair table is SAMPLE until real quarterly source ingestion lands — a named launch gate, not a footnote.
  • Rights-annex entries carry citations and re-verify stamps; they surface context, never conclusions.

Watch a bill give up $250 it can prove — and nothing it can't.

The live demo runs the real detectors and the real grounding guard on sample data. Fifteen minutes, no slides.

Request a demo