How to Fix the 4 Most Common OSHA ITA CSV Upload Errors (Form 300A)

Between January 2 and March 2 each year, covered establishments must electronically submit their OSHA Form 300A Summary data to OSHA's Injury Tracking Application (ITA).

When you open OSHA's sample .csv template in Microsoft Excel and re-save it, Excel silently modifies numeric formatting in ways that cause the ITA batch parser to reject the file.

The 4 validation rules the ITA parser checks

1. Leading Zeros in ein and zip: Excel treats 042819201 as an integer and saves 42819201 (8 digits), which fails the 9-digit EIN check. The same happens to New England and New Jersey 5-digit ZIP codes starting with 0.
2. Hours Worked Ratio (total_hours_worked / annual_average_employees): OSHA ITA checks that average hours worked per employee falls between 500 and 8,000 hours per year. Leaving total_hours_worked as 0 or entering weekly hours instead of annual hours triggers a hard rejection.
3. The G+H+I+J = M1..M6 Equality Check: On Form 300A, the sum of Case Outcomes (total_deaths + total_dafw_cases + total_djtr_cases + total_other_cases) must equal the sum of Injury and Illness Types (total_injuries + total_skin_disorders + total_respiratory_conditions + total_poisonings + total_hearing_loss + total_other_illnesses).
4. The no_injuries_illnesses Flag: In OSHA's CSV specification, no_injuries_illnesses uses 1 when total cases equal 0, and 2 when total cases are 1 or more.

Generate a pre-validated CSV and wall-posting PDF in 60 seconds

Use the free OSHA Form 300A PDF & ITA CSV Generator to validate all four rules in real time and download both your signed-ready breakroom PDF and your ITA-compliant CSV.