Part 2. Information Technology

Chapter 4. IDRS Terminal Input

Section 28. Command Codes STAUP, STATI and STATB

2.4.28 Command Codes STAUP, STATI and STATB

Manual Transmittal

December 01, 2022

Purpose

(1) This transmits revised IRM 2.4.28, IDRS Terminal Input, Command Codes STAUP, STATI and STATB.

Material Changes

(1) The following outlines changes made to IRM 2.4.28, IDRS Terminal Input, Command Codes STAUP, STATI and STATB.

IRM Subsection Description
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
IRM 2.4.28.7.1, CC STAUP, STATI, STATB Input Items Revisions to paragraph (7):

  • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  • Converted paragraph (e) to a bullet list for clarity.

  • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  • Converted paragraph (f) to a bullet list for clarity.
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
IRM 2.4.7.3, CC STAUP, STATI, STATB Tax Module Requirements (IMF, BMF, IRAF)

  • Revised paragraph (4) items (a), (e), and (h) to reflect process changes allowing Field Collection (ICS) to request Status 22 when the current Status is 26.

  • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡"≡ ≡ ≡ ≡" ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

(2) Editorial Changes:

  • Added the title of the IRM subsections to citation;

  • Changed "latest (most current)" or "latest" to "current" for clarity;

  • Changed "earliest (oldest)" to "oldest" for clarity;

  • The terms "Assignment Code" and "Branch Group code" are used throughout for consistency. Prior versions had varied uses of Number or Num or CD and different capitalizations;

  • Typographical and plain language changes were made without altering the meaning of the content.

Effect on Other Documents

IRM 2.4.28, dated April 01, 2020, is superseded.

Audience

LB&I, SB/SE, TE/GE, W&I.

Effective Date

(01-01-2023)


Nancy Sieger
Chief Information Officer

2.4.28.1 (12-01-2022)

Program Scope and Objectives

  1. Purpose: This IRM section describes IDRS Terminal Input Command Code STAUP.

  2. Audience: All IRS business units.

  3. Program Owner: Account Services, which is under the Director, Internal Management

  4. Primary Stakeholders: Wage & Investment (W&I), Large Business and International (LB&I), Small Business Self Employed (SB/SE), and Tax Exempt and Government Entities (TE/GE)

  5. Program Goals: This IRM provides the fundamental knowledge and procedural guidance to allow a user to request IDRS status updates.

2.4.28.1.1 (01-01-2023)

Background

  1. Status update requests are accomplished via Command Code STAUP. The command code is used for modules that are or have been balance due modules. Command Code STAUP is valid for IMF, BMF, IRAF, and NMF. Command Code STAUP can update certain IDRS statuses real-time or request that a specific status and notice be issued during a weekly update. See IRM 2.4.28.2, CC STAUP Notice Requests.

  2. Input of Command Code STAUP causes a history item to be generated in the Action History Section of the tax module. The history item contains the current date, the terminal operator employee number, the Action History Source Code and the activity code STAUP nnnn. (nnnn = the status requested plus the number of cycles delay, if present, requested by the terminal operator.)

  3. Input of Command Code STAUP also causes the tax module's IDRS status to update real-time. The module updates to either status 48, status 50, or the status requested as appropriate.

  4. In addition to updating statuses, STAUP has the capability of updating assignments in the Entity Case Assignment Section and marking the last issued CP 504 notice as destroyed in the Notice History Section.

  5. Command Code STAUP will not process modules with MFT Codes 32, 40, 42, 46, 56, 68, 76, 84, 85 and 86. Also, modules with MFT Code 44 and EO-25-STATUS-IND = 1 will not be processed.

  6. Command Code STAUP will process MFT Code 14 for the new Annual Form 944 of the Quarterly Form 941 which has MFT-CD = 01 for a BMF TIN Account. The MFT-CD 14 will also be processed for an NMF Account, See IRM 2.4.28.7.4, CC STAUP NMF Status Update Request, when executing CC STAUP and CC STATB.

2.4.28.1.2 (01-01-2023)

