Every filing, the plan accounting and the day-to-day operations, at both levels of the arrangement: the MEWA itself and every participating employer beneath it. Designed for arrangements where hundreds to several thousand participating employers each file their own return.
One arrangement on paper, thousands of filers underneath it. The columns are the two levels. The rows are the difference between what gets filed and what has to happen underneath for the filing to be right.
A filing is not where the work starts. It is what a closed set of books produces at the end. Each step below depends on the one before it, which is why the returns can be read straight off the ledger. Nothing is assembled to match it.
The premium register: expected and billed premium by employer, by plan and by coverage month. What the plan is owed, stated before anyone asks what it received.
Whether what was billed matches who was actually covered. Differences surface as the feeds arrive and are raised as exceptions the same day.
The trust’s books, kept on an accrual basis. Contributions are recognized in the coverage month they were earned in, from the same enrollment the register is built on.
The month is closed and the variances are stated: what moved, by how much, and what was done about it. What was approved, and by whom, stays on the record. It is what your auditor works from.
Every return the arrangement owes, at both levels. We are approved to prepare and transmit directly through DOL EFAST2 and IRS AIR, with no filing service in between.
Five steps on a cycle. What feeds them runs continuously, and is the half of this your employers actually see.
The five steps run on a cycle. This does not. Some of it arrives continuously, as terminations and 65th birthdays land in the carrier files; some runs once a plan year, and nothing asked of several thousand employers comes back on the first request. Most of it needs an employer to confirm, sign or receive something before it is done. At sixty employers that is a trickle. At several thousand it is the job, and it is the part of this an employer or a broker actually experiences.
Enrollment is reconciled against the carrier feed first, so what goes to an employer is a short confirmation with the numbers already in it. Gaps are chased on a schedule, per employer, until the count is one the return can be built on.
Terminations are read off the carrier files as they arrive, and the reason decides what is owed. Where the reason is unambiguous the event routes straight through. Where it is not, we ask the employer, and the event waits. Either way the continuation category is determined per employer and per event, federal or state, since most employers on a plan like this sit under the federal threshold. What reaches your continuation vendor is a feed built to their format, carrying confirmed detail.
The enrollment feed shows who is turning 65 at an employer small enough to qualify, so nobody has to remember to look. The Small Employer Exception request is prepared, the employer verifies and signs it in their portal, and it is sent to CMS in the weekly packet. If approved, each one moves claims Medicare could have paid onto Medicare, and off your plan.
Plan documents, SPDs, SMMs, Summary Annual Reports and 1095-Bs are generated from the same data as the returns and issued to each employer with the date recorded. Distribution to participants runs through the employer, so what we hold is the record of what was produced and when it went.
A MEWA takes in more data than anyone outside one would guess, and it puts out more still. Mewa.io manages both sides: every input processed, checked and acted on, every output produced for the party that needs it, in the form they need and on the date it is due. The middle is where the work actually is. Every requirement, every check and every filing sits in one place, tracked, so at any point in the year you can see exactly where each one stands. Nothing is waiting on someone to remember it.
To the agencies
Every return the arrangement owes, at both levels, each on its own date.
To employers and members
Documents, Summary Annual Reports and 1095-Bs, issued and logged.
To your vendors
Confirmed continuation events, in your vendor’s own format.
To you
The dashboard, market insights, and a handful of signatures a year.
Fiduciary status under ERISA follows conduct, not contract labels. The model stays non-fiduciary because the work stays ministerial.
Applying the plan’s terms is our work: eligibility, continuation categories, covered lives, every determination the documents already answer. What we do not do is decide what the plan means where its terms do not reach it. Those few questions are surfaced with the facts assembled and the options laid out, for you to answer.
The separation is structural. Preparing and signing are different acts on different screens, and there is no way to type a figure into a return from the side that signs it. You can object to any figure on any filing, not only the ones our own checks flagged, and nothing is transmitted while a question you have raised is still unanswered. You sign as plan administrator with your own EFAST2 credentials; we transmit as a registered transmitter, straight to the agency.
Mewa.io coordinates the specialist bench; it does not replace it. You are changing one vendor, not restructuring the plan.
Every specialist you work with stays where they are, on the terms they are on now.
Leave your email and you’ll hear from the person who would manage your account. There’s nothing to prepare: much of what we’d need to understand your arrangement is already public, so we can get familiar with yours before we ever take your time.
Or email us directly.