Skip to content
KiweelyKiweelyKiweely

Benefits Life-Event Intake That Starts the Right Workday Process

Change Benefits for Life Event is the process that collects elections after a qualifying change. Intake should start that process for the event type you mapped. The Change Benefits web service replaces every election on the event type you send.

  • Checked against Workday on
  • Applies to Workday Extend
  • 4 min read
  • Published
  • By Kiweely
On this page

A marriage, a birth, or a loss of other coverage is not open enrollment. Workday models it as an enrollment event that starts Change Benefits for Life Event. An intake screen should identify which of your event types applies, create or continue that event as the worker, and let Workday calculate coverage dates. It should not post a full set of elections through the replace-style web service.

Kiweely Leaf (coming next) can host the intake questions. The business process in your tenant decides the plans, the proof, and the approval.

The process Workday runs

The benefits course manual says Change Benefits for Life Event is always a subprocess of Change Benefits, and it can also be triggered from a dependent event or from staffing and HR processes. Putting it on Hire, Onboarding, Change Job, or Termination lets Workday start a benefit event when eligibility changes. The subprocess drives the election pages, including what is elected and what is waived. A Benefits Partner or Administrator approval is a step you add on that definition if you require one.

Enrollment events are any event that changes eligibility or lets the employee change elections: open enrollment, benefit events, and passive events. They can happen any day of the year.

Create Enrollment Events maps an enrollment event type to the business process that should start it, including Change Benefits for Life Event and Change Benefit Jobs. Restricted by Reason limits the eligibility check to reasons you list. If you restrict Job Change to Demotion and Transfer, a promotion does not create that event. A blank reason list means the check runs whenever the process runs. Leave reasons come from Create Leave Type. Staffing and compensation reasons come from Maintain Event Categories and Reasons. Termination reasons come from Maintain Termination Categories and Maintain Local Termination Reasons.

That mapping is the “right” process. The intake screen’s first question has to resolve to one of those event types and reasons. A friendly label such as “We had a baby” is safe only when you have tied it to the event type your benefits team configured for that life change. Two benefit groups can use different event types. Read the worker’s group.

Dates and dependents come from setup

Enrollment event rules set waiting periods, coverage begin dates, and waive dates. For life change types, Workday can use the later of the event date or the submission date, including first of the next month or the next pay period. The submission date is the electronic signature date, or the completion date of Change Benefits for Life Event when there is no signature. The worker’s pay period comes from the pay group on the primary position.

The Change Benefits web service ignores coverage begin and deduction begin dates on the request and calculates them from these rules. It also replaces every election that matches the event type you send. Workday tells integrators to use a separate event type that contains only the plans they intend to update, and not to use an Admin Correction type that would remove unrelated plans such as an FSA or HSA. Waiving is done by sending no replacement election. A dependent required by the new coverage target must already exist in Workday.

An intake screen that “just updates medical” through that web service can waive retirement or spending-account elections the worker never saw. Start Change Benefits for Life Event for the event type that holds the plans this life change may touch. Let the worker finish the election pages Workday builds for that event. If a dependent is required, create the dependent in Workday before the coverage target changes.

The public REST API Explorer overview checked for the open enrollment guide does not list a Benefits REST service. This guide does not add one. Use the business process and the reports your worker can already run.

Intake, in order

  1. Ask the questions that identify the event type and reason you mapped. If nothing maps, stop and point the worker at benefits. Do not pick Admin Correction.
  2. Show the coverage begin rule in words the rule actually uses, or show the date Workday returns after the event exists. Do not promise a date the screen computed on its own.
  3. Continue the event as the worker, on Self-Service: Benefits.
  4. If the process definition includes an approval step, the screen waits on that step. It does not mark the event complete.

Leaf (coming next) publishes this intake when you say so. Annual open enrollment stays on its own decision screen, because that event type and its waive-date rules are different.

Questions

Can one button handle every life event?

Only if every button resolves to the event type and reason in Create Enrollment Events. A single generic event that includes all coverage types is the shape Workday warns against for the replace web service, and it is a poor default for intake too.

What about pre-hires?

Workday’s pre-hire security groups can be added to Change Benefits for Life Event when you want benefit enrollment before the start date. If they are not on the process, a pre-hire intake screen has nothing to start. Check that membership before you invite new hires to the page.

Sources checked

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.