Part 2. Information Technology
Chapter 4. IDRS Terminal Input
Section 25. Command Codes BDADDR, BDADD, BDAPLR, BDAPL, BDOUTR, BDOUT, BDENT and BDINQ
2.4.25 Command Codes BDADDR, BDADD, BDAPLR, BDAPL, BDOUTR, BDOUT, BDENT and BDINQ
Manual Transmittal
May 22, 2024
Purpose
(1) This transmits revised IRM 2.4.25, IDRS Terminal Input, Command Codes BDADDR, BDADD, BDAPLR, BDAPL, BDOUTR, BDOUT, BDENT, and BDINQ.
Material Changes
(1) IRM 2.4.25.1 Added Program Scope and Controls to include the following information: Overview, Purpose, Audience, Policy Owner, Program Owner, Primary Stakeholders, Program Goals
Effect on Other Documents
IRM 2.4.25, dated December 14, 2022, is superseded.
Audience
LBI, SB/SE, TE/GE, TS.
Effective Date
(05-22-2024)
Rajiv K Uppal
Chief Information Officer (CIO)
Program Scope and Objectives
(1) This IRM section provides the instructions for the use of Dishonored Check File (DCF) command codes BDADDR, BDADD, BDAPLR, BDAPL, BDOUTR, BDOUT, BDENT & BDINQ. :
(2) Purpose: To provide system maintenance, capability, specifications and guidance for using the various command codes for adding, researching dishonored checks.
(3) Audience: All IRS business areas.
(4) Policy Owner: The Chief Information Officer
(5) Program Owner: IDRS
(6) Primary Stakeholders: LBI, SB/SE, TE/GE, TS.
(7) Program Goals: Capability to provide system maintenance, correct or delete any record which was entered on the Dishonored Check File.
Background
(1) The Dishonored Check File (DCF DS) contains cases for checks returned from banks as unprocessables or insufficient funds. Command Code BDADD is used to establish a dishonored check record on the Dishonored Check File.
Authority
(1) (1) IRM 20.1, Penalty Handbook, provides guidance to all areas of the IRS for all civil penalties imposed by the Internal Revenue Code (IRC). It sets forth general policy and procedural requirements for assessing and abating penalties, and it contains discussions on topics such as criteria for relief from certain penalties.
Roles and Responsibilities
(1) Overall responsibility for civil penalty programs is assigned to OSP. OSP is a matrix organization residing in the Business Support (Small Business/Self Employed) Function. OSP is charged with coordinating policy and procedures concerning the civil penalty program administration, ensuring consistency with the penalty policy statement, reviewing and analyzing penalty information, researching penalty effectiveness on compliance trends, and determining appropriate action necessary to promote voluntary compliance.
(2) The Director, Business Support, is the director responsible for the servicewide civil penalty program
(3) The Director, Internal Management, is the director responsible for the IDRS Command Code.
(4) Each and every taxpayer has a set of fundamental rights when dealing with IRS as provided in the Taxpayer Bill of Rights (TBOR). All employees handling penalty cases must do so in accordance with the TBOR as listed in IRC 7803(a)(3). The TBOR can also be found at Taxpayer Bill of Rights on irs.gov
Program Management and Review
(1) Program Reports: Every function in the IRS has a role in proper penalty administration. It is essential that each function conduct its operations with an emphasis on promoting voluntary compliance. Appropriate business reviews should be conducted to ensure consistency with the penalty policy statement (Policy Statement 20-1) and philosophy. .
(2) Program Effectiveness:Attention should be directed to penalty program coordination between offices and functions to make sure that approaches are consistent and penalty information is used for identifying and responding to compliance problems.
Program Controls
(1) SACS controls all the IDRS user accesses and permissions
(2) In rare instances, a program’s controls may overlap with program management and review (previous subsection), and both subsections may not be applicable. If you think your program does not have content that applies to both "Program Management and Review" and "Program Controls," consult with your business unit’s IRM/IMD coordinator on what to include.
Error Messages
(1) Sections 25.2.1 through 25.2.6 list error messages for command codes within the Dishonored Check System. Each includes the condition and required action for the error condition.
Error Messages for CC BDADD
(1) DUPLICATE DC CONTROL NUMBER
Condition: A DC Control Number exactly the same as the one being entered already exists on the Dishonored Check File.
Solution: Determine the reason for the duplicate number, then either assign a different control number and reenter or VOID the existing record if in error, and reenter the correct record.
(2) RECALL CODE IS INVALID
Condition: Recall Code is neither " C" nor blank.
Solution: Input "C" or remove invalid character and reenter.
(3) SUBTOTALS NOT AVAILABLE FOR RECALL
Condition: Recall Code "C" was entered but the prior COMMAND-CD was not BDADDR or BDADD: or entry code does not agree with entry code that stored the item Count and Money Count totals.
Note: BDADD format will be displayed, but without the sub-totals.
(4) FIRST NAME LINE EXCEEDS 35 CHARACTERS
Condition: Self-explanatory.
Solution: Input first name line with no more than 35 characters.
(5) SECOND NAME LINE EXCEEDS 35 CHARACTERS
Condition: Self-explanatory.
Solution: Input second name line with no more than 35 characters.
(6) INVALID TRACE ID (SITE-ID)
Condition: SITE ID of TRACE ID invalid for Service Center processing.
Solution: Check to ensure SITE-ID of TRACE ID is valid. This does not have to be a current, valid code. It can be one from the past.
(7) INVALID TRACE ID (SYSTEM-ID)
Condition: SYSTEM ID of TRACE ID invalid for DCF processing.
Solution: Check to ensure SYSTEM ID of TRACE ID is valid for DCF.
(8) INVALID TRACE ID (JULIAN-DATE)
Condition: JULIAN DATE of TRACE ID invalid.
Solution: JULIAN DATE must be greater than 2006001 and JULIAN DATE may not be greater than entry date.
(9) INVALID TRACE ID (SEQUENCE-NUM)
Condition: SEQUENCE NUM of TRACE ID invalid.
Solution: SEQUENCE NUM must be of proper numeric format and greater than zero.
(10) INVALID TRACE ID (TRANS-SEQUENCE-NUM)
Condition: TRANS SEQUENCE NUM of TRACE ID invalid.
Solution: TRANS SEQUENCE NUM must be of proper numeric format and greater than zero.
Error Message for CC BDAPL
(1) Error Message: APPLY NOT ALLOWED-STATUS IS aaaa (aaaa = CLOS, UNPR, VOID, AT&F, MISS, REDP, NIRS, URF)
Condition: An attempt is being made to apply money from a DC record which is Closed, Unprocessable, Void, Alcohol, Tobacco and Firearms, Missing, Redeposited, Non-IRS or Unidentified.
Solution: Make sure this is the record you want.
(2) Error Message: APPLICATION AMOUNT EXCEEDS BALANCE
Condition: An attempt is being made to apply an amount which is greater than the balance on the taxpayers record.
Solution: Determine available amount and re-enter.
(3) Error Message: CANNOT ISSUE 2287 - NO NAME/ADDR
Condition: Screen input specifies Form 2287–C (IDRS Notice 587 — Notice of Check Not Accepted by Bank) is to be issued but neither the Dishonored Check File nor the screen input contains a complete mailing address.
Solution: Enter complete name and address data on screen.
(4) Error Message: TlF MEMO RECORD - APPLICATION DENIED
Condition: Attempt being made to apply money to a MEMO account on the TlF.
Solution: Verify that you are applying money to the correct taxpayer.
(5) Error Message: TIF ACCOUNT ON FILE nn-nnnnnnnv vvvv nnn-nn-nnnnv vwv
Condition: The account is on the TIF but the application name control on the screen does not agree with the TIF name control. The TIN and Name Control from the TIF is displayed in the message.
Solution: Change the name control after verifying that you are applying the money to the correct taxpayer.
(6) Error Message: "TIN NOT ESTABLISHED ON MF"
Error Condition: This TIN could not be matched against the National Accounts Profile (NAP) Database.
Solution: Check to make sure the TIN is correct. If it is, this message means that this taxpayer is not yet on the Master File.
(7) Error Message: "Name Control Mismatch on NAP File"
Error Condition: The Name Control cannot be matched against the National Accounts Profile (NAP).
Solution: Check to make sure the Name Control is correct. if it is, use TXMOD to check for prior names.
(8) Error Message: "INVALID TIN-TYPE "
Error Condition: The TIN TYPE is not valid. The NAP cannot be completed.
Solution: This response indicates a program error, notify the IDRS Control Staff.
(9) Error Message: "TIN IS NOT ON EPMF OR BMF"
Error Condition: The TIN was not found on the NAP as an EPMF account nor a BMF account.
Solution: Check TIN.
(10) Error Message: "TIN IS NOT ON EPMF; IS ON BMF"
Error Condition: The TIN was not found on the NAP as an EPMF account, it was found as a BMF account.
Solution: Check TIN
(11) Error Message: "CRS/NAP ACCESS NOT AVAILABLE: TRY LATER"
Error Condition: The Communication Replacement System (CRS) for the National Account Profile (NAP) is not available at this time. Processing cannot continue.
Solution: Try Later.
(12) Error Message: "NAP ENTITY FILE NOT AVAILABLE: TRY LATER"
Error Condition: The National Entity File is unavailable at this time. Processing cannot continue.
Solution: Try Later.
(13) Error Message: "REASON-CD 23-COMMENTS REQUIRED"
Error Condition: Comments are required when a master file apply is made to an account with a reason code 23.
Solution: Input comment line and re-try.
(14) Error Message: "BMF ACCESS RESTRICTED "
Error Condition: An attempt has been made by the user to access an IMF account. User is not profiled to access this type of account.
Solution: Refer to IRM 2.4 Section 2.2.5.
(15) Error Message: "IMF ACCESS RESTRICTED "
Error Condition: An attempt has been made by the user to access an BMF account. User is not profiled by access this type of account.
Solution: Refer to IRM 2.4 Section 2.2.5.
(16) Error Message: "PLEASE ENSURE THAT THE NAME AND ADDRESS IS VALID"
Error Condition: The name and address information is extracted from either the TIF or DCF database.
Solution: If the information is incorrect, then overlay with correct information, otherwise transmit.
(17) Error Message: "SSN NOT ON MF AS VALID OR INVALID - INOLE CAN BE USED TO VALIDATE DM-1 SSN/NAME"
Error Condition: TIN associated with the NAME-CTRL could not be found on MF.
Solution: Check TIN or NAME-CTRL for valid or use CC INOLE to verify TIN and NAME-CTRL
(18) Error Message: "ACCOUNT FOUND ON OPPOSITE VALIDITY - INOLE BE USED TO VALIDATE SSN/NAME"
Error Condition: The account could not be found on the NAP.
Solution: Check TIN or NAME-CTRL for valid or use CC INOLE to verify TIN and NAME-CTRL.
(19) Error Message: "INVALID REQUEST-NAP "
Error Condition: TIN, TIN-TYPE, MF-SOURCE-CD are invalid. The NAP cannot be completed.
Solution: Verify and re-input data.
(20) Error Message: "IBM PROGRAM ABEND "
Error Condition: Subprogram 'IHXFER' has aborted when CC BDAPL was accessing the NAP.
Solution: Please contact the IBM Programmer.
(21) Error Message: "PROGRAM/REGION PROBLEM AT MCC CICS"
Error Condition: An error has occurred when accessing the NAP.
Solution: Please contact the IBM Programmer.
(22) Error Message: "PROGRAM/REGION PROBLEM AT DCC CICS"
Error Condition: An error has occurred when accessing the NAP.
Solution: Please contact the IBM Programmer.
(23) Error Message: "TIF ERROR - CONTACT DATABASE ADMINISTRATOR."
Error Condition: An error has occurred with the TIF database.
Solution: Please contact the database administrator.
Error Messages for CC BDOUT
(1) Error Message:"PREVIOUS APPLICATION - CHANGE NOT ALLOWED"
Condition: An application has been made to the taxpayer's account and no changes are allowed to the original amount.
Solution: If ORIGINAL-DC-AMT erroneous and all applies have been made, then void the record.
(2) Error Message: "AMOUNT FIELD INVALID "
Condition: The "Changed-To" Amount (which is supposed to change the amount) is equal to the original amount (ORIGINAL-DC-AMT) in the Dishonored Check File record.
Solution: Correct input and reenter.
(3) Error Message: "APPLICATION AMOUNT EXCEEDS BALANCE"
Condition: An attempt is being made to void an amount which is greater than the balance on the taxpayer's record.
Solution: Determine available amount and reenter.
(4) Error Message: "UPDATE NOT ALLOWED - STATUS IS CLOS, UNPR, VOID, AT&F, MISS, REDP, NIRS, URF"
Condition: The status of the DC record is Closed, Unprocessable, Void, Alcohol, Tobacco, and Firearms, Missing, Redeposited, Non-IRS or Unidentified.
Solution: Make sure this is the record you want.
Error Messages for CC BDENT
(1) Error Message:"CHANGES MUST BEGIN ON SCREEN LINE" 4
Condition: Change data not entered on proper line or not entered at all.
Solution: Correct and re-enter.
(2) Error Message: "UPDATE NOT ALLOWED - STATUS IS CLOS, UNPR, VOID, AT&F, MISS, REDP, NIRS, URF"
Condition: The status of the DC record is Closed, Unprocessable, Void, Alcohol, Tobacco, and Firearms, Missing, Redeposited, Non-IRS or Unidentified.
Solution: Make sure this is the record you want.
(3) Error Message: "SCREEN LINES 14 AND 15 MUST BE BLANK"
Condition: Self-explanatory.
Solution: Do not input any data on lines 14 and 15.
(4) Error Message: "NAME CHANGE EXCEEDS 35 CHARACTERS"
Error Condition: An attempt has been made to change the name on a DC record with a name greater than 35 characters.
Solution: Shorten NAME LINE to 35 characters or less.
(5) Error Message: "DUPLICATE CHANGE LITERALS NOT ALLOWED"
Error Condition: Duplicate changes have been detected screen lines 4 through 8.
Solution: Change data and try again.
(6) Error Message: "BLANK LINES BETWEEN CHANGES NOT ALLOWED"
Error Condition: Self-explanatory.
Solution: Change data and try again
(7) INVALID TRACE ID (SITE-ID)
Condition: SITE ID of TRACE ID invalid for Service Center processing.
Solution: Check to ensure SITE-ID of TRACE ID is valid. This does not have to be a current, valid one. It can be one from the past.
(8) INVALID TRACE ID (SYSTEM-ID)
Condition: SYSTEM ID of TRACE ID invalid for DCF processing.
Solution: Check to ensure SYSTEM ID of TRACE ID is valid for DCF.
(9) INVALID TRACE ID (JULIAN-DATE)
Condition: JULIAN DATE of TRACE ID invalid.
Solution: JULIAN DATE must be greater than 2006001 and JULIAN DATE may not be greater than entry date.
(10) INVALID TRACE ID (SEQUENCE-NUM)
Condition: SEQUENCE NUM of TRACE ID invalid.
Solution: SEQUENCE NUM must be of proper numeric format and greater than zero.
(11) INVALID TRACE ID (TRANS-SEQUENCE-NUM)
Condition: TRANS SEQUENCE NUM of TRACE ID invalid.
Solution: TRANS SEQUENCE NUM must be of proper numeric format and greater than zero.
(12) INVALID MFT
Condition: MFT invalid.
Solution: Enter a valid MFT.
(13) INVALID PLAN NUM
Condition: Plan num invalid.
Solution: Plan num must be numeric or spaces. Plan nums are only valid when used with MFT 46, 74, or 76. If MFT other than 46, 74, or 76 is used, the Plan num must either be 000 or spaces.
(14) INVALID PLAN NUM FOR MFT 46
Condition: Plan num invalid as used with MFT 46.
Solution: Plan num must be 000, 100 thru 199, 300 thru 399, 500 thru 599, or 700 thru 799.
(15) INVALID PLAN NUM FOR MFT 74
Condition: Plan num invalid as used with MFT 74.
Solution: Plan num must be 001 thru 999.
(16) INVALID PLAN NUM FOR MFT 76
Condition: Plan num invalid as used with MFT 76.
Solution: Plan num must be 000 thru 499 or 501 thru 999.
(17) INVALID TAXPRD
Condition: TAXPRD invalid.
Solution: Enter a valid numeric TAXPRD (format YYYYMM).
(18) MUST ENTER MFT AND TAXPRD
Condition: Missing either the MFT and/or the TAXPRD.
Solution: Enter a valid MFT and TAXPRD.
Error Messages for CC BDINQ
(1) Error Message: NAME CONTROL INVALID
Condition: Name Control contains invalid characters.
Solution: Correct and re-input.
(2) Error Message: AMOUNT INVALID
Condition: Amount contains invalid characters or is formatted incorrectly.
Solution: Correct and re-input.
(3) Error Message: CONTROL NUMBER INVALID
Condition: Field contains invalid characters or is improperly formatted.
Solution: Correct and re-input.
(4) Error Message: NAME CTRL OR CONTROL NO. REQUIRED
Condition: None of the required search data was input.
Solution: Enter at least the DC Control Number or Name Control and re-input.
(5) Error Message: DO/SC CD INVALID
Condition: District Office is invalid for this service center.
Solution: Correct and re-input.
(6) Error Message: DC CONTROL NUM FOUND/AMOUNT MISMATCH
Condition: DC Control Number found and data has been displayed but the ORIGINAL-DC-AMT entered on screen does not agree with amount on the Dishonored Check File.
Solution: Verify screen input and be sure this is the DC record you want before taking any action.
(7) Error Message: REQUEST EXCEEDS CHARACTER LIMIT
Condition: Request was more that 18 characters.
Solution: Enter the correct information.
Common Error Messages for all Command Codes
(1) Error Message: PRIOR COMMAND CODE INCOMPATIBLE
Condition: The immediately preceding COMMAND-CD is not the required COMMAND-CD.
Solution: Determine and correct COMMAND-CD to use and reenter.
(2) Error Message: PLEASE CORRECT INVALID DATA
Condition: Item asterisked (*) contains invalid characters, is improperly formatted, is missing, or inconsistent with another asterisked item.
Solution: Correct and reenter.
(3) Error Message: ENTER RECOGNIZABLE COMMAND CODE
Condition: Command code is not equal to BDADD.
Solution: Input BDADD as command code.
(4) Error Message: ENTER RECOGNIZABLE CMND CD MODIFIER
Condition: Command Code modifier is not equal to "R" or space.
Solution: Input correct modifier.
(5) Error Message: NO DC RECORD FOUND FOR GIVEN DATA
Condition: Self explanatory.
Solution: Correct and re-enter.
(6) Error Message: CONTROL NUM FOUND/NAME CTRL MISMATCH
Condition: The input DC Control Number is on the Dishonored Check File but the name control input does not match the Dishonored Check File name control.
Solution: Verify the name control and change the name control if necessary.
(7) Error Message: "DEADLOCK CONDITION PRESENT"
Error Condition: This account is currently being used by another run.
Solution: Try later.
(8) Error Message: "RECOVERY IN PROGRESS "
Error Condition: A Recovery is being done to the Database and is unavailable.
Solution: Please try again later.
(9) Error Message: area-name "IS DOWN "
Error Condition: An area of the Database is down and unavailable.
Solution: Please try again later or try another area.
(10) Error Message: area-name "IS RESTRICTED "
Error Condition: An area of the Database is restricted and unavailable.
Solution: Please try again later or try another area.
(11) Error Message: tif-type "TIF" tif-num -"AREA IS UNAVAILABLE"
Error Condition: This particular TIF-AREA is unavailable for use.
Solution: Please try again later or try another area.
Command Code BDADD
(1) Command Code BDADD used to establish a dishonored check record on the Dishonored Check File. The format is generated by CC BDADDR and a new BDADD format will be displayed after each BDADD entry.
(2) Input Display—BDADDR:
(3) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD "BDADD" |
2 | 1 | 6 | COMMAND-CD-MODIFIER "R" |
3 | 1 | 8 | RECALL-CODE — Input "C" to request a BDADD format which will also display the stored sub-totals of the Item Count and Money Count; otherwise leave blank. |
DC Original Format Record
(1) BDADD screen format (with stored sub-totals if Recall Code was properly input) will be displayed as shown below:
DC-ORIGINAL-FORMAT RECORD
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | "BDADD" generated COMMAND-CD |
2 | 1 | 7–11 | ITEM-COUNT generated Literal "ITEMS" |
3 | 1 | 13–15 | ITEM-COUNT — The number of items added to this point (generated). |
4 | 1 | 18–36 | VOUCHER-AMT — The dollar amount added to this point (generated) |
5 | 2 | 1–18 | DC-CONTROL-NUMBER — Must be entered in nn-nnn-nnnnn-nnn-n format. First two digits must be the Service Center of input or a valid District Office within the Service Center of input. Year digit must be that of the current year or the Immediately prior year. Control Day must be 001–366. The Control Day and Year digit combination cannot be greater than the current date. |
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
6 | 2 | 20–21 | DC-REASON-CD — Overlay RC with the code shown on check. Must be entered and must be 01–26. The meanings are as follows: |
|
|
| 01 — Insufficient Funds |
|
|
| 02 — Stop Payment |
|
|
| 03 — Refer to Maker |
|
|
| 04 — Account Closed |
|
|
| 05 — No Account ever in existence |
|
|
| 06 — Lien on Account |
|
|
| 07 — Missing Signature |
|
|
| 08 — Two signatures needed — one present |
|
|
| 09 — Signature not same as bank record |
|
|
| 10 — Uncollected Funds |
|
|
| 11 — Written/Numeric amount mismatch |
|
|
| 12 — Date Missing |
|
|
| 13 — Date altered |
|
|
| 14 — Post dated |
|
|
| 15 — Stale dated |
|
|
| 16 — Foreign Check |
|
|
| 17 — Endorsement not as drawn |
|
|
| 18 — Guarantee of amount |
|
|
| 19 — Cannot handle as cash |
|
|
| 20 — Not MICRO coded |
|
|
| 21 — Make deceased |
|
|
| 22 — Invalid power of attorney signature |
|
|
| 23 — Other |
|
|
| 24 — Mutilated |
|
|
| 25 — Exceeds cash advance limit |
|
|
| 26 — Under minimum withdrawal amount |
7 | 2 | 23–32 | EMPLOYEE-ASG-NUM Optional |
8 | 3 | 1–14 | ORIGINAL-DC-AMT — Overlay $'s with check amount. Must be .01 through 999,999,999.99 (left-justified). |
9 | 4 | 1-24 | TRACE-ID --- Must be entered in nn-nn-nnnnnnn-nnn-nnnnnn format. The TRACE ID specifies the following: SP Campus FLC or other Site ID, System ID, Deposit Date, Seq Number, Transaction Seq Number. Note - The Site ID portion of the TRACE-ID does not have to be a current, valid one. It can be one from the past. |
10 | 5 | 1–4 | PAYMENT-TYPE-CD — Must be entered. Valid codes and meanings are: |
|
|
| REGU — Regular Remittance |
|
|
| MULT — Multiple Remittance |
|
|
| SPLT — Split Remittance |
|
|
| MUSP — Multiple/Split Remittance |
11 | 5 | 6-13 | IRS-RCVD-DT MMDDYYYY or nnnnnnnn |
12 | 6 | 1–35 | FIRST-NAME-LINE 1STbN/Lb ------- b |
13 | 7 | 1–35 | SECOND-NAME-LINE 2NDbN/Lb------- b |
14 | 8 | 1–35 | STREET-ADDR STREETb ------- b |
15 | 9 | 1–35 | CITY-ST-ZIP CY/ST/ZPb ------- b |
16 | 10 | 1–11 | TIN TINb ------- b |
17 | 10 | 13-14 | MFT-CD NN or nn |
18 | 10 | 16-18 | PLAN-NUM or EPN or nnn |
19 | 10 | 20-25 | TXPRD YYYYMM or nnnnnn |
20 | 11 | 1–7 | MRS-IND literal "MRS-IND" |
21 | 13 | 3–37 | ERROR-MESSAGES V ------- v |
Command CD BDADD—DC Original Request
(1) Input Display — BDADD:
DC-ORIGINAL-REQUEST
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | Command-CD "BDADD" |
2 | 1 | 7–11 | ITEM Literal "ITEMS" |
3 | 1 | 13–15 | ITEM-COUNT — The number of items added to this point (generated). |
4 | 1 | 18–36 | VOUCHER-AMT — The dollar amount added to this point (generated). |
5 | 2 | 1–18 | DC-CONTROL-NUMBER — Must be entered in nn-nnn-nnnnn-nnn-n format. First two digits must be the Service Center of input or a valid District Office within the Service Center of input. Year digit must be that of the current year or the immediately prior year. Control Day must be 001–366. The Control Day and Year digit combination cannot be greater than the current date. The DC Control Number specifies the following: |
|
|
| nn nnn nnnnn nnn n |
|
|
| DO-SC-CD | Control Day Julian | Bank Number | Debit Voucher | Series Number Within Debit Voucher | Year Digit |
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
6 | 2 | 20–21 | DC-REASON-CD — Overlay RC with the code shown on check. Must be entered and must be 01–26. The meanings are as follows: |
|
|
| 01 — Insufficient Funds |
|
|
| 02 — Stop Payment |
|
|
| 03 — Refer to Maker |
|
|
| 04 — Account Closed |
|
|
| 05 — No Account ever in existence |
|
|
| 06 — Lien on Account |
|
|
| 07 — Missing Signature |
|
|
| 08 — Two signatures needed—one present |
|
|
| 09 — Signature not same as bank record |
|
|
| 10 — Uncollected Funds |
|
|
| 11 — Written/Numeric amount mismatch |
|
|
| 12 — Date Missing |
|
|
| 13 — Date altered |
|
|
| 14 — Post dated |
|
|
| 15 — Stale dated |
|
|
| 16 — Foreign Check |
|
|
| 17 — Endorsement not as drawn |
|
|
| 18 — Guarantee of amount |
|
|
| 19 — Cannot handle as cash |
|
|
| 20 — Not MICRO coded |
|
|
| 21 — Make deceased |
|
|
| 22 — Invalid power of attorney signature |
|
|
| 23 — Other |
|
|
| 24 — Mutilated |
|
|
| 25 — Exceeds cash advance limit |
|
|
| 26 — Under minimum withdrawal amount |
7 | 2 | 23–32 | EMPLOYEE-ASG-NUM Optional |
8 | 3 | 1–14 | ORIGINAL-DC-AMT — Overlay $'s with check amount. Must be .01 through 999,999,999.99 |
9 | 4 | 1-24 | TRACE-ID -- Must be entered in nn-nn-nnnnnnn-nnn-nnnnnn format. The TRACE-ID specifies the following: SP Campus FLC or other SITE ID, System ID, Deposit Date, Sequence Number, Transaction Sequence Number. Note - The Site ID portion of the TRACE-ID does not have to be a current, valid one. It can be one from the past. |
10 | 5 | 1–4 | PAYMENT-TYPE-CD — Must be entered. Valid codes and meanings are: |
|
|
| REGU — Regular Remittance |
|
|
| MULT — Multiple Remittance |
|
|
| SPLT — Split Remittance |
|
|
| MUSP — Multiple/Split Remittance |
11 | 5 | 6-13 | IRS-RCVD-DT — The IRS received date—Overlay MMDDYYYY with date. Must be entered. Cannot be greater than the current date or earlier than the current year minus one. NOTE: Once a date is input it will be displayed in subsequent screen formats until overlaid or interrupted by a command code other than BDADD. |
12 | 6 | 1–35 | FIRST-NAME-LINE — Must be entered. Valid characters are A–Z, 0–9, hyphen, ampersand, or blank. First position must be alpha or numeric. Only one comma can be present and (if present) must be immediately preceded and immediately followed by at least one alpha or numeric character. Any character following two or more sequential blanks is invalid. Examples of 1st Name Lines entered and the Name Controls which will be generated: |
|
|
| 1ST NAME LINE | NAME CONTROL |
|---|---|---|---|---|
|
|
| Smith,J | SMIT |
|
|
| Smith,John [slashb] R | SMIT |
|
|
| Robert [slashb] A[slashb]Jones[slashb] Corp | ROBE |
|
|
| A&B [slashb]Truck[slashb] Co | A&BT |
|
|
| Lee,Thomas | LEE |
|
|
| Unknown | UNKN |
13 | 7 | 1–35 | SECOND-NAME-LINE — May or may not be entered. If entered, valid characters are A–Z, 0–9, ampersand, hyphen, %, slash or blank. Must contain a valid character other than blank in the first position. Any character following two or more sequential blanks is invalid. |
14 | 8 | 1–35 | STREET ADDRESS — Same validity checks as 2nd Name Line above. If entered, the CITY/ST/ZIP must also be entered. |
15 | 9 | 1–35 | CITY-ST-ZIP — Must be present if Street Address is present, otherwise, may be blank. If field is present, it must contain one of the following: |
|
|
| Examples — Major-City-Code input: |
|
|
| LA |
|
|
| NY 10004 |
|
|
| Example — complete City/State/Zip input: |
|
|
| Bowie, MD 20715 |
|
|
| NOTE: A blank must not immediately precede the comma. |
|
|
| 1. City — valid characters are A–Z, 0–9, hyphen, and blank. Must contain at least three valid characters. Characters following two or more sequential blanks are invalid. |
|
|
| 2. State — valid characters are A–Z and must be a valid state abbreviation. |
|
|
| 3. Zip — Can be up to 9 positions, all numeric with intermittent blanks. If only the first 5 positions are entered they must be 00601 through 99999. Positions 4 and 5 cannot be 00. If positions 6 through 9 are entered they must be all numeric. |
|
|
| Exception: If foreign address, enter pound sign # in position 1 followed by the foreign address. |
16 | 10 | 1–11 | TIN — Enter if available. Format must be nnn-nn-nnnnn-nnnnnnn[slashb] and cannot be all zeros or all nines. Must be entered for transcript request . |
17 | 10 | 13-14 | MFT - Enter if available. Format must be nn. The MFT is necessary to locate posted and pending transactions with TC 840 & 846, Erroneous Refunds. |
18 | 10 | 16-18 | EMP-PLAN-NUM - Necessary to locate posted and pending transactions associated with TC’s 840 and 846 Erroneous Refunds. For BMF valid range is (001-499) - (500-999). If MFT is 46 valid ranges are 000, 100-199, 300-399, 500-599, 700-799. |
19 | 10 | 16-21 | TXPRD - Enter if available. Must be numeric in YYYYMM format. Necessary to locate posted and pending transactions with TC 840 & 846, Erroneous Refunds. |
20 | 11 | 1–3 | MRS-IND — Enter "YES" if transcript desired; otherwise, leave blank or the literal. If "YES" entered, TIN must be present. |
21 | 14 | 3–37 | ERROR-MESSAGES — An appropriate error message will be displayed on line 13. |
(3) Valid Response — New BDADD screen format will be displayed with the message REQUEST COMPLETED on line 13. Subtotals of the item count and money count will also be shown on line 1 if Recall Code "C" was entered on the BDADDR input. Note: To clear these totals at the end of block, input any valid COMMAND-CD except BDADD, e.g. TXMOD, SUMRY, etc.
Command CD BDAPLR — Apply Format Request
(1) Input Display BDAPLR:
APPLY-FORMAT-REQUEST
(2) Record Element Description
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD "BDAPL" |
2 | 1 | 6 | COMMAND-CD MODIFIER "R" |
DC Apply Format Record
(1) BDAPL screen format
DC-APPLY-FORMAT-RECORD
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION | FORMAT |
|---|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD | "BDAPL" |
2 | 2 | 1 | APPLICATION-TYPE | "A" |
3 | 3 | 3–20 | DC-CONTROL-NUMBER | "NN-NNN-NNNNN-NNN-N" |
4 | 3 | 1–4 | DC-NAME-CTRL | "NCDC" |
5 | 3 | 6–9 | APPLICATION-NAME-CTRL | "NCAP" |
6 | 3 | 18 | ORIGINAL-PAY-DT | "MMDDYYYY" |
7 | 3 | 20–36 | MF-ORIGINAL-TRANS-DLN | "NNNNN-NNN-NNNNN-N" |
8 | 4 | 1–3 | PRIMARY-TRANS-CD | "ITC" |
9 | 4 | 5–18 | PRIMARY-TRANS-AMT | "$$$$$$$$$$$$$$" |
10 | 4 | 20–28 | OTHER-PENALTY-AMT | "$$$$$$$$$$$$$$" |
11 | 5 | 1–3 | SECONDARY-TRANS-CD | "280" |
12 | 5 | 5–18 | SECONDARY-TRANS-AMT | "$$$$$$$$$$$$$$" |
13 | 5 | 20–22 | TERTIARY-TRANS-CD | "3TC" |
14 | 5 | 24–37 | TERITARY-TRANS-AMT | "$$$$$$$$$$$$$$" |
15 | 6 | 1–12 | TIN & FILE-SOURCE-CD | "TINb---------b" |
16 | 6 | 14 | DC-NOTICE-IND | "N" |
17 | 6 | 16–17 | DOC-CD | "DC" |
18 | 6 | 19–20 | MFT-CD | "NN" |
19 | 6 | 22–27 | TAX-PRD | "YYYYMM" |
20 | 6 | 29–32 | EP-YR-COUNT & EMPLEE-PLAN-NUM | "YPPP" |
21 | 6 | 20-21 | DESIGNATED-PAYMENT-CD | "DP" |
22 | 7 | 1–36 | COMMENTS | "COMMENTSb----b" |
23 | 8 | 1–6 | TWENTY-THREE-C-DT | "23DATE" |
24 | 8 | 10–14 | LOCATION-CD | "LOCCD" |
25 | 8 | 16–32 | NMF-APPLY-DLN | "NNNNN-NNN-NNNNN-N" |
26 | 9 | 1–36 | FIRST-NAME-LINE | "1STbN/Lb------b" |
27 | 10 | 1–36 | SECOND-NAME-LINE | "2NDbN/Lb------b" |
28 | 11 | 1–36 | STREET-ADDR | "STREETb------b" |
29 | 12 | 1–36 | CITY-ST-ZIP | "CY/ST/ZPb-----b" |
Command CD BDAPL
(1) COMMAND-CD BDAPL — Used to record the application of a dishonored check (in whole or in part) from The Dishonored Check File to a specific tax module. The format is generated by COMMAND-CD BDAPLR and a new BDAPL format will be displayed after each BDAPL entry.
DC-APPLY-REQUEST
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD "BDAPL" generated COMMAND-CD |
2 | 2 | 1 | APPLICATION-TYPE — Must enter M or N as follows: |
|
|
| M — when application is being made to an IMF/BMF/IRAF tax module. |
|
|
| N — when application is being made to a NMF tax module. |
3 | 2 | 3–20 | DC-CONTROL-NUMBER — Must be entered and must match control number on the Dishonored Check File. |
4 | 3 | 1–4 | DC-NAME-CTRL — Must be entered and must match control on the Dishonored Check File. |
5 | 3 | 6–9 | APPLICATION-NAME-CTRL — Must be entered for M type applications only and must match name control on the master file; otherwise, it will unpost. |
6 | 3 | 11–18 | ORIGINAL-PAY-DT — Must be entered and must agree with the date of the credit transaction which is being reversed out; otherwise, it will unpost. |
7 | 3 | 20–36 | MF-ORIGINAL-TRANS-DLN or NMF-UNIT-LEDGER-CARD-ID — Must be entered. |
8 | 4 | 1–3 | PRIMARY-TRANS-CD — Overlay 1TC with a valid transaction code as follows: 611, 621, 641, 661, 671, 681, 691 or 721. See TABLE OF VALID TC/MFT/DOC CD for valid combinations. |
9 | 4 | 5–18 | PRIMARY-TRANS-AMT — Overlay $'s with amount which must be .01 through 999,999,999.99 left justified, e.g. 222,650.50$$$$ |
10 | 4 | 20–28 | OTHER-PENALTY-AMT — If entered, overlay $'s with amount which must be .01 through 99,999.99 left justified. |
11 | 5 | 1–3 | SECONDARY — Trans-CD — Format will contain a generated "280 " penalty transaction. |
12 | 5 | 5–18 | SECONDARY-TRANS-AMT — If left blank ($'s are considered blank), the penalty will be generated. If no penalty is to be assessed, or if the penalty amount being assessed is different than what would be generated, the amount must be entered. Overlay $'s with .00 through 999,999,999.99 left justified. |
|
|
| If the sum of 1st and 3rd amts is: | Generated penalty will be: |
|---|---|---|---|---|
|
|
| Less than $5.00 | No Penalty |
|
|
| $5.00 to $24.99 | Equal to the amount of the check. |
|
|
| $25.00 to $1,249.99 | $25.00 |
|
|
| More than $1,249.99 | 2% of the sum of the 1st and 3rd amounts |
13 | 5 | 20–22 | TERTIARY-TRANS-CD — If entered must be "682". See TABLE OF VALID TC/MFT/DOC CD for valid combinations. |
14 | 5 | 25–37 | TERTIARY-TRANS-AMT — Must be present if TERTIARY-TRANS-CD is present; must not be present if TERTIARY-TRANS-CD is not present. Overlay $'s with .01 through 999,999,999.99 left justified. |
15 | 6 | 1–12 | TIN & FILE-SOURCE-CD — The TIN must be entered in EIN or SSN format followed by a valid FILE Source. Must meet standard validity and consistency checks. Also, the APPLICATION-TYPE (Item 2) must be consistent with the file source entered here. |
16 | 6 | 14 | DC-NOTICE-IND — Must enter "I" if form 2287C (IDRS Notice 587 — Notice of Check Not Accepted By Bank) is to be issued; must enter "S" if the notice is to be suppressed. |
17 | 6 | 16–17 | DOC-CD — Must enter 87, 45, or 24. (Doc Code 24 is valid with N type of applications only.) Also, see TABLE OF VALID TC/MFT/DOC CD for valid combinations. |
18 | 6 | 19–20 | MFT-CD — Must be entered. See TABLE OF VALID TC/MFT/DOC CD. |
19 | 6 | 22–27 | TAX-PRD — Must be entered and must meet standard Tax Period Validity checks and MFT/TAX-PRD consistency checks. If MFT 08, TAX-PRD cannot be earlier than 200412. If MFT 14, TAX-PRD cannot be earlier than 200612. If MFT 17, TAX-PRD cannot be earlier than 200512. If MFT 35, TAX-PRD cannot be earlier than 201412. If MFT 40, TAX-PRD cannot be earlier than 200401. If MFT 43, TAX-PRD cannot be earlier than 201512. If MFT 74 or 76, TAX-PRD must be left blank. |
20 | 6 | 29–32 | EP-YR-COUNT & EMPLEE-PLAN-NUM/ REPORT-NUM — Must be entered for MFT 74 or 76. For NMF applies valid range is (001-999). For Masterfile applies, valid range is (001-499) - (500-999). If MFT 46 a valid range of 000, 100-199, 300-399, 500-599, 700-799. |
21 | 6 | 34-35 | DESIGNATED-PAYMENT-CD — Must enter 44 - 51 if PRIMARY TC is 695. |
21 | 7 | 1–35 | COMMENTS — Enter necessary information. |
22 | 8 | 1–8 | TWENTY-THREE-C-DT — Must be entered when APPLICATION TYPE is "N". Optional if LOC-CD is present. Format is MMDDYYYY. |
23 | 8 | 10–14 | LOC-CD — Must be entered if APPLICATION TYPE is "N". Optional if TWENTY-THREE-C-DT is present. Format is nnnnn. |
24 | 8 | 16–32 | NMF-APPLY-DLN — Must be entered if APPLICATION TYPE is "N"; otherwise leave blank. |
25 | 9 | 1–35 | FIRST-NAME-LINE — If entered, the CITY-ST-ZIP must also be entered. |
26 | 11 | 1–35 | SECOND-NAME-LINE — If entered, the FIRST-NAME-LINE and the CITY-ST-ZIP must also be entered. |
27 | 11 | 1–35 | STREET-ADDR — If entered, the FIRST-NAME-LINE and the CITY-ST-ZIP must also be entered. |
28 | 12 | 1–35 | CITY-ST-ZIP — If entered, the FIRST-NAME-LINE must also be entered. If field is present, it must contain one of the following: |
|
|
| Examples — Major-City-Code input: |
|
|
| LA |
|
|
| Example — complete City/State/Zip input: |
|
|
| Bowie, Md 20715 |
|
|
| Note: A blank must not immediately precede the comma. |
|
|
| 1. City — valid characters are A–Z, 0–9, hyphen and blank. Must contain at least three valid characters. Characters following two or more sequential blanks are invalid. |
|
|
| 2. State — valid characters are A–Z and must be a valid state abbreviation. |
|
|
| 3. Zip — Can be up to 9 positions, all numeric with intermittent blanks. If only the first 5 positions are entered they must be 00601 through 99999. Positions 4 and 5 cannot be 00. If positions 6 through 9 are entered they must be all numeric. |
|
|
| Exception: If foreign address, enter pound sign # in position 1 followed by the foreign address. |
|
|
| Note: — If any name and address data is entered on the screen in Items 24 through 27, the data must constitute a complete name and address data are for ensuring that a complete name and address have been entered. The minimum complete name and address is FIRST-NAME-LINE and CITY-ST-ZIP. |
|
|
| The name and address information is extracted from the TIF. If the name and address is not on the TIF, then the address is extracted form the DCF database. If the address information is incorrect, the information will need to be overlaid with the correct information. |
Table of Valid TC/MFT/DOC CD
Command CD BDOUTR
(1) COMMAND-CD BDOUTR — Used to request COMMAND-CD BDOUT format.
(2) Input Display:
AMT-CHANGE-VOID—FORMAT-REQUEST
(3) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD "BDOUT" |
2 | 1 | 6 | COMMAND-CD-MODIFIER "R" |
BDOUT Screen Format
(1) Terminal Response to BDOUTR is the BDOUT screen format as shown below:
DC-AMT-CHANGE-VOID-FORMAT-REC
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION | |
|---|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD | "BDOUT " |
2 | 2 | 1 | APPLICATION-TYPE | "T" |
3 | 2 | 3–20 | DC-CONTROL-NUMBER | "NN-NNN-NNNNN-NNN-N " |
4 | 3 | 1–4 | DC-NAME-CTRL | "NCDC" |
5 | 4 | 1–14 | CORRECT-AMT | "$$$$$$$$$$$$$$ " |
6 | 5 | 1–35 | COMMENTS | "COMMENTSb----- [slashb]" |
Command CD BDOUT
(1) COMMAND-CD BDOUT — Used to correct or void an erroneous DC record which is on the Dishonored Check File. The format is generated by COMMAND-CD BDOUTR and a new BDOUT format will be displayed after each BDOUT entry.
(2) Input Display:
DC-AMOUNT-CHANGE-VOID-REQ
(3) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION AND VALIDITY |
|---|---|---|---|
1 | 1 | 1–5 | "BDOUT" generated COMMAND-CD |
2 | 2 | 1 | APPLICATION-TYPE — Must enter V, Z, A, I, R, X, P or D as follows: |
|
|
| V — when a record on the Dishonored Check File is being voided. |
|
|
| Z — when the money amount of a record on the Dishonored Check File is being corrected. |
|
|
| P — when a record on the Dishonored Check File is being partial voided. |
|
|
| Use these APPLICATION TYPE codes when the Dishonored Check records must be removed for the following reasons: |
|
|
| A — when the check covers payment of an Alcohol, Tobacco and Firearms return. |
|
|
| I — when it is a non-IRS check. |
|
|
| R — when the check is being redeposited. |
|
|
| X — when it is a missing check. |
|
|
| D — when the check is on the Unidentified Remittance File in whole or in part. |
3 | 2 | 3–20 | DC-CONTROL-NUMBER — Enter the control number of the Dishonored Check File record to be corrected or voided. |
4 | 3 | 1–4 | DC-NAME-CTRL — Enter the name control of the Dishonored Check File record to be corrected or voided. |
5 | 4 | 1–14 | CORRECT-AMT — Amount must be entered if APPLICATION TYPE is Dishonored Check File record. For APPLICATION TYPE "D", leave blank if entire balance amount is unidentified. If it is partially unidentified, enter the amount that is unidentified. |
|
|
| NOTE: When doing a partial BDOUT "D" and a BDAPL to the same record, BDAPL should be done first. If the BDAPL is done last, the record will remain on the Dishonored Check File for three months. If, however, the BDOUT "D" is done last, the record will be dropped at the end of the month. |
|
|
| If the APPLICATION TYPE is V, A, I, R or X, do not enter any amount |
6 | 5 | 1–35 | COMMENTS — Explain the reason for changing or voiding the Dishonored Check File record. |
COMMAND CD BDENT
(1) COMMAND-CD BDENT — Used to update the FIRST NAME LINE, SECOND NAME LINE, STREET ADDRESS, CITY-STATE-ZIP, TIN, EMPLEE-NUM, TRACE-ID, COMMENTS, MFT/PLAN-NUM, and TAXPRD of a record on the Dishonored Check File
(2) Input Display:
DC-ENTITY-CHANGE-REQUEST
(3) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD "BDENT" |
2 | 2 | 1–4 | DC-NAME-CTRL — Enter name control of the Dishonored Check File record. |
3 | 3 | 1–18 | DC-CONTROL-NUMBER — Enter control number of the Dishonored Check File record. |
|
|
| Note: Lines 4–12 will be used to update the 1st NL, 2nd NL, Street Address, City/State/Zip, TIN, EMPLEE-NUM, TRACE-ID, MFT/PLAN-NUM/TAXPRD, and COMMENTS. The first element being changed must be entered on Line 4. The next element being changed must appear on the next line, etc. |
4 | 4 | 1–38 | FIRST-NAME-LINE — If being changed, enter 1N/ immediately followed by the new FIRST NAME LINE. A new name control will be generated for the Dishonored Check File record. Valid characters are A–Z, 0–9, hyphen, ampersand, or blank. First position must be alpha or numeric. |
|
|
| Only one comma can be present and (if present) must be immediately preceded and immediately followed by at least one alpha or numeric character. Any character following two or more sequential blanks is invalid. Examples of 1st Name Lines entered and the Name Controls which will be generated: |
|
|
| 1ST NAME LINE | NAME CONTROL |
|---|---|---|---|---|
|
|
| Smith, J | SMIT |
|
|
| Smith,JohnbR | SMIT |
|
|
| Robert [slashb]A[slashb]Jones[slashb]Corp | ROBE |
|
|
| A& [slashb]Truck[slashb]Co | A&BT |
|
|
| Lee,Thomas | LEE |
|
|
| Unknown | UNKN |
5 | 5 | 1–38 | SECOND-NAME-LINE — If being added or changed, enter 2N/ immediately followed by the new 2nd name line data. If entered, valid characters are A–Z, 0–9, ampersand, hyphen, %, slash or blank. Must contain a valid character other than blank in the first position. Any character following two or more sequential blanks is invalid. To delete an existing SECOND NAME LINE from the Dishonored Check File record, use: |
6 | 6 | 1–38 | STREET-ADDR — lf being added or changed, enter ST/ immediately followed by the new street address data. The field must contain a valid character other than blank in the first position. To delete an existing street address from the Dishonored Check File record, use: |
7 | 7 | 1–38 | CITY-ST-ZIP — If being added or changed enter CY/ immediately followed by one of the following: |
|
|
| Examples — Major-City-Code input: |
|
|
| LA |
|
|
| Example — complete City/State/Zip input: |
|
|
| Bowie, Md 20715 |
|
|
| Note: A blank must not immediately precede the comma. |
|
|
| 1. City — valid characters are A–Z, 0–9, hyphen and blank. Must contain at lease three valid characters. Characters following two or more sequential blanks are invalid. |
|
|
| 2. State — valid characters are A–Z and must be a valid state abbreviation. |
|
|
| 3. Zip — Can be up to 9 positions, all numeric with intermittent blanks. If only the first 5 positions are entered they must be 00601 through 99999. Positions 4 and 5 cannot be 00. If positions 6 through 9 are entered they must be all numeric. |
|
|
| Exception: If foreign address, enter pound sign (#) in position 1 followed by the foreign address. |
8 | 8 | 1–14 | TIN — If being added or changed, enter TN/ immediately followed by the new TIN. Format must be nnn-nn-nnnn or nn-nnnnnnn[slashb] and cannot be all zeros or all nines. |
9 | 9 | 1–13 | EMPLEE-NUM — If being added or changed, enter EN/immediately, followed by a 10 digit employee number. |
10 | 10 | 1-24 | TRACE-ID --- If being added or changed, enter TI/immediately followed by the new TRACE-ID. Format must be all numeric and nn-nn-nnnnnnn-nnn-nnnnnn |
11 | 11 | 1-14 | MFT/PLAN-NUM/TAX-PRD --- If either the MFT, PLAN-NUM,or TAX-PRD are being added or changed, all 3 entities must be addressed. Enter TM/ immediately followed by the new valid MFT, PLAN-NUM, and TAX-PRD. Format must be all numeric and nnnnnnnnnnn. Note: For MFTs 46, 74, and 76, a valid numeric PLAN-NUM must be entered. For MFT 46, the PLAN-NUM must be 000, 100 thru 199, 300 thru 399, 500 thru 599, or 700 thru 799. For MFT 74, the PLAN-NUM must be 001 thru 999. For MFT 76, the PLAN-NUM must be 000 thru 499 or 501 thru 999. If the MFT is other than 46, 74, or 76, PLAN-NUM must be 000 or blank. |
12 | 12 | 1–38 | COMMENTS–If being added, enter CM/immediately followed by comments. Use only in conjunction with entity change. |
13 | 15 | 3–37 | ERROR-MESSAGES — An appropriate error message will be displayed on line 15. |
COMMAND CD BDINQ
(1) COMMAND-CD BDINQ used to display an entire DC record
(2) Input Display
DC-INQUIRY-REQUEST
(3) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD — enter, "BDINQ" |
2 | 2 | 1–4 | DC-NAME-CTRL OR |
|
| 1-14 | ORIGINAL-DC-AMT — enter amount of check with decimal point and commas (left-justified). OR |
|
| 1-18 | DC-CONTROL-NUMBER — enter complete DC Control Number in format of nn-nnn-nnnnn-nnn-n or only first two (2) digits in format nn-[slashb]--------------[slashb] |
3 | 3 | 1–14 | ORIGINAL-DC-AMT — enter amount of check with decimal point and commas (left-justified). |
4 | 4 | 1–18 | DC-CONTROL-NUMBER — enter complete DC Control Number in format of nn-nnn-nnnnn-nnn-n or only first two (2) digits in format nn-[slashb]-------------- [slashb] |
5 | 13 | 3–37 | ERROR-MESSAGES — An appropriate error message will be displayed on line 13. |
Command CD BDINQ Terminal Response
(1) Screen display of all data on the Dishonored Check File pertaining to the particular dishonored check. This consists of the basic dishonored check data plus history records of all actions taken and the current status (Open, Closed, Void, Alcohol, Tobacco, and Firearms, Unidentified, NON-IRS, Redeposited, Missing or Unprocessable, Partial Void).
(2) Terminal Response
DC-INQUIRY-RESPONSE SCREEN ONE
(3) Record Element Description:
DC-INQUIRY-RESPONSE-SCREEN-ONE
LINE | POSITION | DESCRIPTION | FORMAT |
|---|---|---|---|
1 | 1–35 | FIRST-NAME-LINE | v_____v |
2 | 1–35 | SECOND-NAME-LINE | v_____v |
3 | 1–35 | STREET-ADDR | v_____v |
4 | 1–35 | CITY-ST-ZIP | v_____v |
4 | 37–40 | STATUS-DC-CD | "OPEN", "CLOS", "VOID", "UNPR", "NIRS", "UNID", "AT&F", "P/V" |
5 | 3–4 | DC-REASON-CD | 01–24 |
5 | 6–22 | DC-CONTROL-NUMBER | nn-nnn-nnnnn-nn-n |
5 | 24-25 | DC-CAMPUS-CD | nn |
5 | 27–41 | ORIGINAL-DC-AMT | $nnn,nnn,nnn.nn |
6 | 3-26 | TRACE-ID | nn-nn-nnnnnnn-nnn-nnnnnn |
7 | 3–6 | PAYMENT-TYPE-CD | "REGU", "MULT", "SPLT", "MUSP" |
7 | 8–15 | IRS-RCVD-DT | YYYYMMDD |
7 | 17–28 | SSN/EIN | nnn-nn-nnnnv OR nn-nnnnnnnv[slashb] |
7 | 30–37 | IDRS-ENTRY-DT | YYYYMMDD |
8 | 3–4 | MFT | nn |
8 | 6-8 | PLAN-NUM | nnn |
8 | 10-15 | TAX-PRD | MMYYYY |
8 | 17-51 | COMMENTS | v---------------------------------v |
9 | 3-12 | EMPLOYEE-NUM | nnnnnnnnnn |
9 | 14-28 | DC-BALANCE-AMT | $nnn,nnn,nnn.nn |
9 | 30-37 | LAST-APPLICATION-DT | YYYYMMDD |
10 | 1 | REC-TYPE-CD | "M" |
10 | 3–10 | MF-APPLY-DT | YYYYMMDD |
10 | 12–15 | DC-NAME-CTRL | vvvv |
10 | 17–28 | TIN | nnn-nn-nnnnv OR nn-nnnnnnnvb |
10 | 30–39 | EMPLEE-NUM | nnnnnnnnnn |
11 | 3–4 | MFT | nn |
11 | 6–11 | TAX-PRD | YYYYMM |
11 | 13–15 | PLAN-NUM | nnn |
11 | 17–23 | FORM-NUM | vvvvvvv |
11 | 25–41 | APPLICATION-DLN | nnnnn-nnn-nnnnn-n |
12 | 3–10 | ORIGINAL-PAY-DT | YYYYMMDD |
12 | 12–28 | MF-ORIGINAL-TRANS-DLN | nnnnn-nnn-nnnnn-n |
12 | 30 | DC-NOTICE-IND | "I" or "S" |
12 | 32-33 | DESIGNATED-PAYMENT-CD | nn |
13 | 3–5 | PRIMARY-TRANS-CD | nnn |
13 | 7–21 | PRIMARY-TRANS-AMT | $nnn,nnn,nnn.nn |
14 | 3–5 | SECONDARY-TRANS-CD | nnn |
14 | 7–21 | SECONDARY-TRANS-AMT | $nnn,nnn,nnn.nn |
14 | 23–32 | OTHER-PENALTY-AMT | $nn,nnn.nn |
15 | 3-5 | TERTIARY-TRANS-CD | nn |
15 | 7-21 | TERTIARY-TRANS-AMT | $nnn,nnn,nnn.nn |
16 | 37-40 | COMMENTS | v___________v |
(4) DC-INQUIRY-RESPONSE SCREEN-TWO
(5) Record Element Description:
LINE | POSITION | DESCRIPTION | FORMAT |
|---|---|---|---|
1 | 1 | REC-TYPE-CD | "N" |
1 | 3–10 | NMF-APPLY-DT | YYYYMMDD |
1 | 12–23 | TIN | nnn-nn-nnnnv OR |
1 | 25–34 | EMPLEE-NUM | nnnnnnnnnn |
1 | 36–43 | TWENTY-THREE-C-DT | nnnnnnnn or |
2 | 3–4 | MFT | nn |
2 | 6–11 | TAX-PRD | YYYYMM |
|
| EP-YR-COUNT and EMPLEE-PLAN-NUM | Ynnn |
2 | 13–19 | FORM-NUM | vvvvvvv |
2 | 21–37 | APPLICATION-DLN | nnnnn-nnn-nnnnn-n |
3 | 3–10 | ORIGINAL-TRANS-DT | YYYYMMDD |
3 | 12–28 | NMF-UNIT-LEDGER-ID | nnnnn-nnn-nnnnn-n |
3 | 30 | DC-NOTICE-IND | "I" or "S" |
4 | 3–5 | PRIMARY-TRANS-CD | nnn |
4 | 7–21 | PRIMARY-TRANS-AMT | $nnn,nnn,nnn.nn |
5 | 3–5 | SECONDARY-TRANS-CD | nnn |
5 | 7–21 | SECONDARY-TRANS-AMT | $nnn,nnn,nnn.nn |
5 | 23–32 | OTHER-PENALTY-AMT | $nn,nnn.nn |
6 | 3–5 | TERTIARY-TRANS-CD | nnn |
6 | 7–21 | TERTIARY-TRANS-AMT | $nnn,nnn,nnn.nn |
7 | 3–37 | COMMENTS | v____________v |
8 | 1 | REC-TYPE-CD | "U" |
8 | 3–10 | CLOSING-DT | YYYYMMDD |
8 | 12–36 | LITERAL | "WRITE-OFF TO 1510 ACCOUNT" |
9 | 3–17 | CLOSED-AMT | $nnn,nnn,nnn.nn |
10 | 1 | REC-TYPE-CD | "C" |
10 | 3–10 | CHANGE-DT | YYYYMMDD |
10 | 12–23 | OLD-TIN | nn-nnnnnnnvb OR |
10 | 25–34 | EMPLEE-NUM | nnnnnnnnnn |
11 | 3–37 | COMMENTS | v____________v |
(6) DC-INQUIRY-RESPONSE
SCREEN-THREE
(7) Record Element Description:
DC-INQUIRY-RESPONSE-SCREEN-THREE
LINE | POSITION | DESCRIPTION | FORMAT |
|---|---|---|---|
1 | 3–5 | FIRST-NAME-LIT | "1N/" |
1 | 6–40 | OLD-FIRST-NAME | v_____v |
2 | 3–5 | SECOND-NAME-LIT | "2N/" |
2 | 6–40 | OLD-SECOND-NAME | v_____v |
3 | 3–5 | STREET-ADDR-LIT | "ST/" |
3 | 6–40 | OLD-STREET-ADDR | v_____v |
4 | 3–5 | CITY-ST-ZIP-LIT | "CY/" |
4 | 6–40 | OLD-CITY-ST-ZIP | v_____v |
5 | 3-5 | TRACE-ID-LIT | "TI/" |
5 | 6-19 | OLD-TRACE-ID | v_____v |
6 | 3–4 | COMMENTS-LINE-LT | "CM/" |
6 | 6–40 | COMMENTS-LIN | v_____v |
7 | 1 | REC-TYPE-CD | "A, V,D,I,R, P, X" |
7 | 3–10 | CHANGE-DT | YYYYMMDD |
7 | 12–15 | LITERAL | "VOID, AT&F, NIRS, REDP, MISS, NIRSP/V" |
7 | 17–31 | REDUCED-AMT | $nnn,nnn,nnn.nn |
7 | 33–42 | EMPLEE-NUM | nnnnnnnnnn |
8 | 3–37 | COMMENTS | v_____v |
9 | 1 | REC-TYPE-CD | "Z" |
9 | 3–10 | CHANGE-DT | YYYYMMDD |
9 | 12–21 | LITERAL | "AMT CHANGE" |
9 | 24–38 | CHANGE-AMT | $nnn,nnn,nnn.nn |
9 | 39 | SIGN | "+" OR "–" |
10 | 3–10 | LITERAL | "ORIG AMT" |
10 | 12–26 | ORIGINAL-DC-AMT | $nnn,nnn,nnn.nn |
10 | 28–37 | EMPLEE-NUM | nnnnnnnnnn |
11 | 3–37 | COMMENTS | v_____v |
DC-INQUIRY-RESPONSE
(1) Terminal Response
(2) Record Element Description:
ITEM | LINE | POSITION | DESCRIPTION AND VALIDITY |
|---|---|---|---|
1 | 1 | 1–5 | COMMAND-CD-CC BDINQ |
2 | 1 | 10–15 | AMT-LITERAL |
3 | 1 | 26–39 | ORIGINAL-DOLLAR-AMT-EDITED |
4 | 2–20 | 2–5 | NAME-CTRL |
5 | 2–20 | 7–23 | DC-CTRL-NUM-EDITED |
