Accessibility Skip to Top Navigation Skip to Main Content Home  |  Change Text Size  |  Contact IRS  |  About IRS  |  Site Map  |  Español  |  Help  

Part 3. Submission Processing

Chapter 17. Accounting and Data Control

Section 30. SC Data Controls (Cont. 1)

3.17.30  SC Data Controls (Cont. 1)

3.17.30.4 
Adjusting the SCCF

3.17.30.4.2 
From and To Codes

3.17.30.4.2.2  (01-01-2009)
Standard From and To Code Combinations

  1. The standard From–To combinations are:

    From Code To Code Meaning
    0 0 Master Control Record
    0 1 BOB Control Record
    0,1,3,4 5 Good Block Proof Record
    0,1 3 Error Block Proof Record
    0,1,3,6 4 Reject Block Proof Record
    0,1,3,4 2 Old DLN Renumber BPR
    0 0 New DLN Renumber BPR
    5 0 Delete
    1,2,3,4,5,6 0 Reinput Block Proof Record
    0,1,3,4,6 2 Delete Block Proof Record

  2. Any of these From–To combinations may also be input with a SCCF adjustment.

  3. Remember that for any standard adjustment, code 0 or 1 changes the manual balance, code 2 changes the file delete balance, code 3 changes the error balance, and code 4 changes the reject balance. Code 5 affects the good balance, and Code 6 may affect the good or the original balance.

  4. Codes 8–0 and 7–0 should be used when the count and/or amount was established incorrectly Block document counts corrected by batch transmittal changes and BOB Code R corrections are examples where From–To Codes 8–0 and 7–0 should be used.

  5. Code 8–0 indicates that the documents or money is not being moved to another DLN or to another IRACS account. Code 8–0 may be used if the documents or money had previously been established elsewhere.

  6. Use Code 0–2, 1–2, 3–2, or 4–2 if documents or money are being deleted and moved or routed elsewhere.

  7. The distinction is intended to help preserve an effective audit trail. That is, when To Code 2 is used, we should expect the audit trail to lead to a new DLN, new general ledger account, or to a document that has been voided.

3.17.30.4.2.3  (01-01-2009)
Other From and To Codes

  1. Code 8–2 is used to delete a SCCF module immediately. Most normal validity checks are bypassed so that invalid data can be removed.

    1. Code 9–9 is an informational code that may be used with any source code to record a SCCF related action. For example, use 99D to record a delete from TEP or ECC. This code has no effect on SCCF balances or indicators.

    2. Code 2–0 should be used when a document or money amount has a delete adjustment (code 0–2, 1–2, 3–2 or 4–2) that needs to be reversed.

3.17.30.4.2.4  (01-01-2009)
Sequence of Posted Adjustments

  1. On-line SCCF adjustments post in the order that they are input. Batch control records are sorted and posted in the following sequence:

    1. Master file system code

    2. DLN

    3. Record type ID Code—Of the control records input through batch processing, MCRs (Record Type 1) are sorted first, followed by SCCF adjustments (code 0), BOB control records, generated SCCF adjustments, Reinput and delete block proof records, Renumber records, and Good/Error/Reject Block Proof Records.

    4. From Code—Within record type, control records are sorted beginning with the lower numbered From Code.

      Exception:

      Adjustments with codes 3–0, 4–0, 5–0, 7–0, and 8–0 are sorted immediately after Code 0–0.

    5. To Code—Within From Code, the record with the lower To Code is posted first.

    6. Reinput Source Code

3.17.30.4.3  (01-01-2009)
Control Records Source Code

  1. The source code of adjustments identifies the area which initiated the record.

  2. The Control Record Source Code is required for every SCCF adjustment, including renumber adjustments. The code should indicate the source of the adjustment. When selecting a code, remember that only codes D and R will adjust the Block Proof Summary (PCD). Some of the codes that may be used are:

    Code Name
    A Age Review
    B Block-out-of-Balance Status
    C Control Record List
    D ECC Delete
    E Error Delete
    F ERS
    G NMF Good Block Proof Record
    J Journal action pending
    K BBTS Adjustments
    M Miscellaneous
    N Nullified
    P Report period
    R Reject unit
    T Invalid Posting Transcript
    W IRP OCR
    X Generated if no code is input

  3. Source Code A is used when an adjustment is made from the Aged transcripts.

  4. Source Code B is used when an adjustment is made by the BOB Function and for SCCF-related BOB Code adjustments.

  5. Adjustments made from the Control Record list to correct error codes; to correct erroneous MCR's; and to create MCR's normally created on the Master CRL are assigned a source Code C.

  6. Source Code D is used for ECC deletes.

  7. Source Code E is used by the Input Correction Operation.

  8. Source Code F identifies adjustments made by the ERS System or for an ERS record.

  9. Source Code J should be used whenever a IRACS journal action is required but was not completed prior to input. Verify from the adjustment list that the journal action is being completed.

  10. Source Code K identifies adjustments originating from BBTS.

  11. Use Source Code M when none of the other Control Record source codes applies.

  12. Source Code N is used for adjustment to Nullified Unpostables.

  13. Source Code P pertains to the report period. Use code P as an alert that a correction to the MBCS may be necessary for revenue receipt balancing.

  14. Source Code R is used for adjustments input by the Reject Function

  15. For all adjustments prepared as the result of the invalid posting transcript assign Source Code T.

  16. Any adjustment (regardless of source) for an IRP OCR block should include Source Code W.

  17. Other codes may be established locally with designated special meanings.

3.17.30.4.4  (01-01-2009)
Input of Command Code SCFAJ

  1. Enter Command Code SCFAJF to display a SCCF adjustment screen. (See figure 3.17.30-30)

    Figure 3.17.30-30

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Overlay the X's with the required information.

    2. The Block DLN, From-To Code, Master File Code, and Remarks fields are mandatory.

    3. The remaining fields should be entered when needed.

    4. To blank a field after data has been entered, overlay with spaces.

3.17.30.4.4.1  (01-01-2009)
SCFAJ Fields

  1. Enter the fields as follows:

  2. Block DLN—Enter the 12-digit block DLN with year digit.

    1. Be sure that the correct number has been entered before transmitting, as the wrong SCCF module could be updated.

    2. The SCFAJ program does not allow more than 12 digits to be entered.

  3. Master File—Enter the correct numeric code for the file being adjusted.

    • 1 IMF

    • 2 BMF

    • 3 EPMF

    • 5 IRP

    • 6 NMF

  4. From To Codes—See 3.17.30-31 for the appropriate codes.

  5. Reinput Source Code—Leave blank unless one of the following applies:

    1. Enter N for a document that has been Unpostable if the from–to code is 0–0, 6–0, or 6–4.

    2. Enter R for a reprocessable with from–to code 0–0, 6–0, or 6–4. Code R should take precedence over code N if both apply.

    3. Enter U for an IDRS or NMF application from the Unidentified Remittance File with from–to code 0–0 or 0–5 only.

    4. Enter H to override the duplicate DLN check and allow a current list year DLN to be established when the duplication is because of a ten year old SCCF module with Block Status Code H (Historic) or I (Inactive).

    5. Enter E to override the error check and allow multiple deletions for EPMF.

    6. Code 4 may be entered to show a Submission Processing Campus reinput.

