Creating Replacement Files when ACA Files Are Rejected By The IRS Due to AIRSH100 Schema Errors.

(Doc ID 2241329.1)

Last updated on APRIL 19, 2017

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.1 to 9.2 [Release 9]
PeopleSoft Enterprise HCM Benefits Administration - Version 9.1 to 9.2 [Release 9.0 to 9]
Information in this document applies to any platform.

Goal

 The IRS has Rejected our ACA Files due to Schema errors e.g. invalid address, invalid offer of coverage code or invalid safe harbor code.  When we add a new row to change the employee's data, it requires we use Correction which then removes these employees from the Original File.

What steps should be used to ensure these changes are in the Original file when a Replacement File is created?

Solution

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