Note: This page was translated using automation resources with the purpose of providing content in your language more quickly. Consequently, it may have grammatical errors and similar situations. If the content is not useful in this state, in the page footer you can access the original material in Brazilian Portuguese and also give us opinions on this translation.
Tables / Companies / ESocial Settings (AP)

eSocial Definitions

Warning

This documentation applies only to the module: AP.

This screen is used to configure eSocial usage settings in the system.

Important

To change or delete information that has already been sent to eSocial, the process must be done directly at the source of the information. In this way the system is prepared to monitor and generate the treatments automatically, sending the change layouts and exclusion.

When performing these operations manually in the database, the system does not generate the necessary pending for eSocial. This causes irreversible inconsistencies between the system database and the Government.

For this reason, it is not allowed to perform any command directly in the database without specific orientation of the Senior, especially in the tables: R030DES, R000DME, R034MAT and all with R350 * prefix.

Company

Please inform the company for which the settings are valid. It is not allowed to inform a company that is not Brazilian.

Information Tab

Type of eSocial Environment

Identifies the type of environment:

Important

Important

When changing the environment type, it is important to review the eSocial Engine settings (FR000DME) so that the shipments are transmitted to the correct destination (eDocs URL or directory to save to disk, depending on the type of processing).

Delete production data button

This button is available at the bottom of the screen. It allows companies to eliminate all events sent to the Restricted Production environment, including the S-1000 event. This feature makes testing flexible in this environment.

When performing the exclusion, the system will present an alert about the impacts on the system and the basis of government. After deletion the system will display a confirmation message from the employer of the eSocial Restricted Production database.

Note

This button is enabled only for the environment type "2 - Restricted Production - Actual Data". With the option "1 - Production" it is not allowed to carry out data exclusion, therefore, the shipments made with this type of environment are official and are subject to legal effects.

Enable Restricted Production

This button is used to exclude all system-generated queue records for eSocial and to update the Type of Environment for "2 - Restricted Production - Actual Data". No submissions will be made to eSocial with this action.

Top Tables, Home Non-Periodicals and Home Newspapers

The start date of tables assumes the date on which the initial layout S-1000 is sent. The others must be filled in with the date of validity / sending of the non-periodical and periodical sheets, respectively.

ESocial phasing dates will already be suggested when the type of environment is equal to 2 - Restricted production - Actual data, if they have not yet been informed.

When the selected environment type is 1 - Production, the start date of tables can not be earlier than 08/01/2018, which is the start date of eSocial.

Release Date Version 2.4.02

Fill in with the date the organization will start sending the information to eSocial, to the environment with the version 2.4.02 two layouts.

If you are using a production environment, this date must be equal to or greater than 5/1/2018. This is the date foreseen by the Government for entry into production, as foreseen in Resolution 03/2017 of the eSocial Steering Committee.

If the environment is in homologation (tests), in this field can be informed any date.

Generation Stocking

This field is enabled when the field MO Calculation Calculation of the company registration screen, in Companies> Companies (FR030EMP), you have the option other than "N - Do Not Use Rate". The field has the following options:

Last Registration

Uneditable field that displays the enrollment of the last employee whose admission was closed.

Company ID

The system suggests in this field an eight (8) character identifier code for the company, which will be taken to generate the eSocial layouts.

eSocial Function

Field to define if the company uses or not functions. Its default value is "Not applicable", but if the company uses functions, it is used to register if the functions are by job, role or job history. According to the selected option, the eSocial Function field is displayed in certain windows.

Option Field eSocial function shown in ...
0 - Not applicable

Default value, disables the use of functions

1 - Function History

Contributors> Historical> Functions (FR038HFU)

2 - Position History

Collaborators> Historical> Cargo (FR038HCA)

3 - Post History

Contributors> Historical> Historical Maintenance (FRHISCOL) and Employees> Historical> Additional Posts ( FR038HPO)

In this case, besides the field ESocial Function equal to "Yes", the system only takes to the eSocial the Stations that have characteristic Various Positions (at the Post registration) equal to "No" and where the Actuation type be "Holder".

The post history is considered regardless of the type of actuation being the principal or not.

Important

When the value selected in the ESocial Function is different from "0 - Does not apply", it is important to review the employee's records (position, function or position) to ensure that they really represent a role for eSocial.

This review should preferably take place in the current or post-start history of eSocial.

Send Nota Fiscal detail S-1260