3.17.30.4.4.2  (01-01-2009)
Control Record Source Code

  1. Control Record Source Code

    1. Enter the applicable code from IRM 3.17.30.4.3.

    2. If the SCCF adjustment has not been journalized, but will require subsequent journal action from the Adjustment CRL, be sure to enter code J, regardless of what other code may apply.

    3. If the Control Record Source Code is omitted, an X is generated.

  2. Document Count—Enter the number of documents being adjusted, without leading blanks or zeros.

  3. Credit Amount—Enter the amount of the credit being adjusted. Do not enter commas or leading zeros.

  4. Debit Amount—Enter the amount of the debit being adjusted. Debit amounts are valid only with document codes 24, 45, 48, 51, 58, and 87.

  5. ABC—Enter the alpha block control number of the block being adjusted, if known.

  6. Serial Number—Enter the document serial number whenever only one document is being adjusted, or when a reference to a specific serial number would improve the audit trail.

  7. NMF Abstract Number

    1. This field is required for NMF when the To Code is 5, unless the abstract number will be generated.

    2. See IRM 3.17.30.17.1 for additional instructions and IRM 3.17.30.17.3 for a list of manual and generated abstract numbers.

3.17.30.4.4.3  (01-01-2009)
Remarks Section

  1. The 14-position remarks field is a mandatory field that should be used to enter any cross-reference DLN and other audit trail information.

  2. Any time a DLN on the document has been changed, it is important to provide cross-reference DLN information on the SCCF for future research by payment tracers and other functions. If 14 numerics have been entered, the information is retained and displayed on the transcript in DLN format.

  3. If a cross-reference DLN is entered and other information is also required, enter a second SCFAJ adjustment with from–to codes 9–9 and the additional information in remarks.

3.17.30.4.4.4  (01-01-2009)
Completed Screen

  1. After the screen is completed, recheck the record, especially the DLN, to make sure it has been entered correctly. With the cursor in any location after the remarks data, and transmit. (See Figure 3.17.30-31)

    Figure 3.17.30-31

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. At the end of the day, SCFAJ adjustments are downloaded from real time on run SCF–17, accumulated with all other control records in run SCF–01, and listed on the SCF–11–41 Adjustment Control Record List. However, the record has already posted to the SCCF, so it is not passed to the SCF–03 posting run. On-line SCCF adjustments are not revalidated by the batch programs. Only control records from other sources can be error coded or invalid.

3.17.30.4.5  (01-01-2009)
Validation of Command Code SCFAJ

  1. Each SCFAJ adjustment is immediately validated and posted to the SCCF using the same checks as for batch processing.

  2. If the SCFAJ record fails a CRL validity check, it is redisplayed with an error message. (See figure 3.17.30-32)

    Figure 3.17.30-32

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. The same error codes apply as for other control records on the CRL. Up to three error messages may display at one time.

  4. The valid error messages are:

    • Error Code 1: Invalid DLN

    • Error Code 3: Bad Doc Code/Master File Combination

    • Error Code 5: Credit or Debit Fields are Inconsistent

    • Error Code 8: Invalid NMF Abstract Number

    • Error Code 9: Invalid Document Count

    • Error Code 0: Invalid Amount Field

    • Error Code B: Invalid Reinput Source Code

    • Error Code C: Incomplete Adjustment Record

    • Error Code E: Invalid Entry for Deletion

    • Error Code T: Invalid Tax Class

    • Error Code U: Unable to Determine NMF True Tax Class

    • Error Code Y: Invalid From–To Code

    • Error Code Z: Invalid Master File System ID Code

  5. To correct the adjustment screen, overlay with correct data any field that is invalid. Be sure to blank out any field or position that should be removed.

  6. Move the cursor to the bottom of the screen, and retransmit. (See figure 3.17.30-33)

    Figure 3.17.30-33

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  7. If you decide not to input the adjustment, overlay the SCFAJ command code with any other command and transmit.

3.17.30.4.5.1  (01-01-2009)
SCCF CRL Validity Checks

  1. When the SCCF adjustment passes the CRL validity checks, the record attempts to post the SCCF.

  2. If accepted, the screen will display the message "Request Completed—Block DLN XXXXXXXXXXXX Updated" , and re-display the SCFAJ screen with the same record. To input a new adjustment, either overlay the displayed fields (being careful to blank unneeded data) or transmit SCFAJF to receive a blank screen.

3.17.30.4.5.2  (01-01-2009)
SCCF CRL Failed Validity Checks

  1. If the record fails to post to the SCCF, control is passed to Command Code SCFTR which displays the Invalid Transcript. (See figure 3.17.30-34)

    Figure 3.17.30-34

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. A transcript code is displayed to the left of the DLN. The standard invalid posting conditions of SCF–07–43 are made in real time and displayed.

    2. The invalid record is shown at the bottom of the transcript.

    3. When you determine what changes are needed to be made to the adjustment, enter SCFAJF and reenter the corrected record, and transmit. (See figure 3.17.30-35)

      Figure 3.17.30-35

      This image is too large to be displayed in the current screen. Please click the link to view the image.

    4. At any time, if you decide not to complete the adjustment, overlay the displayed command code and transmit.

    5. If the adjustment fails to find a matching DLN on the control file (and will not establish a module), the message "No Matching Record found on Data Base" is displayed.

    6. To prevent incorrect data from posting to the SCCF, be sure to verify the information, especially the DLN, on the screen before transmitting. Once the adjustment has posted to the SCCF, it cannot be backed out, except by preparing a new adjustment, such as an 8–2 after a 0–0.

3.17.30.4.5.3  (01-01-2009)
CRL Posted Adjustments

  1. All on-line SCCF adjustments that posted to the SCCF will be printed on the next Adjustment CRL.

    1. The IDRS employee number is printed for all on-line adjustments to distinguish from ISRP or generated adjustments.

    2. The Remarks information does not appear on the Adjustment list, due to a lack of space. However, the remarks are part of the SCCF record and appear on any on-line or printed transcript.

