S-3000 - Event Exclusion

Non periodic event. This event layout cancels events that were sent to the government by mistake by companies.

Hire Exclusion

Sometimes, companies need to generate exclusions for hire events to have the hiring information removed from the government when:

  • The corresponding hires fail through and no longer exist.

    When that happens, administrators can run the process on the eSocial Hire Exclusion Page to generate driver information of exclusions for these hire events. Then, prepare data and create XML files for the exclusion events on the eSocial Non Periodic Event Page to be submitted to the government.

  • An employee updates:

    Note:

    The employee information discussed in these scenarios is considered key information to the government. The system reports changes of key information through the exclusion of existing events and generation of new events, rather than the rectification of existing events.

    • The eSocial register number on the Additional Information BRA page.

      In this scenario, the system first generates an exclusion event for the employee’s existing hire event, and then generates a new hire event with the new eSocial register number.

    • The company on the Work Location page.

      In this scenario, the system first generates an exclusion event for the employee’s existing hire event, and then generates a new hire event with the new company.

    • The employee class from an employee one to a non-employee one (or vice versa) on the Job Information page.

      In this scenario, the system first generates an exclusion event for the employee’s existing hire event (for example, S-2200), and then generates a new hire event that matches the new employee class (for example, S-2300).

      No exclusion or hire events will be generated, if the old and new employee classes belong to the same employee type.

Note:

If additional events (S-2205, S-2206 or S-2306) have been submitted successfully to the government following the submission of the existing hiring event, you must first submit exclusion events for all of these events before sending an exclusion event for the hiring event itself.

PeopleSoft HCM provides the ability to delete employment record numbers (ERNs) when these numbers are created in error or are not no longer in use. For eSocial to work properly, you need to configure the system to exclude a number of eSocial tables from this process on the PeopleSoft Human Resources Administer Workforce: ERN Delete Exception Tables Page. These tables are:

  • GPBR_DRVABS_XRF (Exception Type: Exclude, Person ID Field Name: EMPLID; Empl Record Field Name: EMPL_RCD)

  • GPBR_DRVCAT_XRF (Exception Type: Exclude, Person ID Field Name: EMPLID; Empl Record Field Name: EMPL_RCD)

  • GPBR_DRVCMP_XRF (Exception Type: Exclude, Person ID Field Name: EMPLID)

  • GPBR_DRVEMP_XRF (Exception Type: Exclude, Person ID Field Name: EMPLID; Empl Record Field Name: EMPL_RCD)

Related Topics