Authority

  1. IRM 5.1.20, Field Collection Procedures - Collection Inventory, provides an overview of the systemic collection inventory routing systems.

2.4.28.1.3 (01-01-2023)

Responsibilities

  1. Applications Development is responsible for the maintenance of Command Code STAUP.

2.4.28.1.4 (01-01-2023)

Program Management and Review

  1. Command Code STAUP validates the user input and provides either a “Request Completed” message or Error Codes, prompting the user to correct the information.

2.4.28.1.5 (01-01-2023)

Program Controls

  1. SACS controls all IDRS user accesses and permissions.

2.4.28.1.6 (01-01-2023)

Terms/Definitions/Acronyms

  1. Commonly used Acronyms in this IRM.

    Acronym Meaning
    BMF Business Master File
    CC Command Code
    CSED Collection Statute Expiration Date
    FC Field Collection
    EPMF Employee Plan Master File
    IDRS Integrated Data Retrieval System
    IMF Individual Master File
    IRAF Individual Retirement Account File
    NMF Non-Master File
    TC Transaction Code
    TIF Taxpayer Information File
2.4.28.2 (01-01-2023)

CC STAUP Notice Requests

  1. By requesting a notice status, STAUP will interrupt, delay, accelerate or skip routine notice issuance. If a notice is requested, the number of cycles delay before issuance of the notice is required. An automatic status delay update to the next sequential notice status, or a request to mark the last issued CP 504 notice as destroyed and request another can be requested for IMF, BMF, and IRAF (not NMF) cases. If the module qualifies for issuance of the notice requested, the weekly update will cause the notice to issue when the number of cycles delay has expired.

  2. The statuses (notices) progress as follows:

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  3. If the status requested is a notice status, the status generated by CC STAUP will be as follows:

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  4. The weekly analysis will generate the appropriate notice and status when the number of cycles delay input has expired, or earlier depending on control base information.

    1. If the requested number of cycles delay is 0-9, the delay is not affected by the absence, presence, or status of any control base. The delay is released when the input number of cycles lapse.

    2. If the requested number of cycles delay is 10-15, the delay may be released earlier depending on control base information as follows: After 9 weeks delay, if there is at least one open control base, release the delay after the full number of cycles input or, if there is no open control base, look to release the delay the later of 9 weeks after input (status cycle + 9), or 9 weeks from the most recently closed control base.

    3. Define "minimum number of cycles delay" as the number of cycles the STAUP will delay the notice regardless of the absence, presence, or status of any control base. It is also the earliest the delay will release. The value of minimum is 9.

    4. Define "balance of cycles delay" as the number of cycles over the minimum delay, during which the delay may be released depending on control base information.

    5. Define "maximum number of cycles delay" as the total number of cycles input. It is equal to the minimum number of cycles delay + the balance of cycles delay.

    6. Control bases do not extend the delay past the maximum number of cycles requested.

  5. A request to mark the CP 504 notice as destroyed ("D" ) will cause the Notice Suppress Code for the latest CP 504 entry in the Notice History Section to be updated to 4. A request to mark the notice as destroyed and to request another ("R" ) will cause the Notice Suppress Code to be updated as above, and will be treated like a status request 58.

  6. Command Code STAUP will only prevent an erroneous IDRS notice if it is input by the Friday before the erroneous notice is scheduled to generate (17 days prior to the 23C date).

2.4.28.3 (01-01-2011)

CC STAUP "I" DEFINER—Terminal Input

  1. The command code STAUP with a definer of "I" must be input prior to using the command code STATI (definer blank) initially. The prerequisite will return a format screen with literals displayed on lines 2 & 3 (See Exhibit 2.4.28-2, CC STATI, STATB Format Screen Output). The terminal will then be ready for status update requests.

2.4.28.4 (01-01-2011)

CC STAUP "B" DEFINER—Terminal Input

  1. The command code STAUP with a definer of "B" must be input prior to using the command code STATB (definer blank) initially. The prerequisite will return a format screen with literals displayed on lines 2 & 3 (See Exhibit 2.4.28-2, CC STATI, STATB Format Screen Output). The terminal will then be ready for status update requests.

