The confusion between these two terms comes from a fact that’s easy to miss: in both an ASO arrangement and a TPA arrangement, the employer is self-funded and holds the claims risk either way. That part doesn’t change. What changes is who does the administering and whose network the plan runs on.
ASO is what a carrier calls it when it administers a self-funded plan on the employer’s behalf, using the carrier’s own provider network, claims platform, and utilization management. The employer gets the carrier’s brand-name network without buying fully-insured coverage — but the administrator is the same company whose network you’re on, and you’re generally on their systems and their terms. In practice, the term is most often used for carrier-administered arrangements, though ASO technically describes the contract type, not the administrator — independent TPAs sometimes use the label too.
TPA is an independent company with no ownership stake in any specific network. A TPA administers the plan — eligibility, adjudication, EOBs, reporting — while the employer (or the TPA, on the employer’s behalf) contracts separately with whatever network makes sense for that group, or runs a reference-based pricing model with no network at all.
Side by side
| ASO | TPA | |
|---|---|---|
| Who holds the risk | Employer (self-funded) | Employer, healthshare, or association (self-funded) |
| Who administers claims | The insurance carrier | An independent, non-carrier administrator |
| Network | The carrier’s own network, bundled in | Rentable/flexible — any PPO network, or reference-based pricing |
| Tied to one carrier | Yes | No |
| Typical buyer | Larger employer that wants a recognizable network and is comfortable with the carrier’s platform | Mid-market self-funded employer, healthshare, or association wanting network flexibility and pricing transparency |
Why the distinction matters when you’re choosing
A group evaluating “carrier ASO vs. independent TPA” is really deciding how much control it wants over network selection, plan design flexibility, and data access. An ASO deal is simpler to set up if the employer is already comfortable with that carrier’s network, but the employer is administratively downstream of the carrier’s systems and reporting cadence. A TPA arrangement takes more assembly — the employer or TPA has to source a network, stop-loss, and a claims platform separately — but it buys real flexibility: the network can change without changing administrators, and the plan design isn’t constrained by what one carrier’s platform supports.
That flexibility is also exactly why independent TPAs need software that isn’t built around a single carrier’s assumptions — a rules engine that can price against whatever fee schedule a given client’s network produces, run multiple client books on isolated configurations, and adjudicate the same claim types a carrier’s ASO platform would, without the carrier attached. Claimaro’s TPA software is built for exactly that independent-administrator position, and the same adjudication logic underneath it works for a self-funded employer evaluating whether to stay on a carrier’s ASO platform or move to an independent TPA relationship.