Medicare Overpayments: How the 180-Day Investigation Clock Works

The dangerous Medicare overpayment is not always the one sitting in a refund queue. It may be the first incorrect payment someone notices—and treats as an isolated billing adjustment. A supervisor finds that an interface mapped a service to the wrong code. A physician discovers that signed notes do not support a billed service. Someone refunds the obvious claim, closes the ticket, and misses the same problem across hundreds of earlier encounters. The dollar amount on that first claim can be small; the obligation it exposes may not be.

As practices approach the final quarter of 2026, their overpayment procedures should reflect an important CMS change already in effect. The calendar year 2025 Medicare Physician Fee Schedule final rule revised the identification standard for Medicare Parts A and B overpayments and established a limited suspension of the return deadline during qualifying investigations of related overpayments. The practical issue is not whether a practice has six extra months to keep Medicare’s money. It is whether the practice can recognize an overpayment, investigate its reach in good faith, calculate what it owes, and document why its timing was lawful. That requires a workflow connecting billing, clinical leadership, compliance, and finance—not just a refund spreadsheet.

1. What changed—and what did not

The central obligation remains familiar: Medicare overpayments generally must be reported and returned within 60 days after identification, or by the due date of an applicable corresponding cost report, whichever is later. For most physician-practice billing problems, the 60-day framework is the relevant one. Keeping an identified overpayment beyond the applicable deadline can create exposure under the False Claims Act.

What changed is how the regulation defines identification. The revised rule uses the False Claims Act’s knowledge standard: actual knowledge, deliberate ignorance, or reckless disregard. It replaces the former regulatory formulation based on reasonable diligence. The rule does not require proof of a specific intent to defraud before the knowledge standard can be met.

CMS also added a defined suspension for a good-faith investigation into related overpayments arising from the same or a similar cause. That suspension can last up to 180 days, subject to conditions and an earlier stopping point. It is not an automatic extension for every refund.

These provisions appear in the Medicare Parts A and B overpayment regulation at 42 CFR 401.305. Do not copy this procedure unmodified into a Medicare Advantage, Medicaid, or commercial payer workflow. Those payments may involve different governing requirements and contractual processes. First identify who paid the claim and which repayment framework applies.

2. Separate a warning signal from an identified overpayment

An unusual payment is not necessarily an overpayment. A duplicate-looking remittance might reflect a reversal and replacement. A code that appears unsupported in a billing extract might be supported elsewhere in the medical record. Staff should validate the facts rather than convert every anomaly into a premature legal conclusion.

But the opposite mistake is more dangerous: deciding that nothing is identified until a committee approves a final report. Under the revised standard, knowledge does not depend on the date a compliance officer signs a memo. A clear payer duplicate, an acknowledged charge-generation defect, or a confirmed service that was never furnished can establish facts well before the organization completes its accounting.

Use two separate fields in the issue log: the date the concern first reached the organization and the identification date determined from the facts and applicable standard. Preserve the reasoning behind the distinction. If the dates differ, the file should explain what was uncertain and what evidence resolved it.

A practice cannot manufacture extra time by leaving messages unread, declining to examine a known system defect, or telling billers not to escalate small balances. Deliberate ignorance and reckless disregard matter precisely because a process built to avoid learning the truth is not a safe process. Ambiguous or material cases deserve prompt review by qualified compliance personnel or counsel.

3. Understand what the 180-day suspension actually does

The investigation provision addresses a common problem: a practice identifies an initial overpayment but does not yet know whether the same or a similar cause produced others. It permits suspension of the reporting-and-return deadline while the practice conducts a qualifying good-faith investigation into those related overpayments.

The suspension ends at the earlier of two points: when the investigation has concluded and the aggregate amount of the initial and related overpayments has been calculated, or 180 days after the initial overpayment was identified. The practice must track both the investigation limit and the underlying return deadline.

In a straightforward case where the qualifying investigation begins when the initial overpayment is identified, the available timeline can reach 180 days for investigation plus the 60-day return period. That is an outer-bound illustration, not a universal 240-day entitlement. A suspension pauses a deadline; it does not erase elapsed time or authorize waiting after the investigation finishes.

Suppose a practice confirms that a charge rule caused incorrect Medicare payments and immediately investigates the affected claim population. If it finishes that investigation and calculates the aggregate amount after 45 days, the suspension ends then. It cannot keep the remaining investigation window simply because 180 days were potentially available.

Conversely, reaching day 180 without finishing the work does not keep the suspension alive. Large datasets, staffing shortages, and an unresponsive vendor are reasons to escalate early, not assumptions that the clock will stop.

4. Define “same or similar cause” before pulling thousands of claims

The investigation needs a coherent scope. “We are reviewing Medicare billing” is too broad to guide an analyst or demonstrate progress. “A charge-interface change may have assigned the wrong units to a specified service at two locations” gives the team a testable problem.

Start with the mechanism that produced the confirmed overpayment. Identify the relevant codes, systems, clinicians, locations, payment dates, and workflow changes. Then ask what else could share that mechanism. A template defect may affect several providers; a single employee’s manual posting error may not. Neither assumption should substitute for testing.

The Parts A and B rule generally requires reporting and returning an overpayment identified within six years of receipt. That makes payment receipt dates important; the lookback is not simply a search of six years of service dates. Records retention and historical system access should support the applicable review.

The initial scope can change as evidence develops. If testing shows that the problem began earlier or reached another location, expand it and record why. If a separate, unrelated issue appears, give it its own assessment and clock rather than silently folding it into the first investigation.

• Write a one-sentence description of the suspected root cause.
• Define the initial claim population and explain exclusions.
• Identify the records needed to establish billing and payment accuracy.
• Document each scope change, its evidence, and its effect on the timeline.

