---
title: "Full File or Changes-Only 834 After Workday Open Enrollment"
description: "Pick one ANSI X12 834 V2 transmission service after open enrollment, and set Effective Date to the new plan year before you send."
url: https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment
---

# Full File or Changes-Only 834 After Workday Open Enrollment

After open enrollment, Cloud Connect reports the benefit plan year of the Effective Date you launch with. A changes-only file sends new, changed, and terminated coverage in that year. A full file sends the snapshot. You enable one of those services, not both.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   7 min read
-   Published November 16
-   By Kiweely

After open enrollment, the carrier either wants a picture of everyone enrolled for the new plan year or a list of what changed. Workday’s ANSI X12 834 V2 template can build either file. It will not build both in one integration system at the same time. You enable one transmission service, and you set the launch dates to the new plan year. Everything else is a variation of that choice.

[Design Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/design-benefits-connectors.html) defines open enrollment as the annual selection of benefits for the upcoming year. Outside life events, it is the window when employees can change, add, or discontinue plans. Cloud Connect for Benefits carries the result of that window to the provider. Customers need a separate license for the Cloud Connect for Benefits catalog.

## The five transmission services

[Create Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/create-benefits-connectors.html) lists the services. Enable one. Workday displays a warning if you enable more than one.

| Service | What the file contains |
| --- | --- |
| CCB ANSI X12 834 V2 Changes Only | New coverage, changes, and terminations in the current benefit plan year. Requires the Transaction Log Service. |
| CCB ANSI X12 834 V2 Actives Only | Active enrollments in the current benefit plan year. No coverage terminations. |
| CCB ANSI X12 834 V2 Full File | Active enrollments in the current benefit plan year. The Ended Coverage History attribute sets how many days of terminations to include. |
| CCB ANSI X12 834 V2 Full File — Report All Ended Coverages Once | Active enrollments, plus every termination of coverage inside the Effective Date and Update Date window. |
| CCB ANSI X12 834 V2 Full File — Report Ended Coverage Once by Plan Type | Active enrollments, plus a termination when every plan of a plan type has ended, inside the Effective Date and Update Date window. |

The Transaction Log Service on this template is preconfigured. Workday says not to configure or modify it. Changes Only uses that log. A full-file service does not turn the same integration into a change file.

The Benefits Connector V2 template, which you use only when no industry-standard or proprietary template fits, has the same split in simpler XML: a full-file service reports the most recent enrollment data on or before the Effective Date, and a separate service choice produces the changes-only file.

## The open-enrollment launch dates

Cloud Connect reports eligibility and enrollment for the benefit plan year of the Effective Date. Plans take a new coverage start date at the start of each plan year. To report coverage that ends with the old year, Effective Date has to be on or before the last day of that plan year. [Enhance Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/enhance-benefits-connectors.html) gives the open-enrollment pattern directly:

| Parameter | Open-enrollment file |
| --- | --- |
| Effective Date | First day of the new plan year. The course uses January 1 as the usual example. |
| From Effective Date | That same first day. |
| Last Update | Current moment. |
| From Last Update | Current moment. |

The same chapter’s other two patterns are easy to confuse with this one:

-   A snapshot of current data uses the current Effective Date and the current moment as Last Update, and leaves From Effective Date and From Last Update empty.
-   A file of changes not already reported uses the current Effective Date, the current moment as Last Update, the effective date of the last completed event as From Effective Date, and that event’s entry time as From Last Update.

Sending the “new changes” pattern on the Monday after open enrollment drops everyone whose election was entered before the last successful run. Sending a snapshot with today’s date, while the new plan year has not started, reports the old plan year. The open-enrollment row exists so the file is about the year the carrier is loading.

## What has to be true in the tenant first

[Setup Considerations: Open Enrollment](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/open-enrollment/saf1564174663312.html) is the configuration the file will reflect:

