Self-Insured Health Plan Administrator: Employer Guide

A self-insured health plan administrator coordinates the day-to-day work that helps an employer-sponsored health plan operate. For a Washington employer considering self-funding, it is important to know which tasks an administrator performs, which decisions remain yours, and how to monitor the arrangement over time. The administrator may process claims and provide reports, but that does not automatically transfer every plan responsibility away from the employer.

Talk with a benefits advisor about your plan

What Does a Self-Insured Health Plan Administrator Do?

In a self-insured arrangement, the employer funds covered medical claims, usually with help from outside service partners. A third-party administrator, often called a TPA, commonly handles operational work under a contract. The administrator may process claims, answer member questions, support enrollment and eligibility files, and prepare reports. The exact scope depends on the service agreement and the employer’s plan documents.

The administrator is not necessarily the insurer that takes on the plan’s claims risk. A TPA generally performs delegated administrative services; the employer retains the financial risk for claims, subject to any stop-loss coverage it has purchased. Some arrangements use a carrier or another service provider for administration. Read the actual agreement rather than relying on labels such as “self-funded,” “administrative services only,” or “level-funded.”

The Texas Department of Insurance describes employer self-funding and explains that a TPA may manage plan tasks using funds provided by the employer to pay covered claims. This is a useful plain-language overview of the administrative relationship, though Washington employers should confirm how their own plan and contracts work: Texas Department of Insurance: Employer self-funding of employee health benefits.

Administration is more than claims processing. A well-defined arrangement connects plan rules, eligibility data, claims decisions, member support, financial controls, and reporting. The employer needs a reliable process for each handoff and a way to spot problems before they affect employees or the plan budget.

Which Responsibilities Usually Belong to the Administrator?

Specific duties vary, so employers should use the contract and service schedule as the definitive list. Common administrative functions include the following:

• Claims intake and processing: Receive claims, apply the plan’s terms and network pricing, route exceptions for review, and arrange payment from plan assets or the employer’s designated funding account.
• Eligibility and enrollment support: Load employee and dependent data, apply effective dates supplied by the employer, and coordinate enrollment changes with the benefits or payroll system.
• Member service: Respond to questions about claim status, plan processes, provider networks, identification cards, and appeals routing. The TPA can explain administrative steps, but it should not replace clear plan materials or appropriate clinical guidance.
• Provider and network coordination: Apply contracted network arrangements when applicable, handle claim repricing, and help resolve issues such as a claim processed with the wrong network status.
• Appeals and documentation support: Track appeal submissions, apply the documented review process, maintain records, and notify the appropriate parties of decisions and deadlines.
• Plan and financial reporting: Provide claims summaries, payment information, utilization trends, and other agreed reports. The detail, frequency, and permitted uses should be specified in writing.
• Compliance administration: Support selected notices, records, or filings if those services are expressly included. The employer should not assume that a TPA has taken responsibility for a legal requirement just because it performs related administrative work.

Some TPAs also coordinate pharmacy benefit, stop-loss, or care-management services through other vendors. Coordination is not the same as direct responsibility. Confirm who owns each task, who supplies the underlying information, and who resolves a missed handoff.

To understand how administrative services fit among other group-plan designs, review the Washington Health Insurance Agency (WHIA) overview of group health plan examples. Employers comparing funding arrangements may also find the explanation of a level-funded health plan useful; it addresses a different funding structure and should not be treated as a substitute for reviewing an administrator’s contract.

What Does the Employer Continue to Own?

Delegating tasks is not the same as delegating every duty. The employer, plan sponsor, plan administrator named in the governing documents, and service vendors may have different roles. Those labels can have legal significance. Employers should have qualified benefits counsel review the plan documents and contracts, especially before deciding who has discretionary authority over claims or appeals.

For many private-sector employee benefit plans, ERISA establishes important plan-governance and reporting rules. The Department of Labor’s annual report describes Form 5500 filing requirements for many private-sector health plans, including the general threshold of 100 or more participants, as well as reporting considerations. Applicability depends on the plan and its circumstances; use the official report and qualified counsel rather than treating a summary as a determination for your business: U.S. Department of Labor: Annual Report on Self-Insured Group Health Plans.

