PAYMENT INTELLIGENCE

Put every payment in perspective.

Compare an observed total allowed amount with an explicit, reproducible Medicare benchmark.

Single service + CSV analysis
Compare like with like. Enter the total allowed amount, including payer and patient responsibility—not just the insurer’s payment. A variance is a research signal, not proof of underpayment or an amount owed.

Analyze a service

Uses the locality, service date, setting, and schedule above

How to read a variance

1
Start with the right context

Confirm the date, locality, provider schedule, component, and place of service.

2
Check the contract

Commercial payer terms and service-specific adjustments can legitimately differ from Medicare.

3
Investigate before taking action

Review caps, multiple-procedure reductions, modifiers, coverage and the remittance advice.

YOUR DATA STAYS YOURS

No patient information needed.

Amounts are compared in your browser. Only procedure codes and pricing context are sent to this app’s server. No claim, patient, or payment records are saved.

Review a batch of services

Up to 200 rows · global/unmodified codes · 100% of the selected Medicare benchmark

Import a de-identified CSV

Exactly three columns: code, units, allowed. Allowed is the total amount for the row. Do not include patient identifiers.

RVU-based Medicare benchmark, before payer adjustments, OPPS caps, sequestration, and patient cost sharing. An estimate, not a payment guarantee.