When Subrogation Negotiations Start Borrowing from ERISA Litigation

By: Stewart P. Miller, Esq.

Routine subrogation negotiations frequently borrow tactics from ERISA litigation. One common example is the use of document requests under ERISA § 104(b)(4), 29 U.S.C. § 1024(b)(4), as leverage in reimbursement discussions.

For plans, TPAs, and recovery vendors, this development is worth watching. A request for plan documents may be perfectly appropriate. Participants and beneficiaries have long had rights to request certain governing plan documents from the plan administrator. But in some reimbursement matters, these requests are no longer being used just to confirm the basis for the plan’s recovery interest. They are being used as pressure points, with counsel suggesting that unless the plan produces a broad range of materials, the plan should reduce, delay, or abandon its reimbursement claim.

This is the wrong framework as it creates unnecessary noise for the plan, member, and professionals trying to resolve the file. A valid 1024(b)(4) request should be taken seriously but it should not be treated as an automatic lien reduction tool.

ERISA § 104(b)(4) generally requires the plan administrator, upon written request from a participant or beneficiary, to furnish certain governing plan documents. If the plan administrator fails to comply, ERISA allows a court, in its discretion, to impose penalties of up to $110 per day. That possibility should not be ignored. Plans should have a process for routing, reviewing, and responding to these requests promptly and consistently.

But a possible document-production issue is separate from the plan’s reimbursement rights. That distinction is the heart of the matter.

A plan’s reimbursement position is governed by the plan terms, applicable law, and the facts of the recovery. A 1024(b)(4) issue poses a different question: whether a disclosure obligation was properly triggered and satisfied. These issues may arise in the same file, but they should not be commingled.

The statutory penalty is also discretionary. It is not automatic simply because counsel alleges a production defect. Courts may consider the circumstances of the request and response, including whether the participant was actually prejudiced. That context matters, particularly where the documents at issue did not affect the member’s understanding of the claim or the plan’s asserted recovery position. It is very different from treating every document dispute as a built-in offset against plan assets.

This is where negotiations can drift off course. Counsel may request core plan documents but may also seek broader categories of materials and attempt to use that request as leverage against the reimbursement claim. The plan should not ignore the request, but it also should not allow the request to reshape the recovery discussion.

The better approach is disciplined, not defensive. The plan does not need to overreact, but it does need to control the process.

First, route the request correctly. If a recovery vendor, TPA, or other service provider receives a document request, it should be escalated to the appropriate channel. The obligation under § 1024(b)(4) generally rests with the plan administrator, and requests should be handled consistently with that structure. Good routing protects the plan and avoids unnecessary confusion on both sides of the file.

Second, confirm authority where appropriate. If the plaintiff’s counsel is making the request on behalf of a participant or beneficiary, the plan should ensure counsel is authorized to do so. This is basic plan administration, especially where personal health information, benefit information, and plan documents may be involved.

Third, identify what the statute requires. The plan administrator should evaluate the request under ERISA and determine what materials fall within the applicable disclosure obligation. Core governing documents should be handled differently from broad requests for materials that are not plan-governing instruments. The response should be careful, timely, and documented.

Fourth, keep the response tracks separate. The plan may respond to a valid document request while maintaining that reimbursement remains governed by the plan terms and recovery facts. If counsel believes there is a penalty issue, that issue can be addressed on its own merits. It should not automatically become a discount on the plan’s reimbursement claim.

The broader takeaway is simple: Subrogation teams should expect more sophisticated ERISA-adjacent pressure in routine recovery files. That does not mean every request is improper. It does mean plans and vendors should avoid being pulled into a negotiation structure where compliance questions are treated as substitutes for the plan language.

None of this means plans can never compromise. There may be practical reasons to consider a reduction, including limited coverage, disputed liability, contested relatedness, procurement costs, litigation risk, collectability concerns, or client direction. But these are reimbursement considerations. A 1024(b)(4) request, by itself, is not one.

For groups, the best defense is preparation. Know where governing documents are located. Know who is responsible for responding to ERISA document requests. Know how authorization is confirmed. Make sure vendors understand when and how to escalate requests. Most importantly, make sure reimbursement language is current, consistent, and administrable. A strong process turns a potential distraction into a manageable administrative issue.

This is not only about avoiding penalty exposure or checking off an administrative box. It is about maintaining a clean record, a consistent process, and a clear division between disclosure compliance and reimbursement enforcement. When a plan has paid claims and later asserts its recovery rights, the conversation should remain focused on the plan terms and the recovery. A document request should not be allowed to become a substitute for that analysis.

The plaintiff’s counsel may continue using 1024(b)(4) requests as leverage in subrogation negotiations. Plans should recognize the tactic, respond professionally, and avoid overreacting. The goal is not to fight every request. The goal is to handle each request correctly while keeping the reimbursement issue grounded where it belongs.

Compliance is not compromise. A plan can take document obligations seriously without surrendering reimbursement rights that belong to the plan and, ultimately, to the participants and beneficiaries the plan protects.