Executive TL;DR
In eSocial, events S-2210 (work accident communication — trail aligned with CAT and technical nexus), S-2220 (worker health monitoring, in line with ASO and PCMSO), and S-2240 (environmental working conditions — exposures and information feeding the exposure profile and dialogue with RMP/NRs) are pieces of the same puzzle. They do not replace NR-1, NR-7, or NR-9, but inconsistency between employment, category, department, ASO, and risk inventory destroys auditability and generates rework in inspections, unions, expert opinions, and M&A due diligence. This text is operational; deadline tables, validation rules, and layout version must be checked in the eSocial Orientation Manual and technical notes in force on the submission date.
Table of contents
- Role of each event in the OHS ecosystem
- S-2210: accident, CAT, and single narrative
- S-2220: occupational health, ASO, and PCMSO
- S-2240: exposures, PPP, and RMP
- Master data trail and governance
- Typical errors in enterprise projects
- FAQ
- References
Role of each event in the OHS ecosystem
eSocial does not “define” labor law; it reports to government and connects databases. Therefore, OHS in eSocial must be read in three layers: (1) legal obligation to manage risk (RMP/ORO, programs, control measures); (2) obligation to document health and exposure (PCMSO, PPRA/LTCAT/ARP as applicable); (3) obligation to transmit events in approved layouts. Failing layer (1) and “getting the XML right” is compliance illusion; failing (3) can generate fines and information incompatibility with plant reality — the worst of both worlds.
One point that frequently distorts internal briefings: S-2220 does not deal with labor lawsuit. The core of S-2220 is worker health monitoring, with content close to what PCMSO organizes clinically (exams, ASO, periodicity, conclusions). Treating S-2220 as “judicial” is a sign of outdated technical documentation or mixing with other legal flows in the same board slide — correct vocabulary before the next risk committee.
S-2210: accident, CAT, and single narrative
S-2210 is submitted when there is work accident communication under eSocial, in convergence with the logic of issuing/receiving CAT and consolidating information relevant to statistics and public policy. In enterprise practice, the accident is also a reputation and claims event; therefore SESMT, medicine, HR, insurance, and legal need a single timeline: what the internal report describes, what the medical certificate records, and what video/CCTV shows must not diverge without a dated explanation.
Governance implications: in M&A, the buyer looks at accident rate, under-reporting (leave ASO without coherent trail), and third parties without CNO/contractual integration. Linking S-2210 to the risk inventory (RMP) helps demonstrate accident learning as systemic corrective action — useful both in ISO 45001 and in labor defense when there is discussion of exclusive fault.
S-2220: occupational health, ASO, and PCMSO
S-2220 supports the role of PCMSO as a program producing clinical evidence — complementary exams, dates, ASO, and conclusions — and must be consistent with exam schedule control (pre-employment, periodic, risk change, return, termination). HR is usually the SLA owner for scheduling, but technical validity is MTE/CRM; therefore the coordinating physician is not “bureaucratic detail,” it is program structure.
Submission deadlines and historical ancillary obligations have been subject to regulatory updates (Federal Revenue / eSocial). Practical counsel remains: implement a monthly reconciliation job between ASOs issued in the occupational system and transmitted events, with an exception queue when there is employment rectification or registration correction. Mature companies treat S-2220 as a data quality indicator, not mere “IT check.”
S-2240: exposures, PPP, and RMP
S-2240 reports environmental conditions relevant to employment — in other words, helps formalize what the worker faced over time in terms of agents and controls. This is where engineering and PPRA (or equivalent instrument by size and regime) meet transactional data: if the master file of department/role in ERP is wrong, the RMP inventory and exposure profile disagree — and Labor Inspection or Courts choose the most harmful narrative to the employer.
PPP (Professional Profile for Social Security Purposes), when applicable in your preparation chain, must be fed with temporal consistency: role change without updating S-2240 creates a gap hard to explain in occupational disease benefit, even when the company did control risk correctly on the ground.
Master data trail and governance
A minimum enterprise trail should cross: CPF, registration, eSocial category, physical and logical assignment, OHS role, risk outcome in RMP, and program status (PCMSO/PPRA). Third parties with service revenue assignment need a clause defining who generates which event — common gap in facilities and logistics.
Tools and shadow IT
Parallel OHS spreadsheets are poison: no versioning and macros swapping comma for period change agent code. Prefer role MDM and workflow with double confirmation when the employee moves from an area with chemical risk to administrative.
Typical errors in enterprise projects
- Training IT without training physicians and nursing — the error starts in ASO, not XML.
- Confusing “transmitted” with “true” — rectifying without RCA (root cause analysis) perpetuates systemic risk.
- Copying competitor layout in the same sector — CNAE, process, and outsourcing change the exposure map.
- Relying on payroll vendor without proof that PCMSO integrates with time clock on night shift change.
- Ignoring that bad data becomes materiality in ESG report when it tells the same story to investors.
Rectifications, exclusions, and “ghost event”
Even with mature ERP, employment rectification after M&A, CBO correction, or branch change without event refactoring creates a ghost: exposure deleted in field, but active in database. Good practices include a reconciliation job comparing domain hash (role, department, HEG) between HR, medicine, and safety before payroll period. In S-2210, incidents with rectification must preserve cause line in internal investigation — deleting bad XML without RCA is self-deception.
Integration with external audits (ISO, corporate client)
Automotive or aerospace clients will audit your S-2210 indirectly via claims and quality PPAP. Inconsistency between medical stop and CAT opens supply chain social non-conformity.
ACSMT supports OHS–eSocial trail design, reconciliation with RMP, and committee training — see /contato.
FAQ
Does S-2220 replace PCMSO?
No. PCMSO is a legal program obligation; S-2220 is transmission of health monitoring information per eSocial rules.
Can I have correct ASO on paper and invalid event?
Yes. Layout, tables, and required fields change; maintain alert for manual updates.
Does S-2240 “prove” the RMP?
It helps demonstrate temporal coherence between reported exposure and planned control; it does not waive control hierarchy or RMP review when the process changes.
Who is responsible in economic group?
Define CNPJ employer controller and SLA with branch units; database mixing is a source of duplication or omission.
Does eSocial not inspect OHS?
eSocial concentrates data for agencies; labor inspection uses field. Two fronts, one liability if data lies.
References
- Brazil. eSocial Orientation Manual and official event tables — consult gov.br / Federal Revenue / eSocial portal and current layout version.
- Brazil. eSocial — Documentation (official technical notes and FAQs).
- Brazil. NR-1 — Risk management (link to inventory and documentation).
- Brazil. NR-7 — PCMSO and NR-9 — PPRA (technical content feeding health and exposure event logic).
- Brazil. CLT and related legislation on CAT and accidents — legal bases parallel to communication trail.
Editorial note: eSocial event codes (S-22xx, etc.) and required fields are updated periodically; always validate against the official manual and the employer's restricted production environment before fixing internal procedure.
