Part 2. Information Technology

Chapter 4. IDRS Terminal Input

Section 14. Command Code NMFST

2.4.14 Command Code NMFST

Manual Transmittal

November 07, 2023

Purpose

(1) This transmits revised IRM 2.4.14, IDRS Terminal Input, Command Code NMFST.

Material Changes

(1) IRM 2.4.14.1 has been revised to include mandatory Internal Controls

Effect on Other Documents

IRM 2.4.14, dated April 17, 2020, is superseded.

Audience

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

Effective Date

(11-07-2023)


Kaschit Pandya
Acting, Chief Technology Officer

2.4.14.1 (11-07-2023)

Program Scope and Objectives

  1. Overview: This IRM section provides an overview of the NMFST Command Code.

  2. Purpose: This IRM contains procedural steps for use of the NMFST Command Code. Command Code NMFST will end up to 10 transactions to a tax module that has already been established on IDRS. Only adjustments, payments, credit transfers, and penalty and interest assessments are valid inputs. DAR transactions must be pended using CC FRM77 or FRM7A. NMFST may be input from Service Center terminals only

  3. Audience: These procedures apply to IRS employees who are responsible for the processing of NMFST records. These employees are located in the following areas: Large & Medium-Sized Business, Small Business/Self-Employed, Tax-Exempt & Government Entity’s, and Wage & Investment.

  4. Policy Owner: IT

  5. Program Owner: The Chief Information Officer (CIO) is responsible for overseeing all aspects of our systems that operate the nation’s tax infrastructure.

  6. Primary Stakeholders: Large & Medium-Sized Business, Small Business/Self-Employed, Tax-Exempt & Government Entity’s, and Wage & Investment

  7. Program Goals: This IRM provides the fundamental knowledge and procedural guidance for employees who work with NMFST cases. By following the processes and procedures provided by this IRM, employees will process NMFST cases in a manner that follows IRS policy and procedures while promoting the best interests of the Government

2.4.14.1.1 (11-07-2023)

Background

  1. This IRM and the contained sections provide the user the necessary information on how to use the command code NMFST

2.4.14.1.2 (11-07-2023)

Authority

  1. NMFST was develop to process subsequent transactions on automatic non-master file (ANMF) accounts established on the TIF

2.4.14.1.3 (11-07-2023)

Responsibilities

  1. NMFST programmer is responsible for

    • Review and implementation of Work Requests that affects NMFST

    • Updating the contents of this IRM

2.4.14.1.4 (11-07-2023)

Program Reports

  1. Entity Record: Each individual taxpayer or business is assigned a unique identity that contains information about them such as SSN/EIN,name and address. Transaction Record: Tracks the subsequent transactions for a NMFTM entity record. Transaction records must contain at least one transaction code. One or more transaction records can be assigned to a Module.

2.4.14.1.5 (11-07-2023)

Program Effectiveness

  1. CC NMFST formatted screen allow input of subsequent transactions for NMFTM accounts. CC TXMODA is a prerequisite for CC NMFST. CC NMFST must operate within the constraints of the Realtime Operating System

2.4.14.1.6 (11-07-2023)

Program Controls

  1. Access to this program is governed by SACS.

2.4.14.1.7 (11-07-2023)

Terms and Acronyms

  1. ANMF AUTOMATIC NON-MASTER FILE
    MFT MASTER FILE TRANSACTION
    TIF TAXPAYER IDENTIFICATION FILE
       

2.4.14.1.8 (11-07-2023)

Related Resources

  1. IRM 2.9.1 Integrated Data Retrieval Systems Procedures

Exhibit 2.4.14-1

NMFST with Definer F Request

1. NMFST is the format request for NMFST, and must be preceded by a successful Command Code TXMODA.
a. Format
This is an Image: 28203356.gif

Please click here for the text description of the image.

b. Record Element Description
ITEM LINE POSITION DESCRIPTION
1 1 1–6 NMFSTF: Command Code and Definer
c. Error messages—returned on line 24 when an invalid request is made.
1. INITIALIZATION INVALID—Entry of NMFSTF was not immediately preceded by a CC TXMOD or NMFTM that correctly assessed an NMF module.
2. COMMAND CODE DEFINER INVALID—Command Code definer is other than F or blank.
Exhibit 2.4.14-2

NMFSTF Response

NMFSTF returns the literals and fields shown on the screen display below, to be overlain for NMFST Input.
a. Format
This is an Image: 28203522.gif

Please click here for the text description of the image.

b. Record Element Description
ITEM LINE POSITION DESCRIPTION
1 1 1–5 NMFST: Command Code
2 1 7–18 TIN and File Source: from preceding TXMODA or NMFTM request
3 1 20–21 MFT: from preceding TXMODA or NMFTM request
4 1 23–29 Tax Period: from preceding TXMODA or NMFTM request
5 2–22 1–80 Literals generated when valid request is made.
Exhibit 2.4.14-3

NMFST Request

(1) NMFST will pend up to 10 transactions to a tax module. Valid information must be entered overlaying the literals output by NMFSTF. The tax module identifying information must not be changed.
a. Format
This is an Image: 28203523.gif

Please click here for the text description of the image.

