Countercharge

Countercharge reads each claim against Medicare's own rulebook, marks what it can prove, and drafts the dispute in triplicate — nothing ships without an advocate's signature.

Audit a sample bill no login required · runs on real audit data

How the three gates work

GATE 1 — ENGINE

Every line, checked against a citation

A deterministic rules engine (duplicates, NCCI bundling, Medicare unit limits, arithmetic, balance billing, No Surprises Act, cash-price, charity care) reads the bill against CMS/HHS reference data. Every finding carries a dataset, version and record — nothing is asserted without a source.

GATE 2 — POLICY

Cedar decides what's allowed to happen next

Before any letter is drafted or sent, an authorization policy checks the role, the recipient, the approval token and the finding set. No citation, no dispute. Wrong recipient, no send. No token, no send.

GATE 3 — HUMAN

Nothing ships without a signature

Every outbound action pauses for an advocate's explicit approval, and the exact amount and recipient approved are hashed and re-checked at send time — a changed number after approval is refused, not silently sent.

Who it's for

Built for nonprofit patient advocates and financial-counseling teams who read hospital bills for a living — not for patients to self-serve. It turns a stack of paper into a worked case file: every disputable dollar traced to a rule and a record, every charity-care eligibility check shown with its math, and a dispute letter that only quotes what the engine already proved.

Proof, not a promise

From the real engine scorecard (evals/results/engine-scorecard.json), run against 45 corpus cases.

—Exact rule-set match
—Exact $ match rate
—FAP tier accuracy
—False positives on clean bills