LIMRA Data Exchange Standards Community Support Forum

We received a request to help determine the intended use for the available hire dates for BEM 1.3. Below is the summation of that request. 

Issues arise with one of the Ben Tech partners where we are receiving the <MostRecentHireDate> populated with the original date of hire for new hires when they are not a rehire. Example - the <MostRecentHireDate> and <OriginalHireDate> are both present in the data for a member/employee, and both have the same dates populated.

‌

We are expecting that in a new hire situation where there is not a rehire, or an adjusted service date because the member/employee changed from PT to FT employment (or something similar), that we would only receive the date of hire in the Original HIre Date tag, and the other tags for Most Recent Hire Date and Adjusted Service Date would be sent as NULL.

Curious how other carriers are handling this or expecting these fields to be provided. Also curious what other Ben Tech partners are doing in these scenarios.

We received a request to help determine the intended use for the available hire dates for BEM 1.3. Below is the summation of that request. 

Issues arise with one of the Ben Tech partners where we are receiving the <MostRecentHireDate> populated with the original date of hire for new hires when they are not a rehire. Example - the <MostRecentHireDate> and <OriginalHireDate> are both present in the data for a member/employee, and both have the same dates populated.

‌

We are expecting that in a new hire situation where there is not a rehire, or an adjusted service date because the member/employee changed from PT to FT employment (or something similar), that we would only receive the date of hire in the Original HIre Date tag, and the other tags for Most Recent Hire Date and Adjusted Service Date would be sent as NULL.

Curious how other carriers are handling this or expecting these fields to be provided. Also curious what other Ben Tech partners are doing in these scenarios.

We received a request to help determine the intended use for the available hire dates for BEM 1.3. Below is the summation of that request. 

Issues arise with one of the Ben Tech partners where we are receiving the <MostRecentHireDate> populated with the original date of hire for new hires when they are not a rehire. Example - the <MostRecentHireDate> and <OriginalHireDate> are both present in the data for a member/employee, and both have the same dates populated.

‌

We are expecting that in a new hire situation where there is not a rehire, or an adjusted service date because the member/employee changed from PT to FT employment (or something similar), that we would only receive the date of hire in the Original HIre Date tag, and the other tags for Most Recent Hire Date and Adjusted Service Date would be sent as NULL.

Curious how other carriers are handling this or expecting these fields to be provided. Also curious what other Ben Tech partners are doing in these scenarios.

We received a request to help determine the intended use for the available hire dates for BEM 1.3. Below is the summation of that request. 

Issues arise with one of the Ben Tech partners where we are receiving the <MostRecentHireDate> populated with the original date of hire for new hires when they are not a rehire. Example - the <MostRecentHireDate> and <OriginalHireDate> are both present in the data for a member/employee, and both have the same dates populated.

‌

We are expecting that in a new hire situation where there is not a rehire, or an adjusted service date because the member/employee changed from PT to FT employment (or something similar), that we would only receive the date of hire in the Original HIre Date tag, and the other tags for Most Recent Hire Date and Adjusted Service Date would be sent as NULL.

Curious how other carriers are handling this or expecting these fields to be provided. Also curious what other Ben Tech partners are doing in these scenarios.

We received a request to help determine the intended use for the available hire dates for BEM 1.3. Below is the summation of that request. 

Issues arise with one of the Ben Tech partners where we are receiving the <MostRecentHireDate> populated with the original date of hire for new hires when they are not a rehire. Example - the <MostRecentHireDate> and <OriginalHireDate> are both present in the data for a member/employee, and both have the same dates populated.

‌

We are expecting that in a new hire situation where there is not a rehire, or an adjusted service date because the member/employee changed from PT to FT employment (or something similar), that we would only receive the date of hire in the Original HIre Date tag, and the other tags for Most Recent Hire Date and Adjusted Service Date would be sent as NULL.

Curious how other carriers are handling this or expecting these fields to be provided. Also curious what other Ben Tech partners are doing in these scenarios.