SIMON® is now called the Vimly Platform. Same login, same data, same features. Get answers

That Platform Wasn’t Built for This: Multiple Employer Benefits Administration Needs a Different Playbook

Most benefits platforms can support multiple employer groups. What matters is how much work it takes to manage them after setup.

In brief

Multiple employer benefits administration requires a platform organized around the plan and the employer groups within it. When each group is treated as a separate employer, setup, updates, and reconciliation have to be repeated group by group. When the groups sit in one hierarchy, the team runs the same workflow for every group while each group keeps its own plans, rates, contributions, and eligibility rules.

For multiple employer trusts, associations, health plans and TPAs, one question comes up early in every platform evaluation: Can it handle multiple employer groups? Most platforms can. The more important question is how the platform structures them. Are the plan and its groups the foundation for how data and work are organized, or is each group treated as another employer inside a system built for one? That distinction determines how much work your team carries for the life of the contract.

Built around one employer at a time

Most benefits administration platforms were designed around a single employer: one company, one set of plans, one set of rates, one set of eligibility rules and one invoice. That design works well for its original purpose. Adding a second employer, or a fiftieth, does not break it. It simply creates another employer that must be configured and managed separately.

The work hides in the word separately. Each group is its own setup, so a change that touches twenty groups is made twenty times. Each group’s rules live with that group, so an eligibility question has to be checked against the right one, and a mismatch is found when someone notices it. Each group’s billing stands alone, so reconciling the carrier bill to what the groups were invoiced means working across every group’s records to find where they differ. None of this is a defect in the platform. It is what a design built around one employer produces when it is asked to run many.

Built around the plan and the groups within it

The Vimly Platform uses the plan, trust or book of business as its organizing structure. Every employer group sits within the same hierarchy while keeping its own plans, rates, contributions and eligibility rules. Administrators can manage shared workflows across the plan without losing the differences between groups.

Where the difference shows up

Group setup. On a platform built around one employer, each new group must be configured as a separate employer. On the Vimly Platform, the group’s plan design, contribution rules and census are entered once to create its enrollment record. When the plans are approved and the census is ready, setup takes about 20 minutes. The practical limit becomes how many groups the organization can sell, not how many its operations team can configure.

Ongoing changes. A rate, plan or rule change that applies across the plan is entered once at the appropriate level and flows to every affected group. A change that applies to only one group stays with that group. Each group’s eligibility rules are applied as members enroll, change coverage or leave, allowing the team to focus on exceptions that require judgment.

Billing and reporting. Each group’s invoice and the carrier file are generated from the same record, so they align by design. Reconciliation is limited to activity the carrier posts late. Billing can roll up to the level the plan requires while each group still receives its own invoice. Reports use the same source, allowing the team to retrieve a group’s prior coverage, invoices and change history without searching across systems.

Was this platform designed around the plan and its employer groups, or around one employer and then extended? The answer decides whether a change is made once or once per group, and whether reconciliation is a check or a search.

The Association of Washington Cities put this structure into practice when its Employee Benefit Trust moved 279 employer groups and approximately 43,500 members onto the Vimly Platform. The transition caused no eligibility issues or disruption to members. Carol Wilmes, Director of Member Pooling Programs, described the result as “one system and one source of truth.”

How to tell in an evaluation

Features can look similar in a demo. Three requests expose the difference between the underlying designs. Ask to watch a new group being created from an approved quote and census, and time the process. Ask to see a plan-level rate change applied, and count how many times it must be entered. Ask to see one month’s carrier bill reconciled against the groups’ invoices, and watch where manual work remains.

A platform extended to support multiple groups leaves the organization managing the gap between what the system was designed to do and what the operation requires. That gap grows with every group added.

Closing call to action

Vimly did not grow into the multiple employer market. Its people have administered multiple employer benefits for more than 30 years, and the Vimly Platform was built around that work. Today, it supports more than 750,000 members.

See how the Vimly Platform runs a multiple employer program

Share

Facebook
Twitter
LinkedIn