L.1
FCR Acknowledgement Suppression and FCR-to-FCR Proactive Match Consolidation of Associated Member IDs |
Option to suppress FCR input transaction Acknowledgement Records – State staff may set parameters based on their unique requirements and needs. Provides the ability to restrict some of the data returned by the FCR.
Proactive Match Consolidation – Provides the state the option to suppress multiple FCR-to-FCR Proactive Match Records for the same person in the same case. Enables the state to restrict some of the data returned by the FCR. |
Suppression – Advantageous if state staff establishes a logical default for records not returned. However, a logical default cannot be assumed if both accepted and pending acknowledgement records are suppressed. Suppression of both accepted and pending acknowledgements will not allow states to distinguish between records pending on the FCR from those that have been accepted. Reference TAG Section 7.4, How to Work With Response Records.
Consolidation – Beneficial to states because it reduces the amount of redundant data returned to states by the FCR. States use this process to consolidate the information returned for a particular case and ease the programming burden so that there is less chance of storing duplicate information. |
| Back to Options Matrix by State |
L.2
FCR Data Inconsistency File |
Provides information on specific data inconsistencies for all active participants on IV-D cases with verified SSNs. Participants with an FV Indicator are excluded. This process allows corrections to be made to improve SCR and FCR data quality. |
Beneficial in identifying data anomalies in person records that allow states to correct participant data within their system. The data anomalies identified in the FCR Data Inconsistency file include: person is identified as a PF but his case record indicates an order exists; person is identified as an adult member of a case but the person's age is less than 11 years old; person's sex code is neither ‘F’ nor ‘M’, or person is identified as a PF but sex code is ‘F’. This file is sent to states on a quarterly basis. Reference TAG Section 7.3.3, How the FCR can Help with Case Clean Up. |
| Back to Options Matrix by State |
L.3
FCR Reconciliation File |
Provides all case and person data stored on the FCR for a state. Enables state staff to verify their case and person information stored on the FCR. |
Recommended that state staff request an FCR Reconciliation File once a year to facilitate synchronization between the SCR and FCR. This file returns case and person data stored on the FCR that may be compared to the SCR in an effort to stay in sync with the FCR. Additionally, the FCR Reconciliation file is helpful for states that have not regularly transmitted data to the FCR. The Reconciliation file is returned to states upon request. Reference TAG Section 7.3.6, How to Stay Synchronized with the FCR. |
| Back to Options Matrix by State |
L.4
NDNH-to-FCR Proactive Match Return Same State Data |
Provides the state the option to receive through the Proactive Match process all appropriate NDNH records, including those records the state sent to the NDNH. States may request all W-4, QW and UI records or any combination of the three record types. |
Developed for those states that do not receive new hire data on a regular basis from their SDNH. This process allows states to receive W-4, QW and UI information in a more timely manner, which increases the possibility of locating an NCP and initiating income withholding orders more quickly. |
| Back to Options Matrix by State |
L.5
NDNH-to-FCR Proactive Match Return Bad Address Data |
Provides the option to receive incorrect addresses and the Address Scrubbing Code on NDNH Proactive Match responses. Some states feel the address is still useful, even though it failed address scrubbing. |
Helpful as a last resort for address data. Many states expressed the need to receive the information maintained on the NDNH even if it is incomplete because it may result in a Locate lead. State systems should allow for the address scrubbing code so that caseworkers can see that there may be a potential problem with the address. |
| Back to Options Matrix by State |
L.6
IRS-1099 Locate |
Provides tax return information from the IRS. States may find this information useful in their efforts to locate CPs, NCPs and PFs; set the amount of, or modify, a child support obligation; or to enforce a child support obligation. |
Useful because it provides income and asset information. Additionally, the source of the asset amount is reported in this record. Project 1099 data responses require that states enter into an agreement with OCSE to obtain this data. For security reasons, Project 1099 data are returned to states in a file separate from all other responses. Many states send Locate Requests to 1099 on a case-by-case basis, once all other Locate sources have been exhausted. States have found that the MSFIDM data provides more current asset information. Reference TAG Section 7.3.2.4, Internal Revenue Service Locate Requests. |
| Back to Options Matrix by State |
L.7
SVES/AWR Locate |
State Verification and Exchange System (SVES) data expands the locate function of SSA as an external Locate source by providing states with access to Title II, Title XVI, Prisoner and Annual Wage Reporting information (W-2) |
OCSE's daily interface with SVES provides information to states in a timelier manner than the current SSA external Locate interface. Title II and Title XVI records contain address information necessary for locating NCPs. Title II responses contain information regarding disability income and SSA benefits, which can be used to initiate income withholding orders. Title XVI responses include SSI benefits, which cannot be withheld for child support purposes. However, this data may be helpful to determine an order modification in the review and adjustment process. Prisoner data provided by SVES can be helpful in locating NCPs particularly if the NCP is incarcerated in another state. This data can be used to determine location, work status, and parole information. Information provided by the W-2 database includes a person's employment and self-employment information. Reference TAG Section 7.3.2.6, Social Security Administration Locate Requests./td>
|
| Back to Options Matrix by State |
L.8
NDNH ‘CS' Locate Return Same State Data |
Provides the state the option to have CS-type Locate Requests return NDNH data that their own state submitted. |
Used by states as a backup for proactive matching. States may submit NDNH Locate Requests to receive W-4, QW and UI information. Prior to this enhancement, the CS locate request type returned QW records provided by Federal agencies and other states, and IRS and Project 1099 data. Now states may request a CS locate type and receive this same information, in addition to their own state's data. This is helpful for those states that do not store QW and UI information as provided by their State Employment Security Agency (SESA) and for those states that can receive new hire data more quickly from the FPLS than from their SDNH. |
| Back to Options Matrix by State |
L.9
SVES Proactive Matching |
Provides the State the option to have FCR request and return SVES information automatically when a 'PF' or 'NP' in a IV-D case is added or changed, under the qualifying conditions. A further option will return “CP' and/or 'CP' as well as the 'PF' and 'NP'. |
This change will expedite the States’ ability to identify obligors who are receiving SSA benefits, which should increase collections, obligations, paternities and Locates. The change will provide States the option to receive through proactive matching, Title II, Title XVI and Prisoner data from SVES for persons in IV-D cases with no family violence indicated. |
| Back to Options Matrix by State |
L.10
Filter Negative Locates |
Provides the State the option to suppress most negative (that is, no match) 'CS' Locate Responses. A further option allows the State to suppress such Negatives, but to receive a Negative if it is the last Locate Response in a Locate (with Locate Closed Indicator). |
This change should reduce the number of duplicate Locate Responses being returned to States, reduce State CPU processing time, reduce worker alerts, reduce negative responses as new Federal and private sources are added, and save workers' time in reviewing old data. States have often indicated that a significant amount of redundant data is returned, requiring that States either filter the duplicates or send repetitive notices to caseworkers. |