=

Document Locator Number for all non-low-level tax modules that have a transaction with the DLN matching the input DLN.

U =

NUMIDENT Transcript returned in approximately three days. This information will be obtained from the Social Security Administration (SSA).

5

MFT (present for Request Type "M" or Specific only).

6

TAX PERIOD/PLAN NUMBER—Can contain Tax Period, Plan Number, or Plan Number and Tax Period (present for Specific requests only). Can also be all zeros for specific request for MFT 01 only.

7

SPOUSE SSN SEARCH INDICATOR-S—Searched the input TIN on the Spouse's SSN File to find a primary SSN for searching the Master File.

8

TRANSACTION CODE/AMOUNT/DATE—Depending on the Request Type this field will carry a transaction cod (TCnnn) the transaction amount (with commas and decimal point) or the transaction date (MMDDYYYY).

9

REQUEST TIME—In format HH:MM, this field shows when the requestor input the request. This will provide aid in resolving whether request was made before or after the cutoff time (generally 4 P.M. Eastern time) for a day's requests.

9A

REQUEST SOURCE AND REQUEST SUB SOURCE—Indicates which system generated this MFTRA request.

10

RECEIVER NAME/REMARKS

11

PROCESSED ON JULIAN DATE-Format NNN. This is the JULIAN date when Master File began processing this request. This will prove helpful in distinguishing between multiple requests on the same account which were processed over a several day period.

12

DUE TO RESEQUENCING Literal—Will appear only when this request is satisfied due to re-sequence processing by the Master Files. Example: If there is no match to the account originally requested, but there is a TIN Change situation, the first request (an advice record) will be returned without this message, but this message will appear when the request is satisfied the next night at NCC using the TIN obtained from the TIN Change file. This message will prove helpful in distinguishing between requests that were immediately satisfied as opposed to those that were re-sequenced.

13

RESEARCH CONTROL MESSAGES—can be a variable number of the following messages: ACCOUNT FOUND ON DMF—The Debtor Master File was searched and at least one Debtor Obligation was found. ACCOUNT NOT ON DMF—The Debtor Master File was searched but no account matches the SSN entered. ACCOUNT FOUND ON SSA FILE—The Social Security Administration File was searched and at least one Numident record was found. ACCOUNT NOT ON SSA FILE—The Social Security Administration File was searched but no account matches the SSN entered. SP SSN NOT ON SP SSN FILE—Input SSN not on Spouse's SSN File. NO TIN ON TIN CHG FILE—TIN was not found on the Master File or on the MF TIN Change File Cross Reference File. INPUT SP SSN-nnn-nn-nnnn—A search of the Spouse's SSN File revealed a primary SSN, this message records the input SSN that was used to obtain the primary TIN. PRIM ON SP SSN-nnn-nn-nnnn—Spouse's SSN Indicator was input and the search of the Spouse's SSN File revealed this Primary SSN. Input ACTRA with this Primary SSN to display account data. OLD INPUT TIN-vvvvvvvvvvvv (v=TIN)—This account is under a new TIN which was found on the TIN Change Cross Reference File. The TIN in this message was the input TIN.

NEW TIN FR TIN CHG FILE-vvvvvvvvvvvv (v=TIN)—A new TIN was found on the TIN Change Cross Reference File and this is that TIN. Input ACTRA with this new TIN to display account data. ACTRA data will be available the second day after the request day. MF NOT SEARCHED—This message should normally only appear if (1) the MFTRA request indicated a Spouse SSN File search, (2) the SSN was of found on the Spouse SSN File and so was forwarded straight to the TIN Change Cross-reference File (bypassing the MF) (3) the TIN was not found on the TIN Change Cross-reference File—therefore the input TIN was not searched for on the MF. (If a search of the MF is desired, input another request without the Spouse SSN Indicator). It will therefore appear along with the messages "SPSSN NOT ON SPSSN FILE" and "NO TIN ON TIN CHGE FILE" . ENTITY NOT ON ACTIVE—Master File was searched and no account was found. This message always refers only to the TIN that was originally requested. If the message "OLD INPUT TIN" (see above) precedes this message, then the TIN to the right of the " OLD INPUT TIN" is the entity that is not on the Active Master File. ACCOUNT DATA DELAYED—Master File was searched, account data was found and will be received in 1 or 2 days. This delay is caused when tax module data is on less active (lower) levels of the MF. REQUEST RESEQUENCED AT MF—An operational problem has occurred at ECC-MTB which prevented extract of requested data. Request will a automatically re-sequenced by ECC-MTB processing for the next night's extract.

