---
title: "Fix Workday CCB 834 Missing Dependent Errors — Kiweely"
description: "Troubleshoot Workday Cloud Connect for Benefits 834 feeds when dependents are missing: Debug Service, ISU security, maps, field overrides, and launch dates."
url: https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors
---

# How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds

Missing dependents on a Workday Cloud Connect for Benefits ANSI X12 834 file usually mean absent elections, Integration System User security gaps, or drops from maps, field overrides, or launch parameters. Prove the layer with View Current Benefit Elections and the CCB Debug Service.

-   **Checked** against Workday on November 13
-   Applies to **Workday Benefits Integrations**
-   6 min read
-   Published November 13
-   By Kiweely

Missing dependents on a Workday **Cloud Connect for Benefits (CCB)** ANSI X12 834 feed are almost never a random EDI glitch. Either the dependent is not present in Workday elections as of the launch dates, the Integration System User cannot see the data, or the connector drops the member through maps, field overrides, file-transmission choice, or Debug filters. Prove the layer with **View Current Benefit Elections**, then a Debug-scoped CCB launch, before editing companion-guide maps.

Cloud Connect for Benefits supports healthcare enrollment file types and carrier integrations for benefit enrollment management. For 834 output, Workday’s current end-to-end path is the **ANSI X12 834 V2** template, not older named vendor 834 templates that Workday does not enhance and plans to deprecate.

## Which Failure Layer Matches the Missing Dependent Symptom?

Run the three CCB test cycles in order: connectivity, file format, then data and events. Format problems and security gaps look identical in a carrier reject email if you skip the first two cycles.

| Symptom in 834 Output | Likely Layer | What to Check First |
| --- | --- | --- |
| Subscriber missing entirely | Security, Benefit Plans attribute, Debug exclude, or no election | ISU and ISSG domains; **View Current Benefit Elections**; Debug Service member list |
| Subscriber present, spouse or child loop missing | Dependent election, coverage tier map, or dependent security | Election coverage level vs. HD05 map; dependent effective dating; ISU access to dependent data |
| Dependent present with blank birth date or wrong relationship | Field override or map | Loop 2100 / DMG and INS maps; calculated field hierarchy used by overrides |
| Prior plan still active at carrier after waiver | File transmission service | Actives Only vs. Full File services that report ended coverages |
| OE plans missing for the new plan year | Benefit Plans attribute and launch dates | Loop 2000 Employee or Dependent Benefit Plans attribute; Effective Date = plan year start |

Security gaps look like “Workday has no data”

Workday recommends an Integration System Security Group per product area (Benefits) and an Integration System User per integration system. Launch the CCB, then compare excluded rows to **View Current Benefit Elections**. If the report shows the dependent and the file does not, treat security and connector configuration before asking Benefits to re-enter elections.

## How Do You Isolate One Worker With the CCB Debug Service?

Most CCB templates include **CCB - Debug Service**, which adds launch parameters to include or exclude specific workers and dependents and to mask support files. Use it so you are not hunting one child loop inside a 10,000-subscriber file.

Works

```
Debug launch for a missing-dependent case:
1. Clone the production CCB integration system before changing templates or maps.
2. On the clone, confirm CCB - Debug Service is enabled.
3. Launch with Only Include Members = the employee (and known dependents if prompted).
4. Keep Enable Test Mode on while validating with the carrier.
5. Compare output Loop 2000 member rows to View Current Benefit Elections for the same as-of date.
```

If the Debug file still omits the dependent while elections show coverage, inspect maps and overrides next. If Debug output matches elections but the population file does not, look for Additional Filters (organization), sequence or delivery differences, or an include/exclude list left behind from an earlier test.

## Which ANSI X12 834 V2 Services and Attributes Drop Dependents?

On the **ANSI X12 834 V2** template, enable exactly one file transmission service at a time. Enabling more than one produces a warning and unpredictable output expectations.

| Integration Service | Behavior That Affects Dependents and Terminations |
| --- | --- |
| CCB ANSI X12 834 V2 Changes Only | New, changes, and terminations within the current benefit plan year; depends on Transaction Log Service |
| CCB ANSI X12 834 V2 Actives Only | Active enrollments only; does not include terminations of coverage |
| CCB ANSI X12 834 V2 Full File | Active enrollments; Ended Coverage History controls how many days of terminations appear |
| Full File - Report All Ended Coverages Once | Actives plus terminations within Effective Date and Update Date |
| Full File - Report Ended Coverage Once by Plan Type | Terminations when all plans for a plan type end |

