Overpayment Calculator

Compare the correct payment against what was actually received to quantify overpayments — the variance that creates refund obligations, not revenue.

The variance that isn’t good news

Getting paid more than the contract says feels like the one billing problem worth having — it isn’t. Identified overpayments are liabilities: they must be refunded, on a clock, and in US federal programs the deadline after identification is 60 days, with serious consequences for sitting on known credits. Enter the correct payment, the received payment, and how often the pattern repeats, and this calculator sizes the exposure.

How to use it

  1. Enter the contractually correct payment.
  2. Enter what was actually received.
  3. Add the occurrence count if the pattern repeats — duplicates and rate errors always repeat.

The formula

overpayment = received − correct · exposure = overpayment × occurrences

A worked example

Expected $650, received $720: a $70 overpayment, 10.8% above contract. Repeated across 12 similar remits, the refund exposure is $840 — small money, big principle: credit balances left unworked are the finding every payer audit and compliance review looks for first, precisely because they’re easy to find and hard to explain.

Estimates only — payer contracts, plan documents, published fee schedules and the EOB are the source of truth, and nothing here is billing, legal or medical advice. The calculator runs entirely in your browser: no patient data is entered, transmitted or stored.

Common questions

Where do overpayments come from?
Duplicate payments, wrong fee-schedule rates, both primary and secondary paying as primary, retro eligibility changes, and patient collections that the OOP max later capped.
Can we just hold the credit until the payer asks?
No — identified overpayments carry affirmative refund obligations, and federal-program credits have the 60-day rule. A worked credit-balance queue is a compliance control, not housekeeping.
How is this different from the underpayment calculator?
Same comparison, opposite sign, opposite workflow — underpayments are revenue to chase, overpayments are liabilities to return. Both start from loaded contract rates.