FUNCTIONAL DESIGN DOCUMENT

Benefit Integration- Hartford

Revision & Sign-off Sheet Change Record:

Date Author Version Change reference

7/4/2023 Poonam Tribhuvan 0.1 Draft

Approvers:

Copy No. Name Position

Revision:

Sr. No Date Issue Recorded by Comments

Dependencies:

Document Name Version Date

Note to Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for
document control purposes. If you receive a hard copy of this document, please write your name on the front cover, for document
control purposes.
Table of Contents

Contents

Table of Contents...................................................................................................................................................................................................... 3

Introduction............................................................................................................................................................................................................... 4

Purpose...................................................................................................................................................................................................................... 4

User story references................................................................................................................................................................................................. 4

Requirements............................................................................................................................................................................................................. 5

Design specification and building blocks.................................................................................................................................................................... 5

New Additional fields................................................................................................................................................................................................. 7

Customizations........................................................................................................................................................................................................... 9

Business Logic.......................................................................................................................................................................................................... 21

Source documents Included..................................................................................................................................................................................... 24

Dependencies........................................................................................................................................................................................................... 24

Assumptions............................................................................................................................................................................................................. 24
Introduction

Pinkerton needs to integrate the benefit plan enrollment of US employees with the Hartford benefit vendor

Purpose
The purpose of this document is to describe the solution design for PINKERTON to integrate the D365 F&O application with the
Hartford benefit vendor

The document highlights the enhancement done to design the integration between the two applications

User story references

User Story Fit/

User Story Module Type Solution Additional Work
Id Gap
HCM- Outbound Human Gap Integratio An outbound Interface
HR1059 Integration of D365 resource n integration needs to be
F&O with Hartford s developed to transmit
benefit vendor the benefit enrollment
data from D365 F&O to
Hartford benefit vendor
Requirements

As per the requirement, employees will self-enroll them in the various benefit plans provided by the Aetna benefit vendor.

Design specification and building blocks

We will design a new outbound interface between the Hartford benefit vendor and the D365 F&O application to transmit the benefit
enrollment information from D365 F&O application to Aetna

Sr. Hartford Field Field Type

No. D365 Field Field details
1 Customer Number Customer String
number Custom
2 Transaction Code If Dependent Enum
details exist for
the selected
plan, then D,
else E to be sent Standard
3 Employee SSN Identification Dropdown
number Standard
4 Employee ID Personnel String
number Standard
5 Member SSN/Member ID Identification String
number Standard
6 Relationship Code Relationship Enum
type Standard
7 Last Name Last name Standard String
8 First Name First name Standard String
9 Middle Initial Middle Name Standard String
10 Date of Birth Date of Birth Standard Date
11 Marital Status Marital Status Standard Enum
12 Gender Gender Standard Enum
13 Member Mailing Address 1 Street Standard String
14 Member Mailing Address 2 Street Standard String
15 Member Mailing Address City City Standard Dropdown
16 Member Mailing Address State State Standard Dropdown
17 Member Mailing Address Zip Code ZIP/ Postal code Standard Dropdown
18 Member Mailing Address Country Code Country code Custom Dropdown
19 Employee Home Phone Contact String
number/address Standard
20 Employee Cell Phone Contact String
number/address Standard
21 Employee Personal E-mail Address Contact String
number/address Standard
22 Employee Work E-mail Address Contact String
number/address Standard
23 Employee Work State Code State Standard Dropdown
24 Employee Work Address Country Code Country code Custom String
25 Employee Status Code Status Standard Enum
26 Employee Status Effective Date Employment Date
start date if
status is A;
Termination
date if
employment
status is T; Date
of death if
employment
status is D Standard
27 Rehire Date Employment Date
start date Standard
 28 Original Hire Date Employment Date
start date Standard
29 Employment Type Employment Enum
Type Standard
30 Exempt/Non-Exempt Job Type Standard Enum
31 Scheduled Hours Per Week Calendar Standard String
32 Benefit Salary Amount Pay rate Standard String
33 Salary Basis Pay rate Real
conversion Standard
34 Salary Effective Date Effective date Standard Date
35 Job Title Title Standard Dropdown
36 Coverage Effective Date Coverage start Date
date Standard
37 Coverage Termination Date Coverage end Date
date Standard

