Every Renewal Plan Change Needs a Carrier File Change

EDI benefits discrepancy: map every renewal change to the carrier file before January 1
At Providence Technology Solutions, we treat every plan change approved at renewal as a carrier file change. A new plan code, a new coverage tier or a new rate each has to be mapped in the file Dayforce sends your carrier before the first January file goes out. When that mapping waits, the carrier receives last year’s setup, and an EDI benefits discrepancy follows.
 
The discrepancy usually surfaces in January at a doctor’s office. An employee has paid for medical coverage through payroll, and the front desk says they are not covered. That call goes to benefits or HRIS, and the carrier’s record does not match the deductions payroll took.

What the employee experiences

The employee saw premiums come out of every check and expects coverage to be there. Answering them means tracing the file: enrollments, terminations, plan codes, coverage tiers, dependent data and the last feed the carrier accepted.
 
Someone you employ cannot use the benefit they funded, and your team has to show what Dayforce holds compared with what the carrier loaded.

How an EDI benefits discrepancy starts at renewal

Renewal changes the values your carrier file depends on. Many carrier feeds follow the X12 834 Benefit Enrollment and Maintenance standard, the format an employer uses to send enrollment data to the payer that administers coverage. Dayforce’s own Benefits Administration Guide lists updating existing carrier feeds for new plan information and testing the feed as part of the work. For background on how carrier feeds support benefits work, see our earlier article, How Can EDI Help My Benefits Administration?
 
Each renewal change has a home in the file:
  • A new or renamed plan needs its plan code mapped to the carrier’s code
  • A new coverage tier needs its tier value mapped to the carrier’s tier table
  • A new rate needs the rate or premium field updated so billing matches the carrier invoice
  • A dropped plan needs its enrollments ended in the feed so coverage closes on the carrier side
If any of these stays on last year’s mapping, the first January file sends the old setup. Employees who elected the new plan may show as ineligible, and terminated coverage may stay active on the bill. Each of those is an EDI benefits discrepancy your team will have to trace by hand.

A practical step before January 1

Start with a list. Write down every change approved at renewal, then pair each change with the carrier file field it affects. Send the carrier a sample file built on the new setup and review their response before January 1.
 
Ask each carrier how they report on a test file and who on your side receives that report. That report is where an EDI benefits discrepancy shows up early, before an employee finds it at a doctor’s office. Name the owner of that report before the test file goes out.

Premium accuracy depends on the same file

The same file drives premium billing. If a termination or a dropped plan never reaches the carrier, your organization keeps paying for coverage that should have ended, and that overpayment becomes harder to recover with each billing cycle.
 
Accurate enrollment data in the feed protects the employee at the doctor’s office and the premium line on the carrier invoice.

Questions to settle with your Dayforce partner

These questions name ownership of the work. Each one can be answered before the first January file:
  1. Who keeps the list of renewal changes and their matching file fields?
  2. Who requests updated carrier specifications after a plan or rate change and updates the feed?
  3. Who sends the sample file and reviews the carrier’s feedback report?
  4. What happens when a carrier rejects a file or returns errors?
  5. Who reconciles payroll deductions with carrier eligibility and the carrier invoice?
Clear answers to these five questions keep an EDI benefits discrepancy from reaching your employees.

Where Providence Technology Solutions helps

Providence Technology Solutions has been a Dayforce System Integrator Partner since 2016. Our Dayforce Benefits and Open Enrollment Management services include EDI Development, Troubleshooting, and Ongoing Support, along with Benefit Carrier Billing Reconciliation Automation. We work beside your benefits and HRIS team to map renewal changes, test carrier files and follow up on discrepancies.

Next step

If your team has renewal changes approved for plans that renew January 1, list them this month and pair each one with its carrier file field. Providence Technology Solutions can review that list with you and plan the carrier test before January 1.
Share This Post
Related Articles

The PTS Blog

Subscribe to our blog to stay up to date on the latest HCM, Data, Recruiting, Technology, and Software trends.

Top Posts From PTS
Explore

View our White Papers

View our Case Studies

Receive the latest updates

Subscribe To
Our Quarterly Newsletter

Get notified about new blog posts, case studies, white papers, and more!