eSocial.
Payroll, social security, labor and OHS in a single pipeline.

What eSocial is and its legal basis

Definition

eSocial is one of the modules of SPED dedicated to centralizing tax, social-security and labor information of employers. It goes beyond the other SPED bookkeeping systems by covering matters that involve four agencies: the Federal Revenue Service of Brazil (RFB), the Ministry of Labor and Employment (MTE), Social Security (INSS) and the Federal Savings Bank (Caixa, for the FGTS severance fund).

Legal basis

• Decree 8.373/2014 — creates eSocial and establishes the Steering Committee (RFB, INSS, MTE, FGTS, IBGE)
• Steering Committee resolutions — layout versions (current: S-1.2)
• Joint SEPRT/RFB ordinances — mandatory-adoption schedule by group
• Law 8.212/1991 — legal basis for social-security contributions and fines
• CLT (Decree-Law 5.452/1943) — labor-law basis
• NR-1 (Regulatory Standard 1) — basis for the OHS module

Replaced obligations

eSocial absorbed, in phases, the following obligations:

• CAGED (General Register of Employed and Unemployed Workers) — since Jan/2020
• GFIP (FGTS Collection Guide and Social-Security Information) — replaced for social-security purposes (FGTS migrated to FGTS Digital)
• RAIS (Annual Social Information Report) — for companies that file the full eSocial
• DIRF — the portion relating to labor income (the portion of general withholdings migrated to EFD-Reinf)
• PPP (Social-Security Occupational Profile) — via event S-2240
• CAT (Workplace Accident Report) — via event S-2210
• MANAD (Normative Manual of Digital Files) — discontinued

Event structure (S-1000 to S-3500)

S-1000 series — Table events (initial registration)

• S-1000 — Employer/contributor information
• S-1005 — Table of establishments, works or public-agency units
• S-1010 — Table of pay items (salary components and deductions)
• S-1020 — Table of tax assignments
• S-1030 — Table of public positions/jobs
• S-1035 — Table of careers
• S-1040 — Table of functions/commissioned positions
• S-1050 — Table of working schedules and shifts
• S-1060 — Table of work environments
• S-1070 — Table of administrative/judicial proceedings
• S-1080 — Table of port operators

S-2000 series — Non-periodic events (employment relationship)

• S-2190 — Worker hiring (preliminary record)
• S-2200 — Initial registration and worker hiring
• S-2205 — Change to worker registration data
• S-2206 — Change to employment contract
• S-2210 — Workplace accident report (CAT)
• S-2220 — Worker health monitoring (ASO)
• S-2230 — Temporary leave
• S-2231 — Secondment/service at another agency
• S-2240 — Environmental working conditions (PPP)
• S-2245 — Training, qualification and simulated exercises
• S-2250 — Prior notice
• S-2298 — Reinstatement
• S-2299 — Termination (dismissal)
• S-2300 — Worker without an employment/statutory relationship — start
• S-2306 — Worker without a relationship — contractual change
• S-2399 — Worker without a relationship — end

S-1200 series — Periodic events (payroll)

• S-1200 — Remuneration of a worker covered by the RGPS (general social-security regime)
• S-1202 — Remuneration of an RPPS (civil-servant regime) employee
• S-1207 — Social-security benefits (RPPS)
• S-1210 — Payments of labor income
• S-1280 — Supplementary information to the periodic events
• S-1295 — Request for totalization
• S-1298 — Reopening of the periodic events
• S-1299 — Closing of the periodic events

S-3000 series — Exclusion/rectification

• S-3000 — Exclusion of events

S-5000 series — Return events (generated by the RFB)

• S-5001 — Social-contribution information by worker
• S-5002 — Income tax withheld at source by worker
• S-5003 — FGTS by worker
• S-5011 — Social-contribution information consolidated by contributor
• S-5012 — Consolidated IRRF (withholding income tax) information
• S-5013 — FGTS consolidated by contributor

OHS module — Occupational Health and Safety

