OUI Navigation

Excel file(s) (.xls, .xlsx) require Excel Viewer.
Portable Document File(s) (.pdf, .PDF) require Adobe Reader.
Word file(s) (.doc, docx) require Word Viewer.

Unemployment Insurance Data Validation (UI DV) Information Center

What is Data Validation?

The purpose of the Data Validation (DV) program is to verify the accuracy of the Unemployment Insurance Required Reports (UIRR) system data.

States report UI data to the U.S. Department of Labor (DOL) on a monthly and quarterly basis under the UIRR system. The UIRR data are used for gathering economic statistics, allocating UI administrative funding, measuring state performance, and accounting for fund utilization. Therefore, it is important that states report UIRR data accurately and uniformly. States use the DV software provided by DOL to conduct the validation and submit results.

States are required to validate reported data every third year, except for data elements used to calculate Government Performance and Results Act (GPRA) measures, which must be validated annually. Items that do not pass validation must be revalidated the following year. The “validation year” coincides with the State Quality Service Plan (SQSP) performance year. It covers data of any reporting period during the twelve months beginning April 1 and ending March 31. Results must be submitted to the National Office by June 10, which allows sufficient time for data validation results to be included in the SQSP process. States that fail DV or do not submit their DV results by the established deadline must address these deficiencies through the SQSP.

What's New_Tilted

DV Results for validation Year 2017 are now available — June 2017

States that believe there is any error in the scores should contact their Regional Office data validation coordinator.

DV Staff Refresher Training — March 2017

US DOL hosted an online staff refresher training on Thursday March 23rd. The recording of this training begins at the 5 minute 50 second mark from the WebEx link listed below. The PowerPoint and a question and answer guide from the session are available under Supplemental Guidance on the right hand side menu of this page. To listen to the recording, visit: WebEx.

Module 3 Upgrade and Module 4 Benefit Timeliness and Quality (BTQ) 3 Change — March 2017

The Module 3 application has been updated to include a “Show All” option that will allow states to edit the entire document as a whole instead of by individual steps. This is intended to assist states that are undergoing modernization to their data management systems and thus require completely new information be included in the Module 3 “road map”. States are reminded to save their work frequently to avoid lost updates if technical issues arise.

For Benefits Module 4 - BTQ 3, an adjustment line has been added to the worksheet to account for a change in the universe size due to withdrawn or dismissed appeals. The software will use the adjusted total to calculate the expected interval size used by the state during their sampling procedure. This change will likely improve the correctness of the interval size and therefore capture more accurate information from the state.

High Dollar Overpayment Threshold Update — February 2016

The High Dollar Overpayments threshold in Population 12 has been increased in the DV SUN system to align with guidance issued in Unemployment Insurance Program Letter No. 08-12, Change 1. The $25,000 threshold will affect lines 112 and 113 in Section A of the Overpayment Detection and Recovery Activities or ETA 227 report. Any state that wishes to validate the population with data prior to the quarter ending on 9/30/2015 that uses the previous $5,000 threshold are encouraged to contact their Regional Office after submitting Population 12 validation results. On an as needed basis, if all other report and sample validations pass, the population score may be manually changed if the SUN system does not recognize the threshold limit used by the state. Existing supplemental guidance on High Dollar Overpayments will be updated on the DV webpage to reflect the new threshold amount.

TOP Validation in Benefits Population 13

Pending Treasury clearance of a permanent method for validating amounts recovered through the Treasury Offset Program (TOP), when building a DV Population 13 extract file, states should not include records for amounts recovered through TOP because such records are considered to contain Federal Tax Information. Also, if those recoveries entail the creation of records for Additions, states should not build such records either. States should go through all the usual steps to conduct the Population 13 validation and submit the results. DOL staff will manually pass the Population if (a) it only fails because Group 13.01, 227 Recovered($) and/or Group 13.04, 227 Additions($) fails, and (b) that failure is due to the discrepancies between reported and validation counts in the six "Federal Offset" cells on line 314 of the 227 and in Additions Total.

Hints_and_TipsFor Validation Year 2017

    The DV software used to track results only saves the most recently transmitted submission

  • DOL saves only the most recent submission of any DV population. If the state submits a failing score in March, it should uncover the cause of the failure and correct it, repeat the validation activity in April, and submit it in May as passing. The only score saved and used for SQSP/CAP purposes is the passing submission from May.

  • Remember – each extract file import changes the cases pulled for the random samples that make up Data Element Validation when “view samples” is selected from the drop down menu for a population.
  • Take a screen shot of the import message screen once the extract file has finished loading

  • This screen appears only once – even though there is a “view import messages” option on the drop down menu on the home screen in the SUN system.

  • The screen shot will indicate that file is error free and all the data was imported correctly, which is helpful for Regional Monitors during reviews at the state agencies.
  • Common Errors include duplicates and “date out of range” messages

  • Before Extract File is imported, the state makes sure dates are in the correct format (“mm/dd/yyyy”) and fall within the report date range of the period being validated.

  • For example, Benefits Population 1 validates the 5159 report: to validate September 2016, the appropriate date range and format would be the weeks claimed between 09/01/2016 and 09/30/2016