Even when a TPA performs operational work, the employer should retain clear ownership of decisions and controls such as:

• Setting plan intent: Decide the benefit design, eligibility rules, cost sharing, and employee contribution approach, then make sure the written plan reflects those decisions.
• Approving vendors and contracts: Understand the services, fees, data access, subcontractors, performance standards, and termination provisions before signing.
• Providing accurate data: Send timely enrollment, termination, dependent, and payroll information through a controlled process.
• Monitoring delegated work: Review reports, service levels, exceptions, complaints, and financial reconciliations. Escalate unresolved issues rather than assuming the vendor will surface every risk.
• Communicating with employees: Make sure employees know where to ask questions, how to appeal a decision, and what the plan covers. Coordinate changes with HR and payroll.
• Meeting applicable obligations: Identify which party prepares and submits required notices, filings, and records, and verify completion. Responsibilities can vary with plan type, employer status, and applicable law.

Self-insured plans and fully insured plans can be subject to different legal frameworks. The EEOC’s enforcement guidance discusses the interaction between ERISA and state law for insured and self-insured plans. It is a legal resource, not a blanket statement that every requirement is identical for all employers: EEOC: Interim Enforcement Guidance on the Application of the Americans with Disabilities Act of 1990 to Disability-Based Distinctions in Employer-Provided Health Insurance.

For general orientation, the National Library of Medicine record on self-insured health plans describes administrative models used by employers. Its research dates to 1986, so it should not be used as a current market estimate; the relevant point is that employers may administer internally or hire outside help.

How Can Employers Set Up Clear Administrative Workflows?

Start by mapping a routine employee event and a routine claim from beginning to end. This reveals where employer data, administrator action, and employee communication meet. For example, when a new employee becomes eligible, HR confirms the eligibility date, payroll records the chosen coverage, the administrator loads enrollment, and the employee receives confirmation and a member ID card. Each handoff needs an owner and a check for completion.

1. List recurring events. Include new enrollment, qualifying status changes, terminations, dependent updates, claim questions, appeals, urgent care access issues, and monthly funding or invoice review.
2. Name a responsible party for every step. Use specific roles, not broad labels such as “HR” or “the vendor.” Identify a backup for time-sensitive work.
3. Agree on deadlines and evidence. State when files are due, how receipt is confirmed, how corrections are handled, and what record proves that the change was completed.
4. Define escalation paths. Set contacts and response expectations for a routine question, a serious claim issue, a privacy concern, and a repeated service failure.
5. Test the process. Before launch, walk through sample enrollment changes and claim scenarios with HR, payroll, the administrator, and any other relevant vendor.
6. Review after implementation. Compare actual service to the agreed process and update procedures when errors, plan changes, or staffing changes expose a gap.

Keep the workflow accessible to the people who use it. A short responsibility matrix can be more useful than a long manual that no one consults. Include a contact route for employees, an internal escalation owner, and the administrator’s documented service channel. For employees who need help finding care, make sure communications point to the correct provider search resource where appropriate, and explain that network participation can change and should be verified.

Which Reporting and Oversight Practices Help?

Useful reports answer a decision question. A large spreadsheet without definitions, comparison periods, or a named owner can create more confusion than insight. Before the plan year begins, agree on a reporting calendar and a short set of measures that leadership and HR will review consistently.

Depending on the plan and the services contracted, reports may cover paid claims, claim counts, large-claim activity in an appropriately protected form, pharmacy spending, enrollment, member-service volume, appeals, and processing turnaround. Ask how each measure is defined, when it becomes available, whether it is preliminary or final, and what limitations apply. Claims experience can be volatile, especially for a smaller group, so do not treat one month’s data as a reliable forecast.

Protect employee information. Request only the detail needed for a legitimate plan-administration purpose, restrict access, and understand how the TPA stores, transfers, and retains data. Aggregate reporting is often more appropriate for leadership review than member-level detail. Confirm the plan’s privacy obligations and the vendor’s contractual safeguards with qualified counsel and privacy professionals.

