A third-party administrator holds something more valuable than its call center scripts or its network discounts. It holds your plan's memory. Who enrolled, when they enrolled, what got paid, what got denied, and why. That record belongs to the plan. The employer remains the ERISA plan sponsor. The TPA is a service provider with a contract. If the vendor controls your data architecture, it controls the renewal conversation.
Most selection processes skip this. HR teams compare per-employee-per-month fees, claims turnaround times, and network discounts before they ask what happens when the contract ends. This ordering skips the costliest failure mode. The exit clause tells you more than the sales deck does.
Start with the exit test
Before you ask about fees, ask the TPA to produce three things in writing. A complete data dictionary. A file transfer standard with documented layouts. A defined extraction timeline that names who pays for the work and how historical data gets delivered after termination. If the TPA cannot produce these three items before the sale, the implementation team will not produce them after the sale. The sales process is a sample of the operating relationship.
Data portability is the control point. A TPA that returns raw claims data on day one after termination treats you as the plan sponsor. One that cannot has leverage at renewal. Ask for a termination assistance clause that states the transfer format, the timeline, and the cost. You want the contract to say the TPA will export all eligibility files, claims history, and plan documents in a standard format within 30 days of termination, with no fee for the first export.
Revenue disclosure before service-level promises
TPA revenue is transactional in most arrangements. Per employee per month. Per claim. Per check. Per network encounter. Some TPAs also collect payments from pharmacy benefit managers, stop-loss carriers, and provider networks. Those arrangements rarely show up in the fee proposal. That means the TPA earns more when claim volume and complexity rise. The employer wants lower claims. The conflict sits inside the revenue model.
Service-level agreements do not fix it. A few hundred dollars in turnaround penalties cannot offset revenue tied to additional claims activity. The selection criterion is written visibility. Request a revenue schedule that lists every payment the TPA receives from carriers, networks, pharmacy benefit managers, and stop-loss partners, including contingent payments and administrative service fees. Estimates put waste at 20 to 25 percent of healthcare spending. When TPA revenue tracks claim volume, every wasted dollar is revenue. If the TPA refuses to disclose its revenue sources, treat that refusal as a disqualifier.
Audit rights and error recovery
TPAs promise high accuracy rates without a shared definition of accuracy. The definition in the contract matters more than the number. Ask for the right to pull a random sample of paid claims each quarter and reconcile them against the plan document. The plan document is the source of truth.
The selection criterion is the correction mechanism. How quickly are overpayments recovered? Who absorbs provider disputes? Is the error rate measured against the plan document or against the TPA's own processing rules? Request the subrogation and overpayment recovery policies in writing. If the TPA will not agree to quarterly audits with recovery terms, the promised accuracy rate is empty.
First-dollar plan coordination
Most TPA RFPs assume one plan. That assumption fails when an employer adds a supplemental medical plan that employees use before the primary plan. A WellthCare™ Plan is one example. WellthCare works alongside an employer's existing health plan and gets used first. Employees receive $0-co-pay care, earn reward dollars at the WellthCare Store™, and build retirement savings through verified preventive health actions. The primary plan sits behind it.
The technical questions matter. How does the TPA adjudicate a claim when a supplemental plan paid first? Can the system accept eligibility files and claim-level data from the supplemental plan without manual re-keying? How does it prevent double payment and report each plan layer's paid exposure? Ask for a reference account with that exact configuration. If the TPA has none, expect to be the test case, and price the implementation timeline accordingly.
Reporting granularity
TPA reporting should answer three questions. Which members used each benefit layer? What did the plan pay? Where did claims occur by diagnosis category and provider? Monthly summary pages do not answer these. Ask for a raw data feed or a reporting tool that lets you rebuild any month's paid claims by member, service date, provider, and plan layer. Employers need this detail for renewal decisions, stop-loss reporting, and nondiscrimination testing.
The short scorecard
Cut the questions that measure sales polish. Number of offices. Years in business alone. Generic client logos. Replace them with these five checks:
- Exit data dictionary, file layout, and extraction timeline
- Written revenue source disclosure
- Quarterly audit rights with recovery terms
- First-dollar supplemental plan experience
- Raw claims data access with plan-layer attribution
Run these checks in the first meeting. If the TPA cannot answer them directly, the remaining RFP responses are not worth scoring.
For benefits teams evaluating a TPA, the data and exit test separates vendors from gatekeepers. If your plan stack includes a first-dollar supplemental layer such as a WellthCare Plan, add the coordination questions above to the RFP. See what a WellthCare Plan would look like alongside your current TPA.
This content is for general information only and is not legal, tax, or medical advice. Employers should consult their own advisors.