Internal Revenue Manual
IRM 2.4.23 — Command Code CHKCLR and CHKCL
Part 2. Information Technology
Chapter 4. IDRS Terminal Input Section 23. Command Code CHKCLR and CHKCL 2.4.23 Command Code CHKCLR and CHKCL Manual Transmittal March 19, 2025 Purpose (1) This transmits revised IRM 2.4.23, IDRS Terminal Input, Command Codes CHKCLR and CHKCL. Material Changes (1) IRM 2.4.23.1 Program Scope and Objectives: This IRM has been revised to change all instances of Wage & Investment (W&I) to Taxpayer Services (TS). (2) Exhibit 2.4.23-3 Add verbiage to Exhibit 2.4.23-3 For Direct Deposit please refer to 21.2.2-2 ACCOUNTS MANAGEMENT MANDATED IAT TOOLS from the IAT SharePoint website. Effect on Other Documents IRM 2.4.23, dated November 27, 2023, is superseded. Audience LMSB, SB/SE, TE/GE, TS. Effective Date (03-19-2025) Rajiv Uppal Chief Information Officer
Program Scope and Objectives
2.4.23.1 (03-19-2025) Program Scope and Objectives This IRM section provides the instructions for the use of CHKCL. Purpose :This transmits revised IRM 2.4.23, IDRS Terminal Input, Command Code CHKCL . Audience: IRS Tax Technicians and Account Management employees. Policy Owner: Chief Information Officer. Program Owner: Customer Service. Primary Stakeholders: Taxpayer Services (TS) Program Goals: This system manages data extracted from Corporate Account Data Stores (BMF, IMF, EPMF) allowing IRS employees to take specific actions on taxpayer account issues and track status of an account .
Background
2.4.23.1.1 (03-19-2025) Background This IRM and contained sections provide the user the necessary information on how to use the command code CHKCL/CHKCLR.
Authority
2.4.23.1.2 (03-19-2025) Authority The CHKCL command code was developed as a means of manually reissuing refunds.
Roles and Responsibilities
2.4.23.1.3 (03-19-2025) Roles and Responsibilities Project Lead is responsible for Review and implementation of WRs and Updating the contents of this IRM
Program Management and Review
2.4.23.1.4 (03-19-2025) Program Management and Review Program Reports:used to input taxpayer claims for lost or stolen refund checks and requests for photocopies of refund checks. Program Effectiveness:This system manages data extracted from Corporate Account Data Stores (BMF, IMF, EPMF) allowing IRS employees to take specific actions on taxpayer account issues and track status of an account .
Program Controls
2.4.23.1.5 (03-19-2025) Program Controls Access to this program is governed by SACS.
Terms and Acronyms
2.4.23.1.6 (03-19-2025) Terms and Acronyms The table lists commonly used acronyms and their definitions: Word or acronym: Meaning: Example of use: BMF Business Master File Corporate Account Data Stores CC Command Code The use of CC has sped up processing time. EIN Employer Identification Number The business Taxpayer identifier is called an EIN. EPMF Employee Plan Master File Corporate Account Data Stores IDRS Integrated Data Retrieval System IDRS only contains accounts being worked on, not all accounts the IRS maintains. IMF Individual Master File Corporate Account Data Stores MFT Master File Tax (code) The Taxpayer used Form 1040 which is MFT-30. RFC Regional Financial Center Where the data goes TC971 Transaction Code Transaction to Master File TIN Taxpayer Identification Number A TIN can be a SSN or EIN. TXMOD or TXMD Tax Module A Tax Module identifiers are MFT, Tax Period and Report-Plan Number.
Related Resources
2.4.23.1.7 (03-19-2025) Related Resources The following is the primary source of guidance on the CHKCL/CHKCLR program. IRM 2.4.23, IDRS Terminal Input, Command Codes CHKCL/CHKCLR
General Overview for Command Code CHKCL/CHKCLR
2.4.23.2 (07-01-2009) General Overview for Command Code CHKCL/CHKCLR Command code CHKCL/CHKCLR is used to input taxpayer claims for lost or stolen refund checks and requests for photocopies of refund checks. The data is then recorded on tape and sent to the Regional Financial Center (RFC) for processing. Check claims were previously submitted to RFC on Form 3911, Taxpayer Statement Regarding Refund. Command codes TXMOD and CHKCLR are prerequisites for CC CHKCL. A dummy module will satisfy the requirement for having a tax module on IDRS. Case Control for CC CHKCL requires that a control base be present for the Terminal operator inputting CC CHKCL.CC CHKCL will only update a control base, not create one. At the time of input, the IDRS control base is updated with the following activity codes to reflect the action taken: 3911TORDCC—for check claims PHOTOREQ—for request for regular photocopy CERTREQ—for request for certified photocopy IDRS Check Claims are subject to Quality Review. CC TERUPC will reject erroneous inputs only on the day of input. See IRM 2.4.13 for CC TERUPC input instructions. CC CHKCL will generate a TC971 transaction to Master File through End of Day processing if the TC 971 Suppression Indicator is set to Y.
Command Code CHKCLR
2.4.23.3 (01-01-2000) Command Code CHKCLR This command code is used to request the screen format for command code CHKCL It must be preceded by a Command code TXMOD input for which data was made available.
Terminal Responses to CC CHKCLR
2.4.23.4 (01-01-2000) Terminal Responses to CC CHKCLR Error responses (are displayed in inverse video on line 13.) COMMAND CODE DEFINER INVALID—The command code definer (sixth position of the command code) is other than "R" . REQUEST DENIED/IMPROPER INITIALIZATION—CHKCLR was not preceded by a CC TXMOD for which a tax module was found and displayed. If the desired tax module is not present on IDRS, enter CC ACTON to establish a dummy module. EMP NO. INVALID-CASE CONTROLLED—The tax module being addressed contains open control bases but not all are assigned to the terminal operator. MEMO ACCOUNT/MODULE PRESENT—The tax module being addressed is a memo module and input is prohibited. CC ACTON can be used to establish a dummy module and to remove the memo data. NO CONTROL BASE ASSIGNED-INITIATE ACTON—No control bases are present or all control bases are closed. CASE CONTROL INDICATOR INVALID-CC TXMOD has returned an invalid case control indicator. FILE SOURCE INVALID FOR CHKCL—An EPMF file source is invalid with CC CHKCL. Valid Responses:The format for CC CHKCL is returned. (TIN, file source, MFT, and tax period from CC TXMOD are generated on line 1), in addition to the current name and address of the taxpayer on line 2 thru 7.
Command Code CHKCL
2.4.23.5 (01-01-2000) Command Code CHKCL This command code initiates a tape record containing claim data for a lost or stolen refund check or a photocopy request. It also updates IDRS of that fact.
Terminal Responses to CC CHKCL
2.4.23.6 (01-01-2000) Terminal Responses to CC CHKCL Error responses (are displayed in inverse video on line 13.) NO CONTROL BASE ASSIGNED-INITIATE ACTON—The only control base in the tax module being addressed is in " B" (background) status and is assigned to other than the terminal operator. COMMAND CODE INITIALIZATION INVALID—The command code input prior to CC CHKCL input was not CHKCLR. ID INFO CHANGED-RESTART-TIN,MFT,tax period or name control on CHKCL entry does not match that of the preceding TXMOD. Begin again with TXMOD. PLEASE CORRECT INVALID DATA ON SCREEN—Input data has not passed validity checks. Invalid data will be indicated on the screen display as follows: When individual data fields contain invalid entries, the format, complete with all entries keyed in by the operator, will be displayed. An asterisk (*) will be displayed following the invalid field or following the literal which identifies the invalid field. Where an inconsistency exists between two or more fields, each field will be annotated with an asterisk. In order to correct an invalid entry in fields marked by an asterisk, input the correct data as an overlay of the erroneous information and reenter. DATA IN NON-INPUT FIELD-PLEASE CORRECT—Data has been entered in other than those fields reserved for input. SYSTEM ERROR ON ACCESS/UPDATE—An error was encountered when accessing the database. Notify RPA. DMS ERROR-REINPUT DATA—The data requested from the database has already been reserved by a prior request or a quick recovery is in progress. Try reinputting data three times. If still not successful, try again tomorrow. Valid Responses REQUEST COMPLETED—No errors were present in the input and the control base was updated. NO CONTROL BASE UPDATE—CC CHKCL processing was completed but the control base was not successfully updated. Use CC ACTON to update the control base.
Input Format, CC CHKCLR
Exhibit 2.4.23-1 Input Format, CC CHKCLR Screen display of input format for CC CHKCLR Please click here for the text description of the image. Record Element Description ITEM LINE POSITION DESCRIPTION AND VALIDITY 1 1 1–6 CHKCLR
Input/Output Format, CC CHKCL
Exhibit 2.4.23-2 Input/Output Format, CC CHKCL Input screen display for CC CHKCL. Please click here for the text description of the image. Record Element Description ITEM LINE POSITION DESCRIPTION AND VALIDITY 1 1 1–5 COMMAND CODE—CHKCL 2 1 7–18 TIN AND FILE SOURCE—Generated from preceding TXMOD. nnvvnnvnnnvv 3 1 20–21 MFT—Generated from preceding TXMOD. nn 4 1 23–25 PLAN–RPT-NUM—Generated from preceding TXMOD. Note: This field will only show if plan-rpt-num is present otherwise will be space filled. nnn 5 1 27–32 TAX PERIOD—Generated from preceding TXMOD. nnnnnn 6 1 34–37 NAME CONTROL—Generated from preceding TXMOD. vvvv 7–12 NAME AND ADDRESS—Data input in these fields must reflect the most current name and address data as prescribed in IRM 3(17)(42)3. Manual or IDRS Generated Refund checks may have been issued to a name other than that of the account from which they were issued. 7 2 1–30 N1-FIRST NAME LINE— An entry must be present in this field. Enter data beginning in position 1, extending to position 30, overlaying the "+" if necessary. Any characters following two sequential blanks are invalid. Acceptable formats are as follows: (a) SSN accounts—Valid characters are A–Z, blank, hyphen, ampersand and right hand bracket. The first position must be A–Z. For IMF only, hyphen is also valid in the first position if immediately followed by right hand bracket. At least one right hand bracket must be present and must precede the surname. The surname must be at least two valid characters. Enter a second right hand bracket following the surname if a suffix follows on the First Name Line. Examples: JOHN]BROWN SAM]SMITHJR (b) EIN accounts—Valid characters are A–Z, 0–9, blank, hyphen, ampersand and right hand bracket. The first position must be alpha or numeric. If the name control is the first four significant characters of the name line, no right hand bracket is necessary. Otherwise, a right hand bracket must immediately precede the name control. Enter a second right hand bracket following the name containing the name control if a suffix or a partner's name follows on the First Name Line. Examples: FRITZBEES FOOD FACTORY (no bracket required) THE RED]ROOSTER(one bracket required) HARRY]HOOPER&HARVEY HOLDER PTR (two brackets required) 8 3 1–30 N2–SECOND NAME LINE—This field may contain an entry. Data will be entered in position 1 and may extend to position 30, overlaying the "+ " . Valid characters are A–Z, 0–9, blank, ampersand (&), hyphen, slash (/) and %. The first position must be alpha, numeric or %. Two sequential blanks followed by a significant character are invalid. 9 4 1–30 N3-THIRD NAME LINE—Same as Item 8 (N2—Second Name Line). In addition, if Third Name Line is present, Second Name Line must be present. 10 4 1–30 N4-FOURTH NAME LINE—Same as Item 8 (N2—Second Name Line). In addition, if fourth Name Line is present, second and Third Name Lines must be present. Note: If any of the name lines are longer than 30 positions, ignore any characters beyond position 30 . 11 6 1–30 ADD-STREET ADDRESS— This field may contain an entry. If present, City/State/Zip code (Item 12) must also be present. Data will be entered beginning in position 1 and may extend to position 30 overlaying the "=" . Valid characters are A–Z, 0–9 blank, hyphen, and slash (/). First position may contain alpha, numeric, or blank. Blank is only valid in the first position if the entire field is blank. Two sequential blanks followed by a significant character are invalid. 12 7 1–28 CY/ST/ZIP-CITY, STATE and ZIP CODE—Data will be entered beginning in position 1 and may extend to position 28, overlaying the "=" . City data will be followed by a comma, a valid state abbreviation, a blank and the zip code (CITY,STZIP). An entry must be present in this field. City, state and zip code must be valid as follows: CITY—Unless a major city code is input, at least three valid characters must be present. Valid characters are A–Z, and blank. A comma must follow the city field. If a foreign address is being entered, a period and blank space (. ) must be entered following the comma which terminates the foreign city field. Major City Codes is not valid with Foreign Address. STATE—A valid state entry must follow the city and comma. A valid state abbreviation must be present. In the case of a foreign address, a period and a blank (. ) must be entered. The state field must be followed by a blank. There in one exception—if a major city code is used a state abbreviation must not be entered (Example for Dallas—DA, [slashb] 38710). MAJOR CITY CODE must be valid within the Service Center's jurisdiction. See LEM 3(27)(68)0 for list of valid MAJOR CITY CODE. ZIP CODE—Data will be entered following the state and a blank. Entry must be five numeric characters from 00601 to 99999. The last two position may not be 00. If a period and a blank were entered in the state field, indicating a foreign address, the zip code must not be entered.* *The ZIP code will be cross check against the state or major city (if used). If the ZIP code is not valid for the state. an "*" will be displayed following the CY/ST/ZIP. If proper procedures have been followed to document the ZIP code as valid for the state, the crosscheck will be bypassed by overlaying the "Z" in the literal with a "/" . 13 8 1–8 Check Number (or first number of Check Range). An entry must be present if type of Payment Code is D (IDRS), R (release) or M (Manual), otherwise an entry may not be present. If present, valid characters are 0–; 9 or blank and first position must be numeric. A blank followed by a significant character is invalid. CHK #### 14 9 1 T-TYPE OF NON RECEIPT CODE—An entry must be present. Valid characters are as follows: N=Non-receipt of check E=Lost, stolen or destroyed endorsed check L=Lost, unendorsed check S=Stolen, unendorsed check D= Destoyed, unendorsed check P= Request for regular photocopy of check. C= Request for certified photocopy of check. F= Non-entitlement J=Non-receipt of substitute check H = Unendorsed check freeze cancellation credit X = Endorsed check freeze cancellation credit Note: F and J are valid upon implementation of full Recertification 15 9 3–16 YYYYJJJSCTLLLL SCHEDULE NUMBER—An entry must be present. The first nine positions must be in "YYYYJJJSC" format: YYYY = YEAR JJJ = JULIAN DATE SC = SERVICE CENTER T = MASTERFILE TYPE LLLL = LITERAL The last five positions may be numeric, alpha, hyphen or blank. A blank followed by a significant character is invalid. . 16 9 18 TC971 SUPPRESSION IND—An Indicator to either allow a TC971 transaction to be generated or to suppress it. Values are: Y = yes do generate a TC971 transaction N = no do not generate a TC971 transaction 17 10 1–6 MMCCYY- ISSUANCE DATE OF CHECK— An entry must be present. Valid characters are 0–9. The first two positions must be 01–12 and the last two must be 1970 or greater. 18 10 8 P-TYPE OF PAYMENT CODE—An entry must be present. Valid characters are as follows: I = IMF B = BMF D = IDRS (CC RFUND) R= issue M=Manual If TYPE OF PAYMENT CODE is "I" , the file source must be IMF. If the TYPE OF PAYMENT CODE is "B" , the file source must BMF. Note: Type of payment code "R" is valid only for checks issued prior to January 1979. 19 10 10-13 SEQ-SEQUENCE NUMBER—An entry must be present and must be 001–999. 20 10 15-16 DO-Business Operating Division Office Identifier—An entry must be present for NMF accounts. Business Operating Division Office Identifier must be a valid Business Operating Division Office Identifier for Service Center of input. If account is not an NMF account, but Service Center is PSC and a D.O. is input, a D.O. code of 98 or 66 is the only valid entry. 21 11 1–10 $$$$$$$$$$$$$-AMOUNT OF CHECK—An entry greater than ".00" must be present in this field. Input the amount as dollars and cents beginning in position 1. Valid characters are numeric, period (.) and comma (,). $$$$$$$$$$$$$ 22 11 16 Split Refund Ind (SRI). A single field entry used by masterfile to identify each refund to be traced. Valid entries are 2 or 3. # 23 13 1–10 $$$$$$$$$$$$$-AMOUNT OF CHECK—An entry greater than ".00" must be present in this field. Input the amount as dollars and cents beginning in position 1. Valid characters are numeric, period (.) and comma (,). $$$$$$$$$$$$$ 24 13 16 Split Refund Ind (SRI). A single field entry used by masterfile to identify each refund to be traced. Valid entries are 2 or 3. # 25 15 1–10 $$$$$$$$$$$$$-AMOUNT OF CHECK—An entry greater than ".00" must be present in this field. Input the amount as dollars and cents beginning in position 1. Valid characters are numeric, period (.) and comma (,). $$$$$$$$$$$$$ 26 15 16 Split Refund Ind (SRI). A single field entry used by masterfile to identify each refund to be traced. Valid entries are 3. #
CC CHKCL Input Example
Exhibit 2.4.23-3 CC CHKCL Input Example For Direct Deposit please refer to21.2.2-2 ACCOUNTS MANAGEMENT MANDATED IAT TOOLS from the IAT SharePoint website. Input example of CC CHKCL Please click here for the text description of the image. Input example of CC CHKCL Please click here for the text description of the image.
Source: official text