# Eligibility Files for Medicare Advantage and Supplemental Benefits Vendors: A Practical Guide

**Published:** Nov 18, 2026
**Author:** Donal Tobin
**Category:** Eligibility file

## Summary

How Medicare Advantage and supplemental benefits vendors can manage eligibility files from every plan they serve: one shared template, full and change files handled correctly, and a plan for the January enrollment surge.


![Eligibility Files for Medicare Advantage and Supplemental Benefits Vendors: A Practical Guide](https://cdn.buttercms.com/ALHbYx4RAebr5LRgYE73)


## Content

Medicare Advantage and supplemental benefits vendors receive member eligibility files from every health plan they serve, and the way to manage them is one intake process per plan built on a shared template, with validation, arrival alerts and extra capacity planned for the January enrollment surge. This guide is for data, engineering and operations leads at companies that Medicare Advantage and Medicaid plans pay to deliver benefits to their members, such as meals, transportation, hearing, fitness, in-home support and care navigation. By the end, you will know what makes these files different and how to set up intake that holds up as you sign more plans.

Every new plan contract means a new eligibility file. The vendors that scale are the ones who can onboard that file in days without adding headcount.

## The Problem: Every Plan Sends Members Differently

A supplemental benefits vendor might serve dozens of Medicare Advantage plans, and each one sends eligibility its own way. One plan sends a monthly 834 file, another a weekly CSV with its own column names, and a smaller plan emails a spreadsheet. Some send full files every time; others send only changes.

The calendar makes it harder. Medicare's Annual Enrollment Period runs from October 15 to December 7, and most coverage changes take effect on January 1, so January files are the largest of the year. Members can also switch plans during the Medicare Advantage Open Enrollment Period from January 1 to March 31, which means more adds and terminations early in the year. Vendors that process files by hand fall behind exactly when plans expect the fastest member activation.

## What You'll Need Before Starting

* A list of every plan you serve, with its file format, delivery method and cadence
* Each plan's file specification or 834 companion guide
* A standard member schema shared by all plans
* A destination for member records, such as a Postgres or Snowflake table or an internal API
* A named owner for each plan's file on your team

## How to Set Up Eligibility Intake as a Medicare Advantage Vendor: Step-by-Step

### Step 1: Inventory Every Plan's File

Start with a clear picture of what you receive today. Most vendors find more variation than they expected.

**What to do:** - For each plan, record its format (834, CSV, fixed-width or Excel), delivery method (your SFTP, the plan's SFTP or email) and cadence - Note whether the plan sends full files or only changes, since change files need different handling - Note which plans offer coverage through Dual Eligible Special Needs Plans (D-SNPs), whose members are also covered by Medicaid and change status more often - Flag plans that still send files by email so they can be moved to SFTP

**Output of this step:** A complete inventory of incoming eligibility files and how each one differs.

### Step 2: Define One Member Schema for All Plans

Every plan's file should land in the same shape. One schema means your service, billing and reporting systems never need plan-specific logic.

**What to do:** - Include member ID, plan ID, name, date of birth, address, phone, coverage start and end dates and benefit eligibility - Add a source_plan field so every record carries its origin - Decide how to represent benefit-level eligibility, since a member may qualify for meals but not transportation - Document the schema so new plan onboarding always maps to it

**Output of this step:** A standard member schema every plan's file maps into.

### Step 3: Build One Template and Configure It per Plan

A template that every plan shares turns onboarding into configuration. Only the details that differ by plan should change.

**What to do:** - Build one pipeline covering intake, mapping, normalization, validation and loading - Move plan-specific details into variables: folder path, file pattern, schedule and field mapping - Keep validation rules and the destination fixed across plans - Onboard each new plan by copying the template and setting its variables

**Output of this step:** A pipeline template that onboards each new plan without a rebuild.

**Where Integrate.io helps:** Pipelines can switch connections and file paths through variables per schedule, so one template runs for every plan, and native 834 parsing turns enrollment files into rows with named columns without custom code.

### Step 4: Handle Full Files and Change Files Correctly

Treating a change file as a full file can terminate every member who isn't in it. This is one of the most damaging mistakes in eligibility processing.

**What to do:** - Mark each plan as sending full files or change files - For full files, treat members missing from the new file as terminated only after a comparison check passes - For change files, apply only the adds, changes and terminations the file contains - Hold any full file that would terminate an unusual share of members, since that usually means a partial file

**Output of this step:** Member status that matches each plan's records, whatever kind of file it sends.

### Step 5: Validate Before Members Are Activated

Validation protects both members and billing. A bad record can deny a member a benefit or bill a plan for someone no longer covered.

**What to do:** - Reject empty, resent and structurally wrong files before reading rows - Check required fields, date formats and benefit codes on every row - Hold duplicate member IDs and conflicting records for review, and load clean rows - Compare each delivery with the previous one to catch partial files

**Output of this step:** Clean member records loaded, and exceptions held for review. For the full checklist, see [how to validate health plan eligibility files before they load](https://www.integrate.io/blog/how-to-validate-health-plan-eligibility-files/).

### Step 6: Plan for the January Surge

The months around January 1 bring the largest files and the tightest timelines. Preparing in the fall keeps activation on schedule.

**What to do:** - Confirm each plan's January delivery dates and any extra files during the Annual Enrollment Period - Test each plan's template against a large sample file before December - Tighten missing-file alerts for January, when a late file affects the most members - Schedule extra review capacity for held rows in the first weeks of the year

**Output of this step:** January files processed on time, with problems caught and resolved quickly.

**Where Integrate.io helps:** Scheduled checks on SFTP and S3 locations confirm each plan's file arrived and send alerts when one is missing, so a late January file is caught within hours.

## Common Mistakes to Avoid

* One pipeline per plan (step 3): each new plan becomes a project. A shared template keeps onboarding to configuration.
* Treating change files as full files (step 4): this can terminate every member not in the file. Record each plan's file type.
* Ignoring benefit-level eligibility (step 2): members may qualify for some benefits and not others. Model it in the schema.
* Discovering January volume in January (step 6): test with large files in the fall and plan review capacity ahead.
* Accepting files by email (step 1): email delivery can't be monitored or automated reliably. Move plans to SFTP.

## Conclusion

Managing eligibility files as a Medicare Advantage or supplemental benefits vendor comes down to six steps: inventory every plan's file, define one member schema, build a shared template, handle full and change files correctly, validate before activation and prepare for January. With those in place, each new plan contract becomes a configuration task, and the January surge becomes a planned event instead of an emergency. Integrate.io supports the whole process, from 834 parsing and per-plan templates to arrival alerts, so vendors can sign more plans without adding manual work. To see how this works for companies serving health plan members, read about [eligibility file ingestion for point solutions](https://www.integrate.io/solutions/insurance-benefits/point-solutions/).

## Frequently Asked Questions

### How do Medicare Advantage plans send eligibility files to supplemental benefits vendors?

Most send them by SFTP on a set schedule, either as 834 enrollment files or as CSV files in a layout the plan defines. Some send full member lists each time and others send only changes, and smaller plans sometimes still send spreadsheets by email.

### Why are January eligibility files so large?

Medicare's Annual Enrollment Period runs from October 15 to December 7, and most changes take effect January 1. Members can also switch plans during the Medicare Advantage Open Enrollment Period from January 1 to March 31, so early-year files carry many adds and terminations.

### What is the difference between a full eligibility file and a change file?

A full file lists every eligible member, so members missing from it are usually terminated. A change file lists only adds, changes and terminations since the last delivery, so members missing from it are unchanged. Processing one as the other causes serious errors.

### How do vendors handle members eligible for some benefits but not others?

They record eligibility at the benefit level in their member schema, so a member can be eligible for meals but not transportation. The plan's file or contract defines which benefits apply to each member or plan tier.


## Tags

834 files, eligibility files, en, Healthcare data integration, Medicare Advantage, supplemental benefits

## Categories

Eligibility file