Effective Dates: 06/23/2008 - Present Previous | Next

TN 43 (06-08)

SI 02310.007 Processing Alerts from Computer Matches

A. Procedure for limited development

1. Screening

Use the following chart when you receive an alert generated from a computer matching operation to determine whether limited development applies:

Step	Action
1	Obtain a Supplemental Security Income Display (SSID).
2	Compare the interface data with the data on the SSID and any FO files or records pertaining to the individual. See SI 02310.005B. for definitions of files and records.
3	Use limited development (See SI 02310.007A.2.) if the data were previously developed, and full development (See SI 02310.007B.) if the data were not previously developed. NOTE: Exercise judgment in determining whether SSR coding indicates that the alert data were previously developed. The coding should be sufficient to establish that it refers to the same income/resource or other issue as the alert and must be consistent with the data on the alert. NOTE 2: Always apply Access to Financial Institutions (AFI) procedures when a resource related diary is present on a redetermination or limited issue. See SI 01140.206 for electronic bank verification procedures. Examples of SSR coding which indicate prior development include: • Direct deposit to the same bank account shown on an IRS alert; • An interest posting showing the name of the bank or account number which corresponds to the data shown on an IRS alert; • An earned or unearned income posting which agrees with the income shown on the alert; and • Case characteristic (CG) codes such as REO1 or RE4O or a message in the Remarks field which indicates ownership of the resources reflected on the alert.

Step

Action

Obtain a Supplemental Security Income Display (SSID).

Compare the interface data with the data on the SSID and any FO files or records pertaining to the individual. See SI 02310.005B. for definitions of files and records.

Use limited development (See SI 02310.007A.2.) if the data were previously developed, and full development (See SI 02310.007B.) if the data were not previously developed.

NOTE: Exercise judgment in determining whether SSR coding indicates that the alert data were previously developed. The coding should be sufficient to establish that it refers to the same income/resource or other issue as the alert and must be consistent with the data on the alert.

NOTE 2: Always apply Access to Financial Institutions (AFI) procedures when a resource related diary is present on a redetermination or limited issue. See SI 01140.206 for electronic bank verification procedures.

Examples of SSR coding which indicate prior development include:

•

Direct deposit to the same bank account shown on an IRS alert;
•

An interest posting showing the name of the bank or account number which corresponds to the data shown on an IRS alert;
•

An earned or unearned income posting which agrees with the income shown on the alert; and
•

Case characteristic (CG) codes such as REO1 or RE4O or a message in the Remarks field which indicates ownership of the resources reflected on the alert.

2. Limited development

See SI 02310.047 regarding limited development of tax data.

When requiring limited development for a diary generated from a computer matching operation, and all documentation can be recorded in the MSSICS path, there is no need to document the disposition of the development on paper.

The MSSICS instructions for documentation can be found in Chapter 145 of the Modernized Systems Operations Manual (MSOM). The MSOM sections that pertain to the various computer matching diaries are:

•

Development Documentation (DDOC), MSOM MSSICS 022.012 (for the K6, K7, J3, J5, I8 and 3D);
•

IRS Interface Development (DIRS), MSOM MSSICS 022.013 (for the 5B);
•

Pension Interface Development (DPEN), MSOM MSSICS 022.014 (for the 5H);
•

Savings Bond Interface Development (DSAB), MSOM MSSICS 022.015 (for the SB);
•

State Wage Match Development (DSWM), MSOM MSSICS 022.016 (for the S2);
•

State Wage Match Development (DORW), MSOM MSSICS 022.028 (for the S7).
•

Unemployment Interface Development (DUEM), MSOM MSSICS 022.017 (for the U5);
•

TXIX Facility Interface Development (DXIX), MSOM MSSICS 022.018 (for the D8).

If requiring limited development for diaries not contained in MSSICS, follow these procedures:

If the decision that the data were previously developed was based on . . .	Then document the file . . .
FO file(s)	by consolidating the current and prior file.
FO record(s)	with a copy of the record or an SSA-5002 (RC) which states that the FO record shows prior development. NOTE: If the FO record is an annotated tax data alert, do not place a copy of the alert in file.
SSR coding	with an RC stating the rationale for the decision or an annotated SSID.

B. Procedure for full development

Use the following procedures whenever a computer match alert generates, even if it is worked with a scheduled redetermination.

1. Contact individual

Send an SSA-L3074-U2 (Notice of Appointment) to schedule a personal contact (i.e., phone or face-to-face interview) for limited issue. Otherwise send an SSA-L8003-U2 (Request for Information).

References:

See SI 02310.042 for special IRS alert procedures and special language for the SSA-L3074-U2 when the taxpayer is not the recipient.

See SI 02305.019 and SI 02305.814 for instructions for the SSA-L3074-U2.

See SI 02306.020 for instructions on form SSA-L8003-U2.

2. Confirm data

a.

If the individual confirms information on the alert, document this confirmation on an SSA-5002. Complete any additional development, if necessary, input the new data, and clear the corresponding diary.
b.

If the individual contacts the FO, but does not confirm the information on the alert and does not submit evidence to resolve the issue, contact the data source. Once the data source responds and confirms match data, input the new data and clear the corresponding diary.

3. Notices about planned action

a.

If confirmed match data causes a prospective payment reduction, let the system send an SSA-L8155, Notice of Planned Action, when you input the data and clear the diary.

NOTE: Between the GK cutoff date and the Treasury cutoff date, a Manual Notice of Planned Action, SSA-L8155-U2, is necessary to stop or reduce the next month's check.
b.

Confirmed match data may cause an overpayment, but not a prospective payment reduction. If this occurs, allow the system to send an automated overpayment notice if no AONS exclusion exists. Otherwise, a manual overpayment notice is necessary.

4. Failure to provide information

If the individual fails to contact the FO in response to the SSA-L3074-U2 or SSA-L8003-U2, follow the instructions in SI 02301.235 to issue a Notice of Planned Action, SSA-L8155, to suspend benefits for failure to provide information (N20). See the NOTE in SI 02310.007B.3.a.

SI 02301.235.B explains when not to use N20.

C. Exhibit for computer matching chart

The following chart provides adjudicators with a summary of computer matches.

MATCH	CMPPA?	DIARY	DATA SOURCE	POLICY	DELETE
IRS	YES	5B	PE ODS	SI 02310.045	MS/RZ *
BPD	YES	SB	PAPER**	SI 02310.015	SB
CMS	YES	D8	PAPER**	SI 02310.064	D8
MEF	NO	K6, K7, J3, J5	DEQY	SI 02310.055	K6, K7, J3, J5
Pension	YES	5H	PE ODS	SI 02310.052	5H
RRB	YES		RRB	SI 02310.020
VA	YES		VA	SI 02310.020
UC	YES	U5	PAPER**	SI 02310.065	U5
OPM	YES		OPM	SI 02310.020
Wage	YES	S2 , S7	PAPER**	SI 02310.062	S2 , S7
DHS	YES	3D	PAPER**	SI 02310.018	3D

*The 5B diary deletion must include the clearance of the limited issue and clearance of the 5B diary by MS input at the same time. All limited issue cases are cleared by transmitting a disposition code in the RZ field per SM 01501.025D.1.c.

**D8, S2 S7, SB, U5, and 3D alerts are sent to FOs via wire transmission.

To Link to this section - Use this URL:
http://policy.ssa.gov/poms.nsf/lnx/0502310007

SI 02310.007 - Processing Alerts from Computer Matches - 06/23/2008
Batch run: 09/12/2013
Rev:06/23/2008

Social Security

Program Operations Manual System (POMS)