-   New plans for the new year belong in a new plan-year definition or a rolling one, created with Create Benefit Plan Year Definitions. Changing the dates on an existing plan-year definition affects current enrollments.
-   Plans you are not offering stay out of the new plan-year definition. Do not remove them from an existing definition. The Do Not Use box on Edit Benefit Plan hides a plan from prompts.
-   The open-enrollment event type has to include every coverage type you are offering, including types that continue from last year.
-   A provider change is a mapping from the old plan to the new plan on the Benefit Plan Mapping tab of Edit Benefit Group. Workday says this mapping prevents a waive. That is enrollment mapping inside Benefits. It is not the 834 integration map. You still need the integration maps, and you still link the new plan to the integration. See [remap the carrier codes](https://kiweely.com/guides/remap-workday-834-codes-after-companion-guide-change).
-   Rates take an effective date of the rate change, often the first day of the new plan year.
-   Cross-plan rules need the same effective date when you add plans.
-   Switching from a nonderived coverage target to a derived one can drop someone to employee-only if they never select dependents. The admin guide says to add instructions so workers select dependents before plans.

Finalize the enrollment events before you treat the file as the year-start load. The merger and acquisition notes point at Finalize Open Benefit Events and the Open Enrollment Status Report for that cleanup. An unfinalized election is not a carrier-ready election.

## A changes-only file after a full load

Many carriers want one full file at year start and changes afterward. That is two launches with two date setups, and it may be two integration systems if you need both transmission services available on a schedule. One system cannot have Changes Only and Full File enabled together.

After the full file is accepted, the changes-only schedule should use the “not previously reported” parameters, with From Effective Date and From Last Update taken from the last completed event. Three worked examples in the course are worth keeping next to the schedule:

| Situation | Why it is or is not in the file |
| --- | --- |
| Termination entered and effective after the last run | Newly effective. The file includes it when the effective date falls in the launch range. |
| Termination entered today and effective before the last run | Newly entered and already effective. The file includes it when the update range covers the entry. |
| Termination entered before the last run and effective after it | The earlier run missed it. This run includes it when the effective date is inside the new effective range. |

Filtering the launch by organization can drop a terminated worker, because that person is no longer a member of the organization. A year-start termination file that is organization-filtered will look clean and be short.

## Where Roots fits

[Kiweely Roots](https://kiweely.com/roots) (coming next) sends 834 files checked against the carrier’s own rules. For a benefits file, a fix is proven on Sandbox with the rows that failed and then waits for approval. The Roots page describes a nightly run that sends the changes since the last run. That is a product choice you confirm against the carrier’s guide, using the Workday services above. Register interest on the Roots page. Roots does not choose the transmission service for you, and it does not remove the Cloud Connect license.

## Questions that decide the file

### The carrier said “send changes only” and also “include everyone who termed in December.” Which service is that?

That is not CCB ANSI X12 834 V2 Changes Only by itself, and it is not Actives Only. Actives Only omits terminations. The full-file variants that report ended coverage once are the services Workday documents for active enrollments plus terminations inside an effective-date and update-date window. Match the carrier’s sentence to one row of the table, then enable that service.

### Can the same scheduled integration emit a full file on January 1 and changes every night after?

Only if both launches use the one transmission service that system has enabled. A true switch of file shape is a switch of service, or a second integration system. Workday warns if both services are on.

### Does Effective Date of January 1 send last year’s terminations?

It reports the plan year of that Effective Date. Coverage end dates for the year that just finished need an Effective Date on or before the last day of that year. If the carrier wants both the old year’s endings and the new year’s elections, plan two launches with two effective dates and read both files.

## Sources checked

-   [Create Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/create-benefits-connectors.html)
-   [Enhance Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/enhance-benefits-connectors.html)
-   [Design Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/design-benefits-connectors.html)
-   [Setup Considerations: Open Enrollment](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/open-enrollment/saf1564174663312.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Remap Workday Benefit Codes When a Carrier Companion Guide Changes A mid-year companion-guide change is an integration-map change, not a new connector. Workday’s ANSI X12 834 V2 template already has the loops. You remap the codes, limit the test to the affected workers, and send only after that file matches the guide.](https://kiweely.com/guides/remap-workday-834-codes-after-companion-guide-change)
-   [### Life-Event 834 Feeds for Birth, Divorce, and COBRA A nightly changes-only 834 follows enrollment events and the launch dates you set. Birth and divorce are configured life events with dependent rules. COBRA is a separate change-only feed with its own dates. Mixing them in one file is how the job breaks.](https://kiweely.com/guides/life-event-834-feeds-for-birth-divorce-and-cobra)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Match Workday People to Okta on the ID That Survives the Job Change](https://kiweely.com/guides/match-workday-workers-to-okta-on-the-right-id)
-   [Why a Delivered Workday File Was Still Rejected](https://kiweely.com/guides/workday-file-delivered-carrier-rejected-rows)
-   [Scoping AI Workday Access for Contingent Workers and Alumni](https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni)
-   [Correlating Workday Audit Events with AI Assistant Tool Calls](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)
-   [Workday Cost Centers and Workers to NetSuite After a Reorg](https://kiweely.com/guides/workday-cost-centers-workers-to-netsuite)
-   [Workday Headcount to Snowflake When Data Cloud Is Not Enough](https://kiweely.com/guides/workday-headcount-to-snowflake-beyond-data-cloud)
-   [Performance Check-In and Goals Screens Managers Will Open](https://kiweely.com/guides/performance-check-in-goals-screens-managers-open)
-   [Building an Open Enrollment Decision Screen on Live Workday Elections](https://kiweely.com/guides/open-enrollment-decision-screen-live-workday-elections)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [The Hallucinated Field Trap: Why Generic AI Can’t Write Reliable Workday Code](https://kiweely.com/blog/hallucinated-field-trap-workday-ai)
-   [Claude Code with a Workday MCP server vs. Claude in kiweely](https://kiweely.com/blog/claude-code-workday-mcp-vs-kiweely)
-   [Consistent, template-based deliverables for your Workday project](https://kiweely.com/blog/consistent-template-based-workday-deliverables)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
