Page 270

Page | 269

14215 PROCESSING IEVS HITS IN INTERIM MONTHS

A. IEVS Hits that are Primary Source Changes Social Security income (BNXV), Medicare premium amounts (BNXV), SSI income (SDX), Reemployment Assistance (UNEM-formerly called Unemployment), and disability (BNXV) information received through IEVS are considered verified upon receipt. BNXV, UNEM, and SDX are primary sources. IEVS hits from these sources must be acted on promptly.

An ACCESS mail is sent to the Benefits Specialist and Supervisor on the 10th of the month for all unresolved BNXV, SDX, and UNEM hits that were received prior to the 10th of the month. Another ACCESS mail is sent on the 17th of the month if there are new unresolved IEVS hit received after the 10th of the month or any IEVS hits that are still unresolved from the first ACCESS mail.

If an IEVS hit is received from one of the above sources, the following actions need to be taken: 1. Review the information and compare it to the budgeted information in the record; 2. If the income is already being budgeted, complete the IEVS screen with an action code of “BN”. No further action is required. 3. If the income is not currently budgeted, change the source code to the appropriate primary source (BNXV, UNEM, SDX) and budget the change, follow 10 adverse action times if it is a negative change. Complete the IEVS screen with the appropriate action code. 4. Complete overpayments, if appropriate.

B. IEVS Hits that are Not Primary Sources IEVS information that is not considered verified upon receipt is wage information from DLR (JOBS). These IEVS hits must be completed within 45 days.

An e-mail is sent to the Benefits Specialist and Supervisor for any IEVS hit that is unresolved 45 days after the IEVS hit is stored. When an IEVS hit is received, the following actions need to take place: 1. Review the information and compare it to the reported/budgeted information in the record; 2. Resolve discrepancies via a contact with the household or appropriate source 3. Correct the case information following budgeting procedures and adverse action time frames (source code is OTH); and 4. Complete overpayments, if appropriate.

Example: A household reports a new household member on June 5 but fails to verify his/her income. The verification request is sent June 6 (within 5 days of the reported change) requesting verification be submitted by June 16. If the customer does not submit the required verification by June 16, the case is closed for July with a notice sent no later than June 20th following the 10 day adverse action time frames.

Example: A household reports a new household member on June 15 but fails to verify his/her income. The verification request is sent on June 15 requesting verification by June 25. If the form is not returned by June 25, the case will be closed for August following the 10 day adverse action time frames.