2.4.13. Command Code TERUP

(1) This sections provides information on the use of the Integrated Data Retrieval System (IDRS) terminal input command code TERUP. The information in this section is a general guide of the input of content.

(2) Audience Customer Service Representatives

(3) Policy Owner Kaschit Pandya

(4) Program Owner Application Development

(5) Primary Stakeholders LMSB, SB/SE, TE/GE and W&I

(6) Program Goals In support of Transaction Perfection when Command Code inputs are done on IDRS, the End of Day (EOD) System provides this command code to allow for the deletion of specified Command Code inputs done in error. This program helps ensure that correct and accurate inputs are processed by IDRS and those that are not correct or do not meet the businesses standards are able to be deleted prior to going into the Quality Review (QR) System.

(1) These instructions describe the input of command codes TERUP (with definer of blank, C, or P). The purpose of these command codes is to allow an employee to delete his/her erroneous entry (i.e. Adjustment, Credit Transfer, FRM77, or some other Command Code input) on the day of input. An employee can only delete their own entries.

(2) For TERUP to delete a entry that was input, the following conditions must be met

• TERUP must input by the same employee that input the entry they would like to have deleted

• TERUP must be input the same day as the entry that is to be deleted. This means the following: If the entry was input between the hours of 12:00 a.m. and 5:59 p.m.Local Campus Time, the TERUP must also be input between those hours. If the entry was input between the hours of 6:00 p.m. to 11:59 p.m. Local Campus Time then the TERUP must be input within those hours.

(3) Input of any of these command codes creates a transaction record that is matched with all of that day's IDRS transactions during End of Day (EOD) processing. Any transaction whose data elements match those same data elements of the TERUP transaction will be deleted. This deletion takes place prior to a DLN being assigned or a transaction being generated for Master File processing. Since the data elements of the TERUP transaction must match the targeted transaction exactly in order for the deletion to be made, it is imperative that those data elements be entered accurately. If not, the match will not occur, the deletion will not take place, and another action must be initiated to negate the effect of the targeted but missed transaction.

(4) When command code TERUP is input and subsequently deletes the transaction during End of Day (EOD), the pending status of the deleted transaction will appear as "DQ", deleted per quality review, on the following day (except CHKCL, & EPLAN).

(5) TERUP will only delete transactions. Any other action that took place at the time the transaction being canceled was entered may need to be reversed by other means—of most concern is control base information.

(6) For all cases where TERUP deleted a transaction, a Quality Review Reject titled REJECTED BY TERUP will be produced and routed to the employee originating the deletion. In the cases where the deletion was unsuccessful, such as duplicate TERUPs and No Match TERUPs, an entry will appear on the Quality Review Reject Index, and the originating employee will be notified of the mismatch.

(1) Use this command code to delete all or part of the entries made to a specific account by a specific employee. You can "tear up" transactions created by the following command codes: ADJ54, BNCHG, EOCHG, INCHG, DRT24, DRT48, FRM77, FRM7A (Except TCs 136, 137, 122 and 126), FRM14/49, CRMNL, FRM34, CHK64, RFUND, IDT48/58, RPM48/58, and CSO48/58. When a credit transfer is being rejected, only the Debit TIN should be input for deletion. It is not necessary to delete the Credit side since the Debit is the primary and controlling transaction. When a CC TERUP is input for a transaction that established a dummy module, the TC902 indicator to Master File is also deleted. If the transaction is re-input, a CC MFREQ must be done to regenerate the TC902. Either TXMOD or ENMOD must precede command Code TERUP. Entries may be deleted in the following combinations:

1. ALL INPUTS FOR A TIN AND FILE SOURCE—Precede CC TERUP with CC ENMOD, which will store the TIN and File Source, and do not input a sequence number.

2. ALL INPUTS FOR A TAX MODULE—Precede CC TERUP with CC TXMOD, which will store the TIN, File Source, MFT, Tax Period and Plan Number (if applicable), and do not input a sequence number.

3. A SPECIFIC TRANSACTION—Precede CC TERUP with either CC ENMOD (for an entity transaction) or CC TXMOD (for a tax module transaction) and input up to three sequence numbers of specific transactions to be deleted. The sequence numbers are the only means of identifying specific transactions for deletion. It will appear on the ENMOD/ TXMOD display of the pending transaction.

(1) Use this command code to delete CC CHKCL (see IRM 2.4.23) inputs only. A successful TERUPC will prevent the check claim data from being sent to RDC. TERUPC does not require a previous TXMOD/ENMOD entry. PLAN or REPORT NUMBERS must be input if the MFT Code is equal to 46 or 76.

(1) Use this command code to delete CC EPLAN inputs only (see IRM 2.4.46). A successful TERUPP will prevent the EPLAN transaction from being processed to the Masterfile.

(1) Error Responses will appear on line 13 in inverse video.

1. PLEASE CORRECT INVALID DATA ON SCREEN—An asterisk will appear to the right of the invalid field. Correct and re-enter.

2. REQUEST DENIED/IMPROPER INITIALIZATION—CC TERUP with a blank definer was not preceded by either CC TXMOD or CC ENMOD.

3. COMMAND CODE DEFINER v INVALID—The invalid definer input is displayed in the message C, F, P and blank are the only valid definers. Correct and re-enter.

4. COMMAND CODE VALID FOR BMF ONLY— TERUPE are valid for BMF only.

5. COMMAND CODE VALID FOR EPMF ONLY—TERUPP is valid for EPMF only.

6. COMMAND CODE INVALID FOR EPMF—TERUPC is not valid for EPMF inputs.

(2) Valid Response REQUEST COMPLETED will appear on line 13. Input data was found to be complete and correct and has been recorded on the gendata file for End of Day (EOD) processing. DOES NOT NECESSARILY MEAN THAT THE DELETION WILL TAKE PLACE. The deletion will take place only if the TERUP data matches the transactions(s) being deleted.

(1) Screen Display

(2) Record Element Description

(1) Screen Display

(2) Record Element Description

(1) Screen Display

(2) Record Element Description