BeyondERP.Newsletter
Menu

Page · Human resources

OSHA 300A report

A report that gives the data needed to prepare the OSHA 300A annual summary of incidents recorded in the OSHA 300 log (USA).

Business process
Audit workplace for safety
Menu item
HcmOsha300AReportGeneration
Setup steps
1 on this page
Show what matters for
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 isA 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 hereUse this report to prepare the yearly summary of work-related injuries and illnesses that must be posted at each workplace.
ExampleFor 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.
OSHA 300A report page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

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

  1. Go to Human resources > Workers > Injury and illness > OSHA 300A report.
  2. Under Parameters, select a Regulatory establishment, enter the required From date and To date, and select a Format mapping.
  3. 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).
  4. Expand Company representative if needed.
  5. Select OK to run the report, or Cancel to close.

Source: Checked in Dynamics 365

Fields on the page

FieldWhat it meansExample
From dateThe first date of the reporting period.Microsoft Learn 1 January 2026
To dateThe last date of the reporting period.Microsoft Learn 31 December 2026
Regulatory establishmentThe workplace location the report is for.Microsoft Learn BEAT US warehouse

Common errors and fixes

MessageWhat to do
The summary counts cases of another siteThe wrong Regulatory establishment was selected. Each establishment has its own 300A summary; run it per establishment. Microsoft Learn

Test checklist

  1. Record two cases for the establishment in the year.
  2. Generate the summary for the year and the establishment.
  3. Check the case counts are 2 and match the OSHA 300A prep report for the same year.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Generate the OSHA 300A summary per establishmentGenerate 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.Who provides hours worked and the average number of employees?Generating it before all cases of the year are recorded, so the posted summary is too low.Test: Summary matches recorded cases

Feature management and licence

Licence or add-inHR and safety staff of US legal entities prepare OSHA records from these reports. No Feature management feature is needed for this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer 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 undoneNothing to undo: Generating the summary doesn't change incidents; run it again after corrections. Microsoft Learn
If you change it laterThe 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 itemHcmOsha300AReportGeneration Checked in Dynamics 365
FormHcmOsha300AReportGeneration Checked in Dynamics 365
Roles to set it up and use itTo 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
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=HcmOsha300AReportGeneration
Data migrationLoad 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
Everyone

8Sources