What changed with OHS digitalization

The entry of the OHS module into production (started in 2022 for Group 1 and expanded in phases through 2024) digitalized obligations historically kept on paper: CAT, ASO, PPP, NR training. The main events:

• S-2210 — CAT: Workplace Accident Report. Deadline: by the next business day after the accident; in the event of death, immediate notice to the competent authority
• S-2220 — ASO: Occupational Health Certificate (on hiring, periodic, on dismissal, return to work, change of function). Deadline: by the 15th day of the subsequent month
• S-2240 — PPP: Environmental working conditions (replaces the old physical PPP). Captures harmful agents, intensity, PPE/CPE. Deadline: by the 15th day of the month subsequent to the event
• S-2245 — NR training: qualifications, mandatory training (NR-10, NR-12, NR-35, etc.). Deadline: 15th day of the subsequent month

Operational impact

Digital OHS transformed the Labor × Social-Security × Occupational-Medicine relationship:

• A company can no longer “keep” the PPP in a physical folder — everything is transmitted and auditable
• Inconsistencies between the transmitted PPP and benefits granted (sickness allowance, special retirement) generate a retroactive social-security charge
• Workers can check their data via MEU INSS and the Digital Work Card — a discrepancy becomes a labor claim
• Failure to file the S-2210 (CAT) on time is a serious infraction — an administrative fine plus criminal liability where a death is not reported

Integration with FAP/RAT

The company’s FAP (Accident Prevention Factor), which multiplies the RAT rate (1%, 2% or 3%), is calculated by Social Security based on the events for leave due to accident, illness and CAT. Companies that omit or under-report OHS end up paying more in the long run — because an “uninformed” FAP does not distinguish between a safe company and a company that hides information.

Critical deadlines and continuous operation

Continuous, not monthly, operation

Unlike most tax obligations (monthly), eSocial runs on a continuous pipeline. Events are transmitted as they happen, with specific deadlines by type:

Non-periodic events — critical deadlines

Periodic events (payroll) — single deadline

S-1200-series events (remuneration, payments) must be transmitted by the 15th day of the month subsequent to the triggering event, with closing via S-1299. Same pattern as EFD-Reinf, aligned with the DCTFWeb deadline.

OHS events

Events S-2220 (ASO), S-2240 (PPP) and S-2245 (training) also follow the 15th day of the subsequent month deadline. Only the S-2210 (CAT) has a short deadline (next business day).

Fines for late filing

• Failure to report hiring on time (S-2200): fine of BRL 800.00 to BRL 6,300.00 per employee (Law 8.213/91 and Ordinance SEPRT/SDE/MTb 1.510/2014)
• Late S-2210 (CAT): fine of 1 to 4 times the maximum limit of the contribution salary (Law 8.213/91, art. 22)
• Late S-1200 (payroll): fine of 3% on the contributions due (Law 8.212/91, art. 32-A)

Integration with EFD-Reinf and DCTFWeb

The tax-labor trio

eSocial is the labor-social-security vertex of the trio centralized by the Federal Revenue Service:

1. eSocial — reports payroll, the employer social-security contribution on payroll (20% + RAT × FAP + Third Parties), IRRF (withholding income tax) on labor income, and FGTS
2. EFD-Reinf — supplements with withholdings on services (R-2010), CPRB (R-2060), rural production (R-2050/R-2055), shows and events (R-3010) and other federal withholdings (R-4000)
3. DCTFWeb — aggregates debits from eSocial + EFD-Reinf, generates the monthly DARF (federal tax payment slip) and replaces the old DCTF for social-security taxes

FGTS Digital — a parallel output

As of March/2024, FGTS migrated from eSocial-GFIP to FGTS Digital — a new system of the Federal Savings Bank (Caixa) that generates the FGTS slip directly from eSocial events S-1200 and S-2299. The company no longer needs to generate GFIP — it simply transmits eSocial and downloads the slip via FGTS Digital.

