You chose self-funding because you wanted control. But here’s what nobody tells you at the sales meeting: the real cost isn’t the claims. It’s the invisible fragmentation between your TPA, your stop-loss carrier, and your own HR system. That fragmentation eats your savings from the inside out.
Most conversations about Administrative Services Only (ASO) stick to the obvious stuff: cash flow, state mandate exemptions, plan customization. But the silent reality is that ASO, as it’s actually implemented today, creates a deliberate fracture between plan design, claims processing, stop-loss coverage, and member experience. And that fracture isn’t a bug-it’s a feature of legacy business models. It’s also a ticking time bomb for employers who lack the tech infrastructure to manage it.
The Three-Legged Stool Nobody Inspects
In a fully insured plan, the carrier owns everything: the network, claims, stop-loss risk, member engagement. The data flows are centralized, even if clunky. In an ASO arrangement, the employer owns the risk, but the administrative skeleton is a three-legged stool of disjointed systems:
- The TPA - handles claims adjudication, provider networks, utilization management.
- The Stop-Loss Carrier - insures catastrophic claims, but needs near-real-time data to price risk correctly.
- The Employer’s HR Ecosystem - eligibility, payroll, wellness platforms, enrollment software.
Each leg runs on its own tech stack. They mostly talk to each other through batch file transfers-ANSI 834 and 837 files that introduce latency, errors, and reconciliation nightmares. It’s like trying to run a marathon with one leg in a different time zone.
Where the Real Cost Lives
Let me give you a concrete example most experts gloss over: stop-loss carrier data alignment.
Every month, the employer sends census and claims data to the stop-loss carrier for premium calculation. But the TPA’s system may code claims differently-different DRG groupings, different bundling rules. The result? You under-reserve or overpay on large claims. I’ve seen employers accidentally self-fund a $300,000 claim that the stop-loss carrier denied because the TPA’s “clean claim” timestamp didn’t match the carrier’s definition of “incurred during the contract period.” Worse, many stop-loss carriers still require manual paper submissions for specific high-cost claims. That defeats the whole point of ASO’s promised agility.
The System Integration Nightmare
From a benefits systems architecture perspective, ASO forces employers to become their own system integrator. Here are three places where things break all the time:
1. Eligibility vs. Claims Matching
An employee terminates in payroll (Workday, ADP, whatever). The TPA receives a delayed flat file two days later. In between, the employee files a claim. The TPA pays it. The employer eats the cost. This is a system latency problem, not malice.
2. COBRA and FSA Crosswalks
In a fully insured plan, the carrier automatically tracks COBRA eligibility. In ASO, the employer’s benefits admin system must manually feed the TPA. One field mismatch and the member is stranded-no coverage, no notice.
3. Wellness Incentive Failures
Your wellness platform issues a reward based on a health screen. But the TPA’s claims system doesn’t recognize the preventive care code. So the member pays full price. That’s a member experience failure directly caused by system fragmentation.
The Control Illusion
Most employers choose ASO because they believe it gives them control over plan design, data, and cost. In reality, they inherit a decentralized, unintegrated administrative machine that requires constant babysitting. The control is an illusion unless you invest in a Benefits Data Hub-a middleware layer that normalizes claims, eligibility, stop-loss, and wellness data into a single source of truth.
Very few TPAs offer this natively. The ones that do-high-end regional firms like Benefit Resource or Aliera-are unicorns. Most rely on legacy mainframes from the 1990s. You wouldn’t drive a 1995 sedan to a business meeting, but you’ll trust your health plan administration to one?
What to Ask Before Going ASO
If you’re advising a client-or making the decision yourself-skip the discussions about risk corridors and aggregate attachment points for a moment. Ask these three questions that expose the administrative skeleton:
- What data format does your TPA use for stop-loss data transmission? If it’s not real-time API or at least daily SFTP with automated validation, you’re setting up a reconciliation liability.
- How do you handle eligibility file timeliness? A three-day lag between HR system termination and TPA update is unacceptable. Demand integration through a modern API-for example, via platforms like Rippling or Workday Benefits Connect.
- Can your wellness platform’s outcomes data feed into the TPA’s medical cost analytics engine? If not, you’re flying blind on population health trends.
The Bottom Line
ASO is not just a financial decision. It’s a technology architecture decision. Treat it like one, and you’ll avoid the silent drag of administrative fragmentation that erodes the very cost advantage you’re chasing.
That data disconnect is real. But it’s also fixable-if you know where to look. Start with these three questions, and you’ll be ahead of 90% of employers running ASO today.