ENTITY FOUND ON ACTIVE MF—Request Type "E" (Entity) was input and the entity was found. ENTITY FOUND ON DROPPED MASTER FILE (Note: This message only appears on HARDCOPY transcripts and is included in this LEM only because some employees do not have access to IRM 21.2.4, Transcripts in IRM 21.2) For every BMF and IMF Entity Request (Type "E" ), there is an automatic attempt at ECC-MTB to locate an account with the same TIN on the Dropped Master File. If there is no match-up on the DROPPED MASTER FILE, no special message is returned to IDRS. If there is a match-up, a hardcopy transcript is returned with this message and a YEAR REMOVED field, so that user can initiate a MICROFILM request (via ESTAB "M" ), if desired. The DROPPED MASTER FILE contains a minimal amount of information about accounts which have aged off the Active Master Files and Lower Level Files. The most valuable item of information is a list of those tax modules for that TIN which have gone to RETENTION. A limitation of the DROPPED MASTER FILE is that it extends back only as far as those accounts which have been dropped since January 1984.

ENTITY FOUND ON DELETED MASTER FILE— (Note: This message only appears on HARDCOPY transcripts and is included in this IRM only because employees do not have access to IRM 21.2.4, Transcripts, in IRM 21.2.) Similarly, for every BMF and IMF Entity Request (Type "E" ), there is an automatic attempt at NCC to locate an account with the same TIN on the Deleted Master File. If there is no match-up on the DELETED MASTER FILE , no special message is returned to IDRS. If there is a match-up, a hardcopy transcript is returned with this message, so that user can initiate a MICROFILM request (via ESTAB "M" ), if desired. The DELETED MASTER FILE can be a valuable source of information about Account Merge situations. The DELETED MASTER FILE transcript contains much the same information as appears on Entity Requests against Active accounts, including Entity posted Transactions (Example: TC 020). A valuable item of information is a list of those tax modules for that TIN which have gone to RETENTION. A limitation of the DELETED MASTER FILE is that it extends back only as far as those accounts that have been deleted since January 1984. ENTITY ONLY FOUND ON ACTIVE MF—Request Type "C" (Complete) was input and only an entity was found on the MF.

ENTITY AND TAX MODULE DATA FOUND ON MF—Request Type " C" (Complete) was input for a non-EPMF account and entity and tax module data was found. ENTITY AND PLAN DATA ONLY FOUND ON MF —Request Type "C" was input for an EPMF account and no tax module(s) was found. ENTITY AND PLAN DATA FOUND ON MF—A request for a specific EPMF tax module did not find a tax module but did find entity and plan data. ENTITY PLAN AND TAX MODULE FOUND ON MF——Request Type "C" (Complete) was input for EPMF and the account has entity, plan, and tax module data. REQUESTED TAX MODULE FOUND ON MF—The specific tax module that was requested was found on the MF.

