How Benefits Relationships Impacts Benefits Processing
Benefits relationships control how a worker's benefits are grouped for processing. A worker might have different sets of benefits attached to different benefits relationships.
Settings That Affect Benefits Relationship Assignments
Configure two default benefits relationship settings for each combination of country or legal entity, and benefits usage:
Setting |
Description |
---|---|
Default Benefits Relationship |
The default benefits relationship assigned automatically to all new hires and workers with one assignment. |
Enable Multiple Assignment Processing |
If disabled, then all workers have the default benefits relationship. If enabled, you must configure whether and how to assign benefits relationships to additional assignments by default. |
Use the Configure Default Benefits Relationships task in the Setup and Maintenance work area.
In the Benefits Service Center page, benefits professionals can change:
-
The benefits relationships associated with individual workers
-
The work assignments associated with the worker's benefits relationships
How Benefits Relationship Assignments Affect Benefits Processing
Benefits relationships affect these benefits entities:
-
Potential life events
-
Life event
-
Eligibility records
-
Electable choices
-
Enrollment options
-
Dependent coverage
-
Beneficiary designations
-
Primary care physician designations
-
Deductions
A worker might have assignments that are associated with different benefits relationships.
The following six examples list:
-
Different ways that worker assignments might be structured within an organization
-
How the benefits relationships would be associated
-
The impact on life events, electable choices or enrollment options, and benefits eligibility
Example 1: Single Legal Entity, Work Relationship, Employment Terms, Assignment and Benefits Relationship
Configuration: Only one assignment and one benefits relationship exist.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy UK |
1 |
Architect |
Architect |
A (default) |
Processing: Life events, electable choices or enrollment options, and benefits eligibility are evaluated based on the assignment in this benefits relationship.
Example 2: Work Relationships in Two Different Legal Entities
Configuration: Two sets of work relationships, employment terms and assignments exist, one for each legal entity. The person has two sets of benefits, one for each legal entity. Each assignment is associated with a different benefits relationship.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy UK |
1 |
Architect |
Architect |
A (default for the legal entity) |
Galaxy US |
2 |
Consultant |
Consultant |
B (default for the legal entity) |
Processing: This table shows the basis for benefits evaluation and processing for each data type:
Data Type |
Benefits Evaluation Processing Basis |
---|---|
Life events |
Primary assignment from each legal entity. |
Electable choices or enrollment options |
One set of data for each legal entity. |
Eligibility |
Use eligibility to provide benefits from the appropriate legal entity. Eligibility criteria are defined at the legal entity level or globally. |
Example 3: Multiple Assignments in a Single Legal Entity
Configuration: One benefits relationship is associated with different employment terms and assignments.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy US |
1 |
Architect |
Architect |
A (default) |
Galaxy US |
1 |
Consultant |
Consultant |
A |
Processing: This table shows the basis for benefits evaluation and processing for each data type:
Data Type |
Benefits Evaluation Processing Basis |
---|---|
Life events |
Primary assignment |
Electable choices or enrollment options |
One set of data for each life event |
Eligibility |
Attributes defined at global person level are used for both life events. Assignment-level attributes are used in the respective life events. |
Example 4: Multiple Assignments in a Single Legal Entity - One Benefits Relationship for Each Assignment
Configuration: Separate benefits relationships are associated with each assignment.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy US |
1 |
Architect |
Architect |
A (default) |
Galaxy US |
1 |
Consultant |
Consultant |
B |
Processing: This table shows the basis for benefits evaluation and processing for each data type:
Data Type |
Benefits Evaluation Processing Basis |
---|---|
Life events |
Separate life events created for Architect and Consultant assignments |
Electable choices or enrollment options |
One set of data for each life event |
Eligibility |
Attributes defined at global person level are used for both life events. Assignment-level attributes are used in the respective life events. |
Example 5: Multiple Assignments in a Single Legal Entity - One Benefits Relationship Has Two Assignments, Another Has Remaining Assignments
Configuration: Two assignments are associated with one benefits relationship, and another assignment with a second benefits relationship.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy US |
1 |
Architect |
Architect |
A (default) |
Galaxy US |
1 |
Product Manager |
Product Manager |
A |
Galaxy US |
1 |
Consultant |
Consultant |
B |
Processing: This table shows the basis for benefits evaluation and processing for each data type:
Data Type |
Benefits Evaluation Processing Basis |
---|---|
Life events |
Separate life events are created for the assignments in benefits relationships A and B |
Electable choices or enrollment options |
One set of data for each life event |
Eligibility |
Attributes defined at the global person level and assignment level are used for life events |
Example 6: Complex Multiple Benefits Relationships
Configuration: Many assignments are associated with one or more benefits relationships.
Legal Entity |
Work Relationship |
Employment Terms |
Assignment |
Benefits Relationship |
---|---|---|---|---|
Galaxy US |
1 |
Product Manager |
Orlando |
A |
Galaxy US |
1 |
Product Manager |
Dallas |
A |
Galaxy US |
1 |
Product Manager |
Atlanta |
B |
Galaxy US |
1 |
Consultant |
San Francisco |
C |
Galaxy US |
1 |
Consultant |
Los Angeles |
D |
Processing: This table shows the basis for benefits evaluation and processing for each data type:
Data Type |
Benefits Evaluation Processing Basis |
---|---|
Life events |
Separate life events created for the assignments in each benefits relationship |
Electable choices or enrollment options |
One set of data for each life event |
Eligibility |
Attributes defined at global person level are used for all life events. Assignment-level attributes are used in the respective life events. |