---
title: "Life-Event 834 Feeds for Birth, Divorce, and COBRA — Kiweely"
description: "Births, divorces, and COBRA each create a different Workday enrollment event. Here is what a nightly 834 picks up, and what it skips."
url: https://kiweely.com/guides/life-event-834-feeds-for-birth-divorce-and-cobra
---

# 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.

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

A nightly 834 job breaks on life events when it assumes every family change is “a new row of medical coverage.” Workday models three different things, and Cloud Connect will only send what the event, the dates, and the transmission service actually contain.

[Design Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/design-benefits-connectors.html) defines a life event as an occurrence that affects benefit plans, and an enrollment event as the change to those plans. The course’s own example is an adoption that adds a child as a dependent on a health plan. Open enrollment is the other window. Outside life events and open enrollment, employees are not in a position to change, add, or drop plans. Changing an enrollment event or its rules changes who the connector includes.

## Birth and divorce are dependent rules, not new connectors

[Create Enrollment Event Rules](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/enrollment-events-and-rules/dan1370797380474.html) shows how narrow a life event is supposed to be:

-   Additional Dependents Allowed lets the worker add or remove dependents on the coverage types you name. The admin guide’s example is a newly married employee adding a spouse. The same page’s birth example is the other direction: employees may add the new child and may be blocked from changing the medical plan or from adding anyone else.
-   May Remove Dependents lets the worker remove dependents and does not allow increases. The example is divorce, where you can require the employee to remove the spouse.
-   Continue with Current Dependents blocks adding or removing dependents. That is the wrong rule on a birth event, and it is why a newborn never appears in the 834 even though the life event “completed.”