TAX MODULE(S) FOUND FOR MFT—Request Type " M" (MFT) was input and tax modules were found for the input MFT. OPEN BAL TAX MODULE(S) FOUND ON MF—Request Type "B" (Open Balance) was input and open balance tax modules were found. CREDIT BAL TAX MODULE(S) FOUND ON MF—Request Type "-" (Credit Balance) was input and credit balance tax modules were found. DEBIT BAL TAX MODULE(S) FOUND ON MF—Request Type "+" (Debit Balance) was input and debit balance tax modules were found. TAX MODULE(S) FOUND FOR TC—Request Type "T" (Transaction Code) was input and the account has a tax module(s) containing the input TC. TAX MODULE(S) FOUND FOR TC AMOUNT—Request Type "A" (Transaction Amount) was input and the account has a tax module(s) containing the input transaction amount. TAX MODULE(S) FOUND FOR TC DATA—Request Type "D" (Transaction Date) was input and the account has a tax module(s) containing the input transaction date. TAX MODULE(S) FOUND FOR DLN—Request Type "#" (Document Locator Number) was input and tax modules for the matching DLN were found. REQUESTED TAX MODULE NOT ON MF—The requested specific tax module, plan data or quarterly modules for the input year are not on the MF. NO TAX MODULE FOR MFT—Request Type "M" (MFT) was input and there were no tax modules on the MF account for the input MFT. NO OPEN BAL TAX MODULE—Request Type " B" (Open Balance) was input but no open balance modules are present on the MF account. NO CREDIT BALE TAX MODULE—Request Type "-" (Credit Balance) was input but no credit balance modules are present on the MF account. NO DEBIT BAL TAX MODULE—Request Type "+" (Debit Balance) was input but no debit balance modules are present on the MF account. NO TAX MODULE WITH TC—Request Type " T" (Transcription Code was input but there were no tax modules containing the TC input.

NO TAX MODULE WITH TC AMOUNT—Request Type "A " (Transaction Amount) was input but there were no tax modules containing the transaction amount input. NO TAX MODULE WITH TC DATE —Request Type "D" (Transaction Date) was input but there were no tax modules containing the transaction date input. NO TAX MODULE WITH DLN—Request Type " #" (Document Locator Number) was input but there were no tax modules containing the DLN input. MERGE IN PROCESS TO THIS TIN REQUEST WILL BE AUTOMATICALLY SATISFIED WHEN MERGE COMPLETE IT IS NOT NECESSARY TO REQUEST AGAIN—An account merge is taking place at the MF. Do not input another request for this TIN. The request will be automatically generated when merge is complete and returned in HARDCOPY format. It could take up to 3 weeks to receive your transcript.

MERGE IN PROCESS FROM THIS TIN REQUEST WILL BE AUTOMATICALLY SATISFIED WHEN MERGE COMPLETE IT IS NOT NECESSARY TO REQUEST AGAIN—An account merge is taking place at the MF. Do not input another request for this tin. The request will be automatically generated when merge is complete and returned in HARDCOPY format. It could take up to 3 weeks to receive your transcript. NEW TIN FROM TIN CHANGE FILE nnnnnnnnn REQUEST FOR NEW TIN AUTOMATICALLY GENERATED—The account merge has completed at the MF. Transcript for new TIN will be received with the following day's transcripts. REQUEST FOR INV SEGMENT TIN IS AUTOMATIC—Whenever no entity for this TIN is found on the IMF, IRAF, or BMF when a Valid segment SSN is requested, there will be an attempt to extract the same data from the Invalid Segment using the same SSN, on the following day. Requester does not need to re-input request using Invalid Segment SSN. This special processing does not apply to requests directed toward the Spouse SSN file. Also note that the automatic search toward the Invalid Segment SSN is not performed once any data in any form (even if only entity information) is returned from the request directed toward the Valid Segment SSN.

14

DATA IS EXTRACTED TO HARDCOPY FROM THE DROPPED MF – (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “1” and Request Type “E” with Output Type “D”.) DROPPED ENTITY DATA IS AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “1” and Request Type is not “E” with Output Type “D”.) DROPPED ENTITY DATA IS AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “1” and Request Type is not “E” with Output Type “I”.) DATA IS EXTRACTED TO HARDCOPY FROM THE DELETED MF – (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “2” and Request Type “E” with Output Type “D”.) DELETED ENTITY DATA IS AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “2” and Request Type is not “E” with Output Type “D”.) DELETED ENTITY DATA IS AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “2” and Request Type is not “E” with Output Type “I”.) DATA IS EXTRACTED TO HARDCOPY FROM THE DROPPED AND DELETED MF – (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “3” and Request Type “E” with Output Type “D”.) DROPPED+DELETED ENTITY DATA AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “3” and Request Type is not “E” with Output Type “D”.) DROPPED+DELETED ENTITY DATA AVAILABLE USE MFTRA REQUEST-TYPE -E- HARDCOPY - (Note: This message appears on HARD COPY transcripts only if the Dropped Deleted Indicator “3” and Request Type is not “E” with Output Type “I”.) 15 – 21 DOCUMENT REQUEST CODE (will appear if CC ESTAB was input without a DLN and no DLN found at the MF).

15

PARTIAL DLN

16

REQUEST CODE

17

FORM NUMBER

18

NAME CONTROL. If MF data was found this is the MF Name Control, otherwise this is the name control input with CC ESTAB.

19–21

REMARKS