5. Build a refund file that someone else can reconstruct

A total on a spreadsheet is not enough. The investigation file should allow another reviewer to understand how the practice moved from a confirmed error to a defensible repayment amount. That means preserving source records, query logic, review decisions, and the payment history—not merely the final export.

For each affected claim, distinguish the original billed amount, the amount Medicare paid, subsequent adjustments, and the amount actually overpaid. An incorrect code does not automatically mean the entire payment must be returned; the appropriate correction depends on the facts and the applicable billing rules. Equally, a service that was not payable cannot be rescued by assuming some lesser payment must have been available.

Reconcile reversals and prior refunds before submitting money again. Duplicate repayment is an avoidable cash-flow injury, particularly when a contractor has already recouped an amount while the practice’s voluntary-refund team is working separately.

For large populations, obtain qualified advice before using sampling or extrapolation. A convenient handful of charts is not automatically a defensible methodology. The approach must fit the issue, the available evidence, and applicable contractor or disclosure requirements.

If outside medical billing services support the analysis, require reproducible queries, claim-level workpapers, and clear escalation dates. The practice should be able to explain its repayment without relying on a vendor employee’s memory or an inaccessible proprietary dashboard.

6. Choose the repayment route before the deadline gets close

The correct route depends on the problem. Medicare Administrative Contractors provide processes for claim adjustments and voluntary refunds, with instructions for identifying the provider, explaining the reason, and connecting repayment to the affected claims. Use the applicable contractor’s current instructions rather than a form saved years ago.

An internal credit entry is not the same as reporting and returning an overpayment. Neither is an email asking the contractor what to do. The file needs evidence that the required action was actually taken through the appropriate channel, along with follow-up to confirm how the contractor processed it.

Ordinary billing mistakes should not automatically be treated as fraud disclosures. But potential kickbacks, physician self-referral violations, or facts suggesting knowing false billing may require a different analysis and a specialized disclosure pathway. The HHS Office of Inspector General and CMS maintain distinct disclosure processes for different issues. Counsel should assess suitability and timing; sending a routine refund check may not resolve the underlying exposure.

Also examine patient accounting. Correcting Medicare payment can affect deductible or coinsurance calculations and secondary claims. Do not automatically move a Medicare repayment amount to the patient’s balance. Whether the patient can be held liable depends on the relevant coverage, notice, and billing rules—not on the practice’s desire to offset a refund.

7. Give the investigation an owner, a calendar, and spending authority

The most common operational weakness is divided responsibility. Billing knows the claims. Clinicians control documentation review. Finance controls disbursements. Compliance interprets the obligation. Each team assumes another team owns the deadline.

Assign one accountable case owner, even when several departments perform the work. That person should maintain the timeline, challenge stalled tasks, and escalate unresolved questions. The owner also needs access to leadership: an investigation cannot move in good faith if a modest data-extraction expense sits unapproved for weeks.

Establish internal checkpoints substantially earlier than the legal limits. These are management targets, not substitutes for the actual deadline. A weekly status review should ask what the team learned, what remains unknown, whether the scope changed, and whether the suspension still applies.

Outsourcing does not remove the practice’s need for oversight. Contracts for revenue cycle management services should specify prompt notice of suspected overpayments, access to historical records, cooperation with refunds, and responsibility for preserving evidence. A monthly summary that buries a material error in an adjustment category is not a workable escalation system.

Finance should forecast the likely cash requirement as the investigation develops. Waiting until the final amount is approved can turn a manageable repayment into an emergency. An accounting reserve, however, does not itself satisfy the obligation to report and return.

8. Correct the source without creating a second documentation problem

Refunding old claims while continuing to generate the same error defeats the purpose. Once the practice understands the mechanism, it should put a prospective control in place: disable the faulty charge rule, add a review step, retrain the relevant staff, or temporarily hold the affected claims.

Make that intervention specific. Freezing all Medicare billing because one service has a units problem may unnecessarily disrupt cash flow. Continuing all billing while waiting for a full historical investigation may create avoidable new overpayments. A targeted control should distinguish known-risk claims from unrelated work.

Preserve the original evidence before modifying templates, interfaces, or workflows. Record what changed, who approved it, and when it took effect. Later testing should establish that the change worked; a closed IT ticket is not proof of correct claims.

Clinical records require particular care. Do not backdate notes or coach clinicians to manufacture support for services already billed. Legitimate amendments and delayed entries must follow applicable documentation rules and accurately reflect their timing and authorship. Whether additional documentation affects payment is a separate question for qualified review.

Finally, test claims after the fix. Use enough follow-up review to determine whether the error stopped and whether the correction introduced another problem. Keep that validation separate from the historical repayment calculation so neither workstream obscures the other.

9. Use the next month to test one complete case

A practical fourth-quarter project is to take one recently resolved Medicare payment error and reconstruct its path. When did someone first notice it? When did the facts establish an overpayment? Was there a reason to investigate related claims? Who calculated the amount, approved the correction, and verified the return?

The exercise should expose missing handoffs, not reward a perfectly formatted policy. If the practice cannot retrieve the initial alert, explain its scope, or prove that Medicare received the repayment or adjustment, revise the workflow before a larger case arrives.

• Update the written policy to reflect the current knowledge standard and conditional investigation suspension.
• Create separate fields for the initial concern, identification, suspension, investigation completion, and return deadline.
• Confirm access to historical claims, remittances, and relevant clinical records.
• Assign a primary case owner and a backup with escalation authority.
• Verify current contractor instructions and require proof of repayment processing.
• Require a documented root-cause correction and follow-up testing before operational closure.