EIN in OSHA ITA Submissions: Why the Field Matters

Every ITA submission must include the Employer Identification Number (EIN) used by each establishment, as required by 29 CFR 1904.41(a)(4). Get it from finance or payroll early, because a parent EIN copied across sites may not match how each establishment is actually registered.

The EIN question often sends safety teams to finance at the worst possible time.

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.

For covered establishments, OSHA requires the EIN used by the establishment in electronic submissions. 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.

Finance holds the EIN and entity records the ITA needs, and early answers from finance prevent the most common last-minute blockers.

Teams sometimes use a parent company EIN without confirming establishment 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.

• Reorganizations and payroll provider changes can create inconsistent EIN history.
• For 300 and 301 case data, OSHA excludes employee names and addresses and health care provider details from the submission (1904.41(b)(9)).

A holding company files for three plants under the parent's EIN. Finance points out that one plant belongs to a subsidiary with its own EIN that appears on that plant's payroll. The ITA profile for that plant is corrected before submission.

1. Collect each establishment's EIN from finance.
2. Reconcile it with payroll records.
3. Add it to the ITA establishment profile.
4. Recheck after reorganizations.

What to keep in the case file:

• 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

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.

• OSHA ITA API vs CSV Upload: Which Submission Method Fits Your Team?
• Correcting an OSHA ITA Submission After You Find an Error
• OSHA ITA FAQs: Submission Dates, Coverage, and Corrections for 2026 Data
• OSHA Recordkeeping for Warehouses: DART, Days Away, and ITA Risks