PeopleSoft Global Payroll for Brazil

S-1070 - Administrative and Legal Proceedings

Basic table event. This event captures changes (insertion, change, and deletion of records) of administrative and legal proceedings for employers, taxpayers, or entities with collective representation of workers against government agencies, which influence the calculation of social contributions, taxes, or FGTS.

The system triggers an S-1070 event when you create, update or delete proceeding information on the PeopleSoft Human Resources Administer Workforce: Administrative/Legal Proceedings BRA Page. Information entered on this page is also used in other eSocial events and in the calculation of taxes and FGTS.

The Initial Loading process rules for the S-1070 event and other Basic Table events are similar. For example, if there are multiple effective-dated rows on or before the company’s eSocial on PeopleSoft date (also referred to as the company’s “go-live” date), the process selects the row with an effective date that is the same as (if not, closest to) the go-live date, and creates a driver for it using the go-live date for the year and month period (YYYY/MM) for the driver record. For effective-dated rows that are after the go-live date, the Initial Loading process creates one driver in each period (YYYY/MM) for the row that has the latest effective date in that period. These drivers will be mapped and processed by the eSocial Basic Tables Initial process (GPBR_ES_ILB), as determined by the limit date on the run control page. As for future-dated rows, the system creates drivers for them as well. These drivers will be mapped and processed by the eSocial Basic Tables process (GPBR_ESOC_MBT), as determined by the limit date on the run control page.

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

General Rules

Here are several rules that apply to the Administrative and Legal Proceedings event:

Only active administrative and legal proceedings will be considered.
Complementary data will only be mapped for the Judicial type of proceedings that are created for Tax only or Tax and FGTS and used in the creation of XML files.
Tax suspension information will only be mapped for proceedings that are created for Tax only or Tax and FGTS and used in the creation of XML files.

Setup Tasks

Because Global Payroll for Brazil delivers support for the S-1070 event after the initial eSocial implementation in PeopleSoft, for customers who like to implement S-1070 event processing in PeopleSoft, they need to follow these steps to prepare their environments:

Enable the Administrative and Legal Proceedings functionality on the PeopleSoft Human Resources Administer Workforce: Adm/Legal Proceedings Parameters BRA Page.

This is a prerequisite for S-1070 event processing.
Enter proceeding information on the PeopleSoft Human Resources Administer Workforce: Administrative/Legal Proceedings BRA Page.
Select the Import Historical Data option on the Events Setup Page for the S-1070 event. The event must be inactive for the option to display.

WARNING:

Perform this step only if you have been using a different system to process S-1070 events, and would like to switch it over to Global Payroll for Brazil (where the rest of your eSocial events are being processed).
Add Government-accepted proceeding data (data that was previously processed in a different system) to text files to be loaded into the PeopleSoft system. Then load the historical data on the Import Historical Data BRA Page. Refer to the same topic for the expected format of the text file for data import.

WARNING:

Perform this step only if you have been using a different system to process S-1070 events, and would like to switch it over to Global Payroll for Brazil (where the rest of your eSocial events are being processed).
Activate the S-1070 event on theEvents Setup Page and Events Activation Page.
Perform initial loading for the S-1070 event on the eSocial Basic Initial Page.

WARNING:

Perform this step only if you are implementing eSocial in Global Payroll for Brazil as a new company, in which case the Initial Loading process will also need to be run for other Basic Table events.

Before executing the Initial Loading process for the S-1070 event, be sure to evaluate the Government's implementation schedule for eSocial.

Start adding, updating, and deleting proceeding information in the PeopleSoft system. The eSocial Basic Tables process on the eSocial Basic Table Event Page handles the mapping and XML file creation for S-1070 event drivers that are generated for online transactions.

Scenarios

In these scenarios, assume that:

Company eSocial on PeopleSoft date (“go-live” date): Jan 1, 2016.
Driver for a proceeding record (effective date: Dec 1, 2015) has been added to PeopleSoft through the initial loading process and reported successfully to the Government. Driver date: Jan 1 2016 and driver status: GSUC.

Here are several examples that describe the behaviors of the S-1070 event when proceeding information is created, updated, or deleted from the PeopleSoft system as online transactions.

If a new effective-dated row is added, and the effective date (Dec 10, 2015) is earlier than the go-live date but later than the existing row (Dec 1, 2015), the system generates an S-1070 event (change event) with information of the new row in the change section (the alteracao group tag) of its XML file for the 2016-01 period.

If a new effective-dated row is added, and the effective date (Nov 1, 2015) is earlier than the date of the existing row, no event will be generated.
If the effective date of the existing row is changed from Dec 1, 2015 to Mar 1, 2016, and the change makes this row the only row in the new date period (and the prior date period no longer has any row), the system generates an S-1070 event (change event) with the new date period (2016-03) in the novaValidade tag within the alteracao group tag for the 2016-01 period, because the new value does not exist in the Government environment yet.

If the effective date of the existing row is changed and the new effective date (Dec 10, 2015) is earlier than the go-live date but later than the existing row (Dec 1, 2015), the result is similar to when you add a new effective-dated row—an S-1070 event (change event) is generated with the changed information in the alteracao group tag for the 2016-01 period.
If the current effective-dated row (Dec 1, 2015) is deleted from the PeopleSoft system, and a row with an earlier date (Jan 1, 2014) still exists, the system generates an S-1070 event (change event) with information of the Jan 1 row in the alteracao group tag for the 2016-01 period.

If the deleted effective-dated row is the one with the earlier date (Jan 1, 2014), no event will be generated.
If a new effective-dated row is added, and its effective date is the latest (Jan 30, 2018) in the date period, the system generates an S-1070 event (change event) with information of the new row in the alteracao group tag for the 2018-01 period.
If a new effective-date row is added (Jan 1, 2019) and it is the only row in that date period, the system generates an S-1070 event (inclusion event) with information of the new row in the inclusao group tag for the 2019-01 period.
If the effective date of the existing row is changed from Jan 1, 2018 to Jan 1, 2019, and the change makes this row the older of the two rows in the new date period (and the prior date period no longer has any row), the system generates an S-1070 event (exclusion event) with information for the 2018-01 period.
If the effective date of the existing row is changed from Jan 15, 2020 to Feb 1, 2020, and the change makes this row the only row in the new date period (and the prior date period has another row), the system generates an S-1070 event (change event) with information of the row in the prior date period for the 2020-01 period, and an S-1070 event (inclusion event) with information of the moved row for the 2020-02 period.