FPLS Minor Release 06-01
Questions & Answers from
Manifest and Specification Conference Calls

NDNH

Question 1: With the changes to verification of SSN/Name, please explain how the name information that is submitted on Quarterly Wage (QW) records affects the verification and posting of data in the NDNH.
Answer 1: In current QW processing, first the SSN is checked to determine if it has been issued by SSA. This is known as the High Group Check. If the SSN has not been issued, the record is flagged as Unverified. If the SSN has been issued, the SSN/Name combination is submitted to SSA for verification. Records that pass SSA's verification are posted to the NDNH as Verified.

Those records with SSN/Name combinations that do not verify at SSA are resubmitted with the First and Last Name reversed. Records that verify are stored on the NDNH as Verified and a warning code (0004) is returned to the submitter, which notifies them that the SSN/Name combination was verified by transposing the First and Last Names.

If the SSN/Name still does not verify, the submitted name information is checked to determine where to post the QW record.

• For records with at least one character in the First Name and no Middle Name:
• If the Last Name is less than seven characters long, the record is posted as Non-Verifiable.
• If the Last Name is seven or more characters long, the record is posted as Unverified.
• For records with at least one character in the First Name and at least one character in the Middle Name:
• If the Last Name is less than four characters long, the record is posted as Non-Verifiable.
• If the Last Name is four or more characters long, the record is posted as Unverified.

CSENet

Question 1: The two CSENet case closure codes (GSC01 and GSC04) that are scheduled for deletion appear to be valid case closure codes. Why are they being deleted?
Answer 1: The two case closure codes noted above were determined to be obsolete, based on revisions to 45 CFR 303.11 published in 1999. An analysis of the existing CSENet case closure codes determined a need to add new case closure codes, as well as deleting the two identified for this release.

The background and analysis for these changes can be found at the following URL: http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenetspec03-01.htm#appA

Federal Tax Offset

Question 1: In regard to Ref #2149 to exclude cases that are certified on the Federal Offset (FO) file from an insurance match, is it okay for states to hard code the 'INS' exclusion indicator into their system now?
Answer 1: No. The insurance match project workgroup is currently gathering requirements for what OCSE's role will be in conducting the insurance match. It has not yet been determined if cases for insurance match will be certified through the FO system. Until this is confirmed, the 'INS' exclusion indicator should not be hard coded into a state's existing exclusion indicator until OCSE notifies them otherwise. If a state sends a transaction using the Case Submission and Update File with an 'INS' exclusion indicator populated in the Exclusion Indicator field, that record will be rejected and returned to the state.