[Event Setup](https://doc.workday.com/workday-education/en-us/course-manuals/benefits-for-administrators/event-setup.html) adds the labels workers see. For a Birth/Adoption of Child event you can show the event date as the child’s birth date or adoption date. Worker Selectable controls whether the employee can start Change Benefits, or whether a Benefits Partner has to start it. If the event is not worker-selectable and nobody starts it, there is no enrollment for the file to carry.

The benefits-for-administrators material also says you can put Change Benefits for Life Event on staffing processes so eligibility changes start a benefit event. The merger guide’s business-process table lists Change Benefits for Life Event as the process that initiates enrollments for life events, and it names births, divorce, and promotion as examples. See [Setup Considerations: Benefits for Mergers and Acquisitions](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/set-up-benefits/ali1600449423833.html).

For the 834 itself, the new child or the removed spouse shows up only if all of the following are true:

1.  The enrollment event finished, including whatever approval the tenant requires. The course notes that enrolling a new dependent may need an approval that a trivial plan change does not.
2.  The launch’s effective-date range includes the coverage start or end. [Enhance Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/enhance-benefits-connectors.html) separates newly effective data from newly entered data. A birth recorded today with a coverage start next Monday waits for a run whose Effective Date reaches that Monday, unless the parameters include it as a future change inside the range.
3.  The transmission service is allowed to report the change. CCB ANSI X12 834 V2 Changes Only reports new coverage, changes, and terminations in the current benefit plan year and uses the preconfigured transaction log. Actives Only will not report a termination of the ex-spouse’s coverage. The full-file variants that “report ended coverage once” exist for that case. Enable only one of these services. See [full file or changes-only](https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment).
4.  Relationship and coverage codes match the companion guide. Loop2000\_INS02 is the individual relationship code. Loop2300\_HD05 is the coverage level. A birth that moves a tier from employee-only to employee-plus-child is an HD05 change. A guide that added a new child code is a map change, described in [remap carrier codes](https://kiweely.com/guides/remap-workday-834-codes-after-companion-guide-change).
5.  An organization filter did not drop the person. The enhance chapter warns that organization filtering can exclude terminated workers, because they are no longer members. A divorce tied to a termination has the same hole.

CCB - Debug Service can launch for one worker and that worker’s dependents. Use it when a single birth or divorce is the row the carrier rejected.

## COBRA is a different file

Workday is not a COBRA administrator. [Steps: Set Up COBRA Automation](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/cobra/dan1370797444502.html) says Workday tracks who is eligible and can feed a third-party administrator. Loss of eligibility can come from a passive event (a child turning 26), a staffing event (termination or fewer hours), or a life event (divorce). Records can be created automatically or with Grant COBRA. If one benefit event can produce different lengths of COBRA, Workday says to create a separate benefit event per outcome, such as an 18-month termination and a 36-month termination.

Automatic detection needs Change Benefit Elections on the underlying process. COBRA records created that way are what an established third-party COBRA integration picks up. You can remove the review step, including on Change Benefits for Life Events, if an administrator should not touch the record first. Grant COBRA Eligibility, including the Grant Cobra Eligibility web service for more than one person, is the manual path. Add a record per benefit plan. See [Grant COBRA Eligibility](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/cobra/dan1370797445092.html).

[Create Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/create-benefits-connectors.html) is just as specific about the file:

-   COBRA connectors are not all one template. Some are provider-specific. Others are WEX COBRApoint, which you can use for any provider that accepts that layout. Confirm the layout with the provider. The CCB Catalog on Community is where provider-specific templates are listed. This guide does not repeat Community-only steps.
-   COBRA integrations generate change-only files. WBN - Launch Change File - Event Based means a change file, not a full file.
-   Initial Rights files (also called General Notice, New Hire, or DOL files) carry demographics so the administrator already has active workers and dependents.
-   Qualifying Events files say that someone recently qualified, and they carry the benefit data.
-   Three dates are required, and they are not interchangeable. COBRA Eligible Date is when the worker or dependent becomes eligible, often the day after the loss of coverage. Qualifying Event Date is the date of the event that caused the loss. COBRA Coverage End Date is when COBRA coverage ends, and Workday says this is not the date the original coverage ends.
-   The maps that matter on COBRA templates are coverage level, plus Plan Bundle Name when you group plans. Run the COBRA Eligibility Reasons report to find the qualifying events you still need to map. Send First Day Of COBRA chooses whether day one of COBRA follows the event date or the start date.

A nightly medical 834 that “also does COBRA” will miss qualifying events or will send COBRA people as ordinary terminations. Give COBRA its own integration, its own change-only service, and its own dates.

## A practical split for the nightly job

| Event | Feed that should carry it | Date that must fall in the launch |
| --- | --- | --- |
| Birth or adoption, child added, tier changed | The medical 834, on the service the carrier uses for changes | Coverage effective date, or the entry date if you are catching a retroactive add |
| Divorce, spouse removed, coverage continued for the employee | The medical 834, on a service that reports changes or ended coverage | Coverage end for the spouse |
| Divorce, termination, or a child aging out, where the person may continue under COBRA | The COBRA qualifying-event file | Qualifying Event Date, COBRA Eligible Date, and COBRA Coverage End Date, each in the field the template asks for |
| New hire who might someday qualify | The COBRA Initial Rights file, if the administrator asked for one | The demographic extract’s own schedule, not the qualifying-event schedule |

Passive events belong in this table. A child who loses eligibility at a set age is a passive event in the event-setup course, and it is one of the COBRA triggers in the admin guide. If Route to Benefits Partner is set, the worker never submits the change. The partner does, or the passive event does. The 834 waits on that completion.

## Where Roots fits

[Kiweely Roots](https://kiweely.com/roots) (coming next) checks 834 files and carrier APIs against the carrier’s rules. A benefits correction is proven on Sandbox with the rows that failed, then waits for approval. A birth that the carrier rejected because the coverage tier was missing is that pattern: fix the map or the event, rerun those rows on Sandbox, and leave Production until someone approves. Register interest on the Roots page. Roots does not collapse the medical 834 and the COBRA file into one feed, and it does not decide the COBRA month-count. That split stays in the enrollment events above.

## Questions that come up the morning after

### The life event is complete and the child is still absent from the file.

Check Allowed Dependent Changes on that event. Continue with Current Dependents hides the add. Then check the coverage start against Effective Date and From Effective Date. Then check whether the launch was organization-filtered or limited by CCB - Debug Service.

### We termed the employee and the carrier never received COBRA.

Termination creates COBRA eligibility only after the COBRA setup is in place: the benefit event, Change Benefit Elections where you want automation, and a COBRA integration that sends Qualifying Events. The medical 834’s termination segment is not that file. Compare COBRA Eligible Date with the day coverage actually ended. Workday’s definition is often the day after the loss, and the COBRA end date is not the original coverage end date.

### Can one Changes Only service carry the divorce and the COBRA election?

It can carry the benefit-plan change the divorce event saved, if that change is in the current plan year and inside the launch dates. The COBRA administrator’s qualifying-event file is a separate connector with its own dates and, often, a COBRApoint or provider layout. Send both, and test each with the debug or launch limits before the nightly schedule owns them.

## Sources checked

-   [Design Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/design-benefits-connectors.html)
-   [Create Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/create-benefits-connectors.html)
-   [Create Enrollment Event Rules](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/enrollment-events-and-rules/dan1370797380474.html)
-   [Steps: Set Up COBRA Automation](https://doc.workday.com/admin-guide/en-us/human-capital-management/benefits/cobra/dan1370797444502.html)
-   [Event Setup](https://doc.workday.com/workday-education/en-us/course-manuals/benefits-for-administrators/event-setup.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)
-   [### 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.](https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment)

### More guides on Reports and calculated fields

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

-   [Expense Report Create-and-Submit Screens Outside Workday Menus](https://kiweely.com/guides/expense-report-create-submit-outside-workday-menus)
-   [Workday calculated field not showing in a report: why it is missing from the field picker](https://kiweely.com/guides/workday-calculated-field-not-showing-in-report)
-   [How to debug a Workday calculated field that returns the wrong value](https://kiweely.com/guides/workday-calculated-field-returns-wrong-value)
-   [Preventing Accidental Indirect-Report Visibility in Workday Intersection Security Groups](https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility)
-   [How to Sum or Count Multi-Instance Rows in Workday Using Aggregate Related Instances (ARI)](https://kiweely.com/guides/workday-aggregate-related-instances-ari-sum-count)
-   [Blank vs. Empty in Workday Report Filters and Condition Rules: Why Your Filter Misses Rows](https://kiweely.com/guides/workday-blank-vs-empty-report-filter-prompts)
-   [How to Fix CellLimitExceededException: Exceeded Cell Limit in Workday Custom Reports and EIBs](https://kiweely.com/guides/workday-report-cell-limit-exceeded-exception)
-   [How to Build Multi-Condition Evaluate Expression Calculated Fields in Workday Without Hitting Nesting Limits](https://kiweely.com/guides/workday-evaluate-expression-nested-calculated-fields)

### From the blog on Reports and calculated fields

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

-   [Kiweely builds a prompted Workday report, then answers from the tenant](https://kiweely.com/blog/workday-report-built-and-tenant-answer)
-   [How to Review an AI-Built Calculated Field Chain Like a Senior HCM Lead](https://kiweely.com/blog/review-ai-built-calculated-field-like-senior-hcm)
-   [Approving Workday Expense Reports and Purchase Requisitions in Teams and Slack](https://kiweely.com/blog/workday-expense-report-and-requisition-approvals-in-teams-slack)

## 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.