2.4.28.5 (01-01-2011)

CC STATI, STATB Terminal Input

  1. Each input field of the format screen will be preceded by a > symbol. The cursor will move automatically to the next field when field input is completed or by use of the tab key.

  2. The Status Request field of the format screen will display an asterisk signifying automatic default to the next sequential status unless overwritten by a specific status request.

  3. STATI and STATB both accept up to 17 lines of input, one tax module to a line. Every screen line will be validated and processed. If all input is valid and no errors occur, the screen will be returned with " STATI" or "STATB" on line 1, the literals on lines 2 & 3 and "REQUEST COMPLETED" on line 24.

  4. If a definer other than I, B, or S is erroneously input, the screen will be returned with the message "INVALID DEFINER" on line 24. The exception is definer "F" , which if erroneously input will return the message "DEFINER F INVALID - PLEASE USE I OR B." Any status update request inputs on lines 4 through 20 will not be processed and will be redisplayed.

  5. If a data item on a screen line is in error or invalid, the item in error and an error code at the end of the screen line will be displayed in inverse video. Up to three alpha characters may appear as error codes for a screen line (See IRM 2.4.28.9, CC STAUP, STATI, STATB Error Codes for an explanation of the error codes.) The message "PLEASE CORRECT INVALID DATA" will be displayed on line 24. All valid input lines will have been processed and will disappear from the screen.

  6. A repeat indicator ("R" ) may be input in the second position of screen lines 5 through 20. This will indicate that the TIN and File Source and possibly other information from the prior line will be repeated on the "R" line. The position of each data item on the line will be checked. If it is blank, the data from the preceding line will be used. Thus the terminal operator will have to input only the Tax Period, Status Requested, Number of Cycles Delay and those items which differ from the previous line.

2.4.28.6 (01-01-2011)

CC STAUP "S" DEFINER—Terminal Input

  1. STAUP with a "S" definer will accept a single line of input using only the requested status and number of cycles delay. To use STAUP in this manner (See Exhibit 2.4.28-4, CC STAUP Command Code Definer “S”), the command code TXMOD will be a prerequisite. The TIN must also be present on line 1. Invalid data or entries will be handled the same way as multiple inputs, all data fields being displayed. Error codes at the end of the screen line and erroneous data fields will be displayed in inverse video.

  2. The first field on line 2 (Positions 1 & 2) is multi-functional. If the input is less than or equal to 15, an automatic status delay update to the next sequential status for the displayed number of cycles is being requested (not allowed for NMF cases). If the value in this field is greater than 15, the request is for update to that specific status for the number of cycles displayed in the next field.

2.4.28.7 (01-01-2011)

CC STAUP, STATI, STATB Validity Checks

  1. Following are the validity checks for CC STAUP, STATI and STATB input items, status update requests, and Tax Module requirements.

2.4.28.7.1 (01-01-2023)

CC STAUP, STATI, STATB Input Items

  1. The TIN must be a valid TIN. If the TIN is valid it is checked for consistency with the file source, if present.

  2. If using STATI, all the accounts processed must be IMF. If using STATB, none of the accounts processed can be IMF. IMF and non-IMF accounts can not be processed in the same batch.

  3. The Name Control must match the name control on the TIF.

  4. The employee must be profiled to access the IMF/non-IMF account requested.

  5. The MFT and Tax Period must be valid, and consistent with each other and with the TIN.

  6. The Status Requested and Number of Cycles Delay will be checked for each input line as described below.

  7. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    5. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

        1. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

        2. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

        3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

        4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    6. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

      • ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2.4.28.7.2 (01-01-2023)

CC STAUP IMF, BMF, IRAF Status Update Request

  1. For IMF, BMF and IRAF status update requests, the requested status must be one of the following:

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2.4.28.7.3 (01-01-2023)