New Additional fields

1. Short Term Disability Plan (NON-STATUTORY) :

a. STD Requested Coverage Plan Option: Indicates the level of coverage requested Percentage up to two decimals if needed
(60 or 66.67 when EOI applies)

2. Long Term Disability Plan:

a. LTD Requested Coverage Plan Option: Indicates the level of coverage requested as a percentage. Percentage up to two
decimals if needed

3. Basic Life Plan

 a. Basic Life Multiple of Salary Face Amount: Basic Life Multiple of Salary Current ( 1 to 7 times), (9V99) (for example 1.65
would come over at 165 or 0.65 would be 065) 9V99 - Decimal is implied. Value(0 or 150). Please pass 150 (1.5x Salary)

b. Basic Life Multiple of Salary Requested Amount: Basic Life Multiple of Salary Current ( 1 to 7 times), (9V99) (for example
1.65 would come over at 165 or 0.65 would be 065) 9V99 - Decimal is implied. 150 applicable for EOI Scenarios

c. Basic Life Requested Amount: Basic Life requested Amount. Whole number - No Decimals. Applicable for EOI scenarios for
Class 1 only when Face Amount exceeds GI ($500k).

4. Supplemental Life Plan for Employee

a. Supplemental Life Requested Amount: Supplemental Life Requested Amount Whole number - No Decimals. Applicable for
EOI scenarios. Please pass the total requested amount here as a whole number.

5. Spouse Supplemental Life Plan

a. Spouse Supplemental Life Requested Amount: SPL Requested Amount Whole number - No Decimals. Applicable for EOI
scenarios. Please pass the total requested amount here as a whole number.
Customizations

1. Basic Employee Life

a) Coverage amount for Class-1: 1.5 * salary

b) Coverage amount for Class-2: Flat - 10,000$

2. Supplemental Employee Life

a) 10000 to $500,000 (Class-1); increments of 20K

b) If contribution amount exceeds between 250K and 500K , then notify to HR via report/alert/notification.

c) For existing employees, when the contributions are changed, HR is to be notified. A report will be desirable to track these
changes to act accordingly

3. Supplemental Spouse Life (Class 1)

a) The Supplemental Spouse life plan benefit rate is computed based on the spouse age. Solution needs to be defined to
calculate the rates based on the spouse age. And it needs to be visible on the ESS (Benefit self service) to the employees to
know the coverage amount and the rate associated with it. This plan will only be allowed to select if the pre-requisite benefit
plan Supplemental Employee Life plan is selected

b) Eligibility rule: labor union: FCA; Non-FCA-> Microsoft/Pinkerton

 c) 5000 to $100,000; increments of 5000

d) Pre-requisite to Supplemental employee life. Not to exceed 50% of employee’s coverage amount

4. Supplemental Spouse Life (Class 2)

a) 2500 to $12,500; increments of 2500

b) Pre-requisite to Supplemental employee life. Not to exceed 50% of employee’s coverage amount

c) For Late entrants, EOI will kick in for any amount

Supplemental Dependent Spouse Age

Life
Per $1000 Spouse Step Employee paid
UNDER 25 $0.054
25 - 29 $0.054
30 - 34 $0.072
35 - 39 $0.081
40 - 44 $0.126
45 - 49 $0.198
50 - 54 $0.315
55 - 59 $0.522
60 - 64 $0.810
65 - 69 $1.404
70 - 74 $2.511
75+ $2.511
d) For Child (0-26), 2500 increment; 5000, 7500, 10000 (Same for both class-1 and class-2)

e) Pre-requisite to Supplemental employee life. Charges are same irrespective of the number of kids. For 2 kids also rate will be
same
Per $1,000 Child Unit $0.13

f) Create a master form to maintain the Supplemental age rate

