← All filing resourcesEvery rejection reason

Why OSHA ITA Rejects a CSV File

The rejection causes OSHA publishes for ITA CSV uploads, with the exact codes, in one place. Check a file in your browser before you submit.

Why this happens

ITA reports a failure by email after the upload queue processes your batch, so a small formatting mistake costs a round trip instead of a correction. OSHA documents the most common causes, and every one of them is checkable before you submit.

What RuleTally checks
Administrative checks based on the current published ITA file guidance.
  • Decimals or commas in number fields — OSHA rejects the file; use whole numbers only
  • ZIP codes that lost a leading zero — Excel strips them on every re-open
  • size must be 1 (<20), 21 (20–99), 22 (100–249) or 3 (250+), not the headcount
  • establishment_type must be 1 (non-government), 2 (State) or 3 (Local)
  • no_injuries_illnesses must be 1 (had cases) or 2 (had none) — 1 means yes
  • djtr_num_tr must be positive when incident_outcome is 3; blanks and zeros are rejected
  • establishment_name must exactly match the 300A submission in your ITA account
  • A 300/301 batch will not process until that establishment has a processed 300A
  • Header names, header order, dates, EIN, NAICS and 300A total consistency

How to fix it

  1. 01

    Open the file in RuleTally; it is parsed in your browser and not uploaded to us.

  2. 02

    Work through each finding by row and field, correcting the source export rather than the copy.

  3. 03

    Re-run the check until only findings you have judged remain.

  4. 04

    Test the corrected file in OSHA’s ITA Preview Environment before submitting for real.

Check the whole file locally.

RuleTally shows the row, field, expected format, and official source without uploading the employee file.

Open local preflight

Official references

Related guides