CC STAUP, STATI, STATB Tax Module Requirements (IMF, BMF, IRAF)

  1. A request will not be accepted for a module created or updated via the online MFREQ or RECON process.

  2. If the request is for an automatic status delay update to the next sequential status, the current IDRS status must not be 22, 24, 26, 48, or 50.

  3. If the requested status is 20, 56 or 58, module must meet the following conditions:

    1. Master File first notice status (19 or 21) must be present on the module.

    2. Number of cycles must be present. The valid range for the number of cycles is 00 through 15.

    3. If the current Master File status is 19 or 21, the current date plus the number of cycles entered must be subsequent to the return due date.

    4. The status request must be equal to or later than the last notice issued. See IRM 2.4.28.2, CC STAUP Notice Requests for notice progression.

    5. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    6. The current IDRS status must not be 14, 22, 24, 26, 41-46, 60, 71, 72 (except with COLL-CLOSING-CD 76/77) or 91.

  4. If the requested status is 22:

    1. The current IDRS status must be 20, 22, 24, 26, 56, 58.

    2. Master File first notice status (19 or 21) must be present.

    3. Number of cycles must be present with the requested status. The valid range for the number of cycles is 00 through 15.

    4. If the current Master File status is 19 or 21, the current date plus the number of cycles entered must be subsequent to the return due date.

    5. The number of cycles entered must be 00 if the current IDRS status is 22, 24, or 26.

    6. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    7. The current IDRS status cannot be 60.

    8. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    9. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    10. If the current IDRS status is 72, then the COLL-CLOSING-CD must be 76 or 77.

  5. If the requested status is 24:

    1. The current IDRS status must be 26.

    2. The number of cycles entered must be 00 or blank.

    3. Master File first notice status (19 or 21) must be present.

    4. If the current Master File status is 19 or 21, the current date plus the number of cycles entered must be subsequent to the return due date.

    5. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    6. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  6. If the requested status is 26:

    1. The current IDRS status must be 26.

    2. The number of cycles entered must be 00.

    3. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    5. Master File first notice status (19 or 21) must be present.

    6. If the current Master File status is 19 or 21, the current date plus the number of cycles entered must be subsequent to the return due date.

    7. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  7. If the requested status is 51:

    1. The number of cycles must not be entered.

    2. Master File first notice status (19 or 21) must be present.

    3. The current status must not be 22, 24 or 26.

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  8. If the requested status is 71:

    1. The number of cycles must not be entered.

    2. A TC 480 without a subsequent TC 481, 482, 483, 781, or 788 must be present in the module.

    3. Master File first notice status (19 or 21) must be present.

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  9. If the requested status is 91:

    1. The number of cycles must not be entered.

    2. The current IDRS status must be 22, 24, 26 or 60.

    3. A TC 914 or 916 without a subsequent TC 912 or 917, respectively, must be present in the module, or a TC 918 without a subsequent TC 919 must be present in the entity.

  10. If the request is to mark a CP 504 notice as destroyed:

    1. MF First Notice status (19 or 21) must be present on the module.

    2. The last CP 504 notice must have been issued in the past two cycles.

    3. The number of cycles must be blank.

  11. If the request is to mark a CP 504 notice as destroyed AND to request another CP 504 notice (status 58):

    1. The requirements in Items (a) and (b) under (10) above must be met.

    2. The number of cycles must be 00 through 15.

    3. The current IDRS status must be 58.

    4. ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

2.4.28.7.4 (01-01-2011)

CC STATB NMF Status Update Request

  1. For NMF status update requests, the requested status must be one of the following:

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

  2. For NMF status update request, MFT-CD 14 will be processed by CC STATB.

  3. Listed below are the module requirements for NMF that must be met before the status update request is accepted.

    If the requested status is 12 ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    The number of cycles must not be entered.
    If the requested status is 23 ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    The number of cycles must not be entered
    If the requested status is 26 The number of cycles must not be entered
    If the requested status is 29 The number of cycles must not be entered
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    If the requested status is 89 No restrictions apply at this time.

2.4.28.7.5 (01-01-2011)