Build a regular review rhythm. A practical monthly check can reconcile funding and claims payments, identify outstanding operational issues, and confirm eligibility files were processed. A quarterly review can examine service performance, appeals, member experience themes, and emerging cost patterns. Ahead of renewal, review the full year alongside plan design, employee feedback, and any stop-loss terms. These reviews should focus on actionable questions, not simply collecting more metrics.

What Should the Administrator Agreement Make Clear?

Do not rely on a sales presentation to define service. The signed contract, service schedule, plan documents, and data agreements should fit together. Ask for plain-language answers before execution and record them in the appropriate agreement.

Area	What to clarify	Employer oversight question
Claims processing	Included claim types, exceptions, appeals support, payment workflow, and records	How will we see and resolve a claim handled outside the normal process?
Eligibility files	File format, delivery frequency, effective-date rules, error notices, and correction process	How do we verify that a change was loaded before a coverage issue arises?
Member service	Channels, service hours, response targets, escalation steps, and reporting	Who owns a case that remains unresolved after initial contact?
Financial controls	Claims funding, payment authorization, reconciliation, fees, and audit records	Which report lets finance match activity to the plan’s funding account?
Data and privacy	Permitted uses, security controls, access, retention, breach response, and subcontractors	Who can access identifiable information, and how is access reviewed?
Performance and exit	Service measures, remedies, transition assistance, data return, and termination terms	How can we move the plan and its records if the service relationship ends?

Ask for definitions behind service-level promises. “Fast processing” is not measurable unless the agreement says what is measured, what starts and stops the clock, how exceptions count, and how performance is reported. Clarify whether the TPA has authority to make claim determinations or only applies rules set in the plan. Have counsel review discretionary authority, appeals procedures, and any allocation of fiduciary responsibilities.

How Should Employers Evaluate an Administrator’s Performance?

Set a baseline at implementation, then compare performance over time using agreed definitions. Avoid judging an administrator on one anecdote or one favorable month. Look for recurring patterns and test whether the underlying data is complete.

• Accuracy: Are enrollment records and claims processed according to plan terms? Track corrected errors and their causes.
• Timeliness: Are files, reports, claim payments, and member responses delivered within agreed timeframes?
• Resolution: Are escalated problems closed with a documented answer, or merely transferred between vendors?
• Transparency: Can the employer understand fees, claim activity, network arrangements, and report limitations?
• Employee experience: Do members know where to get help, and are repeated complaints pointing to a communication or process gap?
• Coordination: Does the administrator work effectively with payroll, HR, brokers, stop-loss providers, and other contracted partners?

Use a review agenda and keep a short issue log with an owner, due date, status, and evidence of resolution. When performance falls short, first determine whether the issue is a contract gap, a data problem, an unclear plan provision, a vendor execution problem, or a communication failure. The remedy differs for each. Repeated issues may justify a corrective action plan or a broader review of the service relationship.

Employer size and plan complexity affect the level of support required. A smaller HR team may need an administrator that can manage more routine coordination, while a larger organization may have in-house benefits staff who want configurable reporting and defined interfaces. Consider your capacity, not just a feature list. WHIA’s pages on small-group coverage and large-group coverage offer additional context for Washington employers at different group sizes.

What Questions Should HR Ask Before Choosing an Administrator?

Keep the conversation focused on work, accountability, and fit. Ask the prospective administrator to show how a real workflow would operate rather than relying only on a list of capabilities.

• Which tasks are included in the base service, and which require separate fees or another vendor?
• Who performs claims processing, appeals support, member services, and reporting? Are any functions subcontracted?
• What plan documents and eligibility data do you need from us, and how do you flag missing or conflicting information?
• What reports will we receive, how often, and who can explain definitions and limitations?
• How are serious claim problems and time-sensitive member issues escalated?
• What access will the employer have to plan records and claim information, and how are privacy and security handled?
• How will you coordinate with our payroll, HR, stop-loss, network, pharmacy, and other service partners?
• What implementation support, employee communication, and training are included?
• What happens to records, open claims, and member support if we terminate the agreement or change administrators?