Also verify the core services that shape member loops: **CCB ANSI X12 834 V2 Transformation**, **Loop 1000 Employer**, **Loop 2000 Employee**, Transaction Log Service (preconfigured; do not casually rewrite it), Additional Filters, Sequence Generator, Delivery Service, and Document Retention.

New plan-year medical, dental, or vision plans must be present on the Benefit Plans integration attributes that feed employee and dependent loops, and coverage tiers must be mapped (commonly HD03 / HD05 style maps on Loop 2300). Unmapped tiers produce carrier rejects or wrong family composition even when Workday elections are correct. Keep map and [field override](https://kiweely.com/guides/workday-cloud-connect-field-overrides-maps) changes small: overrides accept one field value, so conditional dependent logic belongs in Evaluate Expression calculated fields, then one override.

## How Do Launch Parameters Hide Dependents at Open Enrollment?

CCB change detection includes newly effective and newly entered enrollment activity. Launch parameters define those windows:

-   **Effective Date** / **From Effective Date** for newly effective enrollments
-   **Last Update** / **From Last Update Date** for newly entered enrollments
-   Payroll start and end dates when the template collects payroll data

CCBs report eligibility and enrollment activity based on the benefit plan year of the **Effective Date** launch parameter. To report end-of-year coverage end dates, Effective Date must fall on or before the last day of that plan year. For a benefits provider Open Enrollment file, set Effective Date and From Effective Date to the first day of the new plan year (often January 1) with current moment update stamps, matching Workday’s documented OE launch pattern.

Organization filters can also drop terminations: for connectors that use payroll data, filtering by organization may exclude terminated workers who are no longer organization members, even when the integration should report their termination. Validate terminated subscribers separately from active family builds.

## Step-by-Step: Fix a Missing Dependent Before the Carrier Cutover

1.  **Confirm functional data.** Open **View Current Benefit Elections** (and Benefit Coverage History if dates matter) for the employee as of the 834 Effective Date. Confirm the dependent, relationship, coverage level, and plan. If the dependent is missing here, fix elections or [dependent effective dating](https://kiweely.com/guides/workday-dependent-effective-dating-future-dependents) first.
2.  **Confirm ISU visibility.** Review the Benefits ISSG and the integration’s ISU. Rerun Debug include for that worker after any security change.
3.  **Confirm template and transmission service.** Use ANSI X12 834 V2. Pick the Full File or Changes Only service the carrier companion guide requires; do not leave Actives Only enabled for a restatement that must send terminations.
4.  **Confirm plans, maps, and overrides.** Add new plan-year plans to Benefit Plans attributes. Remap HD coverage codes. Inspect calculated fields with **View Calculation Hierarchy** when overrides build dependent demographics.
5.  **Confirm launch parameters.** Align Effective Date with the plan year. For change files, set From Effective Date and From Last Update from the last completed integration event so newly entered dependents are not skipped.
6.  **Retest in three cycles.** Connectivity to the endpoint, format validation on the Debug file, then event scenarios (OE, newborn, overage dependent, termination) before removing Debug filters.

Clone the integration system before changing templates. Changing an end-to-end connector template forces you to reconfigure services, attributes, maps, and overrides that do not exactly match the new template.

When Open Enrollment corrections collide with later life events, remember that fixing OE alone may not update a subsequent future-dated benefit event. Check enrollment history and re-run CCB after both events are consistent, especially if Coordination of Events recreated OE mid-window.

For large OE restatements, [Kiweely Vine](https://kiweely.com/vine) can compare finalized benefit elections to Debug 834 member loops for named workers and flag subscribers whose dependent rows exist in Workday but not in the connector output before you widen the launch beyond test mode.

## Frequently asked questions

### Why does View Current Benefit Elections show a spouse but the 834 file omits that dependent?

The election data exists, so focus on Integration System User security, Benefit Plans attributes on the CCB, Loop 2000 or Loop 2300 maps, field overrides, and Debug Service include or exclude lists. Functional reports prove whether Workday holds the dependent; the integration event proves whether the connector can see and map it.

### Which CCB file transmission service should I use for an annual Open Enrollment restatement?

Carriers that need terminations and waivers usually need a Full File service configured to report ended coverages, not Actives Only. Actives Only reports active enrollments and does not include terminations of coverage.

### How do I test one worker with missing dependents without parsing the whole population file?

Enable the CCB Debug Service and launch with Only Include Members for that worker and dependents. Validate connectivity, file format, and data and events in separate cycles before reopening population delivery.

### Can wrong Effective Date launch parameters drop dependents at plan-year changeover?

Yes. CCB eligibility and enrollment activity follow the benefit plan year of the Effective Date launch parameter. For Open Enrollment restatements, set Effective Date and From Effective Date to the first day of the new plan year so new coverage and ended prior-year coverage land in the correct file.

## Sources checked

-   [Reference: Cloud Connect for Benefits Capability](https://doc.workday.com/admin-guide/en-us/workday-feature-descriptions/workday-human-capital-management/future--cloud-connect-for-benefits.html)
-   [Create Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/create-benefits-connectors.html)
-   [Test Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/test-benefits-connectors.html)
-   [Enhance Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/enhance-benefits-connectors.html)

## Related guides

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

-   [### Why is a worker’s Workday Open Enrollment On Hold or missing after a backdated change? A backdated life event or staffing change triggers Coordination of Events, which puts the later Open Enrollment event On Hold until the earlier event completes, then rescinds and recreates it. Finish or cancel the earlier event in Benefit Election History.](https://kiweely.com/guides/workday-open-enrollment-stuck-disappeared-elections)
-   [### How Future-Dated Dependents and ‘View Dependent As Of’ Work in Workday Benefits Workday tracks dependent relationships and eligibility attributes as effective-dated records, isolating upcoming additions in the Future Dependents grid and evaluating historical or upcoming states via View Dependent As Of. Correct wrong initiation dates with Revise Dependent Event.](https://kiweely.com/guides/workday-dependent-effective-dating-future-dependents)
-   [### Workday Cloud Connect for Benefits and Payroll: field overrides, integration maps and unmapped value errors Packaged connectors can’t be edited, but four tasks customize them. Use Integration Maps to translate Workday values into vendor codes and Field Overrides for fields the template lacks. Workday warns calculated-field overrides can hurt performance; past 30 overrides, consider another integration.](https://kiweely.com/guides/workday-cloud-connect-field-overrides-maps)
-   [### Workday EIB vs Core Connector vs Cloud Connect vs Studio: which to use Use an end-to-end Cloud Connect connector if one exists for the vendor, a Core Connector for a delivered template with change detection, EIB for simple guided loads, and Studio for multiple web service calls or complex error handling.](https://kiweely.com/guides/workday-studio-vs-eib-vs-cloud-connect)
-   [### How do I set up an integration system user and API client in Workday so an external app can authenticate? Create the ISU, put it in an Integration System Security Group, grant domain permissions and activate them, register the client for integrations, then generate its refresh token and pick the ISU as the Workday account.](https://kiweely.com/guides/workday-integration-system-user-api-client)

### More guides on Integrations and APIs

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

-   [Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing](https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts)
-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)
-   [How to change job profile and compensation in one Change Job SOAP request](https://kiweely.com/guides/workday-change-job-soap-profile-compensation)
-   [Why the Workday REST /workers endpoint leaves out terminated workers](https://kiweely.com/guides/workday-rest-api-workers-terminated)
-   [How to get the instance ID back after a POST to the Workday REST API](https://kiweely.com/guides/workday-rest-api-instance-id-after-post)
-   [How the Workday REST API batch protocol works](https://kiweely.com/guides/workday-rest-api-batch-protocol)
-   [Workday Studio XPath 2.0 and XSLT 2.0/3.0 Performance and Memory Streaming](https://kiweely.com/guides/workday-studio-xslt-xpath-streaming-memory)

### From the blog on Integrations and APIs

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

-   [Personal AI Plus Shared ISU Credentials: The Compound Workday Failure Mode](https://kiweely.com/blog/personal-ai-plus-shared-isu-compound-failure)
-   [BYO API Keys on a Workday Consultant Laptop: Who Is the Controller?](https://kiweely.com/blog/byo-api-key-workday-consultant-laptop)
-   [Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)

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