S-2206 - Employment Contract Changes

Non periodic event. This event layout captures changes in employments for employees after the completion of the initial loading process. These changes include, but not limited to, compensation and schedule payment, length of contracted work, work, position or function, journey work and so on in the Job Data component, and other related pages such as the Additional Information BRA and Unions pages.

If the last Employment Contract Changes event was sent incorrectly, a rectification event or an exclusion event for it will be submitted to update or cancel the information.

General Rules

Refer to the General Rules section of the S-2205 - Personal Data Changes event.

Employment Contract Changes Rules

• If a rectification for an existing event or a new event is generated, all events with the same event code and greater effective date than the rectified or generated event need to be rectified as well. For example:

  (Update address) On September 10, an individual was hired and the job data information was sent to eSocial. Event used: S-2200 - Employees Initial Loading and Hiring. Effective date: September 10.

  On October 1, salary information was added for the employee and it was sent to eSocial. Event used: S-2206 - Employee Contract Changes. Effective date or change date: October 1.

  On October 10, the job code for the employee is updated for the same employee, and the information is sent to eSocial. Effective date: September 10.

  In this job data update example, the system sends rectifications to S-2200 and S-2206 (change date October 1) events.

• If a data row is added, updated, or deleted, no event is generated, if:

  • Its effective date is not the most current one of its month and year period, and

  • Its effective date is earlier than or equal to (< or =) the eSocial on PeopleSoft date, and

  • Its last hire date is earlier than (<) the eSocial on PeopleSoft date.

• If a data row is added, updated, or deleted, rectification events may be sent to S-2200, S-2300, S-2206, S-2306 as needed, if:

  • Its effective date is the most current one of its month and year period, and

  • Its effective date is earlier than (< ) the eSocial on PeopleSoft date.

  For example, on August 31 2016, an employee’s hire and salary information was loaded to eSocial. Event used: S-2200 - Employees Initial Load and Hiring. Effective date: July 01, 2015.

  On September 1 2016, more salary information was added for the employee and the information was sent to eSocial. Event used: S-2206 - Employee Contract Changes. Effective date or change date: October 1 2016.

  On September 5 2016, salary information is updated for the employee, and the information is sent to eSocial. Effective date: July 01 2015.

  In this salary update example, the system sends rectifications to S-2200 and S-2206 (change date October 1) events.

• This example shows an effective-dated row deletion scenario. Suppose that these rows exist in the PeopleSoft system:

  From the Job Data component:

  • KR00011 emplID, Hire action and Add reason, effective date: June 01, 2014

  • KR00011 emplID, Hire action and Add reason, effective date: July 01, 2014

  • KR00011 emplID, Pay action and Merit reason, effective date: July 01, 2015, event used: S-2200

  • KR00011 emplID, DTA action and DTA reason, effective date: September 01, 2016, event used: S-2206

  • KR00011 emplID, Pay action and Merit reason, effective date: September 01, 2016, event used: S-2206 (rectification), change date: September 01, 2016

  • KR00011 emplID, DTA action and DTA reason, effective date: November 01, 2016, event used: S-2206, change date: November 01, 2016

  • KR00011 emplID, DTA action and DTA reason, effective date: January 01, 2017, event used: S-2206, change date: January 01, 2017

  From the Payee Parameters page:

  • KR00011 emplID, begin date: June 01, 2014

  • KR00011 emplID, begin date: June 01, 2015, event used: S-2200

  • KR00011 emplID, begin date: September 01, 2016, event used: S-2206

  • KR00011 emplID, begin date: October 01, 2016, event used: S-2206, change date: October 1, 2016 (deleted)

  • KR00011 emplID, begin date: December 01, 2016, event used: S-2206, change date: December 1, 2016

  If a row is deleted, and:

  • Its effective date is equal to or greater than (= or >) the eSocial on PeopleSoft date (for example, September 1, 2016), and

  • Its effective date is greater than (>) the last hire date, and

  • The data row is the only one in its month and year period.

    The system generates an S-3000 - Event Exclusion event for the event with <dtAlteracao> that is equal to effective date of the deleted row. In this example, the exclusion event is generated for the S-2206 event with the effective date of October 1, 2016. In addition, rectifications are sent for events with <dtAlteracao> that are later than the excluded event. In this example, these events include the two S-2206 events with November 01, 2016 and January 01, 2017 effective dates from the Job Data component, and the S-2206 event with the December 1, 2016 effective date from the Payee Parameter page.

• This example shows an effective-dated row update scenario. Suppose that these rows exist in the PeopleSoft system:

  From the Job Data component:

  • KR00011 emplID, Hire action and Add reason, effective date: September 01, 2016, event used: S-2200

  • KR00011 emplID, DTA action and DTA reason, effective date: September 15, 2016, event used: S-2206, change date: September 15, 2016

  • KR00011 emplID, DTA action and DTA reason, effective date: changed from October 01, 2016 to November 1, 2016, event used: S-2206, change date: October 01, 2016

  • KR00011 emplID, Pay action and Merit reason, effective date: December 01, 2016, event used: S-2206, change date: December 01, 2016

  From the Payee Parameters page:

  • KR00011 emplID, begin date: September 01, 2016, event used: S-2206

  • KR00011 emplID, begin date: November 01, 2016, event used: S-2206

  • KR00011 emplID, begin date: January 01, 2017, event used: S-2206

  If the effective date of a row is updated, and:

  • Its (old) effective date is equal to or greater than (= or >) the eSocial on PeopleSoft date (for example, September 1, 2016), and

  • Its (old) effective date is greater than (>) the last hire date, and

  • The data row is the only one in its month and year period.

    The system generates an S-3000 - Event Exclusion event for the event with <dtAlteracao> that is equal to old effective date of the updated row. In this example, the exclusion event is generated for the S-2206 event with the effective date of October 1, 2016. A new event (S-2206) is generated for the new effective-dated row of November 1, 2016. In addition, rectifications are sent for events with <dtAlteracao> that are later than the exclusion event. In this example, these events include the two S-2206 events with November 01, 2016 and December 01, 2016 effective dates from the Job Data component, and the two S-2206 events with November 1, 2016 and January 01, 2017 effective dates from the Payee Parameter page.

• If multiple contract data actions are performed on the same day, and these changes trigger the same event, only one instance of this event is generated. For example, if you update a work shift code, change an employee’s risk level on the Payee Parameters page, and update a job code on the same day (October 1, 2016), and all of these changes need to be submitted to eSocial through the S-2206 event, the PeopleSoft system generates one S-2206 event with <dtAlteracao> set as October 1, 2016.

Employment Contract Changes Rules for Retroactive Payments

Sometimes, employees receive retroactive payments due to changes in contracts with their unions. These changes can be the result of collective agreements, collective disputes, collective conventions or legislative updates. The employer is responsible for reporting information of these salary increases to the Government, which then uses the data to calculate retroactive payroll using the S-1200 event accordingly.

Here is a list of rules that apply to the Employment Contract Changes event when reporting union-specific retroactive payments for employees (these rules are not applicable to non-employees):

• For S-2206 events to be generated for employees who receive retroactive payments due to union contract changes, they must be associated with unions on the PeopleSoft Human Resources Administer Workforce: Job Labor Page (the Union Code field).

  For unions with contractual changes, be sure to fill out the Union Contract Revision section of General Parameters Page. The system uses information provided here to determine the begin and end dates of the retroactive payroll, among other things.

  In addition, you also need to select the Collective Agreement Indicator option for a Data Change action and reason combination on the Other Action/Reason Page. The system uses this action and reason code for union-specific retroactive payroll processing. Oracle recommends that the same Data Change action for Sefip 650 be used for this purpose.

• When an employee job data row is added with the action and reason combination that is used for collective agreement, a positive compensation change percent on the PeopleSoft Human Resources Administer Workforce: Compensation Page, and an effective date that falls within the begin and end dates of the contract revision specified for the associated union of the employee, the system generates an S-2206 event with that effective date (also referred to as the effect date in this section).

  Note:

  If the action and reason of the added row is not used for collective agreement, an S-2206 event is generated without the effect date.

  If the employee was hired before the begin date of the contract revision, the effective date of the job data row should be set as the same as the begin date.

  If the employee was hired after the begin date of the contract revision, the effective date of the job data row should be set as the same as the hire date, and the effective sequence to 1.

  If other effective-dated job data rows exist after the begin date, the effective sequence of these rows must be adjusted in order for the retroactive payroll calculation to be done properly.

  The S-2206 event captures information such as the effect date ({dtEf} tag), alteration date ({dtAlteracao} tag, the system date of the action and reason setup that is specified for collective agreement), contractual change description from the union revision setup ({dscAlt} tag), and new salary amount ({vrSalFx} tag).

• Note that retroactive salary payments are reported in S-2206 events with corresponding effect dates ({dtEf} tag). For other updates of employees (for example, job code changes, shift changes and so on) that also use the S-2206 event layout to report to the Government but are unrelated to union-specific retroactive salary change, the system captures the updated value from the job data row that has the maximum effective date for the month when the change took place, and reports it without an effect date ({dtEf} tag).

• If the system is supposed to generate an S-2206 event for a newly added employee job data row but the required union information is missing, mapping errors are returned so that the administrator can take appropriate actions.

• For any salary update in job data rows that took place during the specified union revision period, no S-2206 events are generated if the compensation change percent value is equal to or less than zero. This scenario applies when the S-2206 event that was generated for the newly added salary change row is pending, and subsequent effective-dated rows are updated with the new salary amount as well but the change percent remains zero.

• The Government can accept more than one S-2206 event with the same alteration date, as long as the effect dates are different.