If you run a self-funded health plan, you already know the drill: vet your TPA, benchmark stop-loss premiums, negotiate PBM contracts, and document every decision for your fiduciary files. But one question rarely comes up: Is your benefits administration system actually making you a worse fiduciary?
Many platforms were built for fully-insured plans. They handle enrollment, eligibility, and carrier feeds. But they weren't designed to support the ongoing monitoring and documentation that self-funded plans demand under ERISA. The result is a hidden gap between what you should do and what your technology lets you do. The gap shows up in three places.
Three Ways Your System Fails Your Fiduciary Duty
1. The Eligibility Black Hole
Your stop-loss policy hinges on accurate eligibility records. If an employee was supposed to be dropped due to reduced hours but stays active in your system, and then files a large claim, the stop-loss carrier can deny coverage. Under ERISA section 409(a), a fiduciary is personally liable to restore those losses to the plan. Does your platform automatically sync hours tracking with eligibility rules? Does it flag part-timers approaching the 30-hour threshold? Does it produce a clear audit trail for stop-loss audits? The 30-hour figure comes from the Affordable Care Act's full-time definition, and your plan document and stop-loss terms define eligibility, so any drift between your system and the document creates exposure. Most systems do none of this, leaving you to manage eligibility via spreadsheets. That is a lawsuit waiting to happen.
2. The Data Fragmentation Trap
Your self-funded plan lives in four different systems: your benefits admin (eligibility), your TPA (claims), your PBM (drug data), and your stop-loss carrier (history, pend lists, aggregate reports). Each uses different formats and updates at different frequencies. How do you spot a spike in ER visits at one location, a sign of possible network or utilization issues, when the data is scattered? Most plan sponsors can't. They rely on quarterly TPA reports that are already outdated. That leaves plan sponsors flying blind.
3. The Fee Transparency Blind Spot
ERISA sections 404(a) and 408(b)(2) require fiduciaries to ensure the compensation paid for plan services is reasonable. That means auditing TPA admin fees, stop-loss premiums, PBM spread pricing, and vendor charges. Those duties are about to get a statutory boost: the Consolidated Appropriations Act of 2026, signed February 3, 2026, requires PBMs to disclose direct and indirect compensation to health plans, pass through 100% of certain price concessions, and grant plan audit rights, effective January 1, 2029 for calendar-year plans. But your benefits system probably has no way to store every vendor's contracted fee schedule, compare actual charges to contract terms, or give you a single-pane view of total plan costs. Without system-level monitoring, you rely on annual RFPs or ad hoc audits, and you miss hidden fees until they've already drained plan assets.
What a Fiduciary-Grade System Should Do
Here are the capabilities that most platforms lack, but that every self-funded plan needs:
- Real-time eligibility validation with stop-loss carrier feeds to prevent coverage denials.
- Centralized fee schedule reconciliation to catch billing discrepancies immediately.
- Cross-vendor claims analytics to spot trends, benchmark against peers, and find errors.
- Fiduciary action tracker with timestamps for every decision (e.g., “Why did we stick with TPA X despite a rate increase?”).
- Compliance dashboard that monitors ERISA deadlines, HIPAA logs, ACA reporting, and stop-loss triggers automatically.
Some platforms now offer these integrations. Most still leave fiduciaries to assemble them manually.
Three Things You Can Do Today
- Audit your system's fiduciary readiness. Ask your vendor: Can you export eligibility data with change history? Can you combine eligibility, claims, and stop-loss data in one report? Can you track vendor fee changes over time? If the answer is no, document the gap. That documentation itself shows good faith diligence.
- Negotiate data transparency with your TPA. Include a contract clause requiring routine data extracts (claims, eligibility, fees) in a format your system can ingest. Many TPAs push back. Don't budge. Without that data, you can't monitor properly.
- Vet stop-loss carriers on data feeds. Ask carriers what data they provide: daily file drops, real-time pend list access, API connections. Avoid those that only send quarterly PDFs. Better data flow means better oversight.
Cybersecurity Is a Fiduciary Duty, Too
Plan sponsors often treat data security as an IT issue rather than a benefits one. It is a fiduciary issue too. In April 2021, the U.S. Department of Labor's Employee Benefits Security Administration (EBSA) issued three pieces of cybersecurity guidance, including “Cybersecurity Program Best Practices” and “Tips for Hiring a Service Provider.” In 2024, EBSA clarified through Compliance Assistance Release No. 2024-01 that this guidance applies to all ERISA plans, including health and welfare plans as well as retirement plans.
Your benefits platform is where that duty applies. It holds participant Social Security numbers, medical records, and financial information. The guidance directs fiduciaries to evaluate whether a service provider follows strong cybersecurity practices before signing a contract and to keep monitoring after. During your vendor review, ask for SOC 2 audit reports, encryption standards, incident response procedures, and access controls, and file the answers. A breach drains plan assets and participant trust at once, and the vendor review you documented is part of the record that shows you acted prudently.
The Bottom Line
Fiduciary due diligence now depends on who you hire and on how your technology helps you monitor, document, and protect the plan. Your benefits platform is a fiduciary tool. If it can't support your responsibilities, it is creating exposure. Start asking these questions now. Your plan, and your personal liability, depend on it.