ACA Data Extract - Not Populating 2B Safe Harbor Code (Doc ID 2223132.1)

Last updated on JANUARY 30, 2017

Applies to:

PeopleSoft Enterprise HCM Benefits Administration - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Affordable Care Act

ACTUAL BEHAVIOR
---------------
ACA Data Extract - Not Populating 2B Safe Harbor Code

The ACA Data Extract process is not populating the 2B safe harbor code for part-time employees that are part-time for part of the year but then transfer to full-time positions.

Example: Employee was in a non-assessment period from 1/1/2015 - 3/31/2015, is determined to be a part-time employee as of 4/1/2015, then transfers to a full-time benefit eligible position 8/18/2015 and enrolls in health insurance effective 10/1/2015.

The ACA Eligibility page is populated as follows:
1/1/2015 - 3/31/2015 - TBD with the non-assessment period flag checked;
4/1/2015 - 8/18/2015 - Ineligible,
8/18/2015 - 9/30/2015 - Always Eligible with the non-assessment period flag checked;
10/1/2015 - 12/31/2015 - Always Eligible with no non-assessment flag checked.

The ACA Data Extract process populates the Series 2 codes as follows:

Jan - Mar - 2D - correct
Apr - Jul - blank - incorrect should be 2B
Aug - blank - incorrect should be 2D
Sep - 2D - correct
Oct - Nov - 2C correct

EXPECTED BEHAVIOR
-----------------------
Expected the 2B safe harbor code

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms