S-1010 - Wage Types Table

Basic table event. This event layout is used to load all elements (wage type codes) initially and track all changes related to earnings and deductions, their social and taxation bases, nature of the elements, and impacts to specific features such as 13th Salary, DSR, vacation and terminations.

Note:

The S-1000 - Employer Data event must be transmitted prior to sending this event.

Companies are associated with wage types tables on the Application Fundamentals: (BRA) Company Details BRA Page. The initial data loading process takes, for each eSocial-enabled company, the earnings and deduction elements available in the wage types table that the company associates with, and submit them to eSocial using the S-1010 event. Wage types table information with a begin date that is equal to or greater than the eSocial on PeopleSoft date of a company is submitted to eSocial for that company. If a company has more than one effective-dated row and each is associated with a different wage types table, an S-1010 event will be generated for each wage types table that meets the begin date requirement.

After the initial loading process is completed, when a change occurs to a wage types table, S-1010 events are submitted to eSocial for all companies that are associated with that wage types table. When a change is made to exemption proceeding, an S-1010 event is sent to the eSocial system for the associated company only.

Wage types table changes must be sent to eSocial no later than the seventh day of the month following the update occurrence, or prior to the transmission of any event that requires this information for validation, whichever comes first.

Refer to the S-1000 - Employer Data section for general rules that apply to basic table events.

Scenarios

This example describes a few scenarios for submitting wage types table information and exemption proceeding details to the eSocial system:

• If an element row is added to a wage types table, for example:

  1 wage types table ID; 2501 wage type code, PREMIO element, INSS: 92, IRRF: 11, FGTS: 11, begin date: September 1, 2016

  Because this element is associated with a code that requires exemption proceeding details to be entered, the proceeding information is specified for a particular company using that element, for example:

  1 wage types table ID, KRC company, 3265659789 proceeding number, CP (INSS) proceeding ID, PREMIO element, begin date: September 1, 2016

  One wage types table event gets generated for the element row, and the row information is populated in the inclusion section (the inclusao group tag) of the generated XML file.

• If a company (KRI) is newly linked to the wage types table mentioned above on the Company Details BRA page, and it needs to specify exemption proceeding details for an element (PREMIO) that already has proceeding code identified, for example:

  1 wage types table ID; 2501 wage type code, PREMIO element, INSS: 92, IRRF: 11, FGTS: 11, begin date: November 1, 2016

  1 wage types table ID, KRI company, 2822587222 proceeding number, CP (INSS) proceeding ID, PREMIO element, begin date: November 1, 2016

  One wage types table event gets generated for the element row, and the row information is populated in the inclusion section of the generated XML file. Note that a new begin date is selected for the element to avoid error when generating the event.

• If data is updated in an element row that has been submitted to eSocial, for example, the DSR option is selected on an element row, one wage types table event gets generated for each company that is linked to that element and begin date. The updated information is populated in the change section (the alteracao group tag) of the XML file.

• If the begin date of an existing element row is updated along with other changes that require exemption proceeding details to be entered, for example:

  1 wage types table ID; 1205 wage type code, ADIC NOTURNO element, INSS: changed from 11 to 92, IRRF: changed from 11 to 92, FGTS: 11, begin date: changed from September 1, 2016 to January 1, 2017

  1 wage types table ID, KRC company, 2566225322 proceeding number, CP (INSS) proceeding ID, ADIC NOTURNO element, begin date: January 1, 2017

  1 wage types table ID, KRC company, 1452252229 proceeding number, IRRF proceeding ID, ADIC NOTURNO element, begin date: January 1, 2017

  One wage types table event gets generated for the element row, and the row information is populated in the inclusion section of the generated XML file if the new begin date is the only date of its month and year period. If proceeding details are missing, error message is generated in the event monitor.

• If the begin date of an existing element row is updated along with a change that requires exemption proceeding details to be entered, for example:

  1 wage types table ID; 1205 wage type code, ADIC NOTURNO element, INSS: changed from 11 to 92, IRRF: 11, FGTS: 11, begin date: changed from September 1, 2016 to January 1, 2017

  Multiple companies use the same wage type code and element, but only one company has specified exemption proceeding details, for example:

  1 wage types table ID, KRC company, 2566225322 proceeding number, CP (INSS) proceeding ID, ADIC NOTURNO element, begin date: January 1, 2017

  One wage types table event gets generated for the element row, and the row information is populated in the inclusion section of the generated XML file for the KRC company. Error messages are generated in the event monitor for other companies that didn't specify proceeding details for the updated element.

• If the begin date of an existing element row is updated along with other changes that no longer require additional proceeding details to be entered:

  1 wage types table ID; 1205 wage type code, ADIC NOTURNO element, INSS: changed from 92 to 11, IRRF: changed from 92 to 11, FGTS: 11, begin date: changed from January 1, 2017 to February 1, 2017

  One wage types table event gets generated for the element row, and the row information is populated in the inclusion section of the generated XML file if the new begin date is the only date of its month and year period. No action is necessary for the element's proceeding details with the old begin date (January 1, 2017).

• If proceeding details for a few elements are deleted, one wage types table event gets generated for each element for the associated company. In each event, the deleted row information is populated in the exclusion section (the exclusao group tag) of the XML file.