What Is an ASO Health Plan? How It Differs from a TPA

An employer moving off a fully insured plan for the first time usually hears two terms almost interchangeably: ASO and TPA. A broker or consultant may use them side by side as if they describe the same arrangement. They do not, and the difference affects cost, flexibility and control over the life of the plan. Understanding which structure fits before signing a contract changes what an employer can negotiate and what they are left working around later.

The confusion is understandable. Both arrangements administer a self-funded plan instead of insuring it, and from the outside the day-to-day services, such as claims processing, network access and member support, can look nearly identical. What separates them is who is running the administration and how much of the platform is built around the employer’s specific plan rather than a standard book of business. That difference shows up directly in how much room there is to negotiate plan design, vendor partners and service levels. This article breaks down what ASO means, how it differs from a standalone TPA relationship and where each one fits for a plan your size.

What is ASO?

ASO stands for administrative services only. It describes an arrangement where an insurance carrier handles the administrative side of an ASO health plan, claims processing, provider network access, ID cards and customer service, without taking on the financial risk of paying claims. The employer funds the claims. The carrier runs the machinery.

This structure exists because carriers already have the infrastructure built for their fully insured book of business: networks, claims systems and call centers. An ASO contract lets a self-funded employer plug into that infrastructure without paying a premium for risk transfer it no longer needs.

The tradeoff is that the employer is buying into the carrier’s existing systems and rules rather than a custom-built administration model. Plan design flexibility, reporting access and vendor integrations are generally shaped by what the carrier’s platform already supports.

For a 150-employee group, that often means working within the same claims platform and reporting format built for the carrier’s block of much larger, fully insured accounts, with limited room to adjust for what that specific group needs.

What is a TPA, and how does it differ from an ASO?

A third-party administrator provides the same core function, running claims, eligibility and network access for a self-funded plan, but a TPA is not necessarily tied to a carrier. Many TPAs, MagnaCare included, operate independently of any single insurance company, which changes what an employer can ask for.

An insurance carrier’s core business is selling insurance. Plan administration is something it offers on top of that, using whatever systems and networks it already has in place. For a TPA like MagnaCare, administration is not an add-on: it’s the entire service. That tends to show up in three places: more willingness to customize plan design and network structure around what the employer needs, more flexibility to integrate outside vendors instead of working from a fixed partner list and more direct account access instead of routing through a call center built for millions of members across many employers. We covered how that model benefits self-funded groups in Why Self-Funded Health Plans Need a Third-Party Administrator.

ASO vs. TPA: The practical differences

Set side by side, the differences between an ASO health plan and TPA administration come down to six areas that shape how a self-funded plan runs day to day.

Ownership

ASO administration is run by an insurance carrier. TPA administration may or may not be tied to a carrier.

Network Access

ASO plans typically use the carrier’s existing network as is. A TPA like MagnaCare can rent, build or customize a network around your employee population, rather than defaulting to the carrier’s existing panel.

Plan design flexibility

ASO arrangements are built around the carrier’s standard platform. A dedicated TPA is generally more willing to customize plan rules, exclusions and benefit design around your group specifically.

Vendor integrations

Carrier ASO plans often limit outside point solutions to an approved list. A dedicated TPA tends to take a more open approach to pharmacy, wellness and specialty vendors.

Reporting and data access

Carrier ASO reporting is built for the carrier’s broader book of business. TPA reporting can be tailored to the employer’s specific plan and cost drivers instead of a standard book of business.

Account management

ASO service often runs through the carrier’s general customer service infrastructure. TPA service is typically dedicated to your plan specifically.

When an ASO arrangement makes sense

For employers who want to stay close to a familiar carrier relationship, or who value the size and stability of a national network without building anything custom, an ASO health plan can be a reasonable entry point into self-funding. Self-funded plans are still governed under ERISA, so the compliance groundwork is the same regardless of which administration model an employer chooses. An ASO arrangement is often the path an employer’s existing fully insured carrier proposes first when a group considers moving off a fully insured plan, since the carrier already has the relationship.

This tends to fit best for employers early in their self-funding transition, particularly smaller groups moving off a fully insured plan for the first time. Staying with the same carrier’s ASO product avoids a network disruption for employees mid-transition, and it gives HR a familiar point of contact while the organization gets comfortable with the mechanics of funding claims directly. The cost of that convenience tends to show up later, once the group outgrows the carrier’s standard playbook.

When a standalone TPA makes more sense

Employers who have outgrown a one-size-fits-all platform, who want a network built around where their employees live and work or who need plan design flexibility a carrier’s standard ASO product will not support usually move toward a dedicated TPA relationship. The same applies to employers frustrated by slow service, restricted vendor lists or reporting that does not answer the questions they have about their plan’s cost drivers.

This shift typically happens once a plan has a few years of self-funded claims data showing specific cost drivers, a network mismatch or a point solution the carrier will not support, problems a standard ASO product is not built to fix. At that stage, the flexibility a TPA offers usually outweighs the convenience of staying put.

Questions to ask before you choose

• Is the administrator also the network owner, or does it work with a network you can shape?
• Can plan design and exclusions be customized, or are you working within a fixed template?
• What vendors can be integrated, and is there an approved list?
• Who handles service issues, a dedicated account team or a general call center?
• How detailed is claims and cost reporting, and can it be customized to your plan?

Frequently asked questions

Is an ASO health plan the same as self-funded insurance?

An ASO health plan is one way to administer a self-funded plan. Self-funding describes who bears the financial risk, the employer. ASO describes who runs the administration, in this case a carrier acting in an administrative-only capacity.

Does an ASO plan still involve an insurance carrier?

Yes. The defining feature of an ASO arrangement is that a carrier administers the plan without assuming claims risk. The employer, not the carrier, pays the claims.

Can an employer switch from an ASO plan to a TPA later?

Yes, and many do as their self-funded plan matures. Moving from an ASO arrangement to a TPA typically happens at renewal and involves transferring network access, claims history and member data to the new administrator.

Are TPA fees higher or lower than ASO fees?

It varies by group size, plan complexity and the services included. Employers should compare fees against what each administrator delivers rather than sticker price alone, since a lower fee paired with less flexibility or slower service can cost more over the life of the plan.

Does a TPA take on financial risk the way a fully insured carrier does?

No. Like an ASO arrangement, a TPA relationship keeps claims risk with the employer. The TPA handles administration; the employer funds the claims, typically backed by stop-loss coverage against high-cost claims.

Why employers choose MagnaCare

MagnaCare has administered self-funded health plans for employers for more than 30 years and is not tied to a single insurance carrier. Whether you are weighing an ASO health plan against a standalone TPA for the first time or reconsidering a setup that no longer fits, MagnaCare builds plan design, network structure and vendor integrations around what an employer’s population needs rather than what a standard platform already supports.

Considering a move from an ASO arrangement to a dedicated TPA? Talk with MagnaCare’s team about what self-funded plan administration built around your business could look like.