Ops Memo 2014-12A: Failure to Verify Social Security Administration (SSA) Data
To comply with program rules, a Social Security Number (SSN) must be provided either orally or in writing for each applicant or client (hereafter called client) applying for or receiving TAFDC, EAEDC and/or SNAP, unless good cause exists, in accordance with 106 CMR 701.230(C) and 362.500(C). An overnight batch process using the State Verification Exchange System (SVES) with the Social Security Administration (SSA) is used to validate the SSN.
Clients with temporarily assigned numbers in the SSN field are processed through a monthly batch process using the Enumeration Verification System (EVS) with SSA.
If a client fails to provide, or verify, mandatory verifications as matched with or obtained from SSA, the case must be closed for failure to provide verifications.
Operations Memo 2014-12, now obsolete, described procedures and DTA staff responsibility for closing a case when a client failed to provide or verify SSA-matched data. This Operations Memo is being reissued because, as a result of the implementation of the Program Integrity (PI) checklist in Build 46.3, this process has become largely automated.
The purpose of this reissued Operations Memo is:
- to advise staff of the changes to the SSN Match process as a result of implementation of the PI checklist functionality in BEACON;
- to describe the automated SSN Verification Match and automated closing process;
- to clarify case manager and FIDM responsibilities;
- to provide examples of case scenarios; and
- to explain how to close cases on BEACON for failure to verify SSA-matched data.
Obsolete Operations Memo
Operations Memo is 2014-12: TAFDC, EAEDC and SNAP – Failure to Verify Social Security Administration (SSA) Data is now obsolete.
|OM 2014-12A.pdf||47.4 KB|