S-2200 - Employees Initial Loading and Hiring

Non periodic event. Use this event layout to:

• Report lists of employees for companies.

  This event needs to be invoked when a company is being activated for eSocial reporting, which can be the time right before eSocial becomes effective, or when the company is newly created or acquired after the implementation of eSocial (on the eSocial on PeopleSoft date).

  After the initial loading of employees is completed, employee information needs to be reported whenever changes are made.

• Report the hiring of employees in companies.

  It is triggered when the Hire action is selected in the first row of job data for an employee, and the employee belongs to an employee classification that is specified on the Labor Regime page.

  Hiring must be reported no later than the day before the employee starts to work either through the S-2190 - Pre-Hiring or S-2200 - Employees Initial Loading and Hiring event. If an S-2190 event is sent, the rest of the hiring data needs to be submitted by the seventh day of the month following the occurrence of the hiring, using the S-2200 event.

  After the submission of hiring events, changes to the employee’s personal data need to be sent to eSocial through S-2205 - Personal Data Changes events, and job data through S-2206 - Employment Contract Changes events.

General Rules

Here are several rules for the Employees Initial Loading and Hiring event:

• It applies to employees with employment relationships (employees are associated with employee classifications that are specified on the Labor Regime Page, with a selected work type.

• It reports the employee data row with the most current effective date that is either earlier than or equal to (< or =) the eSocial on PeopleSoft date.

• For an employee to be included in the report, the employee’s hire date needs to be equal to or later than (= or >) the Company creation date, as well as equal to or earlier than (= or <) the eSocial implementation (eSocial on PeopleSoft) date.

  Information of individuals who are hired after the eSocial implementation date needs to be submitted using either this event (for employees) or the S-2300 - Workers who have no employment relationship - Begin event (for non-employees).

• The eSocial Reg. Number field value on the PeopleSoft Human Resources Administer Workforce: (BRA) Additional Information BRA Page is required for employees with employment relationships.

  Employees are not specific to or keyed by company, and can work for more than one company at a time. Therefore, any personal data change (personal data table are keyed by EMPLID) of an employee needs to be submitted to eSocial for all companies with which the employee has employment relationships.

  Job data is keyed by EMPLID and EMPL_RCD. With that, changes in job data need to be submitted to eSocial for the company associated with the employment record. If the employee has multiple employment relationships, the same number of S-2200 events need to be generated. In those events, the personal data section remains the same, the job data section, however, contains data that is distinct for each relationship.

• If an employee is in temporary absence, the <dtIniAfast> and <codMotAfast> tags of the S-2200 event are populated with the initial absence date and absence reason.

• If an employee was terminated before the implementation of eSocial, the <dtDeslig> tag of the event is populated with the termination date.

• If the only component or table that was updated for an employee is not effective-dated, and the maximum effective date for all components and records used to generate the event is earlier than or equal to (< or =) the eSocial implementation date, a rectification event is generated for the S-2200 event.

• An update in the CPF national ID, PIS, or birth date of an employee is considered a critical change. When it occurs, a rectification is generated for the S-2200 or S-2300 event as appropriate.

• If the update is made in the company or employee class in the employee’s job data, an S-3000 - Event Exclusion is generated for the corresponding event, followed by a new initial loading event for the employee.

• If an employee has personal data and job data rows that are effective-dated after the eSocial on PeopleSoft date, while the S-2200 event takes care of the current effective-dated row (the most current effective date that is earlier than or equal to eSocial on PeopleSoft date), future rows will be reported using the S-2205 - Personal Data Changes and S-2206 - Employee Contract Changes events respectively.