Compare responses against your operational needs and the contract language. A polished demonstration does not establish that a service is included. Ask for sample report formats, implementation milestones, escalation procedures, and a clear statement of the employer’s responsibilities. If a vendor gives different answers in a meeting and in its written agreement, resolve that difference before signing.

How Do Administration Needs Change at Renewal or During a Vendor Transition?

Administration should be reviewed when the plan changes, not only when a contract is up for renewal. A change in eligibility rules, plan options, network, pharmacy arrangement, payroll platform, or funding approach can affect the data and decisions the administrator handles. Give the TPA enough lead time to confirm system configuration, test files, update employee materials, and explain how exceptions will be handled. Avoid assuming that a plan amendment automatically updates the administrator’s operating procedures.

Before renewal, compare the current service to the written scope. Check whether reports arrived as promised, whether recurring issues were resolved, whether HR understands the escalation process, and whether employees can find help. Review fees alongside the services actually used. If the employer is considering a different vendor, compare the transition workload and risk as carefully as the proposed service features.

A practical transition plan should cover:

• Ownership and timing: Name a project lead on the employer side and a counterpart at each vendor. Build a schedule that includes the last date for old-system activity and the first date for new-system activity.
• Data transfer: Identify which eligibility, claims, appeal, and plan records must move; who authorizes the transfer; how accuracy will be checked; and how access to old records will remain available when needed.
• Open work: Inventory pending claims, appeals, eligibility corrections, and member complaints. Assign a responsible party and tracking method so that unresolved items do not disappear during the handoff.
• Employee communications: Explain what is changing, when new cards or contact details will be available, and where employees should go for help during the transition. Keep messages factual and coordinate timing with HR and payroll.
• Testing and fallback: Validate sample files and workflows before launch. Decide who will respond if enrollment data fails, a claim is routed incorrectly, or members cannot reach the expected support channel.

Document decisions and keep a single issue tracker during implementation. Ask the outgoing administrator to confirm its final service date and the steps for handling activity received after that date. Ask the incoming administrator to confirm readiness in writing. These steps do not guarantee a seamless transition, but they make ownership visible and give the employer a way to identify problems quickly.

Talk with Washington Health Insurance Agency about your plan administration

Frequently Asked Questions

Is a self-insured health plan administrator the same as an insurance carrier?

No. An administrator often handles plan operations under contract, while the employer funds covered claims in a self-insured arrangement. The exact relationship depends on the plan and contracts. Some providers may offer both administrative services and other products, so identify who bears each risk and who performs each task.

Does hiring a TPA make the employer no longer responsible for the plan?

No. A TPA can perform delegated work, but the employer still needs to understand its plan-sponsor and governance responsibilities. Who has legal authority depends on the plan documents and applicable law. Employers should confirm the allocation with benefits counsel.

Can an administrator decide whether a claim is covered?

It may process claims by applying the plan terms, and the governing documents may grant it specific authority. The employer should verify who makes initial determinations, who reviews appeals, and what procedures apply. Do not infer decision-making authority from a vendor’s job title.

What reports should an employer request?

Start with reports that support specific oversight decisions: claims and payment summaries, eligibility processing, service activity, appeals, and agreed performance measures. Ask for definitions, timing, limitations, and privacy protections. The right set depends on plan size, design, and contractual services.

How often should we review the administrator?

Set a cadence in advance. Many employers benefit from a short monthly operational check and a deeper quarterly or annual review, adjusted to their plan and service agreement. Review sooner when a serious member issue, repeated processing error, or major plan change occurs.

Ready to Review Your Employer Health Plan Administration?

Washington Health Insurance Agency (WHIA) helps employers understand benefit-plan options and the operational questions that come with them. Learn how WHIA supports employers, or speak with an advisor about the questions your team should resolve before selecting or changing an administrator.

Schedule a conversation about your benefits strategy

A clear division of work, documented service expectations, and steady employer oversight can help keep plan administration understandable for HR, leadership, and employees.