S-5000 return events

After each monthly closing (S-1299), the RFB processes all events and generates S-5000 return events with the consolidated figures for contributions, IRRF and FGTS by worker and by company. These figures automatically feed the pre-filled DCTFWeb.

Systemic inconsistencies

Common divergences that generate a tax audit flag:

• eSocial payroll smaller than the withholdings declared in EFD-Reinf by the service taker (under-declaration)
• FGTS collected diverging from the amount calculated by the S-5003 events
• Social-security contribution paid diverging from the S-5011 consolidation
• Workers with an initial S-2200 registration with no corresponding S-1200 in payroll

Operational challenges and common pitfalls

1. Late hiring

The S-2190 (preliminary hiring) must be transmitted before the start of the contract. Later transmission generates a fine of BRL 800 to BRL 6,300 per employee. In companies with high turnover or emergency hiring (events, seasonal retail), control requires automated ERP × eSocial integration.

2. Confusion among pay items (S-1010)

The table of pay items (S-1010) classifies each salary component by incidence: social security, IRRF, FGTS, vacation/13th-salary averages. Systematic classification errors generate over- or under-paid contributions — a later inspection is painful because it involves a historical review of the entire payroll.

3. Forgotten monthly closing

The S-1299 (closing of the periodic events) is mandatory, even with no activity. Without closing, S-5000 events are not generated, the DCTFWeb is not pre-filled, and the slip cannot be issued in time.

4. Late or omitted CAT

The S-2210 (CAT) is the most critical OHS obligation. A delay constitutes a serious infraction; omission in the event of death may have criminal implications (art. 169 CLT, art. 19 Law 8.213/91). The company needs a clear flow between HR/Occupational Safety × the eSocial pipeline.

5. Digital PPP ≠ old physical PPP

The S-2240 (environmental conditions) covers information that used to be kept in a physical file. Companies with a legacy of paper PPP must migrate to the eSocial layout — retroactive social-security audits began in 2024 and identify companies with a backlogged base.

6. Poorly done rectifications

S-3000 (exclusion) + resending the correct event is the standard procedure. Companies that try to “fix” an event by resending it (without S-3000) end up with duplicate events in the base — generating cumulative inconsistency in the S-5000 and a tax audit flag.

7. Successive layout changes

eSocial is at version S-1.2. Each version change requires adapting the payroll system and the ERP — companies that do not keep up end up transmitting events in an outdated layout, rejected by the national environment.

How the firm works on eSocial

The firm works on three eSocial fronts:

1. Implementation and configuration

• Diagnosis of the classification (groups 1-4) and the applicable mandatory-adoption schedule
• Configuration of tables S-1000 to S-1080 (employer, establishments, pay items, assignments, proceedings)
• Integration between the payroll/HR system × eSocial × financial ERP
• Configuration of the OHS module based on the Occupational Health and Safety operation
• Training of the internal team in maintaining the events

2. Continuous operation and preventive audit

• Monitoring of non-periodic events (hirings, changes, terminations) and periodic events (payroll)
• Monthly cross-reconciliation eSocial × EFD-Reinf × DCTFWeb
• Validation of the S-5000 (return events) — the basis for collection
• Quarterly preventive audit — identification of divergences before a tax audit flag
• Review of the classification of pay items (S-1010) — the most common source of liability

3. Defense in inspections and retroactive remediation

• Response to summons from the RFB/Attorney’s Office over systemic divergences
• Rectifications via S-3000 + resending (a delicate operation when it involves old events)
• Defense in administrative tax proceedings against assessments for social-security, FGTS or IRRF under-declaration
• Defense in labor lawsuits that challenge eSocial pay items/components
• Negotiation through voluntary disclosure where possible (Tax Code, art. 138)

The model combines a fixed part (implementation or a one-off audit) and a variable part tied to the liability reduction identified (retroactive audit). The recurring monthly operation may be conducted by the client’s internal team under the firm’s technical coordination, with quarterly reviews.