Navigation: Human resources > Benefits management> Setup > Dependent Rates
g) Calculation logic:

Employee A (non-Manager) – 35 year old employee, $60,000 Annual Salary, 40 year old spouse, no children

Supplemental Spouse Life (Class 1)

Benefit: employee selected the non-medical max of $50,000

 Premium: 40-44 year old SP rate is $0.126 per $1,000 = $0.126 x 50 = $6.30 per month

h) The computed amount must be visible on the following forms:

5. Supplemental Employee AD&D (Class 1)

Benefit: employee selected the max benefit of $300,000

Premium: $0.040 per $1,000 = $0.040 x 300 = $12.00 per month

Supplemental Employee Life

Per $1000 Employee Stepped
UNDER 25 $0.05
25 - 29 $0.05
30 - 34 $0.06
35 - 39 $0.07
40 - 44 $0.11
45 - 49 $0.17
50 - 54 $0.26
55 - 59 $0.44
60 - 64 $0.68
65 - 69 $1.17
70 - 74 $2.09
75+ $2.09

The Supplemental Employee AD&D (Class 1) will be configured to compute the rates based on the employee’s age. So, no
customization is required for this plan
 5.1 Standalone Supplemental Dependent AD&D

The coverage amount of the needs to be auto populated

i. If spouse, then coverage amount is 50% of employee’s coverage amount

ii. If spouse + child, then coverage amount is 40% of employee’s coverage amount for spouse and 10% for
child

iii. If it is child only then 15% for child

5.2 Calculation logic:

Benefit: Spouse is 50% of employee’s amount = $150,000 (Employee’s coverage amount: $3000,000)

Premium: $0.060 per $1,000 = $0.060 x 150 = $9 per month

6) Voluntary Short Term Disability (Class 1)

The Class 1 population for this benefit plan needs to be determined based on the earnings (fixed compensation) of the employee

Class 1= annual earnings are $90,000 or more

Calculation logic:

Benefit: 66.67% of weekly earnings, max of $2,564; $60,000 / 52 weeks = $1,153.85 x 66.67% = $769.26 per week
Premium: 35-59 year old rate is $27.95 per month (see age grid, these are purely age based and do not need to be calculated based on
salary)

Voluntary Short Term Employee paid on a

Disability (<$90k) bi-weekly basis
Per Employee Per Month Employee Age
<25 $47.38
25-29 $37.26
30-34 $36.05
35-39 $27.95
40-44 $30.38
45-49 $34.02
50-54 $40.91
55-59 $48.60
60-64 $56.70
65-69 $62.37
70+ $62.37
7) Voluntary Short Term Disability (Class 2)

The Class 2 population for this benefit plan needs to be determined based on the earnings (fixed compensation) of the employee

Class 2= annual earnings are less than $90,000

Calculation logic:

Benefit: 60% of weekly earnings, max of $1,308; $60,000 / 52 weeks = $1,153.85 x 60% = $692.31 per week

Premium: 35-59 year old rate is $60.15 per month (see age grid, these are purely age based and do not need to be calculated
based on salary)

Voluntary Short Term Disability Employee paid on a bi-

(<$90k) weekly basis
Per Employee Per Month Employee Age
<25 $101.71
25-29 $96.24
30-34 $45.94
35-39 $60.15
40-44 $65.62
45-49 $78.75
50-54 $98.43
55-59 $121.40
60-64 $147.65
 65-69 $162.97
70+ $162.97

8) Voluntary Long Term Disability (Class 1)

The Class 1 population is determined based on the Title (Manager)-> Job eligibility rule

Benefit: 66.67% of monthly earnings, max of $13,000; min of 10$; $60,000 / 12 months = $5,000 x 66.67% = $3,333 per month

Per $100 Of Covered Salary

Long Term Disability - Class 1 For managers monthly salary

ER Paid of employee max: 233988
Per $100 Of Covered Salary $0.28

9) Voluntary Long Term Disability (Class 2)

The Class 2 population is determined based on the Title (Non manager)-> Job eligibility rule