This field defines whether production marketing information will be sent or not to eSocial, that is, it is optional information. When "S - Yes" is selected, the system enables fields on the screen Production Marketing.

Send Remarks Events S-1010

Enter whether you want to send field information Note (Tables> Events> Events> Registration (FR008EVC)) to eSocial Layout S-1010.

Send Group Contract Schedule S-2200 / S-2206

This field defines whether information regarding employee schedules should be taken to eSocial through S-2200 and S-2206. If it is filled in with:

Consisting Leaf Closing S-1299

This field defines whether consistency for the eSocial payroll validation rule will be applied when processing the Closing (eSocial> Periodic Events> Closing (FRFECFOL)). This validation assists in the receipt of the layout S-1299, avoiding that it is pointed with errors.

Important

This tagging was created because the original rule defined by eSocial would oblige the system to go through the list of collaborators registered in the database to apply the validation. Depending on the number of records, this can cause slow generation of the S-1299 layout.

When this flagging is used, the validation rule is applied with the following conditions:

  1. Shipments of valid S-2190 shipments are verified, and have no corresponding S-2200. They are validated only when the date of admission is equal to the reference date of S-1299 being generated.

    Different from what the original rule says, the system will not check all occurrences of the S-2190 as long as you start using eSocial, but only the month in which the S-1299 is being generated. This was done to gain system performance, otherwise there would be many occurrences and significant loss of performance.
  2. This item checks if there are any collaborators in the base (looking in table R034FUN) that do not have compensation events (S-1200) sent.

    The exceptions to this rule are:
    • Only consistency for employees whose type of employee is equal to "1";
    • It only makes consistency for collaborators sent on the S-1200 (those of S-1202 are ignored, as the rule suggests);
    • Disregard employees dismissed;
    • It disregards the employees who have been removed throughout the period, with these removal codes: 3, 5, 6, 7, 11, 12, 13, 14, 21, 22, 23, 24, 25, 27, 28, 30, 31;
    • Disregard employees with an eSocial category equal to "111" in the entire reporting period. Example: If the category is changed to "111" on the 15th of the reference month, the employee will not be consisted, even if he had this category only from the middle of the month onwards;
    • Disregard employees admitted after the reference month of the S-1299 layout.

To learn more about the checks made by the original rule, see the eSocial Readme Annex II file - Validation Rules, available at official eSocial website.

Dissidio Option S-2206

When there is a collective bargaining agreement with retroactive effect, this field determines whether the system should:

Decentralized Base

This field aims to serve customers who have branches registered in separate databases or have branches registered in the Personnel Administration system in the company registry.

The options to select are:

Options 1 and 2 make available in the branch register, in the eSocial Employer and eSocial Establishment tabs, and in the Judicial Decentralized Base Option.

This treatment is necessary so that eSocial does not receive duplicate files in the S-1000, S-1005 and S-1070 layouts, where its key is CNPJ or Process Number.

For the other table layouts where the key is code, the field Company ID, where the client will inform a different identifier in each company, thus preventing duplication of eSocial code.

Company Closing Date

Inform the closing date of the company's activities to be sent to eSocial. This action will cause all table layouts to be closed (S-1005 to S-1080).

Before informing the closure of the company, it is necessary to inform the one of the subsidiaries, in the Cadastre of these (FR030FIL). You can not record company closure with a back date or with active employees.

Contact Us

This guide has the purpose of defining how the layout will be sent to the eDocs. For this you must be informed in the field Send to eDocs one of the "1 - Automatic" or "2 - Manual" options. After that, the sending must be done through the eSocial To-do List screen, in eSocial>FR350STA).

Note

Some of the layouts listed in this guide are available only for definition, ie the fact that a layout is listed in this guide does not mean that it is available for use.

Optional tab of the S-2300 layout

In this guide it is possible to inform in a historical way (by date of competency) and by category, the contributors of the optional categories of the S-2300 layout that should be sent to eSocial. The optional categories of the layout are: 701, 711, 712, 741, 751, 903, 904, 905, 308.

Check the column Submit the optional categories that will be considered by the system when closing the employee's admission and sent to the S-2300 layout.

In addition to the taxpayers required by the S-2300 layout, eSocial allows companies and public bodies to optionally register other individual taxpayers whom they deem necessary. This guide provides flexibility for the employer to decide whether or not to send employees from these optional categories as a means of internal control, for example.

(missing or bad snippet)