CC STAUP, STATI, STATB Validation And Processing

  1. All data items on a screen line will be validated and processed. When a line has been correctly processed, it is blanked out. If all input lines are processed correctly, a blank screen will be returned with the message "REQUEST COMPLETED-(SC Abbreviation)." The service center abbreviation is that of the service center the request was routed to. If a data item is invalid, that item and an error message (signified by an alpha character) will be displayed in inverse video. Up to three error messages (characters) can be displayed at the end of a line. An error in one line will not prevent processing of further lines; all lines on the screen will be processed. The screen will be returned with all of the error lines moved up to the top of the screen. An error message "PLEASE CORRECT INVALID DATA-(SC Abbreviation)." The service center abbreviation of the service center the request was routed to will appear on line 24 of the screen. If it is intended that the erroneous line is not to be re-input, then it must be blanked out

2.4.28.8 (01-01-2023)

CC STATI, STATB Line 24 Messages

  1. No data may be input on lines 21-24. If data is input on lines 21-24, the screen will return the message "DATA INVALID ON LINES 21-24." Lines 4 through 20 will not have been processed. Line 24 will be used only for returning screen messages to the terminal operator.

  2. The typical messages returned to the terminal operator and their meanings are:

    1. REQUEST COMPLETED-(SC Abbreviation) — all data validated and processed.

    2. PLEASE CORRECT INVALID DATA-(SC Abbreviation) — an error has been detected in one or more input lines. (Invalid fields and an error code at the end of the input line will appear in inverse video.) For description of error codes See IRM 2.4.28.9, CC STAUP, STATI, STATB Error Codes.

    3. INVALID DEFINER — a definer other than "I" , "B" , "S" , or "F" has been used.

    4. DEFINER F INVALID — PLEASE USE I OR B -definer "F" has been used.

    5. NO DATA INPUT — no input on Lines 4 through 20.

    6. DATA INVALID ON LINES 21-24 — data is present on lines 21-24.

2.4.28.9 (01-01-2023)

