Billing operations guide

Create a monthly underpayment recovery worklist that closes

A repeatable worklist method for identifying, ranking, pursuing, and closing payer underpayments without duplicate effort.

Published 6 min read
On this page

Identify underpayments worth pursuing

An underpayment is a payment below the contracted or expected amount for a service that was billed correctly. Not every variance deserves a recovery effort, because the cost of pursuit can exceed the difference. Set a dollar threshold and a minimum evidence standard before building the list. The threshold should reflect the staff time and payer response time, not only the balance.

Compare the allowed amount on the remittance with the contracted rate for the same code and modifier. Use the contract exhibit that was in effect on the date of service, not the current one. Record the expected amount, the paid amount, and the difference on the worklist row. A variance without a contract reference is an opinion that the payer can dismiss.

Attach contract evidence before assignment

Attach the contract page, fee schedule line, or payer policy that supports the expected amount. If the contract is ambiguous, mark the item for review instead of sending a challenge. A weak challenge teaches the payer to reject the next one. The evidence should let a reviewer reach the same conclusion without calling the billing team.

Check whether the variance is already explained by a documented adjustment, such as a sequestration reduction or a patient responsibility amount. Remove those items from the worklist before assignment so the team does not pursue legitimate reductions. A clean list preserves credibility with the payer and with the staff who work it. An item that belongs to a different workflow should be routed there with a note, not challenged as an underpayment.

Rank the worklist by recoverable value

Rank items by the recoverable amount multiplied by the likelihood of a successful challenge, not by the raw dollar difference alone. A large variance with ambiguous contract language may be worth less effort than a small one with clear support. Group similar items so one contract review can support several challenges. Rank order should tell the specialist what to work first on a short day.

Cap the list at a size the team can actually finish within the month. An oversized list creates a permanent tail of stale items that makes the whole effort look unsuccessful. Carry forward only items that still have a live path and remove the rest with a recorded reason. A worklist that closes is more useful than one that impresses with volume.

Set a closure rule for stalled items

Define how long an item may wait for a payer response before it is escalated or closed. Record each contact attempt with the date, channel, reference number, and outcome. If the payer does not respond after the defined attempts, move the item to a documented write-off or escalation path. Silence is not a resolution and should not keep an item open indefinitely.

Require a closure reason that another reviewer can understand, such as paid in full, upheld denial, contract ambiguity, or below pursuit threshold. A free-text note alone makes the monthly report hard to group. Use a short list of closure codes and review the list quarterly. Consistent closure codes turn a pile of individual cases into a management signal.

Report recovery and write-off separately

Report recovered dollars, sustained variances, and written-off amounts as separate lines. Combining them into a net recovery number hides how much effort produced no payment. Track the age of recovered items and the number of payer contacts per dollar recovered. Those ratios show whether the process is improving or just getting busier.

Compare the monthly recovery with the cost of the staff time spent on the worklist. If the ratio is poor for a payer or a contract line, revisit the pursuit threshold for that segment. Do not apply a single threshold to every payer when response rates differ. The report should help the team decide where not to spend effort next month.

Check the worklist for duplicate pursuit

Search the open items for the same claim, service date, and expected amount before adding a new row. Duplicate pursuit wastes payer goodwill and can trigger a fraud review when the same claim is challenged repeatedly. Assign a unique item number and keep prior correspondence attached to it. A duplicate check at intake is cheaper than a cleanup later.

Review the worklist with the posting and appeals teams so a challenge does not conflict with an open appeal or a corrected claim. Record the related item number when two workflows touch the same claim. One owner should decide which path proceeds first. Coordination prevents the team from sending contradictory requests to the same payer.

Authoritative references

  1. CMS Medicare Learning Network
  2. CMS Administrative Simplification
  3. X12 Health Care Claim Payment 835
  4. GAO Green Book

Philippines staffing intake

Define the role before hiring begins.

Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.

Contact Us