S-2300 - Workers who have no employment relationship - Begin
Non periodic event. This event layout provides employment information for workers who have no employment relationships with companies. Examples include temporary workers, union leaders, non-employee directors, members, and so on. It is used in the initial data loading of employees without employment relationships, and for new hires without employment relationships after of the eSocial implementation.
General Rules
Here are several rules that apply to the Workers who have no employment relationship - Begin event:
-
It applies to employees without employment relationships (employees are associated with employee classifications that are specified on the Labor Regime Page, without a specified work type. It is triggered when the Hire action is selected in the first row of job data for an employee without employment relationship.
-
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 date.
Information of employees who are hired after the eSocial implementation date needs to be submitted using either the S-2200 or S-2300 event.
-
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 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 needs to be generated for the S-2300 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 event is generated for the corresponding event, followed by a new initial loading event for the employee.
Related Topics