PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone
1What it is and why
What it is
A report that gives the data needed to prepare the OSHA 300A annual summary of incidents recorded in the OSHA 300 log (USA).
What you do here
Use this report to prepare the yearly summary of work-related injuries and illnesses that must be posted at each workplace.
Example
For example, for 2026 BEAT selects its US warehouse establishment, enters 1 January to 31 December 2026, 58 employees on annual average and 116,000 hours worked, and generates the 300A summary to post at the warehouse.
The page in Dynamics 365. page title tab to open what to set or check
About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
Setup steps on this page
Generate the OSHA 300A summary per establishment
Produce and post the yearly summary for each US workplace.
How to use it
Go to Human resources > Workers > Injury and illness > OSHA 300A report.
Under Parameters, select a Regulatory establishment, enter the required From date and To date, and select a Format mapping.
Review the Company identification information FastTab (Establishment name, Address, Establishment size, Industry description, NAICS) and the Employment information FastTab (Establishment type, Total hours worked, Annual average number of employees, Change reason).
Generate it once a year per regulatory establishment for the calendar year, with the establishment's employee count and hours worked, after the 300 log is complete.The OSHA 300A is the annual summary of the OSHA 300 log and must be posted at each workplace.
Per company data, US only: the OSHA reports read injury or illness incidents, which Data management lists as not shared, and are run per regulatory establishment, the workplace location (Data management lists Regulatory establishments as shared). Checked in Dynamics 365
Can it be undone
Nothing to undo: Generating the summary doesn't change incidents; run it again after corrections. Microsoft Learn
If you change it later
The summary counts the incidents recorded for the establishment in the period; cases added or changed after it is generated need a new run, and it must be posted at each workplace. Microsoft Learn
Technical architect
6Technical
Menu item
HcmOsha300AReportGenerationChecked in Dynamics 365
Form
HcmOsha300AReportGenerationChecked in Dynamics 365
Roles to set it up and use it
To use itHuman resource manager HcmHumanResourceManagerHuman resource assistant HcmHumanResourceAssistantCompensation and benefits manager HcmCompensationAndBenefitsManagerGive people one of these roles. On this system, 3 roles can open this page.Checked in Dynamics 365
Load order: The OSHA 300A report has no data entity in Data management, so it can't be loaded from a file or a configuration template. It is generated from the incidents and the regulatory establishment; load those and generate it in each environment.Microsoft Learn