Work Comp EDI: FROI/SROI Filing, Deadlines, and Penalties

Workers’ comp EDI is the electronic reporting system that insurance carriers, self-insured employers, and third-party administrators use to send workers’ compensation claims data to state regulators, built on technical standards published by the International Association of Industrial Accident Boards and Commissions (IAIABC).1International Association of Industrial Accident Boards and Commissions. EDI Claims Instead of mailing paper forms to a state workers’ compensation board, you submit structured digital files that flow directly into regulatory databases. Rejected or late filings can mean penalties, so the details matter.

Who Has a Filing Obligation

Three groups do the actual filing in every state that has adopted EDI reporting: licensed insurance carriers writing workers’ compensation policies, self-insured employers (including municipalities, school districts, and other government entities), and third-party administrators handling claims for either of the first two. The obligation follows whoever controls the claims data, not the employer where the injury happened.

If you’re a small employer with a standard workers’ compensation policy, you rarely touch EDI directly. Your carrier or its claims administrator handles it. EDI becomes your problem when you self-insure, administer your own claims, or act as a TPA for other employers.

FROI and SROI: What You’re Actually Filing

Claims EDI runs on two transaction types. The First Report of Injury (FROI) is the initial electronic notification that a workplace injury or illness has occurred. It carries the basic facts: who was hurt, where and when it happened, what the injury was, and which employer and insurer are involved. The Subsequent Report of Injury (SROI) tracks everything that happens afterward, including benefit payments, changes in disability status, medical developments, disputes, and claim closure.

The FROI opens the file. The SROI updates it for the life of the claim. A single injury might generate one FROI and dozens of SROIs across months or years as benefits are paid, treatment evolves, and the claim moves toward resolution.

Which IAIABC Release Version Applies

The IAIABC publishes the technical standards that define how claims data must be structured, down to each field’s format, character length, and business rules. The current standard is EDI Claims Release 3.1, maintained on an ongoing basis with revised documentation published each January; the most recent publication date is January 1, 2026.1International Association of Industrial Accident Boards and Commissions. EDI Claims Release 3.0 had a final publication date of January 1, 2017, and Release 1.0 dates to February 15, 2002. Some jurisdictions have been slow to migrate, but the trend runs toward 3.1. The IAIABC has also marked the XML ACORD Companion Guides for both Release 3.0 and Release 3.1 as no longer supported, which means reporting entities still leaning on those companion guides need to update their systems.

Before building or upgrading EDI infrastructure, check which release your specific state requires. Submitting in the wrong release format is a guaranteed rejection.

Release 3.1 Reference Documents

Several technical documents sit under Release 3.1. The Implementation Guide frames the overall standard. The Element Requirement Table specifies which fields are mandatory, conditional, or optional for each transaction type. The Edit Matrix defines the validation rules a jurisdiction’s system applies on receipt. The Event Table maps out the claim lifecycle and which transactions correspond to each event.1International Association of Industrial Accident Boards and Commissions. EDI Claims The 2026 publication also adds a Business Scenarios document illustrating how different claim situations should be reported.

Medical and Proof of Coverage EDI

Claims EDI is the piece most filers deal with, but the IAIABC maintains two separate standard sets you may also encounter. EDI Medical Bill Data Reporting Release 2.0, published February 1, 2023, covers reporting of workers’ comp medical bill data at the transaction level.2International Association of Industrial Accident Boards and Commissions. EDI Medical EDI Proof of Coverage Release 3.0, revised each July 1, is how insurers report policy initiation, renewal, and cancellation so states can verify that employers carry active coverage.3International Association of Industrial Accident Boards and Commissions. EDI Proof of Coverage Carriers often have obligations under all three standard sets; self-insureds and TPAs usually only touch Claims EDI, and sometimes Medical.

Data You Need to Pull Together

A compliant FROI or SROI draws from several internal systems. Employee information covers the injured worker’s name, Social Security number, date of birth, and address. Employer information covers the Federal Employer Identification Number, the physical worksite, and the specific policy number in effect on the date of injury. Claim-specific information covers the date and time of the accident, where it occurred, the worker’s occupation, and wage details.

Wage data matters more than it looks. It drives benefit calculations, and a mismatch between reported wages and the indemnity amounts your system computes is one of the fastest ways to trigger a rejection or an “accepted with errors” response.

Injury Coding

Every workplace injury is classified using standardized codes maintained by the Workers Compensation Insurance Organizations (WCIO). Three separate coding systems work together.4Workers Compensation Insurance Organizations. Injury Description Tables Nature of Injury describes the type of harm, so a strain codes differently from a fracture or a burn. Part of Body identifies where the injury occurred, such as lower back, left hand, or head. Cause of Injury captures how it happened, such as a fall, struck by an object, or repetitive motion.

A single injury requires all three codes used together. A warehouse worker who strains their lower back lifting a heavy box gets one nature code (strain), one body part code (lower back), and one cause code (lifting). New reporters sometimes mix the three systems or pull a code from the wrong category. Individual jurisdictions may not use every code on the national reference list, so check your state’s accepted values before filing.

Getting Approved as a Trading Partner

You can’t submit a single production transaction until each jurisdiction recognizes you as an approved trading partner. The steps are consistent across states even when the paperwork differs: complete a trading partner profile, execute a trading partner agreement, pass a round of test transactions, and receive formal approval.

