S-2210 - Accident at Work Communication (CAT)

Non periodic event. This event layout reports workplace accidents involving employees, even if they were away from their work activities when accidents happened. An Accident at Work Communication event is triggered when work incident or injury is reported using the Injury Details BRA or Incident Details BRA component.

Work accidents need to be sent to eSocial by the next business day after the occurrence of accidents, and immediately in case of death.

General Rules

Here are several general rules that apply to the Worker Health Monitoring – ASO event:

• To activate S-2210 event reporting for companies:

  • The eSocial functionality has to be enabled on the eSocial Parameters BRA Page.

  • Companies must be enabled and configured using the Company Parameters component.

  • The S-2210 event must be activated on the Events Activation Page and listed on the Non Periodic Events Page, and not to be inactivated in companies’ parameter setup.

• An Accident at Work Communication (CAT) event is triggered when a work incident or injury is reported using the Injury Details BRA or Incident Details BRA component with the Accident incident type, and the incident date entered is equal to or greater than the Health/Safety Go Live date. No S-2210 event is generated if either condition is not met.

Scenarios

Here are several examples that describe the behaviors of the Accident at Work Communication event:

• For each Accident incident row, do not enter more than one row for the Death Communication or Initial CAT type in the CAT Information section. Multiple rows are supported for the Reopened CAT type.

• If the injured employee works for multiple companies, the system submits an S-2210 event to each one of them.

• When the system creates an S-2210 event for an incident with the Reopened or Death Communication CAT type, it takes the receipt number from the latest S-2210 event that was submitted for the same incident with the Initial CAT type, and populates the value in the nrRecCatOrig tag of the new event.

  For example, an S-2210 event was created and submitted to the Government two months ago for an incident with the Initial CAT type. A month later, the system submitted a rectification for the same event to the Government. Now, as the system creates an S-2210 event for the same incident row with the Reopened (or Death Communication) CAT type row, it takes the receipt number that it received for the rectification from the Government, and populates it in the nrRecCatOrig tag of the new event.

• If a work accident results in an absence of the injured employee, an S-2230 - Temporary Absence event needs to be submitted as well. Customers need to report absence for the employee on the Absence Event BRA page so that the temporary absence event can be created accordingly.

• If changes are made to work accidents that were reported using the Injury Details BRA or Incident Details BRA component, the system sends rectifications for corresponding S-2210 events. The same is true for sending exclusion events for S-2210 events, if work accidents were excluded from associated components.

• If an S-2210 event happens to be rectified or excluded, any S-2230 event created as a result of it needs to be rectified or excluded as well. This is not done automatically and customers need to make the change in absence on the Absence Event BRA page.