CC STAUP, STATI, STATB Error Codes

  1. All elements of data from the input screen will be validated. If any data is invalid, the entire line of input will be displayed for potential operator correction. The error field will display in inverse video, and an error code will be displayed as an alpha character following the erroneous input line. Up to three alpha error codes may be shown on each line where an error condition is discovered.

  2. Following are the meanings and conditions for each error code.

    Error Code Error Condition
    A TIN/FILE SOURCE INVALID —
      1 The TIN or File Source is invalid or
      2 File Source indicates an EPMF account or
      3 TIN or File Source not present on screen input or
      4 IMF/BMF Access Restricted or
      5 An attempt was made to process a Non-IMF account through STATI or
      6 An attempt was made to process an IMF account through STATB.
    B NAME CONTROL INVALID —
      1 The Name Control is invalid or
      2 Name Control not present on screen input or
      3 Name Control does not match TIF Name Control.
    C MFT/TAX PERIOD INVALID —
      1 MFT or Tax Period is invalid or
      2 MFT or Tax Period not present on screen input or
      3 MFT or Tax Period inconsistent with TIN or
      4 MFT not processed by CC STAUP.
    D ACCOUNT NOT IN FILE —
      1 No Basic Entity present on TIF (No data fields will be in inverse video) or
      2 Account is dummy or memo account.
    E TAX PERIOD NOT IN FILE —
      1 Tax Period not present on TIF (No data fields will be in inverse video) or
      2 Tax Period is for memo or dummy module or
      3 Tax Period was created or updated via online MFREQ or RECON process.
    F REQUESTED STATUS INVALID —
      1 Status requested is not an appropriate status or
      2 Status requested is other than those specified or
      3 Status requested is 51 and current IDRS status is 22, 24, or 26 or
      4 MF first notice not found for Status requests 20, 51, 56, 58, 71, 22, 24 or 26 (IMF, BMF, IRAF) or
      5 Status request is 91 and current IDRS status is not 22, 24 or 26 or 60 or
      6 Status requested is 24 and File Source is NMF or
      7 Status History Record not present on TIF (No data fields will be in inverse video) or
      8 Automatic next sequential notice status is requested and File Source is NMF or
      9 Request to mark CP 504 notice as destroyed and request another ("R" ) and the current IDRS status is not 58
      10 Request is to mark CP 504 notice as destroyed (either "R" or "D" ) and the CP 504 notice was not issued in the last 2 cycles.
      11 Status request is 20, 54, 56, 58, or * (the next sequential notice status) and the MFT Code is 82 or 83.
    G NUMBER OF CYCLES —
      1 Requested Status update requires an entry in the number of cycles field and the field is blank or
      2 Number of cycles is present but is not in the valid range (00–15) or
      3 Number of cycles is present but is invalid for the status update requested or
      4 Requested status is 22 but current IDRS status is 72 and the COLL-CLOSING-CD is not 76 or 77.
    H DUPLICATE STATUS REQUESTED —
      1 Update status requested is the exact duplicate of a status update requested that week or
      2 Update status requested is for immediate TDA and an immediate TDA request (Status 50, Next Notice = 505) is the most current status on the module
    I RETURN DUE DATE NOT REACHED —
      1 MF status is 19 or 21, but the current date plus the number of cycles delay requested is not later than the return due date.
    J NEXT STATUS INVALID —
      1 Status requested is 20, 56, or 58, but the current status is 14, 22, 24, 26, 41 - 46, 71, 72, or 91 or
      2 Status request is 20, 54, 56, 58 however the status requested is not equal to or greater than the last notice status generated or
      3 Status request is 22, 24, or 26 but the current status is 60 or
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    Note:

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡

    Note:

    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      5 Service Center Status History Record is not present on TIF (No data fields will be in inverse video) or
      6 Status request is * (the next sequential notice status) and current IDRS Status is 48 or 50 or
      7 Status request is * (the next sequential notice status) and current IDRS Status is 22, 24, or 26.
      8 Status request is 58 but the current MFT is 35 or 65.
    K STATUS REQUIRES TC 480 —
      1 Status requested is 71 and the module does not have an unreversed TC 480 present.
    L STATUS REQUIRES TC 914, 916, or 918 —
      1 Status requested is 91 and an unreversed TC 918 is not present in the entity nor is an unreversed TC 914 or 916 present in the tax module.
    M STATUS INCONSISTENT/BALANCE DUE —
      1 NMF status requested is 12, 23, or 29 and the module balance is not consistent with the requirements for that status.
    N ASSIGNMENT CODE INVALID —
      1 The assignment code is not numeric or is invalid (Neither status update nor assignment change has been done) or
      2 Entity Case Assignment Record is not present on the TIF (No data fields will be in inverse video) or
      3 The assignment code is reserved or restricted or
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
      ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡
    R RESERVED
    S ACTION HISTORY —
      1 This action history record cannot be added due to systemic problem. (Status update has been done.)
    T CASE ASSIGNMENT PROBLEM —
      1 The assignment code cannot be updated due to systemic problem. (Status update has been done.)
    U READ OR WRITE TO FILE ERROR, TRY AGAIN LATER
    V FILE NOT OPENED, TRY AGAIN LATER
    W Command code initialization invalid Command Code TXMOD did not immediately precede Command Code STAUP.
    *** INDICATES A SYSTEM ERROR
      No update has been done. Re-input data or contact a CSA.

Exhibit 2.4.28-1

CC STAUP Command Code Definer "I" or "B"

Input Display

This is an Image: 28219121.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STAUP
2 1 6 Command Code Definer - must be "I" or "B"
Exhibit 2.4.28-2

CC STATI, STATB Format Screen Output

Output Display
This is the screen that will be returned when the "I" or "B" definer is used.

This is an Image: 28219125.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STATI or STATB
2 3 1–3 Literal "RPT" - Repeat Indicator
3 3 10–12 Literal "TIN" - Taxpayer Identification Number
4 3 20–22 Literal "MFT" - Master File Tax Code
5 3 26–31 Literal "TX-PRD" - Tax Period
6 3 35–41 Literal "NM-CTRL" - Name Control
7 2 & 3 44–46 Literal "STS REQ" - Status Requested
8 2 & 3 49–52 Literal "CYC DLAY" - Number of Cycles Delay
9 2 & 3 55–60 Literal "ASGNMT CODE" - Assignment Number
Note: 1. The symbol "=" represents the ">" that will actually appear on the display screen.
  2. Data is to be entered beginning on line 4, keeping the literals on the screen as a guide.
