Underpayments: How to Spot Them and Recover Revenue Without Adding Headcount

Underpayments: How to Spot Them and Recover Revenue Without Adding Headcount

Insurance underpayments can hide in plain sight. Even when a claim “processes,” the paid amount may fall short of what your clinic expected, and the remittance can look routine enough to miss during a busy week.

However, underpayment recovery does not have to require more staff. With a defined variance workflow, clear triage rules, and a tight tracking loop, a billing lead can surface issues early, route only the right cases to appeals or reopenings, and prevent repeat leakage.

This guide lays out a practical, repeatable process you can run weekly in an outpatient clinic environment, using chiropractic-forward examples that still translate to PT and behavioral health.

What counts as an underpayment (and what does not)

Define “expected” before you chase variances

An underpayment is a payment that is short of the amount your clinic reasonably expected for that claim line or claim, based on your fee schedule and contract expectations, after accounting for legitimate contractual adjustments and patient responsibility.

In contrast, a “small payment” is not automatically an underpayment. For example, the remittance may legitimately assign patient responsibility, apply a deductible, or indicate a non-covered service depending on the benefit and the coding scenario. The key is to compare what happened to what should have happened under your rules.

Use remittance codes to understand why the payer adjusted the amount

When you review an ERA/EOB, the adjustment explanation typically relies on standard remittance code sets. In the X12 framework, Claim Adjustment Reason Codes (CARCs) describe the overall adjustment reason, while Remittance Advice Remark Codes (RARCs) add detail or additional context. CMS also summarizes how group codes allocate financial responsibility, such as contractual obligation versus patient responsibility, which directly affects your next action. See References.

A weekly underpayment recovery workflow that scales without adding headcount

Step 1: Build a “variance-ready” dataset from your remits

First, pick a consistent cadence. Weekly works well because it keeps timelines tight while avoiding daily churn. Next, pull a remit-based list that includes, at minimum: payer, date of service, procedure code, units, billed, allowed (if present), paid, patient responsibility, adjustment group/reason, and remark codes.

Then, standardize how you store that data. If your system supports exports, use one export format for the whole quarter. Otherwise, use a simple tracker template and keep the column set fixed so your team can filter and pivot without rework.

Step 2: Calculate “expected allowed” using a simple rule hierarchy

Because contracts and fee schedules vary, you need a consistent way to compute an expected target. Start with a hierarchy:

• Rule A: If your contract modeling is available for the payer and code, use the modeled expected allowed.
• Rule B: If you do not have modeled rates, use your internal expected allowed table (payer + code + unit rule), updated when you learn new outcomes.
• Rule C: If neither exists, flag the line as “no expected rate” and route it to a separate learning queue rather than mixing it into underpayment work.

Importantly, this structure keeps your underpayment queue clean. Otherwise, the team spends time debating “what should it be,” which slows recovery and burns capacity.

Step 3: Apply a variance threshold and a reason filter

Next, set triage rules that prevent your team from chasing noise. For example, you might review all variances over a small dollar threshold, plus any variance tied to specific CARC/RARC patterns that historically indicate a payer processing issue.

Additionally, treat “patient responsibility” differently from “payer underpayment.” CMS explains that group codes assign who is financially responsible for an unpaid portion, which helps you avoid mixing collection work into the underpayment queue. See References.

Step 4: Triage each variance into one of four action paths

Once the variance list is filtered, assign each item to a single action category. This step is where you protect staff time.

• Category 1 — Clinic-correctable: A claim detail needs correction (e.g., modifier, units, diagnosis linkage, place of service). Action: corrected claim, not an appeal.
• Category 2 — Documentation or medical record support needed: The payer requests records or a coverage rationale. Action: gather the minimum necessary documentation, then submit through the payer’s required channel.
• Category 3 — Payer processing or contract variance: The claim processed, but the allowed or paid amount does not match the expected rate. Action: initiate the payer’s variance dispute or appropriate appeal route.
• Category 4 — Not recoverable / informational: The variance is explainable and aligned with benefits or known rules. Action: log the reason so the tracker learns, then close it.

Because you pick one path per item, you reduce multi-touch handling and keep your follow-up calendar realistic.

How to work the “contract variance” lane efficiently

Use a standard dispute packet checklist

For contract-related underpayments, create a short, consistent packet checklist so every dispute has the same core elements:

• Claim identifiers and dates of service
• Line-level expected allowed and the method used to calculate it
• ERA/EOB excerpt details (no PHI beyond what the payer requires)
• Relevant remittance codes supporting the payer’s processing explanation
• A concise statement of the variance and requested correction

Although each payer has different portals and forms, your internal packet can stay consistent. That consistency is what allows a billing lead to delegate assembly steps without adding headcount.

Decide between correction, appeal, and reopening based on the scenario

If the variance stems from a clinic-correctable issue, a corrected claim often resolves faster than an appeal. On the other hand, when the payer made a determination you dispute, the payer’s appeal path may be required.

For Medicare fee-for-service, CMS describes the formal first level of appeal (redetermination) and the broader multi-level appeals structure, which can guide how you frame documentation and timelines. See References.

Separately, CMS manuals also describe “reopenings” as a distinct mechanism contractors may use to change a determination that resulted in an underpayment, which can matter when the issue is not truly a medical-necessity dispute but an adjustment that needs correction. See References.

Preventing repeat underpayments with a “root-cause loop”

Turn every resolved variance into a prevention rule

After you resolve a variance, capture the root cause in a structured way. Then, map it to a prevention lever:

• Front desk: eligibility workflow, benefit notes, authorization tracking
• Clinical documentation ops: missing elements that delay billing or trigger adjustments
• Charge entry: unit rules, modifier logic, code pairing checks
• Claim submission: clean claim edits and pre-bill review criteria
• Follow-up: status cadence and escalation triggers

Consequently, your underpayment tracker becomes a training system, not just a recovery log.

Specialty notes: chiropractic-first, still inclusive

• Chiropractic: track variances that correlate with plan-of-care documentation completeness, coding consistency, and front-desk benefit capture, because those issues often show up as adjustments rather than outright denials.
• Physical therapy: separate authorization-related reductions from true pricing variances, and tag them distinctly so appeals follow the correct path.
• Behavioral health: flag variances tied to telehealth or place-of-service handling and keep documentation and eligibility notes tight to reduce repetitive rework.

Operational metrics that keep the workload stable

To keep recovery work from expanding, track a short set of metrics weekly:

• Number of underpayment variances identified
• Number routed to each action category
• Average days from remit to first action
• Rework rate (items touched more than once before submission)
• Top repeat root causes

Then, use those results to refine thresholds and filters. Over time, the queue shrinks while your team’s precision improves.

Conclusion

Underpayment recovery works best as a disciplined workflow rather than a heroic effort. When you define “expected,” filter variances intelligently, triage into clear action paths, and feed outcomes back into prevention rules, you can recover missed revenue while keeping staff time under control.

References

• CMS: Health Care Payment and Remittance Advice (CARC/RARC and group codes)
• X12: Remittance Advice Remark Codes (RARC) overview and code list access
• CMS: Medicare Claims Processing Manual, Chapter 22 (Remittance Advice)
• CMS: Medicare Claims Processing Manual, Chapter 34 (Reopenings and revisions; underpayment context)
• CMS: First Level of Appeal (Redetermination) overview
• CMS: Medicare Claims Processing Manual, Chapter 29 (Appeals overview)
• HFMA: Revenue cycle management overview (includes underpayment management as revenue leakage control)