Blog · Denials and appeals
The Medicare 60-day overpayment rule: when the clock starts and how to refund
The Medicare 60-day overpayment rule in 42 CFR 401.305 requires a provider that has identified an overpayment to report and return it within 60 days of identification, or by a corresponding cost report's due date if later, and suspends that deadline for up to 180 days during a timely, good-faith investigation of related overpayments. We cover what identified means, how a credit balance becomes a reportable overpayment, the refund routes, and the log that holds the dates up.
Filed under denials and appeals on the Remitwright medical billing blog.
What does the Medicare 60-day overpayment rule require?
Report and return any Medicare overpayment you’ve identified by the later of 60 days after you identified it or the date a corresponding cost report is due1. That’s 42 CFR 401.305(b)(1), and it applies to any provider or supplier holding Medicare funds it isn’t entitled to after reconciliation1.
The teeth are in paragraph (e): an overpayment retained after that deadline is an obligation for purposes of 31 U.S.C. 3729, the False Claims Act1. So a billing error that was innocent on the day it happened becomes something else on day 61 if you knew and sat on it. That’s why this rule belongs to the billing office, not only to compliance.
And it isn’t about payer demands: a MAC that finds its own error sends a demand letter and recoups on its own timetable2. The 60-day rule covers the money you find.
When is an overpayment “identified” under the current regulation?
Under the current regulation, an overpayment is identified when you knowingly receive or retain it, with knowingly taken from the False Claims Act definition, rather than on the day a payer first flags it. The 2025 edition, as amended in December 2024, says a person has identified an overpayment when the person knowingly receives or retains an overpayment, borrowing the meaning of knowingly from 31 U.S.C. 3729(b)(1)(A)1. The question is what you knew, not when a payer told you; ask your compliance adviser how that standard fits your review process.
In billing terms, a credit balance is a flag, not yet an identification. Identification is the day your review confirms Medicare paid money it shouldn’t have and you can say roughly how much. Log that date.
How does the 180-day investigation pause work?
The deadline is suspended while you run a timely, good-faith investigation into related overpayments, for at most 180 days from the first identification. Paragraph (b)(3) applies when you’ve identified an overpayment but haven’t completed a good-faith investigation into related overpayments from the same or similar cause, and you’re conducting it in a timely way1. The suspension ends on the earlier of the day the investigation concludes and the aggregate is calculated, or the date 180 days after the initial identification1.
Two conditions, both yours to prove: timely and good faith. An investigation that opens on day 1 and does nothing until day 150 isn’t timely; one that looks only at the claims you already found, not the pattern behind them, isn’t a good-faith search. Document both as you go.
And the lookback: an overpayment must be reported and returned if you identify it within six years of the date it was received1, so the search for related overpayments reaches back six years.
How does a credit balance on your A/R become an overpayment?
When posting shows Medicare paid more than it should have and nobody has a reason it’s right. Most credit balances begin on the 835: a duplicate payment posts against a claim already at zero, a patient pays a deductible Medicare then also covers, or a corrected claim processes and the original payment is never taken back.
Posting from the 835 rather than the check is what makes them visible. A Medicare remittance must balance at the service, claim and provider levels, and provider-level adjustments carry PLB reason codes4; that’s where a MAC’s recoupment or your own refund appears later. How to read an ERA walks the segments.
Remark codes help you sort the cause. X12 describes RARCs as additional explanation for an adjustment already described by a CARC, or as information about remittance processing, with the informational type prefaced “Alert:”3. A duplicate denial such as CO-18 on a later claim is often the first hint that an earlier one paid twice.
But not every credit is an overpayment: some are posting errors, unapplied patient payments or contractual adjustments taken twice. Work the credit balance report weekly and classify each line.
Which refund route applies: voluntary refund, claim adjustment or a MAC demand?
The one your MAC sets out, chosen by who found the error and how many claims it touches. The regulation says you report and return using an applicable claims adjustment, credit balance, self-reported refund, or other reporting process set forth by the Medicare contractor, and you describe the methodology if you used statistical sampling1.
| Trigger | Date identified | Deadline to report and return | Pause available? | Route |
|---|---|---|---|---|
| Duplicate payment visible on the 835 | Posting date your review confirms the second payment1 | 60 days after that date1 | Rarely: one claim, no pattern | Claim adjustment or the MAC’s self-reported refund1 |
| Audit finds payment for a service the record does not support | Audit date the finding is confirmed1 | 60 days, unless suspended1 | Yes, if the same cause may have hit other claims1 | Self-reported refund with a claim list1 |
| Coding error that repeats across claims | Date the first instance is confirmed1 | Suspended during a timely, good-faith investigation, up to 180 days1 | Yes1 | Self-reported refund for the aggregate; describe sampling if used1 |
| Payer and patient both paid the same balance | Date posting shows both payments | 60 days for the Medicare share1 | No | Claim adjustment to Medicare; patient refund under your own policy |
| MAC demand letter after a post-payment review | Not yours: the contractor identified it | The demand letter’s terms2 | No; appeal rights apply2 | Pay, or appeal within the letter’s deadline2 |
The last row is the contractor’s process, not the 60-day rule. A MAC, RAC, SMRC or CERT post-payment records request gives you 45 calendar days to respond, a UPIC request 30, and where a UPIC finds an overpayment the MAC sends the demand letter and collects2. Appeal rights run through Medicare Part B appeal levels and deadlines.
How do you document the review so the dates hold up?
With a log that records when you knew what, who decided it, and what you did next. Every date in the regulation hangs on identification and on the investigation being timely and in good faith1.
Minimum entries: when the credit or finding first appeared; when your review confirmed an overpayment, and the amount; when the investigation opened, who ran it, and the six-year scope1; interim entries showing it kept moving; the conclusion date and aggregate; the refund route, submission date and MAC acknowledgement; and the PLB or deposit entry showing the money left4.
A medical billing audit that samples paid claims against the record finds these before a contractor does, and a payment posting routine that works the credit balance weekly keeps the list short. The recoupment glossary entry covers the vocabulary; the billing KPIs guide shows how unresolved credits distort net collection rate.
Worked example: 14 claims, one audit and the 180-day clock
A hypothetical dermatology group runs a quarterly internal audit of paid Medicare claims. On November 2, 2026 the reviewer confirms that 14 claims from one provider paid for a visit level the notes don’t support, and the group logs that date as the identification date1.
The same day it opens an investigation into related overpayments: same provider, same code pattern, every Medicare claim back six years1. The investigation concludes on January 15, 2027 with 41 affected claims and a calculated aggregate, 74 days in and well inside the 180-day limit that would have fallen on May 1, 20271.
With the suspension lifted on January 15, the group treats March 16, 2027 as its report-and-return date and doesn’t wait for it. On February 20 it submits the MAC’s self-reported refund with a claim-level spreadsheet, the reason, the method used to find the 41 claims, and payment1. The log gets the submission date, the MAC’s acknowledgement and, later, the PLB entry on the 8354. The group also fixes the cause: a template that defaulted to a higher level. This is a hypothetical example.
What to do this week
- Pull the Medicare credit balance report and classify every line: posting error, unapplied patient payment, or possible overpayment with a date.
- Add an identification date and a suspension-start date to your refund log1.
- Confirm your MAC’s self-reported refund process and form, and save the link where the posting team can find it1.
- Ask your biller to read the PLB on every Medicare 835, not just the claim lines4.
- Schedule a sample audit of paid claims against documentation; the audit date is the cleanest identification date you’ll have.
Questions people ask
What is the Medicare 60-day rule?
When does the 60-day clock start?
Can I take longer to investigate?
How far back do I have to look?
What if I disagree that it is an overpayment?
Next step
Want this looked at in your own numbers?
Three quick questions, no patient data. A billing specialist reads every request and replies in writing.
- Three questions, about two minutes
- No patient data, no software to buy
- A written reply from a biller, not a sales deck
You answer three questions
A billing specialist reads them
A written reply by email
Prefer email? sales@remitwright.com
Request received
Thanks. Your review request is in.
Reference . Quote it if you write to us about this request.
- A billing specialist reads your answers and replies by email.
- If a look at real claims makes sense, we agree read-only access under a BAA first.
- You get a written summary of what is worth working and what it would take. No commitment.
While you wait: see the sample weekly report or read how switching works. You can also download the sample weekly report (PDF).