Electronic USR Submission Testing Phases and Test File Requirements

This guide is intended to help insurers and their authorized third party entities (data submitters) through the steps required to become approved for electronic USR data reporting.

Prior to electronic USR submission testing, data submitters must review and complete all pretesting requirements (see the Getting Started Guide and Checklist for Electronic USR Submission Testing page). The testing process verifies that the data submitter can submit USR data electronically in accordance with the Workers Compensation Insurance Organizations’ (WCIO), Workers Compensation Statistical Reporting Specifications (WCSTAT) and the California Workers' Compensation Uniform Statistical Reporting Plan—1995 (USRP). The WCIRB will not begin testing until all pretesting requirements have been completed.

Timeframe to Complete Electronic USR Submission Testing

All data submitters must complete USR testing with the following USR Types and within the following timelines:

First Reports – 3 months from the valuation date of the first report

Example:

Policy Effective DateValuation Date (1st Report)Required Completion Date
1/1/20247/1/202510/1/2025

Correction Reports (Exposure, Loss, Header, Multiple and Total Corrections) – 3 months after the initial fine list for the first report

Example:

Policy Effective DateInitial Fine List (1st Report)Required Completion Date
1/1/202411/1/20252/1/2026

Subsequent Reports – 3 months after the valuation date of the second report

Example:

Policy Effective DateValuation Date (2nd Report)Required Completion Date
1/1/20247/1/202610/1/2026

Failure to complete testing within the listed timeframes may result in fines for delinquent USRs, escalation to WCIRB management and potential remedial actions.

Electronic USR Submission Testing Process

Step 1: USR validation by Preprocessing and Audit Edits testing. This step involves basic edit errors and validations to ensure that the submitted data meets the specification requirements.

As part of testing, the data submitter must provide examples of the scenarios listed in Exhibit 1 below. While not required, the data submitter is strongly encouraged to use production transactions for testing purposes. If production data is unavailable for a specific testing scenario, fictitious data may be used. If a data submitter chooses to use fictitious data, both policy and USR data must be submitted for testing.

General Testing Process

  1. Data submitter notifies the WCIRB that testing will begin. 
  2. Data submitter submits test file via CDX.
  3. The WCIRB provides test results (typically within 5 to 10 business days).
  4. Data submitter reviews the WCIRB’s feedback, makes system updates to resolve reporting deficiencies and submits an updated test file to the WCIRB.
  5. Steps 3 and 4 are repeated until all identified deficiencies have been addressed. 
  6. The WCIRB will notify the data submitter once the testing phase has been completed.

Electronic USR Submission Test File Format and Reporting

  • All test files must be submitted via CDX, and the Submission Type Code (position 64 of the Electronic Transmittal Record [ETR]) must have a value of T to indicate that it is a test file.
  • The ETR is the required first record in every submission file; it begins with “$!+WORKCOMP+!$” and includes identifying information about the submitter and its data.
    • Please refer to the ETR specifications on the WCIO website for the ETR fields and their attributes. All fields that are required for California must be reported in the ETR.
  • Test files must be submitted in compliance with the WCSTAT specifications published on WCIO.org.

Exhibit 1: Transactions to Be Sampled 

Please note that most data submitters use P and R records.

USR TypeArea of TestingNumber of Examples1
First Reports
  • Exposure only
  • Split exposure for multiple experience modification factors, if possible
  • Combination of exposure and losses
3–5 USRs
Exposure Corrections
  • Add a new exposure (Update Type Code R/A only)
  • Delete a previously reported exposure (Update Type Code P/D only)
  • Change a previously reported exposure value, including split exposure for multiple experience modification factors, if applicable (Update Type Codes P/D and R/A Records)
3–5 USRs
Loss Corrections
  • Add a new loss (Update Type Code R/A only)
  • Delete a previously reported loss (Update Type Code P/D only)
  • Change a previously reported loss value (Update Type Codes P/D and R/A Records)
  • Change a regular claim to an exception claim or vice versa (e.g., subrogation, joint coverage, partially fraudulent and compromised death claim)
  • Change a regular claim to noncompensable or vice versa
4–6 USRs
Header Corrections
  • Change Estimated Audit Code
  • Change USR Expiration Date
At least one example of each scenario
Multiple Corrections
  • Change exposure and loss amount (Update Type Codes P/D and R/A Records)
  • Change loss and header information (Update Type Codes P/D and R/A Records)
At least one example of each scenario
Total Corrections
  • Change total exposure or standard final premium
  • Change loss totals on incurred indemnity/incurred medical
At least one example of each scenario
Subsequent Reports
  • Add a new loss (Update Type Code R/A only)
  • Delete a previously reported loss (Update Type Code P/D only)
  • Change a previously reported loss value (Update Type Code P/D and R/A Records)
  • Change a regular claim to an exception claim or vice versa (e.g., subrogation, joint coverage, partially fraudulent and compromised death claim)
4–6 USRs

1 Number of examples requested during testing is based on the insurer’s policies and expected book of business. The WCIRB may request additional examples if determined necessary.