b. Record Element Description
ITEM LINE POSITION DESCRIPTION AND VALIDITY
1 1 1–5 Command Code: NMFST
2 1 6 Definer: Must be blank
3 1 7–18 TIN and File Source: Generated from preceding TXMODA or NMFTM.
4 1 20–21 MFT: Generated from preceding TXMODA or NMFTM.
5 1 23–29 Tax Period: Generated from preceding TXMODA or NMFTM
6 2 1–3 Transaction Code: May or may not be present. If present, must be one of the following:
      a) Debit transactions are either 290 or 300.
      b) Credit transactions are either 291 or 301.
7 2 5–12 Transaction Date: Must be present if Element 6 is present. The format is MMDDCCYY.
8 2 14–27 DLN: Must be present if Element 6 is present. The 14 digit DLN of the transaction. The first DLN entered on the screen must be numeric, and all 14 digits must be entered. The first two digits must be a valid district office service center. An " R" may be entered at the first character position of the DLN for subsequent transactions if it is desired that the transaction carry the same DLN as the previously entered DLN. Otherwise subsequent DLNs must be numeric.
9 3 1–15 Transaction Amount: Must be present if Element 6 is present. Valid range is .00 to 999,999,999.99. For valid credit transaction amounts, a minus sign will be displayed.
10 4 1–3, 20–22 Abstract Number: If abstract numbers and amounts are to be entered with an adjustment, overlay the "AB#" with the 3 digit abstract number. Validation will be the same as for input to NMFTM. See Exhibit 2.4.11–4 Element 59.
MFT ABSTRACT NUM MFT ABSTRACT NUM
  20 004, 188, 189 69 210–212
  29 160, 162, 177 70 173–181
  33 220 74 165–167
  40 087, 093 76 150, 163, 164
  41 070–072   200–206, 209
  42 155, 157 77 218
  45 009–069,
073–076, 098		 78 217
  46 022, 024, 206 81 030
  50 150–154 90 102, 103, 105–
  53 220   117, 119–122
  56 185, 186 94 075–083, 085, 086
  65 070–137   089–092, 094
  66 150–154, 213, 214 95 131
11 4 5–19, 24–37 Abstract Amount: Must be entered if Element 10 was entered. Overlay dollar signs with an edited amount from .00 to 999,999,999.99.
Abstract amounts must total to equal to transaction amount on line 2 (Element 9).
     
     
12 5, 7, 9, 11, 13, 15, 17, 19, 21 1–3 Transaction Code: May or may not be present. If present, must be one of the following:
      a) Debit Transactions
      160 170 180 200 234 240 270 280
310 320 340 350 360 402 535 607
609 611 612 641 642 651 652 662
671 672 681 682 691 692 695 702
712 732 742 762 765 772 820 830
840 850 860
     
     
     
     
     
       
      b) Credit Transactions:
      161 181 201 235 241 271 281 311
321 341 351 361 400 430 534 606
608 610 640 650 670 680 690 694
700 710 730 740 760 764 770 800
822 832 841 842 851 852 862
     
     
     
     
     
      c) Other Transactions:
      582 583 912 914
13 5, 7, 9, 11, 13, 15, 17, 19, 21 5–12 Transaction Date: Must be present if Element 12 is present. If present, must be in MMDDCCYY format.
14 5, 7, 9, 11, 13, 15, 17, 19, 21 14–27 DLN: Must be present if Element 12 is present. See Element 8 for validity checks.
15 6, 8, 10, 12, 14, 16, 18, 20, 22 1–15 Transaction Amount: Must be present if Element 12 is present. Valid range is .00 to 999,999,999.99. For valid credit transaction amounts, a minus sign will be displayed
Exhibit 2.4.14-4

NMFST Response

a. Format
This is an Image: 28203524.gif

Please click here for the text description of the image.

b. Record Element Description
NOTE:All elements from Lines 1 through 22 will be returned. There will be a message on Line 24.
ELEMENT LINE POSITION DESCRIPTION AND VALIDITY
1–15   1–22   See Exhibit 2.4.14–3
16   24 1–17 " REQUEST COMPLETED" , Message returned after successful NMFST.
       
17   24 19–40 Updated Module Balance: In positions 26–40 of the screen will be the new module balance after a successful NMFST. The displayed module balance includes the transactions input on the screen.
       
       
c. Error Messages: Returned on line 24 when an invalid request is made. Element 18 will not be present with an error.
  1. INITIALIZATION INVALID—Entry of NMFST was not preceded by valid NMFSTF. Reinput TXMODA and NMFSTF or NMFSTN before trying again.
  2. ID CHANGED-REINITIALIZE—the input TIN, File Source, MFT or Tax Period is not the same as that input to TXMODA or NMFTM.
  3. COMMAND CODE DEFINER INVALID—Element 2 is other than F or blank.
  4. CORRECT INVALID DATA—The asterisked input field(s) is invalid or inconsistent. Correct the asterisked field(s) and re-enter. The following fields may be inconsistent
  a. Adjustment Transaction Amount and Abstract Amount(s)
  b. Abstract Number and MFT Code
  c. Transaction Code and MFT Code
  d. Transaction Code and Transaction Amount:
  e. Transaction Amounts for credit transactions do not have a minus sign as the last character
Exhibit 2.4.14-5

NMFST Display Screen

This is an Image: 28203525.gif

Please click here for the text description of the image.