OSHA ITA CSV Validation Errors: How to Fix Rejected Rows Before the Deadline
Most rejected ITA rows come from establishment fields and formats, such as a missing EIN, an invalid NAICS code, or totals that do not add up.
What you are aiming for
Most rejected ITA rows come from establishment fields and formats, such as a missing EIN, an invalid NAICS code, or totals that do not add up. Fix the source data, regenerate the file, and upload again, rather than editing the CSV by hand.
CSV rejection usually points to establishment data or field formatting before it points to the injury totals.
What you need before you start
Gather these first, and keep them with the record afterward:
- The coverage decision for each establishment: peak headcount, NAICS code, and which appendix applies
- The EIN used by each establishment
- The submitted file or payload and the ITA confirmation
- Notes on any corrections made after submission
The rule behind the steps
Covered establishments submit injury data to OSHA's Injury Tracking Application (ITA) by March 2 each year for the previous calendar year; for 2026 data that is March 2, 2027 (29 CFR 1904.41). Three groups must submit: establishments with 250 or more employees that must keep records (300A data); establishments with 20 to 249 employees in an industry listed in Appendix A to Subpart E (300A data); and establishments with 100 or more employees in an industry listed in Appendix B (300A data plus 300 and 301 case data). Headcount means every individual employed at any time in the prior year, including part-time, seasonal, and temporary workers, and every submission includes the establishment's EIN.
Checks to run before you upload
- Every establishment row has an EIN, a legal company name, and a complete address.
- The NAICS code is six digits and matches what the establishment actually does.
- Annual average employees and total hours worked are filled in and plausible together (full-time workers average about 2,000 hours a year).
- Case counts by outcome (deaths, days away, restricted, other) add up to the same total as cases by type (injuries and each illness category).
- Day totals are zero when the matching case counts are zero, and not zero when they are not.
- The year is the calendar year the data covers (2026), not the filing year.
Step by step
- Export a test file.
- Review each error message.
- Fix the source data.
- Regenerate the file and upload it again.
- Keep the confirmation.
Tip: Validate the EIN, NAICS code, employee count, hours worked, and 300A totals before uploading.
Where this usually goes wrong
Teams wait until deadline week to discover rejected rows.
Most ITA problems are establishment data problems: an old NAICS code, a parent-company EIN, or a headcount measured at the wrong level. The fix is to decide coverage per establishment in the fall, clean the EIN, NAICS, and address data then, and leave only validation and submission for February.
Analysts are measured on numbers leadership trusts, so document every input and assumption behind a rate or a total.
Special situations
- Corrections after the deadline still need a controlled source-data update.
- For 300 and 301 case data, OSHA excludes employee names and addresses and health care provider details from the submission (1904.41(b)(9)).
Example
An upload rejects two rows: one site shows 45 average employees and 4,500 hours worked (a missing zero), and another has 3 recordable cases by outcome but 2 by type. Both are fixed in the source records, the file is regenerated, and both rows pass.
How it affects the rest of your records
The ITA submission is built from the certified 300A (and, for Appendix B establishments, the 300 and 301), so every correction to the log has to be reconciled with what was submitted.
Where 300log helps
300log validates EIN and NAICS formats, produces ITA-ready CSV files for the 300A and for case data, and can authorize auto-filing of 300A data once you connect an ITA API token.
For a quick answer without an account, use the free ITA coverage checker.
Frequently asked questions
Do temporary and part-time workers count toward the thresholds?
Yes. Each individual employed in the establishment at any time during the year counts as one employee, including part-time, seasonal, and temporary workers (29 CFR 1904.41(b)(2)).
Does electronic submission replace posting the 300A?
No. Posting the certified 300A from February 1 to April 30 is a separate duty under 29 CFR 1904.32.
How can we submit to the ITA?
Through the ITA by entering data in the web form, uploading a CSV file, or sending it through the ITA's API. OSHA publishes CSV and API documentation.
Who has to submit to the OSHA ITA?
Establishments with 250 or more employees that keep records, establishments with 20 to 249 employees in Appendix A industries, and establishments with 100 or more employees in Appendix B industries (which also submit 300 and 301 case data).
Sources
Primary regulation and agency guidance this article relies on.
- [1]OSHA Injury Tracking Application informationOccupational Safety and Health Administration · osha.gov(opens in a new tab)
- [2]OSHA Injury Tracking Application frequently asked questionsOccupational Safety and Health Administration · osha.gov(opens in a new tab)
- [3]OSHA ITA CSV documentationOccupational Safety and Health Administration · osha.gov(opens in a new tab)
Written and reviewed by the 300log Editorial Team. Guidance, not legal advice: confirm edge cases with OSHA or counsel.