Benefit: 60% of monthly earnings, max of $5,000; $60,000 / 12 months = $5,000 x 60% = $3,000 per month

Premium: 35-39 year old rate per $100 of monthly covered salary is $0.281; $5,000 / 100 = 50 x $0.281 = $14.05 per month

For non-managers monthly salary of employee (Any

Voluntary LTD - Class 2 EE Paid
annual salary going above 100K, rate calculation stops)
 Per $100 Of Covered Salary Emp age
<25 $0.13
25-29 $0.17
30-34 $0.22
35-39 $0.28
40-44 $0.45
45-49 $0.66
50-54 $1.00
55+ $1.33

10) Calculation logic understanding with example

For simplicity, I’ve assumed that the employee is in the regular “Pinkerton” group but if there is a particular employee example
that you’d like me to show instead, just let me know.

Employee A (non-Manager) – 35 year old employee, $60,000 Annual Salary, 40 year old spouse, no children

Basic Life (Class 1)

Benefit: 1.5 x $60,000 salary = $90,000

Premium: $0.217 per $1,000 = $0.217 x 90 = $19.53 per month

Basic AD&D (Class 1)

Benefit: Equal to Life amount = $90,000

Premium: $0.020 per $1,000 = $0.020 x 90 = $1.80 per month

Benefit: employee selected the non-medical max of $240,000

Premium: 35-39 year old EE rate is $0.068 per $1,000 = $0.068 x 240 = $16.32 per month

Supplemental Spouse Life (Class 1)

Benefit: employee selected the non-medical max of $50,000

Premium: 40-44 year old SP rate is $0.126 per $1,000 = $0.126 x 50 = $6.30 per month

Supplemental Employee AD&D (Class 1)

Benefit: employee selected the max benefit of $300,000

Premium: $0.040 per $1,000 = $0.040 x 300 = $12.00 per month

Supplemental Dependent AD&D (Class 1)

Benefit: Spouse is 50% of employee’s amount = $150,000

Premium: $0.060 per $1,000 = $0.060 x 150 = $9 per month

Voluntary Short Term Disability (Class 2)

Benefit: 60% of weekly earnings, max of $1,308; $60,000 / 52 weeks = $1,153.85 x 60% = $692.31 per week

Premium: 35-59 year old rate is $27.95 per month (see age grid, these are purely age based and do not need to be calculated
based on salary)

Voluntary Long Term Disability (Class 2)

Benefit: 60% of monthly earnings, max of $5,000; $60,000 / 12 months = $5,000 x 60% = $3,000 per month
 Premium: 35-39 year old rate per $100 of monthly covered salary is $0.281; $5,000 / 100 = 50 x $0.281 = $14.05 per month

Business Logic
1. Transaction Code:
E = Employee
D=Dependent

Based on the enrollment for a particular plan, if the plan selected is ‘EE only’ then the ‘E’ flag needs to be sent.
If the plan selected is ‘E+ (1,2,Family)’ then ‘D’ flag needs to be sent

1. For the below scenario in the Benefit plans since Coverage option, “EE only” is selected and in the Benefit, plan details there
are no Dependent data so ‘E’ flag needs to be sent in the file only if the Confirmed is checked
2. For the below scenario in the Benefit plans since Coverage option, “EE+1” is selected and in the Benefit, plan details there are
Dependent data so ‘D’ flag needs to be sent in the file only if the Confirmed is checked
3. The home address, contact information (phone/email) which is set to primary will be sent. Assumption is Home address and
personal email, and phone will always be set to primary for an employee

4. The work email address will be sent based on the logic of “@pinkerton” string in the email address

5. Any other address apart from primary will be sent as Work address

6. Any other contact number apart from primary will be sent as Work phone number

7. Employee Status Effective Date: Employment start date if status is A; Termination date if employment status is T; Date of
death if employment status is D. We do not maintain any effective date for Retired and Leave of absence status. If these
needs to be captured, then additional custom field is required to be added as below:
Source documents Included

Dependencies

NA

Assumptions