May 17, 2005



FROM:         Byron Zuidema
                   BYRON ZUIDEMA
                   Regional Administrator

SUBJECT:    Unemployment Insurance Integrity Crossmatch Systems Funding Opportunity

1.  Purpose.  To inform state workforce agencies (SWAs) of the opportunity to submit supplemental budget requests (SBRs) to fund the implementation and/or enhancement of integrity crossmatch systems for preventing and detecting unemployment insurance (UI) overpayments. 

2.  Reference.  ET Handbook No. 336, UI State Quality Service Plan Planning and Reporting Guidelines; and Workforce Development Letters 001-03, SWAs Implementation of Funding for Data Sharing via the ICON with SSA, and 001-03, Change 1.

3.  Links.  This Letter is in the Region 5 website archive at:

4.  Background.  Preventing, detecting and recovering overpayments of UI benefits is a top priority for the Department of Labor.  In calendar year 2004, $34 billion was paid in State unemployment benefits.  Through intensive audits (Benefit Accuracy Measurement) of a small sample of weekly payments, we estimate that about $3.4 billion of these (9.9%) were overpayments, many of which could be prevented or detected by State Workforce Agencies.  However, States detected only about $1.1 billion of the total.  One of the most effective methods of preventing or quickly detecting overpayments is cross-matching of UI claims against data held by other State and Federal agencies.  Supplemental funds for these cross-matches were made available to States in fiscal years (FYs) 2003 and 2004.

5.  FY 2005 Funds Available.  In FY 2005, supplemental funds are again available to States to implement or improve systems for matching UI data with other State and Federal agencies such as departments of motor vehicles, State directories of new hires, and the Social Security Administration, for the prevention or detection of UI overpayments.  States may request up to $100,000 for each data source with which a cross-match will be implemented or improved.  Requests for implementing the real-time data exchange with the Social Security Administration should follow guidelines provided in WDL 001-03.

6.  Guidelines for the Preparation of SBRs.  ET Handbook No. 336 contains instructions for completing SBRs.  SWAs are encouraged to submit SBRs using the following format.  Requests that do not contain complete information, as indicated in the format below, will not be funded.

a.  Description of the Crossmatch/Integrity System.  The narrative description of the system must:

·         Identify the data that will be received from the crossmatch, e.g., name, date of birth, address, etc.

·         Estimate the amount of overpayments the system will prevent or detect in a year.

·         Estimate the percentage of claimants that will be a part of the system/crossmatch.

·         Describe the data system(s) that the SWA will utilize to crossmatch claimant records.

·         Indicate how often the crossmatch will be conducted.

·         Describe assurance(s) that the SWA has received from the owner(s) of the data which demonstrates a willingness to participate in the proposed crossmatch.

·         Provide the planned implementation schedule identifying dates of critical steps through implementation.

b.  Hardware, Software, and Telecommunications Equipment.  The SBR should include descriptions of the hardware, software, and/or telecommunications equipment purchases that are a part of the proposed project.  Descriptions must include the number of items and the cost per item.   A table similar to the following, which contains an example relating to personal computer (PC) acquisition, should be used to provide the required information:



Cost Per Item

Total Cost





The technical specifications of the hardware must also be provided.  Specifications should include any of the following that are applicable:

·         Processors (number, type, size, etc.)

·         Memory (type, size, etc.)

·         Storage (hard drive, controllers, back-up devices, etc.)

·         Hardware peripherals (monitors, network connectivity, tape drives, external modem, etc.)

·         Operating system

·         Warranty, field service, and/or system support specifications.

A detailed narrative description of the software should include the technical specifications of the version to be purchased including the version type and the license type, as appropriate.

All estimated cost information is required.  If any of the above information cannot be provided, the narrative should explain why it is not included.  Ongoing maintenance and telecommunications costs cannot be funded through these SBRs.

c. Staff Needs.  The proposal should identify one-time SWA staff needs and/or contract staff   needs.  Staff needs should include the type of position (e.g., program analyst), the expected number of staff hours, and the projected hourly costs.  All staff funded under this grant must be in excess of base staff, and proposals must state this in writing.  If contract staff are requested, documentation must include the type of position, estimated contract staff hours, and the projected hourly costs for contract staff.  SWAs should include information in a format similar to the following table containing an example relating to system analyst usage.

Position Title

# of Hours

Cost Per Hour

Total Cost

System Analyst




     d.  Other.  The proposal should include and explain any one-time costs for other activities, not   identified above, that will be obtained from vendors – such as telephone companies, Internet service providers, and telecommunications providers.

7.  Project Management.  SWAs should refer to Handbook 336 concerning the time allowed for obligation of funds, specifically, funds used for automation acquisitions.  For example, funds used for purposes of the security verification - Independent Verification and Validation (IV&V) - necessary for the SSA data exchange that meet the definition of automation acquisitions may be obligated through September 30, 2007, and liquidated within 90 days.  Any SBR funds used for non-automation activities must be obligated by December 31, 2005, and liquidated within 90 days.  The liquidation period cannot be extended to fund agency staff.  There are no provisions allowing for an extension of the obligation period.  Requests to extend the expenditure must be submitted in a letter by the state in accordance with 29 CFR 97.23 (b).  The letter should include the Federal grant number for the year of the SBR funding which is located in item 2 on the state’s Financial Status Report, SF–269.  Regional Offices should forward the letter with appropriate recommendations to the National Office, attention Diane Wood.  Requests to extend the expenditure period should be submitted prior to the deadline for obligation of the funds. 

Forms SF-424 and SF-424A serve as the basis for the grant agreement between the U.S. Department of Labor and the SWA, and they must reflect the SWA’s best estimate of costs in each individual category.  If during the performance period states wish to move funds among categories within a project, a new SF-424A must be submitted to the Regional Office for approval if the amount moved exceeds 20 percent of any category in the initially awarded amount for the project.  States may move funds from one project to another, if needed, to implement all funded projects in a timely manner.  However, the same approval requirement applies to movement of funds between projects if the amount moved exceeds 20 percent of either the donating or receiving project as initially funded. 

8.  Action.  State Workforce Administrators are encouraged to take advantage of this funding opportunity and transmit requests for implementation or enhancement of BPC integrity crossmatch systems and include the following:

     a. Two copies of each SBR proposal to the Regional Office, Attention:  Pat Hernandez, by June 15, 2005. 

     b. Notification of project approval will include the total amount approved for the state and a request that a signed SF-424 be submitted to the Regional Office.     

9.  InquiriesQuestions or comments concerning UI Integrity Crossmatch Systems SBRs may be directed to Pat Hernandez on  312.596.5438. Questions or comments about the format of this Letter may be directed to Tom Coyne on 312.596.5435.

10.  Attachments. None

11.  Expiration Date. June 15, 2005

Top of Page