3.17.30.4.6  (01-01-2009)
Preparation of Form 4028

  1. Prepare Form 4028 when an adjustment to the SCCF will be input by ISRP or when required by local procedures to document an adjustment input on SCFAJ. (See Figure 3.17.30-36)

    Figure 3.17.30-36

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Serial #—This is a Consecutive two digit serial number assigned later for transcribing for the ISRP system. See 3.17.30.4.8

    2. SC or Alpha Block Control Number—For adjustments made from the Invalid Transcript, use the actual ABC to prevent problems on the Cycle Proof List. For other adjustments, the CRL julian date or other audit trail information may be used.

  2. Adjustment Code

    1. From Code—identifies where the record is coming from.

    2. To Code—identifies where the record is moving to. (See IRM 3.17.30.4.2

  3. Reinput Source Code

    1. Enter N for a document that has been unpostable. This code is necessary only with adjustment codes 00, 60, and 64.

    2. Enter R for a reprocessable. This code is normally used with 00, but is necessary for 60 and 64 if a reprocessable subsequently unposts and is nullified. Code R should take precedence over the N.

    3. Enter U for an IDRS or NMF application from the Unidentified Remittance File with adjustment code 00 or 05 only.

    4. Code H will override the duplicate DLN check, reactivate the original module from Historic, and allow a block that has been completely processed to be set up with 00 again. The H is valid with SCFAJ only.

    5. Code E will override the error check for multiple EPMF deletes, but should rarely be used. Code E is valid only with Command Code SCFAJ.

    6. Code 4 may be entered to indicate a Submission Processing Campus reinput.

3.17.30.4.6.1  (01-01-2009)
Master File

  1. Master File—identifies the Master File

    • IMF use number 1

    • BMF use number 2

    • EPMF use number 3

    • IRP use number 5

    • NMF use number 6

3.17.30.4.6.2  (01-01-2009)
Block DLN

  1. Block DLN is the DLN of the block being adjusted.

    • Submission Processing Campus or Area Office—2 digits

    • Tax Class and Document Code—3 digits

    • Julian Date—3 digits

    • Block Number—3 digits

    • Year—1 digit

3.17.30.4.6.3  (01-01-2009)
Document Count and Adjustment Amount

  1. Document Count—this is the total number of items being adjusted. Do not precede with zeros.

  2. Adjustment Amount—This is the total amount being adjusted.

    • Credit

    • Debit

3.17.30.4.6.4  (01-01-2009)
Serial Number

  1. Serial Number—Enter the DLN serial number whenever only one document is affected by the adjustment. This will improve the SCCF audit trail by allowing many Aged review and posting transcript cases to be identified by 14-digit DLN.

3.17.30.4.6.5  (01-01-2009)
Control Record Source Code

  1. Control Record Source Code—This is the code identifying the area where the adjustment is being initiated from. See 3.17.30.4.3 for the Codes.

3.17.30.4.6.6  (01-01-2009)
NMF Abstract Number

  1. NMF Abstract Number—For NMF adjustments with To Code 5, enter a valid NMF abstract number, unless the abstract number will be generated. See IRM 3.17.30.17.3 for a list of NMF document codes and related abstract information.

    1. Reason for Adjustment—This is the reason the SCCF is being adjusted. Use journal number for references if applicable. Use Form 2345 number and Program number. Enter the julian date of the CRL or transcript being adjusted.

    2. The top of the Form 4028 identifies the Master File, the control number of the adjustments, name of preparer, date and number of pages submitted by preparer.

    3. The SCCF does not require adjustments to be input separately for each master file. However, a master file sort may be required locally.

    4. Form 4028 is used as a tool when researching and balancing accounts or resolving error codes on the CRL adjustment list.

3.17.30.4.7  (01-01-2009)
Preparation of Form 4028–A

  1. Prepare Form 4028–A to delete one DLN and simultaneously establish a renumber DLN on the SCCF. (See figure 3.17.30-37)

    Figure 3.17.30-37

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. Serial #—An assigned, consecutive 2 digit number assigned later.

  3. SC or ABC number—the document ABC number or julian date of the CRL.

  4. From Code—Normally "0" when prepared by Data Controls. The To Code is generated and not part of the input record.

  5. Reinput Source Code—"R" for Reprocessable, "N" for Nullified Unpostables, or "4" for Submission Processing Campus reinput. Usually blank.

  6. Master File Code—See top of form for the appropriate code.

  7. Original DLN—DLN of block being deleted.

  8. Document Count—Number of items being deleted and established under new DLN.

  9. Adjustment Amount—Credit or Debit Field Money amount being deleted and established under new DLN.

  10. Original Serial No.—the serial number of the deleted record, if only one document.

  11. Control Record Source Code—Enter a code from the listing in IRM 3.17.30.4.3.

  12. New Block DLN—the new DLN being established for the new block. A DLN must be entered. Literal are valid only from rejects or ERS.

  13. New Serial Number—the serial number of the New DLN, if only one document.

  14. New Master File—Enter the numeric code of the new master file (as shown on top of form) whenever the new DLN is for a master file other than the original DLN. Leave blank if the master file is not changed.

  15. Remarks—Information for an audit trail and a good research tool.

3.17.30.4.7.1  (01-01-2009)
Information on Top of Form 4028–A

  1. The top of the Form 4028–A identifies the Master File and control number of the Adjustments, name of preparer, date, and number of pages used by the preparer.

  2. A To Code "2" will always be generated by the ISRP system.

3.17.30.4.8  (01-01-2009)
Input and Control of SCCF Adjustments

  1. Form 4028–A and any Form 4028 that is not being input with SCFAJ must be blocked for input in the same manner as ISRP Master Control records. Forms 4028 and 4028–A must be blocked separately.

    Figure 3.17.30-38
    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Assign a consecutive two-digit serial number down the left column beginning with 00. The block cannot exceed 100 adjustment records. If no lines are skipped, the serial number is required only on the first and last entries on each page.

    2. No sort by master file is required.

  2. Verify the source document against the corresponding CRL list to assure that all SCCF adjustments have been transcribed. (See figure 3.17.30-39)

    Figure 3.17.30-39

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.5  (01-01-2009)
Control Record List

  1. The following information pertains to the Control Record List.

3.17.30.5.1  (01-01-2009)
Explanation and Contents

  1. The Control Record Listing (CRL) is the name given to the consolidated listing of all records that are processed to the SCCF on a given day.

  2. Although the CRL is produced by a single computer run (SCF–11), the control records are divided into five major segments and printed separately by master file.

    • Master Control Record List

    • Control Record List Adjustment

    • Tape Control Record List

    • Renumber Control Record List

    • Nullified Control Record List

  3. Some control records are so invalid that the CRL program cannot determine the correct list for displaying the record. These will be printed on the Control Record List—Invalid Control Records.

  4. The SCF–01 Run Control Report (SCF–01–60) is a 3–page report listing all of the inputs and outputs of SCF–01.

    1. Page 1 lists all of the input files with the number of records from each file. (See figure 3.17.30-40)

      Figure 3.17.30-40

      This image is too large to be displayed in the current screen. Please click the link to view the image.

    2. Use page 1 to identify any files or records that may have been omitted from the run.

    3. Page 1 may also be used to assist in the daily error and reject balancing.

    4. Page 2 is the output report which lists the number of each type of control record being passed to subsequent runs.

    5. Page 3 provides a copy of the date record information that was used to compute revenue receipts and determine whether the Cycle Proof List and Master Block Control Sheet would be printed.

    6. The bottom of page 3 provides a count of each error code that is printed on the different sections of the CRL.

    7. A copy of page 3, along with instructions for updating the date record can be found in 3.17.30.15.3.

3.17.30.5.2  (01-01-2009)
Invalid Control Record List

  1. Any control record that cannot be recognized as belonging in one of the regular CRL listings will be printed on the Control Record List-Invalid Records.

  2. The Invalid Records List is printed in the input format. (See figure 3.17.30-41)

    Figure 3.17.30-41

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. The conditions included on this listing are:

    • Invalid Record Type Code. Position 1 must be 0,1,2,4,5,6,7, or 8.

    • Invalid From-To Code. Positions 5 and 6 must be a valid from–to combination. See 3(17)(30)4.2

    • Invalid Master File System Code. Position 8 must be 1,2,3,4,5, or 6.

    • Invalid tax class. Position 11 must be numeric and must be a valid tax class for the master file in position 8.

    • Invalid tax class/document code combination on a BOB Release Record. No correction is needed for the SCCF but an adjustment may be needed to the Block Proof Summary.

  4. To help identify and correct the invalid record, the entire record should be examined.

  5. The error code should identify the specific reason that the record is invalid.

  6. For NMF, if the tax class is not equal to 6 (except for SCCF-generated Trans Deletion Control Records), a blank tax class appears on the Invalid List.

  7. Error Codes T, U, V, X, Y, and Z are valid on this listing. See 3.17.30.6 for procedures.

3.17.30.5.3  (01-01-2009)
Adjustment Control Record List

  1. All SCCF adjustments that pass the initial validity checks are printed on the Adjustments portion of the CRL. (See Figure 3.17.30-42)

    Figure 3.17.30-42

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. The records included on this listing include:

    1. On-line adjustments from Command Code SCFAJ.

    2. SCCF adjustments from Form 4028 input through ISRP.

    3. Generated reinput or delete adjustments from Rejects or ERS.

    4. Generated reinput or delete adjustments from IRP input correction.

    5. Generated delete or count change adjustments from BOB correction.

    6. Trans Deletion Control Records from TEP.

    7. NMF Trans Deletion Control Records from SCCF.

    8. NMF applications from URF.

  3. Adjustments (other than on-line which have been already validated) that do not meet the preliminary validity checks will print on the Invalid Records List rather than the CRL Adjustment List.

    1. The preliminary checks are for invalid tax class, master file system code, record type code, and from-to-code.

    2. Once the adjustment record passes these validity checks, the standard CRL error codes apply.

  4. The "CR CD" field is the Control Record Source Code. The codes are explained in 3.17.30.4.3.

  5. The "RC" code is the Reinput Source Code. This field may be blank; significant Reinput Source Codes appearing on the Adjustment CRL are:

    • Code "N" for nullified unpostable.

    • Code "R" for a reprocessable return.

    • Code "U" for an URF application.

    • Code "H" indicates bypass of an error check.

    • Code "E" indicates bypass of an error check.

    • Code "4" indicates a reinput. Although valid on any control record, this code should be present only on certain generated records but serves no function in controls processing.

  6. The "DC" code is the Delete Source Code.

    • Code C indicates a computer generated delete or reinput from BOBs, errors, or tape edit processing.

    • Code S is a TEP delete from an "S" coded delete.

    • Code M is a TEP delete from an "M" code delete.

  7. For on-line SCCF adjustments, the Employee Number of the person entering the Command Code SCFAJ is printed.

  8. The "Net Increase or Decrease" in the summary section is the net effect on open SCCF balances.

    • A record that adds to the manual, error, or reject balance is counted as an increase.

    • A record that subtracts from these balances is counted as a decrease.

    • An adjustment that moves money from one open balance to another, such as from errors to rejects, is not counted as a net change.

  9. The summary of the Adjustment Control Record List provides separate counts for the different types of records on the listing.

    • Form 4028 Adjustments are the SCCF adjustments that have been input by ISRP from Form 4028.

    • SCFAJ Adjustments are the on-line adjustments that have already been validated and posted.

    • Generated SCCF Adjustments contain record type 4 and include count change adjustments from corrected block out of balance registers.

    • Generated Reinputs and Deletes include Trans Deletion Control Records from the TEP and generated reinputs and deletes from rejects, ERS, and BOBs.

3.17.30.5.4  (01-01-2009)
Master Control Record List

  1. The Control Record List-Master Control Records is a listing of blocks established on the Service Center Control File. (See figure 3.17.30-43)

    Figure 3.17.30-43

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.5.4.1  (01-01-2009)
MCR Columns

  1. The MCR list contains five different money columns. The money amount for each MCR will be shown in one of the columns, based on the document code, type of input, and error condition.

  2. The Prejournalized Debit column is used only for current year debit items with document codes 24 and 87.

  3. The Prejournalized Deposit Credit column should balance to the deposit ticket totals for the same processing period.

  4. All prejournalized credits should print in this column except:

    • Document code 24

    • Applications from Unidentified (Reinput Source Code U)

    • Invalid document code (error code 3)

    • Records that have printed on the Invalid Records List

    • Records with a prior fiscal year julian date.

  5. If the deposit cutoff is different from the mainline processing cutoff, additional reconciliation may be necessary to account for timing.

  6. The Non-deposit Credit column contains only document code 24 and applications from Unidentified.

  7. The Other Prejournalized Debit Column contains debits for document codes 45, 48, 51, and 58, plus any invalid document code (error code 3) or prior fiscal year document code 24 or 87 record.

  8. The Other Prejournalized Credit column contains the following:

    • Any credit items with document code 45, 48, 58, or 68.

    • Any credit with an invalid document code (error code 3).

    • Any credit item with a prior fiscal year julian date or no year digit.

3.17.30.5.4.2  (01-01-2009)
Reinput Source Code

  1. The "RC" code is the Reinput Source Code. This code may be blank; significant Reinput Source Codes appearing on the Master CRL are:

    • Code "R" for a reprocessable return.

    • Code "U" for an application from the Unidentified Remittance File (URF).

3.17.30.5.4.3  (01-01-2009)
Input System Source Code

  1. Code "IS" is the Input System Source Code. Any MCR that is generated by other than normal ISRP input will identify the type of input with this code.

    • Code A—ASFR

    • Code C—SCRIPS

    • Code D—Electronic Transmitted Document (ETD)

    • Code E—Electronic Filing

    • Code F—Error Resolution System (ERS)

    • Code G—OPAC/GOALS

    • Code I—IDRS

    • Code R—RRPS

    • Code S—IRP OCR

    • Code U—Unpostables

    • Code Blank—GMF

3.17.30.5.4.4  (01-01-2009)
Serial Number for Reprocessables

  1. The serial number is displayed for Reprocessables only.

3.17.30.5.4.5  (01-01-2009)
Control Date Recap

  1. Each MCR list is accompanied by a Control Date Recap, summarizing by control date the amount of money received in each category. (See figure 3.17.30-44)

    Figure 3.17.30-44

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.5.4.6  (01-01-2009)
NPJ Batch Recap

  1. The NPJ Batch Recap is also received as part of the MCR list and verifies that the volumes were correct. This listing is used to verify that all batch transmittals were transcribed. For Batch Recap balancing procedures, see 3.17.30.2.4 (See figure 3.17.30-45)

    Figure 3.17.30-45

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.5.5  (01-01-2009)
Renumber Control Record List

  1. The Renumber Control Record List contains all Renumber Block Proof Records and Renumber Adjustment Records input through IDRS by the Rejects function using CC NWDLN. Renumber adjustments may also be input through ISRP using the form 4028–A. (See Figure 3.17.30-46)

    Figure 3.17.30-46

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. The renumbered transactions appearing on this listing can come from four sources:

    • BOBS—From Code 1 (non-remit only)

    • Rejects—From Code 4

    • Input Correction—From Code 3 (IRP only)

    • Renumber SCCF Adjustments from Form 4028–A

  3. The Renumber Block Proof Record posts to the old DLN with a cross-reference to the new DLN.

  4. Each renumber record includes either a new DLN or a literal in the renumber field. The valid literals are:

    • URF—Unidentified Remittance File.

    • EXC—Excess Collection

    • SMCR—Small Debit/Credit write off

    • DEPF—Deposit Fund

    • WASH—Washout

    • OTHER—Other write off, including prior fiscal year DLNs and non-revenue DLNs renumbered to Unidentified Remittance

  5. The Renumber Listing may be used to document entries for IRACS. Be sure that every remittance document with a new literal, a change in Master File, or change in tax class is accounted for by IRACS.

  6. A copy of the renumber listing should be sent to the reject function.

  7. The Renumber BPR is invalid if the new DLN is blank, incomplete, or is incompatible with the original DLN for revenue receipts. A literal is valid only with a remittance document. If invalid, the record will print with CRL Error Code 7.

  8. Renumbered transactions are also printed on a list sorted by new DLN. The New DLN Record List, SCF–11–48 allows cross-reference DLN research using either the new or the original DLN. (See figure 3.17.30-47)

    Figure 3.17.30-47

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. This list provides document count total and net money amount total of new DLN's.

    2. The original master file system ID code will be shown if different from the new master file.

    3. This list is routed to Rejects daily for verification of renumbered documents prior to release to Batching.

    4. Be sure to annotate the list before sending to Rejects, so that adjustments that failed to post may be corrected by Rejects.

3.17.30.5.5.1  (01-01-2009)
Renumber Reclassification Summary

  1. The Renumber Reclassification Summary, SCF–11–47, is used by IRACS for journalization of renumbered items.

  2. The "Prejournalized" side of page 1 provides net reclassification of revenue receipts of journalization. The prejournalized side is included on an output tape from SCCF (SCF 11–01) for interface with IRACS for automatic journalization. If changes or corrections are necessary for any part of the prejournalized section, it must be coordinated with IRACS. (See figure 3.17.30-48)

    Figure 3.17.30-48

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Every current fiscal year revenue receipt item that is renumbered to a new current fiscal year DLN or to URF is included and summarized under "Prejournalized."

    2. Both the debit and credit fields show a plus for an increase and a minus for a decrease to the respective field.

    3. Net Reclass amounts are credit balance: Any net increase of a credit and net decrease of a debit is shown with a plus sign; any net increase of a debit and net decrease of a credit is shown with a minus sign.

    4. All non-revenue receipt items renumbered to other non-revenue receipt DLNs or to EXC or SMCR are included under "Other Prejournalized."

    5. Items renumbered to literals DEPF, WASH, and OTHER are not included on page 1, but are included on page 3.

  3. Page 2 is used for IRACS journalization between the SCCF and other accounts. (See figure 3.17.30-49)

    Figure 3.17.30-49

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  4. Every DLN renumbered to a new master file or to URF, EXC, or SMCR is included in Part 1, General Ledger Account Summary.

    1. Part 1 is included on the SCF 11–01 tape interfaced to IRACS for automatic journalization.

    2. No changes to Part 1 should be made without coordination with IRACS.

  5. Every DLN renumbered to DEPF, WASH, or OTHER is included in Part 2, Miscellaneous Accounts.

    1. Items included in Part 2 are included in the summary on page 3.

    2. Journalization of Part 2 must be entered manually into the IRACS system.

  6. Each amount is listed with item count for easier association with the related transactions on the renumber list.

  7. All net amounts are credit balance: Any net increase of a credit or net decrease of a debit is shown with a plus sign; any net increase of a debit or net decrease of a credit is shown with a minus sign.

3.17.30.5.5.2  (01-01-2009)
Reclassification Summary

  1. Page 3 is a reclassification summary which includes items from page 2, Part 2, Miscellaneous Accounts, in DEPF, WASH, and OTHER. (See figure 3.17.30-50)

    Figure 3.17.30-50

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. This summary should be reviewed for accuracy and for potential effect on revenue receipt accounts before routing for journalization by manual entry into the IRACS system.

    1. Corresponding WASH items of current fiscal year revenue receipts require IRACS window 250 reclassification.

    2. Annotate with any other changes based on a review of the documentation that should have been received from rejects.

  3. The literal OTHER may include prior fiscal year items and non-revenue items transferred to Unidentified Remittance. Annotate specific accounts and breakdown of amounts included in OTHER.

  4. Some of the items may effect other general ledger accounts.

3.17.30.5.6  (01-01-2009)
Nullified Control Record List

  1. Any record that is rejected, reinput, or voided by the Generalized Unpostable Framework (GUF) will be printed on the weekly Nullified Control Record List. The format of the list is the same as the format of the Adjustment CRL, except the Reinput Source Code will always be Code "N." (See figure 3.17.30-51)

    Figure 3.17.30-51

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Rejected records (To Code 4) are those items that have been transferred directly from the Unpostable inventory to the Reject or ERS inventory with Unpostable Resolution Code 8.

    2. Reinput records (To Code 0) should be used infrequently, normally only for records that cannot be rejected or voided. These records have been corrected with Unpostable Resolution code 1.

    3. Any uncorrectable non prejournalized document other than some returns can be voided from the unpostable file with Unpostable Resolution code 2 or D. These records contain To Code 2.

  2. Rejected or reinput records are validated using standard CRL error codes.

  3. Voided unpostable records are validated by CRL error codes and are identified with either an asterisk (*) or an Error Code 5.

    1. Records identified with an asterisk are invalid for SCF processing; no attempt should be made to resolve these error codes. Asterisked records are not counted in the total error coded records.

    2. Records identified with Error Code 5 indicate an invalid condition of an attempt to void or delete an unpostable record containing a money amount. These records have been deleted from the GUF system and must be controlled on SCCF. Correct the error coded record on SCFAJ with from–to code 6–0 for reinput. Resolution of Error Code 5 records should be coordinated with the unpostable function.

    3. IMF Tax Class 4 unpostables with IMF DLNs closed with Resolution Code 2D are recorded on the SCF 11–49, Nullified CRL, for IMF TC 4 and are dropped from further SCCF processing.

    4. IMF Tax Class 4 unpostables with IMF DLNs, which are closed with Resolution Codes 1 and 8, will be recorded on the SCF 11–49, Nullified CRL, for IMF, and will be processed in the normal manner as IMF.

  4. The Nullified Unpostables list is accompanied by a Control Date Recap, summarizing by control date money amount brought back onto the SCCF in each category. (See figure 3.17.30-52)

    Figure 3.17.30-52

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  5. See 3.17.30.12.3 for instructions regarding the nullified listings produced by the GUF system.

3.17.30.5.7  (01-01-2009)
Tape Control Record List

  1. The Tape Control Record List contains the control records for all documents going to errors, rejects, or good tape. (See figure 3.17.30-53)

    Figure 3.17.30-53

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Each block DLN can have good, error, and reject documents shown with counts and amounts on the same line.

    2. Only the From Code (FC) is shown on the listing. The To Code is 5 for trans tape items, 3 for errors, and 4 for rejects.

    3. The error codes are the same as the other CRL errors, except that only one code can be printed. If multiple error conditions exist, the additional codes will be suppressed.

    4. Error coded block proof records should be extremely rare, since each record is generated from a mainline program with its own validity checks.

    5. One invalid condition that is not checked in mainline is a reprocessable document with money.

    6. If the document is a true reprocessable and the money should not have been transcribed, delete the block and reinput.

    7. If the R code is incorrect, the return can be allowed to post and the SCCF adjusted manually.

    8. If an unexplained error occurs, notify the Computer Branch of the problem.

    9. If the document must be deleted in TEP, add the record to the delete file using Command Code SCFDLA. Also prepare any necessary SCCF adjustments to put the documents back into manual balance on the SCCF.

    10. The "TI" field is the Treasury Reports Data Indicator. Although the Treasury Report is not produced from SCCF controls, the indicator can still be used to identify ECC deletes or other blocks requiring adjustments to the report.

    11. The "ABS NUM" field is the abstract number for NMF. This field is not currently used as the NMF records are input through SCFAJ.

  2. Error coded Good Block Proof Records are passed to the Revenue Receipts program and included on the RRCS. However, the error coded records do not attempt to post to the SCCF.

  3. The Control Date Recap-Good Block Proof Records is a summary by DLN control date, of all documents and amounts converted to good tape and listed on the corresponding Tape Control Record List. (See figure 3.17.30-54)

    Figure 3.17.30-54

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  4. The Block Sequence List is a listing of all block DLNs shown on the Tape CRL as going to good tape. This list is printed in tape sequence number order. An asterisk indicates that the same block DLN appears twice. Normally, this is not an invalid condition as reprocessable block DLNs frequently are input twice on the same day. (See figure 3.17.30-55)

    Figure 3.17.30-55

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.5.8  (01-01-2009)
Merged Control Records

  1. Some records are consolidated prior to posting to the SCCF.

  2. Multiple control records for the same block DLN on the same day are consolidated in SCF–01 when the following fields are the same on each record:

    • Record type code—The code must not be 0 (SCCF adjustment) or 7 (good block proof record).

    • Alpha block control (if present)

    • From code

    • To code

    • Reinput source code (if present)

  3. When records are consolidated, the item counts and money amounts are added together. The DLN serial number on the consolidated record is XX. (See figure 3.17.30-56)

    Figure 3.17.30-56

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  4. Although the record on the SCCF has been consolidated, each record is listed separately on the CRL. (See figure 3.17.30-57)

    Figure 3.17.30-57

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. Use the CRL to research the serial number or money amounts of the individual records.

    2. As the records have been consolidated before attempting to post to the SCCF, it will be necessary to research the CRL whenever an Invalid Transcript contains an XX on the invalid record.

3.17.30.6  (01-01-2009)
CRL Error Codes

  1. General instructions and error codes are defined in the following sections.

3.17.30.6.1  (01-01-2009)
General Instructions

  1. Every control record is validity checked before attempting to post to ensure that each element of the record contains valid data and is consistent with the other information on the control record.

    1. Any control record that is invalid is identified with an error code and is not passed on for posting to the SCCF.

    2. On-line SCCF adjustments are validity checked immediately and any error codes are identified and displayed for correction.

    3. All other control records are validity checked in SCF–01 and printed with the CRL in SCF–11.

    4. The instructions in this section apply to error codes for both on-line SCFAJ adjustments and SCF–11 CRL errors.

  2. Compare the source document with the error coded record to determine the reason for the error.

    1. If a keying error was made, use Command Code SCFAJ to enter the correct record.

    2. The source document for most error codes on the printed CRL is a Form 2345, Form 9382 or Form 813.

3.17.30.6.1.1  (01-01-2009)
Researching Errors

  1. If the error was not caused by transcription, it may be necessary to locate the block of returns or documents to determine the cause of the error.

    1. Access the Batch Query function of BBTS. Input the program and batch numbers or the DLN of the block to determine the current location of the document(s). When the document(s) are located, verify them to the form 813 or 2345. If the DLN(s) do not match, determine which is correct, the document(s) or form 813/2345.

    2. If the documents are correct, input Command Code SCFAJ with From-To code 0–0 to establish the correct DLN on the SCCF database. Annotate the correct DLN on the CRL. For remittance documents, verify the block total to the journalization done by the IRACS function.

    3. If the SCCF database is correct, have the block deleted out of it's current function in BBTS. Renumber the document(s) and send the block to the Batching function to begin Pipeline processing again.

    4. CRL errors codes for some generated Master Control Records will also appear as a posting transcript on the SCF07–43, SCCF Invalid Transcript Listing. Coordinate with both listings to resolve the error code and annotate the CRL when the correction has been made. Note on both listings when the correction has been made.

    5. Any control record that fails a validity check is error coded on the CRL and will not attempt to post to the SCCF.

    6. Up to three error codes may be present for the same on-line SCCF adjustment, Master Control record, CRL adjustment record, renumber record, or nullified record.

    7. The Tape CRL may have only one error code.

    8. Error Codes T, U, V, X, Y, and Z are found only on SCFAJ records and the Invalid Control Record List, SCF–01–41.

3.17.30.6.2  (01-01-2009)
Error Code 0—Alpha in Money Field

  1. This error condition occurs whenever a character other than numerics or blanks is printed in the debit or credit amount field on the CRL. The condition can also occur if a blank is present in a money field that contains significant data. (See figure 3.17.30-58)

    Figure 3.17.30-58

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. Review the source document or transaction to determine the correct amount. Input Command Code SCFAJ to reconstruct the error coded record. (See figure 3.17.30-59)

    Figure 3.17.30-59

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. Remember that amounts coded with Error Code 0 are not included in any of the tax class summaries, or control date recap totals. When the correct amounts are determined, the totals should be adjusted to include the error coded amounts.

  4. The page total amounts are unreliable if an Error Code 0 is present, because the program converts the invalid character to a numeric when the totals are computed.

3.17.30.6.3  (01-01-2009)
Error Code 1—Invalid DLN

  1. A control record will print with error code 1 if any of the following conditions are present: (See figure 3.17.30-60)

    Figure 3.17.30-60

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. The DLN contains a File Location Code that is invalid for the processing Submission Processing Campus. District codes that were previously valid but have been transferred to other Submission Processing Campuses are now invalid regardless of year digit.

    2. The DLN year digit is for the current year, and the control date is more than ten days later than the current processing date.

    3. The DLN year digit is for next year.

      Exception:

      during the last ten days of the year, the year digit for the following year is valid if the control date is 001–010.

    4. The DLN control date is other than 001–366 or 401–766.

    5. The tax class/document code combination is invalid.

    6. The NMF document code/block number combination does not represent a true tax class.

    7. An NMF revenue receipt document code contains a Submission Processing Campus code rather than Area Office code in the DLN.

    8. The DLN contains non-numeric characters.

    9. The DLN serial number contains other than two numerics or blanks.

  2. Review the source document for transcription errors and prepare any necessary SCCF adjustments. (See figure 3.17.30-61)

    Figure 3.17.30-61

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. If the error code is the result of a true numbering error, assign a new DLN according to local procedures.

3.17.30.6.4  (01-01-2009)
Error Code 2—Invalid Control Record for Source of Input

  1. This error condition occurs whenever a control record contains characteristics inconsistent with those prescribed for records from the indicated source of input.

  2. The Submission Processing Centers identified below are currently processing electronically filed documents. For these Centers, the Area Office codes listed below are restricted for use as File Location Codes (FLC) in the DLN of electronically filed documents.

    Submission Processing Campus P S Submission Processing Campus P S
    Andover 16 14 Kansas City 70 79
    Austin 76 75 Ogden 88 92 93  
    Austin 76 75 Philadelphia 30 66 98 32
    Fresno 80 90      

    • P: Primary FLC

    • S: Secondary FLC

  3. For original MCRs (record type 1, From–To code 0–0, reinput source code blank) with the following document codes, if the FLC in the DLN is a restricted Area Office code, the corresponding Input System Source code must be present. (See Figure 3.17.30-62)

    DOCUMENT CODES
          Input
          System
          Source
    IMF BMF EPMF Codes
    07, 09 16, 44, 65 30, 37, 38 E
    11, 12     E
    21     E
    17     B
      97   T,B
      19, 24, 35   G

    Note:

    Doc. code 28 represents telefile

    Figure 3.17.30-62

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  4. For every control record generated by the Remittance Processing System (RPS), the program number and debit amount must be blank.

  5. Identify the source of input to determine the reason for the error code.

    1. If a file location code reserved for electronic filing was erroneously assigned to a regular block, assign a new DLN and input Command Code SCFAJ to establish the record on the SCCF. (See figure 3.17.30-63)

      Figure 3.17.30-63

      This image is too large to be displayed in the current screen. Please click the link to view the image.

    2. If the record was not an original MCR, input Command Code SCFAJ to recreate the record with a Reinput Source Code.

3.17.30.6.5  (01-01-2009)
Error Code 3—Invalid Document Code

  1. This condition occurs whenever the document code is not valid for any type of input. (See figure 3.17.30-64)

    Figure 3.17.30-64

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. Because the program is unable to recognize the document code, any money amount cannot be accumulated as prejournalized. For this error code only, the money is automatically counted as other Prejournalized.

  3. When an adjustment is prepared to establish the correct DLN, be sure to correct the PJ and OPJ totals. (See figure 3.17.30-65)

    Figure 3.17.30-65

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.6.6  (01-01-2009)
Error Code 4—Duplicate DLN

  1. This condition occurs in the following situations (See figure 3.17.30-66)

    Figure 3.17.30-66

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. An MCR matches the DLN of the previous record and does not contain a reinput source code R (Reprocessable) or cross-reference DLN (renumber record).

    2. An MCR, or Renumber record with a cross-referenced DLN matches the DLN and serial number of the previous record. For this check, the new serial number must be numeric, not blank.

    3. The New DLN and serial number of a Renumber record with a cross-referenced DLN matches the New DLN and serial number of the previous record. For this check, the new DLN must be numeric, not a literal, and the new serial number must be numeric, not blank.

  2. Review the source documents for transcription errors or duplicate input. Prepare an adjustment to correct the record. (See figure 3.17.30-67)

    Figure 3.17.30-67

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  3. Coordinate the Renumbered duplicate DLN with the rejects function, if appropriate.

3.17.30.6.7  (01-01-2009)
Error Code 5—Invalid Amount for Type of Record

  1. This condition occurs in the following situations.

    1. Any control record contains significant amounts in both the credit and debit fields.

    2. A debit amount is present for a document code that allows only credits. (See figure 3.17.30-68)

      Figure 3.17.30-68

      This image is too large to be displayed in the current screen. Please click the link to view the image.

    3. A credit amount is present for a document code that allows only debits.

    4. An amount is present for a document code or master file that allows only non-prejournalized transactions.

    5. Reinput source Code R (reprocessable) is present on a control record that contains a debit or credit amount.

    6. On the Nullified CRL, an unpostable control record containing a money amount has been voided in GUF processing. See 3.17.30.5.6

  2. Review source document or block to determine the reason for the error. Prepare a SCCF Adjustment to input the correct record. (See figure 3.17.30-69)

    Figure 3.17.30-69

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.6.8  (01-01-2009)
Error Code 7—Invalid Renumber Block Proof Record

  1. This condition occurs in the following situations (See figure 3.17.30-70)

    Figure 3.17.30-70

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. A Renumber Block Proof Record contains a literal in the new DLN field but the money amount is zero.

  3. The new DLN contains other than twelve numerics or other than one of the following literals:

    • URF—Unidentified Remittance File

    • EXC—Excess Collection

    • DEPF—Deposit Fund

    • SMCR—Small Debit/credit write off

    • WASH—washout of offsetting transaction

    • OTHER—Other write off and PFY DLNs transferred to Unidentified Remittance

  4. The original DLN and new DLN are incompatible on revenue receipts.

    1. If the original DLN contains money and is for a revenue receipt document code and the julian date/year is within the current fiscal year, then the new DLN must also contain a revenue receipt document code and be within the current fiscal year.

    2. If the original DLN (with money) is for a prior fiscal year or non-revenue receipt document code 45, 48, 51, 58 or 74, then the new DLN must also contain a prior year date or a non-revenue receipt document code.

    3. New DLN literal URF is valid only when the original DLN was for current year revenue receipts.

    4. New DLN literal OTHER is valid for transfer of credits to the Unidentified account when the original DLN is prior fiscal year but, because IRS received date is less than one year old, the amount is acceptable to Unidentified.

    5. New DLN literal EXC is valid only when the original DLN represents non-revenue receipts by doc code or Julian date/year.

  5. Review the source document to determine the reason for the error.

    1. Most renumber records were generated from the rejects or ERS system and have already been removed from that system.

    2. Coordinate with rejects to determine the correction. Rejects may assign another new DLN.

    3. Input Command Code SCFAJ or prepare Form 4028–A to create the correct record. If SCFAJ is used, delete the original DLN with From–To Code 4–2 or 0–2 and establish the correct DLN with From–To Code 0–0. Be sure to include cross-reference DLNs on both records. (See figure 3.17.30-71)

    Figure 3.17.30-71

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.6.9  (01-01-2009)
Error Code 8—Invalid NMF Abstract Number

  1. Every NMF good block proof record (From–To Code 0–5) for a revenue receipt document requires an abstract number.

    1. For some documents the abstract number is generated by the SCCF program because only one number can be valid for the DLN. If the number is generated, an input abstract number is invalid with error code 8.

    2. For all other NMF revenue receipt documents, a valid abstract number must be part of the input record or the record is invalid with error code 8. (See figure 3.17.30-72)

    Figure 3.17.30-72

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. See the table in IRM 3.17.30.17.3 for a list of NMF document codes, true tax classes, and abstract numbers.

  3. If the error coded good block proof record is a subsequent payment or other miscellaneous revenue receipt document code, the document must be renumbered to the blocking series indicative of the true tax class compatible with the abstract generated by Automated NMF account.

    1. Renumbering by Form 4028–A for ISRP entry will provide audit trail on SCCF through the XREF DLN and SCF 11–46, Renumber CRL, as well as automatic reclassification from the SCF 11–47, Reclassification Summary.

    2. If renumbering is done through Command Code SCFAJ, be sure to provide cross reference to both old and new DLNs via the Remarks field. Use Control Record Source Code J for pending reclassification by IRACS on Screen 250, which must be requested according to local procedures.

    3. Annotate the Form 813 with the corrected blocking series, and clear the good block proof record through Command Code SCFAJ in the normal manner.

  4. Determine the correct abstract number by reviewing the source document. If the abstract number cannot be determined from the Form 813, coordinate with the NMF accounting function for resolution.

3.17.30.6.10  (01-01-2009)
Error Code 9—Invalid Document Count

  1. This condition occurs in the following situations (See figure 3.17.30-73)

    Figure 3.17.30-73

    This image is too large to be displayed in the current screen. Please click the link to view the image.

    1. The document count is not numeric. Blanks are converted to zeros prior to the check.

    2. For MCRs, (From–To Code 0–0), and generated block proof records, the document count cannot be zero.

    3. For all control records, the document count cannot be greater than 100.

  2. Review the source document or block. Determine the correct count. Create the correct record with a SCCF adjustment. (See figure 3.17.30-74)

    Figure 3.17.30-74

    This image is too large to be displayed in the current screen. Please click the link to view the image.

3.17.30.6.11  (01-01-2009)
Error Code B—Invalid Reinput Source Code

  1. The reinput source code on all control records must be N,R,U,4,H,E, or blank. For most mainline processing the code will be blank. (See figure 3.17.30-75)

    Figure 3.17.30-75

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. Review the source document to determine if the code should be present:

    • N—Nullified

    • R—Reprocessable

    • U—Application from Unidentified

    • 4—Reinput—This code is never required for control records

    • H—Duplicate of Historic block (valid with SCFAJ only)

    • E—Override for multiple EPMF deletions

  3. Input Command Code SCFAJ to reconstruct the error coded record. Leave the Reinput Source Code field blank unless one of the above codes clearly applies.

3.17.30.6.12  (01-01-2009)
Error Code C—Incomplete Adjustment Record

  1. Any SCCF adjustment code that affects a module balance must adjust the count or amount of that block, except From–To Code 8–2.

    1. From–To Code 8–2 requires only the DLN in the adjustment record to delete the entire DLN module from SCCF in the next posting run.

    2. From–to Codes 1–0, 7–7, 8–7, and 9–9 are exempt from this check, because no SCCF balance is ever affected by these codes.

    3. All other SCCF adjustments must contain an entry other than zero for document count, credit adjustment amount, or debit adjustment amount. (See Figure 3.17.30-76)

      Figure 3.17.30-76

      This image is too large to be displayed in the current screen. Please click the link to view the image.

    4. Remarks are required entry for audit trail.

  2. Review the SCFAJ screen and the source document and overlay with the correct information.

  3. If the error code is on the CRL, it may be necessary to locate the original source listing or register.

3.17.30.6.13  (01-01-2009)
Error Code E—Invalid Entry for Deletion

  1. This on-line condition occurs for deletions of EPMF document codes 30, 37, or 38 in the following situations:

    1. When the document count is 001 and the serial number field does not contain two numerics.

    2. When the document count is greater than 001 but is not equal to the total in process count.

  2. Use of Reinput Source Code E will override this error check, but should be used very rarely.

3.17.30.6.14  (01-01-2009)
Error Code T—Invalid Tax Class

  1. This condition occurs on the Invalid Control Record List or SCFAJ adjustment whenever a tax class has been input that is not numeric or not valid for the master file. (See figure 3.17.30-77)

    Figure 3.17.30-77

    This image is too large to be displayed in the current screen. Please click the link to view the image.

  2. Compare the DLN and master file code of the record with the source document. When the reason for the error has been determined, input a SCCF adjustment on SCFAJ to correct the record.


More Internal Revenue Manual