Testing is where most of the work happens. You submit sample FROIs and SROIs against the state’s test database, the system validates them against its edit rules, and errors come back for correction. The cycle repeats until your submissions consistently meet the acceptance thresholds. Some states set explicit benchmarks, such as a 90 percent acceptance rate for FROIs and 85 percent for SROIs before granting production access. Most jurisdictions require an annual review of the trading partner agreement afterward, particularly when contacts, claim administrators, or submission methods change.

Many filers never connect directly to state systems. They route transactions through an approved EDI transaction partner, essentially a clearinghouse that maintains the technical connection and keeps up with each jurisdiction’s format requirements. That makes sense if you file in multiple states. Direct filing means meeting the jurisdiction’s direct-filer criteria and running your own SFTP or equivalent connection.

How Transmissions and Acknowledgments Work

Transmission runs through a secure channel: either a Value-Added Network (VAN), which acts as a secure mailbox where you deposit files for the jurisdiction to retrieve, or a direct Secure File Transfer Protocol (SFTP) connection to the state’s servers. Both methods encrypt data in transit.

After the jurisdiction processes your file, it returns an acknowledgment (commonly called an AKC). Each transaction in your batch comes back with one of three outcomes:

  • Transaction Accepted. The report met all technical and business rule requirements and is in the jurisdiction’s permanent records. No further action.
  • Accepted with Errors. The report is filed, but it carries data issues that need correction in a subsequent filing. Usually minor discrepancies rather than fundamental problems.
  • Transaction Rejected. The report is not filed. The jurisdiction has no record of it, and you need to fix the errors and resubmit. Until a rejected transaction is corrected and accepted, your filing obligation isn’t met.

Monitoring acknowledgment files isn’t optional. Submit 200 transactions, skip the acknowledgments, and you may have 15 rejections sitting unaddressed while deadlines tick down. A compliance team moving real volume needs a daily process for reviewing AKC files and routing rejections to the responsible adjuster.

Why Filings Get Rejected

Rejections follow predictable patterns: mandatory fields left blank, code values the jurisdiction doesn’t accept, invalid event sequencing (reporting a benefit payment before the initial injury, for instance), duplicate transactions where the same claim data was already accepted, and match data discrepancies where key identifying information doesn’t line up with what the state has on file.

The rejection file carries specific error codes pointing to which element failed and why. A missing mandatory field is a different fix than an invalid code value. If the same error code shows up across many claims, the problem is usually systemic, like a misconfigured field mapping in your claims management software, rather than a one-off entry mistake.

Pre-submission validation catches many of these before the file leaves your system. Most EDI software and transaction partners offer built-in edit checks that mirror the jurisdiction’s rules. Running them beforehand keeps acceptance rates high and shaves days off the correction cycle.

Filing Deadlines and Penalties

Every state sets its own FROI deadline. Windows typically run from a few business days to 30 days after the injury. The clock usually starts when the employer learns of the injury, not when the carrier is notified, so a slow handoff between employer and carrier can eat your filing window before you even know about the claim. SROI deadlines are also state-specific and are tied to particular events in the claim lifecycle, such as the first indemnity payment or a change in disability status.

Penalties vary widely. Some states charge per-transaction fines that accumulate for each day a report is overdue. Others penalize based on patterns, hitting carriers whose overall timeliness falls below a performance threshold rather than targeting individual late reports. Dollar amounts range from modest per-transaction fines to significant penalties for systemic noncompliance. Know your deadlines in every state where you file and build workflows that prioritize timely submission.

One point catches people off guard: a rejected transaction does not count as filed. You submitted on time, but the rejection means the jurisdiction has no record. The deadline keeps running until you resubmit and get an accepted acknowledgment back. A buffer of several days between your internal submission target and the statutory deadline gives you room to catch and fix rejections without crossing into penalty territory.

Security and Recordkeeping

EDI transmissions carry Social Security numbers, medical information, wage data, and other sensitive personal details. The HIPAA Security Rule’s technical safeguards at 45 CFR ยง 164.312 require covered entities to put transmission security measures in place that guard against unauthorized access to electronic protected health information moving over a network.5eCFR. 45 CFR 164.312 – Technical Safeguards The rule treats encryption as an “addressable” specification rather than a blanket mandate, meaning you must either implement it or document why an equivalent alternative is appropriate.

In practice, every major EDI transmission method already encrypts. SFTP is encrypted by design, and VAN providers encrypt within their networks. The common gaps show up before and after transmission: claims data sitting unencrypted on a shared drive, acknowledgment files with personal information stored in unsecured email inboxes, or test files with real claimant data sent to vendors during system setup. Your security posture needs to cover the full data lifecycle.

Maintaining a detailed transmission log is a baseline compliance requirement. It is your proof during audits that filings were made on time and accepted. Retention commonly falls in the three to five year range from the date of the transaction, though some jurisdictions or internal risk policies call for longer, especially for claims with permanent disability or ongoing benefits. The log should capture the submission date and time, the transaction type, the jurisdiction, the claim identifier, the acknowledgment status, and any error codes returned. When a regulator asks whether a specific report was filed on time, the answer should take less than a minute to pull.