Key Takeaways “We didn’t know” doesn’t eliminate MSP obligations. Employers can still face repayment or compliance issues when Medicare pays claims that a group health plan should have paid first. Medicare isn’t automatically primary when an employee turns 65. Whether Medicare or the employer plan pays first depends on factors such as employment status, employer size, the type of Medicare entitlement, and the circumstances of the coverage. Section 111 reporting matters. Employers need to understand who is responsible for reporting to CMS and make sure accurate employment and coverage information reaches the appropriate reporting entity. Outsourcing reporting doesn’t eliminate oversight. Even when a carrier or TPA handles reporting, employers should understand the process, provide accurate information, and monitor whether responsibilities are being fulfilled. MSP problems can become expensive over time. A relatively small coordination error can grow into significant recovery exposure when it affects multiple employees or remains unresolved for years. CMS can pursue recovery of mistaken payments. Employers, insurers, TPAs, and other responsible parties may become involved when Medicare paid primary despite a group health plan having primary responsibility. Documentation is one of the best safeguards. Employers should maintain clear processes for employment-status changes, eligibility, coverage information, reporting responsibilities, and responding to CMS inquiries. Acting quickly matters. Reviewing MSP procedures before a recovery notice arrives can make it easier to identify errors, correct problems, and respond appropriately when an issue is discovered. A Medicare Secondary Payer (MSP) recovery notice lands in your compliance officer’s inbox. Medicare has been paying claims that your group health plan may have been responsible for paying first, the problem has been going on for three years, and the potential repayment amount is substantial.
When your benefits team is asked how this happened, the response is immediate and sincere: “We didn’t know.”
It’s not a lie. Nobody fully understood the Medicare Secondary Payer rules. Nobody realized that inaccurate employment or coverage information could affect how claims were paid, and nobody knew the issue could sit unnoticed for years while the potential exposure continued to grow.
Unfortunately, not knowing doesn’t eliminate the obligation. If Medicare paid claims that another plan was legally responsible for paying, CMS may pursue recovery from the parties responsible for that payment. Being under-resourced is understandable, and good intentions certainly matter, but neither one changes which plan was legally required to pay first.
That’s the compliance reality employers need to understand.
The MSP Mandatory Reporting Requirement Medicare Secondary Payer, or MSP, rules determine when Medicare pays first and when another plan, such as an employer-sponsored group health plan, is responsible for paying first.
That answer depends on several factors, including whether the individual is actively employed or retired, whether their coverage is based on current employment, the size of the employer and why the person qualifies for Medicare in the first place. (I've written several prior newsletters on some of the nuances with MSP, so go check them out!)
For example, an employee turning 65 and enrolling in Medicare does not automatically make Medicare their primary coverage . If that employee is still actively working and covered by a qualifying employer plan, the group health plan may continue to pay first. Retiree coverage generally works differently. Medicare is usually primary for someone covered through a former employer’s retiree health plan, with the retiree plan paying second.
Disability and end-stage renal disease have their own rules, which is part of what makes this so confusing. There isn’t one simple rule that applies to every Medicare-eligible person on an employer’s health plan. The facts matter, and broad assumptions can create expensive problems.
Employers also need to understand how information about their health plan gets to CMS. Under Section 111, the organization responsible for reporting is called the Responsible Reporting Entity, or RRE. For an insured or TPA-administered plan, that organization is generally the insurance carrier or third-party administrator. If a plan is both self-insured and self-administered, the plan administrator or fiduciary may be responsible for reporting directly.
That doesn’t mean the employer gets to wash its hands of the process. Carriers and administrators rely on employers to provide accurate information about employment status, eligibility, coverage dates and other plan details. Employers may also be required to respond to CMS data-match requests. If the information being provided is late, incomplete or wrong, claims may not be coordinated correctly.
At a minimum, employers should know who is responsible for reporting, what information that organization needs and how quickly employment and coverage changes are being communicated. They should also have some way of confirming that the process is actually happening. Outsourcing the reporting function doesn’t mean outsourcing oversight.
A few warning signs that this process may already be breaking down:
HR and payroll systems don't automatically flag employees approaching age 65 No one on your benefits team could tell you, today, who your Responsible Reporting Entity is If any of these sound familiar, it's worth a closer look before CMS takes one for you.
What CMS Can Do When Mistaken Payments Are Discovered When Medicare discovers that it paid claims an employer plan should have paid first, CMS may seek to recover those payments. Depending on the situation, recovery may be pursued from the insurer, plan administrator, third-party administrator, employer or another entity responsible for making the primary payment.
CMS can demand repayment of claims Medicare paid conditionally or by mistake. Interest may also apply, and separate penalties may be possible when the organization responsible for Section 111 reporting fails to meet its obligations.
The repayment itself can be painful, but the administrative burden is often just as frustrating. Your company may need to go back through years of claims records, employee files, coverage dates, carrier reports, Medicare eligibility information and prior coordination decisions to figure out what actually happened.
Even if you eventually prove that the group health plan wasn’t responsible for some of the claims, researching and defending those decisions still costs time and money. The longer the problem has been sitting there, the harder it usually is to untangle.
How Historical Exposure Can Grow There isn’t one simple lookback period that applies to every MSP recovery situation. How far CMS can reach depends on the facts, the type of recovery action, when CMS received notice and the specific legal authority involved. If an employer uncovers a historical problem, this is an area where experienced benefits counsel should be involved.
The practical concern is pretty straightforward: a mistake can continue for months or even years before anyone realizes it exists.
Let’s say Medicare mistakenly paid an average of $5,000 in claims for each of 100 people whose employer plan should have paid first. That could create $500,000 in potential recovery exposure before interest, penalties or the cost of responding to the investigation.
That’s only an illustration, of course. Actual recovery amounts are based on real claims, not a flat monthly calculation. The point is that a coordination problem that looks small on the surface can add up quickly when it involves multiple people over several years.
This isn’t some obscure, theoretical risk either. CMS has systems specifically designed to identify situations in which another payer may have been responsible for claims Medicare paid.
The hardest thing for many employers to accept is that compliance obligations exist whether the benefits team fully understands them or not.the person responsible for Medicare coordination left the company and the process fell through the cracks. Maybe everyone assumed the carrier was handling it. Those things may explain how the failure happened, but they don’t automatically eliminate the obligation to correct it.
This is where documentation becomes so important. You may not be able to prove that every decision your team made was perfect, but you should be able to show that the company had a real process for understanding and following the rules.
You should know who owns the reporting function, what information is being shared, how employee data is validated, when coverage changes are communicated and how mistakes are corrected . If you rely on a carrier or TPA, someone inside the company should still be responsible for monitoring that relationship and making sure important information isn’t falling through the cracks.
A documented process can help show that your company made a good-faith effort to comply and acted quickly when a problem was discovered. It won’t automatically erase repayment obligations or penalties , but it puts you in a much better position than admitting nobody knew who was responsible.
“We didn’t know” may explain the failure, but it doesn’t fix the problem.
A much better answer is: “We had a process, we documented it, and when we found a problem, we moved quickly to correct it.”
That’s the answer every benefits leader should want to be able to give.
MSP Compliance Starts Before the Recovery Notice Medicare Secondary Payer compliance can feel complicated, especially when responsibility is divided among an employer, carrier, TPA and other benefits partners. But complexity is not a reason to leave the process undefined.
“We didn’t know” may be an honest explanation, but it isn't a compliance strategy.
If your organization needs help navigating Medicare coverage , employee transitions, and the complexities that come with employer-sponsored benefits, Exact Benefits can help. Learn more about our Medicare benefits solutions at Exact Benefits .
Frequently Asked Questions About MSP Compliance What is Medicare Secondary Payer? Medicare Secondary Payer is the set of rules that determines when Medicare pays second instead of first because another payer has primary responsibility for certain medical expenses. Employer group health plans can be primary to Medicare in specific circumstances.
Does the employer have MSP responsibilities if the TPA handles Section 111 reporting? Potentially, yes. The exact responsibilities depend on the plan's structure and reporting arrangement. CMS states that an RRE can use an agent to submit reports, but the RRE remains accountable for its reporting obligations and the accuracy of the information.
What happens if Medicare paid a claim that the group health plan should have paid? CMS may pursue recovery of the mistaken payment. For GHP Parts A and B claims, the Commercial Repayment Center handles the recovery process and may issue a demand to the employer, with claim information also provided to the insurer or TPA when known.
Can MSP reporting failures result in penalties? Yes. CMS currently has civil monetary penalty rules for certain Section 111 GHP reporting failures. CMS states that GHP RREs may be subject to a CMP of $1,000, as adjusted for inflation, per calendar day of qualifying noncompliance.
What should an employer do after receiving an MSP recovery notice? Review the demand promptly, identify the claims and beneficiaries involved, compare the claims against employment and coverage records, and determine whether any portion of the demand can be supported by a valid documented defense. Because recovery matters can involve significant financial and legal consequences, employers should consider involving qualified benefits or legal professionals when appropriate.
Next issue: IRMAA: How Income Impacts Medicare Premiums — What higher-earning employees need to understand before they retire.