Exhibit 2.4.28-3

CC STATI, STATB Input

Input Display

This is an Image: 28219129.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STATI or STATB
2 5–20 2 Repeat indicator = R
3 4–20 6–15 EIN = nn-nnnnnnn
    or  
    6–16 SSN = nnn-nn-nnnn
4 4–20 16 (EIN) File Source = *, V, N, P, X, W, or blank
    or 17 (SSN)  
5 4–20 21–22 MFT code = nn
6 4–20 27–32 Tax Period = yyyymm
7 4–20 36–39 Name Control = a/n/e/blank
8 4–20 45–46 Status request = nn or * for next sequential status
      or D for marking last CP 504 notice as destroyed
      or R for marking last CP 504 notice as destroyed and requesting another
9 4–20 50–51 Number of cycles delay = 00 through 15, or blank
10 4–20 56–59 Assignment code = nnnn, or blank
Exhibit 2.4.28-4

CC STAUP Command Code Definer "S"

Input Display

This is an Image: 28219132.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STAUP
2 1 6 Definer - S
3 1 7-16 EIN = nn-nnnnnnn
    or  
    7-17 SSN = nnn-nn-nnnn
4 2 1–2 Cycle or Status Request - R or D or nn (00 - 15) an automatic update to the next sequential status for the number of cycles displayed on this field or (more than 15) a requested status for the number of cycles displayed on the next field
5 2 4–5 Number of Cycles Delay — 00 through 15 or blank
Exhibit 2.4.28-5

CC STATI, STATB Valid Screen Output

Output Display

This is an Image: 28219666.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
       
1 1 1–5 Command Code - STATI or STATB
2 3 1–3 Literal "RPT" - Repeat Indicator
3 3 10–12 Literal "TIN" - Taxpayer Identification Number
4 3 20–22 Literal "MFT" - Master File Tax Code
5 3 26–31 Literal "TX-PRD" - Tax Period
6 3 35–41 Literal "NM-CTRL" - Name Control
7 2 & 3 44–46 Literal "STS REQ" - Status Requested
8 2 & 3 49–52 Literal "CYC DLAY" - Number of Cycles Delay
9 2 & 3 55–60 Literal "ASGNMT CODE" - Assignment Number
10 24 2–18 Literal "REQUEST COMPLETED" - Message With Service Center Abbreviation
       
NOTE: Unless the entry code is entered before line 24 any data or message appearing on line 24 must be blanked out.
Exhibit 2.4.28-6

CC STATI, STATB Error Screen Output

Output Display

This is an Image: 28219670.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STATI or STATB
  4 through 20   See Exhibit 2.4.28-3, CC STATI, STATB Input
11 4–20 63–65 Alpha Error Code = alpha character or blank
12 24 2–28 Message = "PLEASE CORRECT INVALID DATA" With Service Center Abbreviation
       
NOTE: The erroneous input item(s) will be displaced in inverse video along with an alpha error code(s) at the end of the line also in inverse video. Valid input lines will be processed and blanked out. Invalid lines will be moved to the top of the screen.
 
Exhibit 2.4.28-7

CC STAUP Screen Error Present

Output Display

This is an Image: 28219674.gif

Please click here for the text description of the image.

Record Element Description

ITEM LINE POSITION DESCRIPTION
1 1 1–5 Command Code - STATI or STATB
2 2–3 1–60 Literal screen lines
3 4–20 1–59 Input screen lines
4 24 2–24 Error message — "NO INPUT" or "DATA INVALID ON LINE 21–24" or "DEFINER F INVALID - PLEASE USE I OR B" or "INVALID DEFINER"
       
NOTE: Screen lines 2 through 20 will be redisplayed, but no data will have been processed.