S-1000 - Employer Data

Basic table event. This event reports employer’s registration information, rates, and other data necessary for the completion and validation of other eSocial events, including calculation contributions.

Information provided in this event change over time, and when that happens, separate events will be sent to report specific changes.

General Rules for Basic Table Events

Here are several general rules that apply to all basic table events, after the initial data loading for them are completed and eSocial becomes effective:

Note:

Basic table events consist of a wide variety of company information; job code is used in the examples provided in this section.

  • In order for events to be generated and submitted properly for companies implementing eSocial:

    • Companies must be enabled and configured using the Company Parameters component (event rules, setID setup, and XML option setup).

    • The effective dates (or begin dates) of basic table changes (including insertion, change, or deletion of data) must either be equal to or greater than the eSocial on PeopleSoft date of companies on the Company Parameters Page. For example:

      Effective date: used by S-1000 and S-1005 events

      Begin date: used by the S-1010 event

      Both dates: used by the S-1020 event

  • The eSocial system (of the Brazilian government) accepts only one report from any Basic Table event code at any given period (month and year) for any eSocial-enabled company, whereas in PeopleSoft, effective dates for data rows are captured in the form of day, month, and year. When there are more than one effective-dated row for an event code during the same month and year period, the latest one is submitted to eSocial. Each time a new effective-dated row is added in PeopleSoft, the system checks to see if an event has already been sent for the same month and year period. If yes, a change event, in which the new row information is entered in the alteracao group tag of the XML file, is generated to send the update to the eSocial system. If no, an inclusion event, in which the new row information is entered in the inclusao group tag, is generated instead.

  • In this example, suppose that three effective-dated job code rows are entered in PeopleSoft:

    1. KRSI1 setID, 120000 job code, Administrator, effective date: September 01, 2016, active effective status

    2. KRSI1 setID, 120000 job code, Director, effective date: September 03, 2016, active effective status

    3. KRSI1 setID, 120000 job code, President, effective date: September 20, 2016, active effective status

    • If these rows are processed all at the same time (for example, initial data loading), one Job Code event gets generated for the latest data row (#3), and the row information is populated in the inclusion section of the generated XML file.

    • If these rows are entered and processed at different times after eSocial becomes effective, three different Job Code events get generated as a result. The row information of the first event is populated in the inclusion section of the generated XML file. The second event contains row information of #2 in the change section of its XML file, and the third event with row information of #3 in the change section as well.

  • Here is another example for effective-date changes. Suppose that three effective-dated job code rows are entered in PeopleSoft, and the effective date of one row is changed:

    1. KRSI1 setID, 120000 job code, Director, effective date: September 01, 2016, active effective status

    2. KRSI1 setID, 120000 job code, President, effective date: September 20, 2016, active effective status

    3. KRSI1 setID, 120000 job code, Senior President, effective date: changed from October 04, 2016 to September 25, 2016, active effective status

    • If the old effective date of the changed row is the only date of its month and year period, and the new effective date is the latest date of its month and year period (like the example), two different Job Code events get generated as a result. The old effective date is populated in the exclusion (the exclusao XML file tag) section of the first generated event. In the second event, the information of the new effective date (Senior President for effective date September 2016) is populated in the change section of its XML file.

    • If the old effective date of the changed row is the only date of its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 01, 2016, active effective status

      KRSI1 setID, 120000 job code, President, effective date: September 20, 2016, active effective status

      KRSI1 setID, 120000 job code, Senior President, effective date: changed from October 04, 2016 to November 01, 2016, active effective status

      One Job Code event gets generated. In this Job Code event, the old and new effective dates are populated in the change section of its XML file.

    • If the old effective date is not the only one and is the latest date of its month and year period, and the new effective date is one but not the latest of its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 01, 2016, active effective status

      KRSI1 setID, 120000 job code, President, effective date: changed from September 20, 2016 to October 1, 2016, active effective status

      KRSI1 setID, 120000 job code, Senior President, effective date: October 04, 2016, active effective status

      One Job Code event gets generated. In this Job Code event, the new row information (Director) for September 2016 is populated in the change section of its XML file. The existing information for October 2016 stays intact because the changed row is not the latest data row.

    • If the old and new effective dates are not the latest or the only date of their month and year period, no events are generated.

  • This example shows a few effective-dated row deletion scenarios.

    • If a row is deleted, and it is the only row in its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 03, 2016, active effective status

      KRSI1 setID, 120000 job code, President, effective date: September 20, 2016, active effective status

      KRSI1 setID, 120000 job code, Senior President, effective date: October 04, 2016, active effective status (deleted)

      One Job Code event gets generated. In this Job Code event, the deleted row information is populated in the exclusion (the exclusao XML file tag) section of its XML file.

    • If a row is deleted, and it is the latest of the rows in its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 03, 2016, active effective status

      KRSI1 setID, 120000 job code, President, effective date: September 20, 2016, active effective status (deleted)

      KRSI1 setID, 120000 job code, Senior President, effective date: October 04, 2016, active effective status

      One Job Code event gets generated. In this Job Code event, the deleted row information is populated in the change section of its XML file.

    • If a row is deleted, and it is not the latest or the only date of its month and year period, no event is generated.

  • This example shows a few effective-dated row insertion scenarios.

    • If a row is added, and it is the latest of the rows in its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 20, 2016, active effective status

      KRSI1 setID, 120000 job code, Senior President, effective date: October 04, 2016, active effective status

      KRSI1 setID, 120000 job code, Vice President, effective date: October 20, 2016, active effective status (added)

      One Job Code event gets generated. In this Job Code event, the added row information is populated in the change section of its XML file.

    • If a row is added, and it is the only row in its month and year period, for example:

      KRSI1 setID, 120000 job code, Director, effective date: September 20, 2016, active effective status

      KRSI1 setID, 120000 job code, Senior President, effective date: October 04, 2016, active effective status

      KRSI1 setID, 120000 job code, Vice President, effective date: November 01, 2016, active effective status (added)

      One Job Code event gets generated. In this Job Code event, the added row information is populated in the inclusion section of its XML file.

    • If a row is added, and it is not the latest or the only date of its month and year period, no event is generated.

  • When a change is made to a basic table (for example, job code) and the change does not apply to the effective date, PeopleSoft generates an event (with update in the change section) only if the change happens to the data row with the latest date of its month and year period.

Related Topics