3.17.30  SC Data Controls (Cont. 2)

3.17.30.6 
Control Record Listing (CRL) Error Codes

3.17.30.6.14  (01-01-2010)
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 IRM 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. 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.

3.17.30.6.15  (01-01-2010)
Error Code U—Unable to Determine True Tax Class for NMF

  1. This condition occurs for any NMF revenue receipt record in which the DLN does not represent a valid true tax class. (See IRM 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.
    1. Normally this code will occur in combination with other error codes, as the DLN is also invalid.

    2. Error Code U will appear only on the Invalid Control Record List and on Command Code SCFAJ.

  2. Review the source document and the invalid record. Prepare the corrected record with SCFAJ.

  3. See the table in IRM 3.17.30.17.3 for a list of the valid tax classes for each document code.

3.17.30.6.16  (01-01-2010)
Error Code V—Invalid Block Out of Balance Release Record

  1. BOB release records (record type 8) are created to update the Block Proof Summary (PCD) by showing that a correction has been entered for the BOB record. These records are only passed through the SCCF and do not post.

  2. If any of these records are invalid for any reason, they will be printed on the Invalid Control Record List.

  3. No correction to the SCCF is needed, but an adjustment to the Block Proof Summary may be necessary. See IRM 3.40.37, General Instructions.

3.17.30.6.17  (01-01-2010)
Error Code X—Invalid Record Type ID Code

  1. Only the following record type codes are valid in SCCF processing:

    • Record Type 0—SCCF Adjustment

    • Record Type 1—Master Control Record

    • Record Type 2—BOB Control Record

    • Record Type 4—Generated SCCF Adjustment

    • Record Type 5—Reinput, Delete, or Trans Deletion Control Record

    • Record Type 6—Renumber Control Record

    • Record Type 7—Good, Error, or Reject Block Proof Record

    • Record Type 8—BOB Release Record

  2. If any other record type ID code is read into the SCF01 program, it will be printed on the Invalid Control Record List.

  3. Examine the invalid record to determine if the record was actually intended for SCCF processing. If the record type was not transcribed correctly and the correct identity of the record is determined, input SCFAJ to post the record to the SCCF.

3.17.30.6.18  (01-01-2010)
Error Code Y—Invalid From–To Code

  1. Any record that is input to the SCCF with an invalid from–to code combination is error coded on the Invalid Control Record List or the SCFAJ screen with code Y. (See IRM 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. See IRM 3.17.30.4.2 for a list of the valid code combinations.

  3. Review the invalid record and the source document to determine the correct from–to combination. Input Command Code SCFAJ to post the corrected record.

3.17.30.6.19  (01-01-2010)
Error Code Z—Invalid Master File System ID Code

  1. Every valid control record must contain one of the following Master File codes:

    • Code 1—IMF

    • Code 2—BMF

    • Code 3—EPMF

    • Code 5—IRP

    • Code 6—NMF

  2. Any record with a Master File code other than 1–6 is printed on the Invalid Control Record List or displayed on the SCFAJ screen with error code Z. (See IRM Figure 3.17.30-78)

    Figure 3.17.30-78

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  3. Review the invalid record and the source document to determine the correct Master File. Then input the corrected record using Command Code SCFAJ.

3.17.30.6.20  (01-01-2010)
Error Code*—Invalid for SCF Processing

  1. Although the asterisk (*) is not a true error code, an * will appear in the error code field whenever a control record that is invalid for SCF processing is introduced to SCCF. The * normally appears on the Nullified CRL for voided unpostable control records which require no action on SCCF.

  2. The asterisk (*) will appear by some adjustments which are valid for SCF processing; these should not be considered error coded adjustments. These adjustments are tape generated for deletion and restoration on the same day of non-scannable SCRIPS returns to the data base. Tape generated From–To Codes 2–0 and 0–2 for Form 1040EZ will appear on the Adjustment CRL with asterisks.

  3. If there is an attempt to void an unpostable with a money amount (a condition which is invalid in SCF processing), the asterisk will be replaced by a true error code, Error Code 5. See IRM 3.17.30.6.7 and IRM 3.17.30.5.6.

3.17.30.7  (01-01-2010)
SCCF Invalid Transcripts

  1. General instructions and definitions pertaining SCCF invalid transcripts follow.

3.17.30.7.1  (01-01-2010)
General Instructions for Invalid Transcripts

  1. Each validated control record is systemically analyzed to assure compatibility for posting to the appropriate module on the SCCF data base.

    1. A control record validated on-line by SCFAJ but incompatible with a SCCF module is immediately identified as an invalid transcript.

    2. A control record validated in SCF01 through batch processing but incompatible with SCCF in SCF03 posting analysis is identified as an invalid transcript and printed on the Transcript Invalid Modules, SCF0743.

  2. Invalid transcripts are coded to identify the condition which makes the control record incompatible with SCCF. These codes are called Transcript Codes and apply to both on-line and printed transcripts. See IRM 3.17.30.8.

  3. On-line transcripts will appear on the invalid line at the bottom of the SCCF module display.

    1. The invalid line is prefaced by "ADJ."

    2. The invalid line contains a from–to code and various data entered on the SCFAJ screen.

  4. Invalid transcripts on SCF0743 are printed with the appropriate SCCF module.

    1. Each invalid is identified by Record Type. Record Types are literals indicative of the effect on SCCF by the from–to code. See IRM 3.17.30.7.2 through IRM 3.17.30.7.7.

    2. Each invalid control record is printed in the original format.

    3. Invalid transcripts for good tape transactions (Record Type GBP) must be resolved on a priority basis, prior to running the daily TEP (GMF15).

    4. All transcripts should be resolved and SCCF adjustments input by the day following date of receipt.

3.17.30.7.2  (01-01-2010)
Record Type Master Control Record (MCR)

  1. Record type code MCR indicates that the control record causing the transcript was a Master Control Record. (See IRM Figure 3.17.30-79)

    Figure 3.17.30-79

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. Correction of the MCR record type depends on the type of error condition encountered.

    1. Review the source document used for the establishing of the Master Control Record, normally BBTS Form 9382, Form 813, RRPS, or SCRIPTS.

    2. Query the batch and program number on the BBTS system and review for transcribing errors.

    3. Notify the RPS Function if a RPS MCR occurs.

    4. Notify IDRS Function if an IDRS MCR occurs.

  3. This record type may have created a BOB condition if the documents have been input. Coordinate any corrective action with the BOB Function.

3.17.30.7.3  (01-01-2010)
Record Type ADJ

  1. Record type code ADJ indicates a record causing the transcripts was an adjustment trying to post to the SCCF. This type of record normally appears with an SCFAJ screen, but can be caused by a generated adjustment or ISRP Form 4028. (See IRM Figure 3.17.30-80)

    Figure 3.17.30-80

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The type of error condition encounter determines the correction.

    1. Review source document making sure the adjustment was prepared properly.

    2. Review the Adjustment Control Record List for transcribing errors.

  3. If the adjustment to the SCCF is still necessary, input or overlay Command Code SCFAJ to reconstruct the invalid record.

3.17.30.7.4  (01-01-2010)
Record Type BCR

  1. Record Type Code BCR is a BOB Control Record. Normally the invalid condition will be resolved automatically by the correction of the BOB register or by the input of Batch Transmittals or CRL SCCF adjustments.

  2. Coordinate any corrective action with the BOB Function.

  3. The BCR invalid transcript will print on SCF0743, Invalid Modules, with the money amount in the record without any SCCF validation. Verify and post the correct money amount to SCCF on the appropriate BCRs with the audit trail postings.

3.17.30.7.5  (01-01-2010)
Record Type E/R

  1. Record Type Code E/R is an Error or Reject Block Proof Record. This record is in error status or reject status. (See IRM Figure 3.17.30-81)

    Figure 3.17.30-81

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The E/R record type will be corrected according to type or error condition.

    1. Analyze the source documents.

    2. Determine if SCCF is in error or if deletion of the error or reject register is needed.

  3. If the SCCF is in error, input a SCCF adjustment to correct the SCCF and additional adjustments to reconstruct the invalid records.

  4. If the block must be deleted notify Input Correction to delete all related ERS, error, and reject records. Be sure to include the control day (date of GMF listings) on each request for deletion of an error record.

    1. Error registers (except IRP) should be coded with Action Code 3. Reject and IRP error registers should be coded 2–R.

    2. For ERS, Action Code 660 should be entered with Command Code SSPND for items in the error or Command Code RJECT for items in the workable suspense inventory. Items in unworkable suspense should be activated with Command Code ACTVT, with "RJECT 660" entered the following day.

    3. At Submission Processing Campus option, ERS records may be deleted by Data Control personnel who have Command Codes GTREC, RJECT, and ACTVT in their operator profile.

    4. To verify that the required RJECT 660 has been entered, receive a copy of the ERS Rejected Records List, ERS0540 or use Command Code ERINV.

3.17.30.7.6  (01-01-2010)
Record Type GBP

  1. Record Type Code GBP indicates that the record trying to post to the SCCF is a Good Block Proof Record. (See IRM Figure 3.17.30-82)

    Figure 3.17.30-82

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. For each GBP transcript, a record has been added to the on-line delete file. See IRM 3.17.30.10.2 for instructions for the on-line delete file and Command Code SCFDL.

  3. These transcripts must be worked immediately to determine if the block must be deleted by TEP.

3.17.30.7.6.1  (01-01-2010)
Analysis

  1. Analyze the transcript and source documents (Form 9382, Form 813, CRL, returns, and other available documents).

  2. If SCCF is in error, enter Action Code R on the SCFDL file, and input SCCF adjustments on SCFAJ to post each of the following records.

    1. Prepare an adjustment to correct the SCCF.

    2. Prepare an adjustment to post the Good Tape Block Proof Record.

    3. Prepare an adjustment to record the error portion of E/R BPR.

    4. Prepare an adjustment to record the reject portion of E/R BPR.

  3. If the SCCF is correct:

    1. Enter Action Code D on the SCFDL file, so that the record will be deleted in TEP.

    2. Prepare Form 2275 to insert into the block as the documents are pulled.

3.17.30.7.7  (01-01-2010)
Record Type BPR

  1. Record Type Code BPR is a Delete, Renumber, or Reinput Block Proof Record. (See IRM Figure 3.17.30-83)

    Figure 3.17.30-83

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. The delete BPR transcript occurs when the Trans Deletion Control Record or generated delete record from BOBs, errors, or rejects fails to post to the SCCF.

    2. The Renumber BPR is generated when a record on the CRL Renumber Transaction List fails to post to the SCCF.

    3. The Reinput BPR occurs when a reinput record from Rejects, Error, Nullified Unpostables, or BOB Function fails to post to SCCF. The record appears on the CRL Adjustment List or CRL Nullified Unpostables List.

  2. Resolution of these record types will depend on the type of error condition occurred.

  3. Analyze the source documents and coordinate any corrective action with the function responsible for the input of the record.

  4. If the invalid record is necessary, reconstruct with a SCCF adjustment. A BPR with Transcript Code 07 will normally require no corrective action, because Input Correction is merely clearing deleted documents from their inventory at the request of data controls.

3.17.30.7.8  (01-01-2010)
BOB P Code Block List

  1. Blocks of documents that have been input without the DLN being established on the SCCF are identified with BOB Code P.

  2. BOB P blocks are included in the regular BOB inventory, but a separate BOB P Code Block List (GMF0641) allows the Data Controls function to identify and resolve these blocks. (See IRM Figure 3.17.30-84)

    Figure 3.17.30-84

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  3. The BOB P Block List contains five types of Blocks in the order listed:

    1. Release Code B—These blocks were corrected yesterday from BOB P status, but are still in the BOB inventory with some other BOB code. These documents should be associated with the re-BOB registers and worked by the BOB unit.

    2. Release Code C—These blocks have been corrected with the input of a BOB correction record. The documents will be released to the Input Correction Operation.

    3. Release Code S—These Blocks have been corrected on the SCCF so that the BOB P condition no longer exists. Unless other BOB codes are present, all BOB P blocks are automatically rechecked daily against the SCCF. If the SCCF has been corrected, the block is released from BOB status without the input of a correction record from the BOB register. These documents should be routed back to the BOB unit for release to Input Correction with other corrected BOBs.

    4. Unresolved BOB P blocks—These blocks are carryover BOB P blocks that are unresolved from the previous day. The P–Date is other than the current date and the Release Code is blank.

    5. New BOB P blocks—These blocks are identified by the current processing date in the P–Date column. The documents should be pulled from the carts of new BOB documents and routed to Data Controls.

  4. Resolve each block by ensuring that the Batch Transmittals have been properly routed to Data Conversion. Review the CRL–Master Control Record listing to verify that adjustments have been prepared for error coded records. If the wrong DLN was established on the SCCF, input Command Code SCFAJ to remove the incorrect DLN with From–To Code 0–2 and a separate adjustment to establish the correct DLN with From–To Code 0–0. Be sure to enter the cross-reference DLN in the remarks field for both adjustments.

  5. If the MCR is correct, but the wrong DLN was transcribed on the block header, annotate the block of documents and route the block immediately to the BOB unit for the correction to be input.

  6. Any BOB P block that also contains other BOB conditions should be routed to the BOB unit as soon as the BOB P condition is identified and the correction prepared. The block will not be revalidated until a BOB correction record has been input.

  7. It is important that blocks on the BOB P listing be pulled and resolved daily to assure proper document control and minimize the chance of lost blocks. It is also important to release the documents as soon as the Release Code appears on the BOB P list, because the BOB function and Input Correction Operation will be needing these documents on the same day that they appear on the listing.

3.17.30.8  (01-01-2010)
SCCF Invalid Transcript Codes

  1. The description of SCCF invalid transcript codes are provided in the following section.

3.17.30.8.1  (01-01-2010)
Transcript Code 04—Duplicate DLN

  1. This transcript code occurs with any of the following conditions:

    1. An original MCR or 0–0 SCCF adjustment attempts to post to a module that is already on the SCCF or is present on the Historic data base file. (See IRM Figure 3.17.30-85)

      Figure 3.17.30-85

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    2. A renumber MCR (cross-reference DLN present) attempts to post to a module that already contains a 0–0 record with the same numeric serial number.

    3. A 0–0 SCFAJ record with reinput source code H attempts to post to an active (open balance) module.

  2. Review the source document and SCCF module to determine the cause of the invalid condition. If necessary, research the historic by using command code SCFTR with definer H.

    Figure 3.17.30-86

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  3. If the DLN was transcribed incorrectly, input Command Code SCFAJ with From–To Code 0–0 to establish the correct DLN. (See IRM Figure 3.17.30-86)

3.17.30.8.1.1  (01-01-2010)
Duplicate DLN

  1. If the DLN is a true duplicate, obtain a new DLN according to local procedures.

    1. The new DLN should be for the block that can be corrected with the least impact on processing, not necessarily the block that was invalid on the transcript.

    2. A block in BOB status can often be corrected on the register without re-transcribing the documents.

    3. Enter CC SCFAJ with 0–0 to establish the new DLN, unless the new DLN will be established on the SCCF from the BOB register. Enter the original DLN in the remarks field to preserve the audit trail. Be sure that the new DLNs are stamped on the documents.

  2. Rarely, the duplicate condition may be caused by the presence on the Historic file of a DLN actually assigned ten years earlier. If it is deemed appropriate to continue processing with the DLN that is a duplicate of one from a decade earlier, the duplicate DLN check may be over-ridden.

    1. Input SCFAJ with 0–0 and reinput source code H to bypass the duplicate DLN checks.

    2. The 0–0 H record may be input after using SCFTRH to reactivate the Historic module for research, or it may be input immediately if the historic cycle on the data base provides sufficient information to resume processing. The 0–0 H record is not valid for active (Block Status A) blocks.

    3. Reinput source code H is valid only with SCFAJ.

    4. The historic record for the previous DLN will be retained on the SCCF module with the 0–0 H record listed after the old activity. Only the 0–0 H record and subsequent activity will be used to determine module balances, aging, and other SCCF indicators.

  3. This check is bypassed when the following conditions exist:

    1. When Reinput Source Code R is present.

    2. When a cross-reference DLN is present and the serial number is not a duplicate.

    3. When CC SCFAJ From–To Code 0–0 with Reinput Source Code H is entered for a DLN with a Block Status Code of I (Inactive) or H (Historic).

3.17.30.8.2  (01-01-2010)
Transcript Code 05—Inconsistent Amount Fields

  1. This condition occurs when the money amount on a control record is inconsistent with the amount present on the SCCF. Transcript Code 05 is created by one of the following conditions.

    1. A control record with a debit amount attempts to post to a credit module or a control record with a credit amount attempts to post to a debit module.

    2. A block proof record (record type 7) attempts to post without an amount when the module contains an open money amount. This check is bypassed for reprocessables or if money has been deleted from the block. (See IRM Figure 3.17.30-87)

    Figure 3.17.30-87

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The non-matching debit and credit condition should occur only for document codes 24, 45, 48, and 58 because other codes permit only debits or credits through the CRL.

    1. If the control record is correct, input a SCCF adjustment with code 8–0 to delete the money.

    2. Then input a second adjustment with code 7–0 to establish the correct money amount.

    3. Also reconstruct any control records that failed to post.

    4. If the SCCF is on-line, all adjustments are entered consecutively on the same day.

    5. If the SCCF was correct, use the normal procedures to delete the transactions from TEP and request deletion of error and reject records. For record type ADJ, input Command Code SCFAJ to reconstruct the record with the proper amount field.

  3. For non-remittance items input to remittance blocks, review the source documents to determine if money should be present on the block or should not be present on the SCCF.

    1. If the money amount was erroneously omitted from the block header, take the necessary action to have the block deleted and reinput.

    2. If the block header was correct, use Command Code SCFAJ to reconstruct the invalid record and make any other corrections to the SCCF. The record that was invalid as a block proof record will be valid as a SCCF adjustment, even if no other adjustments are made unless other transcript conditions are present. (See IRM Figure 3.17.30-88).

    Figure 3.17.30-88

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

3.17.30.8.3  (01-01-2010)
Transcript Code 06—Count Greater than 100 or Greater than Original

  1. This condition occurs with any of the following situations. (See IRM Figure 3.17.30-89)

    Figure 3.17.30-89

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. A 7–0 control record would increase the original count of the block to more than 100.

    2. An 0–3 or 1–3 control record would increase the error count of the block to more than 100.

    3. A 5–0,6–0, or 6–4 control record would increase the total in process count of the block to more than 100.

    4. A 6–4 control record would increase the reject count of the block to more than 100.

    5. A control record would increase the manual, error, or reject balance to more than the original balance.

  2. Review the erroneous control record and the related source document.

    1. If a GBP record is incorrect, code the corresponding record with "D" on SCFDL to delete in TEP. Notify Input Correction to delete erroneous E/R records.

    2. Prepare any necessary adjustments to correct the appropriate DLN or to reverse an erroneous posting. (See IRM Figure 3.17.30-90)

    Figure 3.17.30-90

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

3.17.30.8.4  (01-01-2010)
Transcript Code 07—Block Proof Record with ADSI On

  1. This condition occurs whenever the Action Delete Status Indicator (ADSI) is on and any of the following records attempts to post to the SCCF: (See IRM Figure 3.17.30-91)

    Figure 3.17.30-91

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

    • Reinput Block Proof Record

    • Delete Block Proof Record

    • Trans Deletion Control Record—This record will turn on the ADSI, but will not post if the ADSI is already on.

    • Good Block Proof Record

    • Error Block Proof Record

    • Reject Block Proof Record

  2. The ADSI is turned on whenever a Trans Deletion Control Record or a SCCF adjustment From—To Code 7–7 posts to a SCCF DLN. A Trans Deletion Control record is always generated by the TEP whenever a block has been deleted.

3.17.30.8.4.1  (01-01-2010)
Block Proof Record with ADSI Off

  1. The ADSI is turned off with From–To Code 8–7 or whenever the error and reject balances have been reduced to zero.

    1. On Record Types ADJ and BPR, review the transcript and source documents. If the record is correct and the ADSI is not needed, prepare a SCCF adjustment From–To Code 8–7 to turn ADSI off and post the record with SCFAJ.

    2. On Record Types GBP and E/R, review the transcript and source document.

    3. If the document should not be deleted, prepare a SCCF adjustment From–To Code 8–7 and a second adjustment to post the GBP or E/R record. (See IRM Figure 3.17.30-92)

      Figure 3.17.30-92

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    4. If the GBP record should not post, enter Action Code D on the SCFDL record and notify Input Correction to delete any remaining records on the error and reject register or See IRM 3.17.30.7.5 for instruction to delete on ERS. Pull the block for further processing.

    5. The ADSI is turned on to prevent documents in Input Correction or Rejects from posting when the rest of the block has been deleted.

    6. For deleted GBP and E/R records, input SCCF adjustment From–To Code 8–7 after the error and reject items have cleared.

3.17.30.8.5  (01-01-2010)
Transcript Code 09–First BPR Unequal to Original Balance

  1. For an initial block, the sum of the good, error, and reject block proof records with From Code 0 or 1 must equal the original count and amount on the SCCF. (See IRM Figure 3.17.30-93)

    Figure 3.17.30-93

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. This check is bypassed if the incoming control record contains reinput source code R for reprocessable.

    2. For the purposes of this check, a block is considered initial if the 0–0 control record did not contain reinput source code R or N, and no control records other than 7–0, 8–0, or 0–1 have posted since the module was created.

  2. Review the transcript and MCR source documents, Form 9382 or Form 813 to assure that the SCCF is correct. Be alert for adjustments which might have been made in error. Reverse and remake these adjustments as necessary.

  3. Review the block of documents for a missing document. The documents can normally be located in the Input Correction Operation. Check to see if notification has been sent to accounting to increase or decrease volume from Receipt and Control Branch.

    1. Prepare the necessary adjustment to correct the SCCF.

    2. Prepare an adjustment to post the GBP record and/or the E/R record. (See IRM Figure 3.17.30-94)

    Figure 3.17.30-94

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  4. If a document failed to be transcribed, delete the GBP by entering Action Code D on the SCFDL record. Notify Input Correction to delete the records in error and reject status or see IRM 3.17.30.7.5. Pull the block for future processing.

3.17.30.8.6  (01-01-2014)
Transcript Code 10—Count or Amount Less than Zero

  1. This condition occurs with any of the following situations: (See IRM Figure 3.17.30-95)

    Figure 3.17.30-95

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. An 0–3, 1–3, 0–4, or 1–4 control record would reduce the Manual count or amount to less than zero.

    2. An 8–0 control record would reduce the original count or amount to less than zero.

    3. An 0–2, 1–2, 3–2, 4–2, 0–5, 1–5, 3–5 or 4–5 control record would reduce the total in-process count or amount to less than zero.

    4. A control record with From Code 3 would reduce the error count or amount to less than zero.

    5. A control record with From Code 4 would reduce the reject count or amount to less than zero.

    6. A nullified unpostable 6-4 control record fails to post. IDRS will not allow a 6-4 to be coded. See 3.17.30.8.6(6) for posting instructions.

  2. Review the erroneous or duplicate record that created the condition. If the SCCF is in error, prepare an adjustment to correct the balance on the SCCF or reverse the erroneous posting. (See IRM Figure 3.17.30-96)

    Figure 3.17.30-96

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

  4. If a GBP record is incorrect, enter Command Code SCFDL, and enter code D in the Action column for the block to be deleted. Notify Input Correction Section to delete any error and reject items or see IRM 3.17.30.7.5. Pull documents for future processing.

  5. If the record has failed to post because of a previous duplicate posting, prepare adjustments to reverse the erroneous postings on the SCCF. Initiate action to delete any unposted duplicate items. Also, post the control record that has transcripted.

  6. Input the following adjustments to post an Error/Reject error for a 6-4 control record.

    1. Input 7-0 for count and money.

    2. Input 0-4 for count and money.

    3. Input 9-9 for audit trail purposes noting that the system will not allow a 6-4 posting.

3.17.30.8.7  (01-01-2010)
Transcript Code 11—Amount with no Count on SCCF; Count with no Amount on SCCF

  1. This condition occurs whenever a control record would reduce any SCCF count to zero while the corresponding amount is still present. (See IRM Figure 3.17.30-97)

    Figure 3.17.30-97

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. The amount can be removed with items still present using SCFAJ. Thus money can be moved to unidentified or another document without affecting the DLN of the original document.

    2. A reprocessable document previously containing money can be created on an existing SCCF module without causing a transcript condition.

  2. This condition occurs whenever a Good Block Proof Record (record type 7) would reduce any in process amount to zero while the corresponding count is still present.

  3. Review the source documents

    1. If the SCCF is in error, prepare the necessary adjustment and post the transcript record. (See IRM Figure 3.17.30-98)

      Figure 3.17.30-98

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    2. If the record ADJ or BPR is necessary, reconstruct the record.

    3. If the GBP or E/R record is incorrect, have the transactions deleted by coding the record with a D on the SCFDL file.

    4. Notify the Input Correction Operation to delete the error and reject records or See IRM 3.17.30.7.5.

    5. If the record has failed to post because of a previous duplicate posting, prepare a 5–0 adjustment to reverse the erroneous posting on the SCCF. Initiate action to reverse any erroneously posted transactions or to delete any unposted duplicate items. Also, reconstruct the control record that has transcripted.

3.17.30.8.8  (01-01-2010)
Transcript Code 8–2—SCCF Delete

  1. This transcript will print whenever a SCCF adjustment with From–To Code 8–2 has been entered to delete a block from the SCCF. (See IRM Figure 3.17.30-99)

    Figure 3.17.30-99

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. This is not an invalid condition and requires no corrective action. However, the transcript should be retained for reference if additional action will be taken on the block. The 8–2 action is generally taken when a SCCF module has exceeded the 150 transcript line limitation. These modules require reconstruction of the module by consolidating "like" from and to codes within the module. Reconstruction must be completed the day the module appears on the invalid transcript listing to ensure the database record is restored timely. Refer to IRM 3.17.30.9.5 for detailed instructions.

3.17.30.8.9  (01-01-2010)
Transcript Code CR—Control Record Out of Sequence

  1. This code is caused by the input of a control record tape in the incorrect posting sequence.

  2. Contact the computing center according to local procedures. The computing center will probably rerun the program that caused the out of sequence condition, then rerun the SCCF.

3.17.30.8.10  (01-01-2010)
Transcript Code MX—Overflow Transcript

  1. The SCCF program allows a maximum of 149 transactions on a single SCCF module. (See IRM Figure 3.17.30-100)

    Figure 3.17.30-100

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The Transcript Code MX condition occurs when the 150th record attempts to post.

  3. Input a SCCF adjustment with code 8–2 to delete the block from the SCCF. The program will allow this record to post as the 150th.

  4. See IRM 3.17.30.9.5 for correction procedures.

3.17.30.8.11  (01-01-2010)
Transcript Code NR—No Record on SCCF

  1. This condition occurs whenever a control record, other than a record that normally establishes a block, attempts to post to a DLN that is not on the SCCF. (See IRM Figure 3.17.30-101)

    Figure 3.17.30-101

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. From–To Codes that normally establish a block on the SCCF are 0–0R, 0–0, 6–0, and 6–4.

  3. Trace record trying to post to source documents for possible corrections. Prepare the necessary adjustments. (See IRM Figure 3.17.30-102)

    Figure 3.17.30-102

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

3.17.30.8.12  (01-01-2010)
Transcript Code BN, BQ, BR, and BS and NR—BOB Transcripts

  1. These transcripts are generated to provide immediate SCCF research for SCCF related BOB conditions. Technicians resolving blocks out of balance should be encouraged to use SCFTR for more current information.

  2. Each BOB code N, Q, R, or S will automatically produce a SCCF transcript BN, BQ, or BS; BOB Code P will produce a SCCF transcript for a BCR with Transcript Code NR (no record on SCCF).

  3. The BOB Control Record is not automatically invalid and will post to the SCCF if a module is available. Any other control record attempting to post after the BOB Control Record (on the same day) will be invalid.

  4. No corrective action is required for the transcript unless invalid records are present.

  5. Route all BN, BQ, BR, and BS transcripts for association with the BOB register.

  6. Following resolution of BCRs, provide audit trail on SCCF with SCFAJ postings to show cross-reference DLNs in Remarks.

    1. Post From–To Code 1–0 with the ABC of the block erroneously input to the DLN under which this BCR posted to turn off the BOB indicator unless there is a valid unresolved BCR for this block. In Remarks show the correct DLN as a cross reference.

    2. If there is a valid unresolved BCR posted to the block, use From–To Code 9–9 rather than 1–0 (leaving BOB indicator on for the valid BCR) with the correct DLN in the Remarks section on the SCFAJ screen or appropriate column of the Form 4028.

    3. Post From–To Code 0–1 with the ABC to the correct DLN, showing in remarks the DLN to which the BCR was initially input as a cross reference.

    4. Whenever it is inappropriate to turn on or turn off the BOB indicator (From–To Code 0–1 or 1–0), use SCFAJ with From–To Code 9–9 to show the cross-reference DLNs for both old and new DLNs in the Remarks field.

  7. The audit trail may be further enhanced by posting the corresponding money amounts whenever available for verification.

3.17.30.9  (01-01-2010)
SCCF Posting Controls

  1. The SCCF posting controls outlines the balancing routine with associated reports.

3.17.30.9.1  (01-01-2010)
Tape Control Record List

  1. The Tape Control Record List is a list of all blocks of data in DLN Sequence in which the blocks or part of blocks which went to "good tape" , "error tape" , or were rejected from normal processing. (See IRM Figure 3.17.30-103)

    Figure 3.17.30-103

    This image is too large to be displayed in the current screen. Please click the link to view the image.
  2. The listing indicates:

    1. The portion of a block that has been placed on the Submission Processing Campus Transaction Tape for processing to the Master File.

    2. The portion of each block, if any, which was placed on the Submission Processing Campus Error Tape file or ERS error file.

    3. The portion of each block, if any, which has been placed on the SC Reject Control File or ERS suspense file.

3.17.30.9.1.1  (01-01-2010)
Fields of Data

  1. The fields of data printed for each block are:

    1. Alpha/Numeric Submission Processing Campus block number—three (3) digit code assigned for Submission Processing Campus processing controls. It is used to reference data records to a block header record containing block DLN, reducing card volume and transcription efforts.

    2. Document Locator Number—twelve (12) digit number representing the block DLN and year digit.

    3. Prejournalized amount—credit items will bear a minus "−" sign.

    4. Record count—number of records being processed to Enterprise Computing Center. The count will always be as great as the number of documents but may be greater.

    5. Document count.

    6. Trans Tape Sequence number.

    7. Error Tape items failing to meet mathematical verification or validity tests, such as Prejournalized amounts or document count.

    8. Reject items. as above, such as Prejournalized amounts or document count.

    9. 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.

    10. Batch number of Form 9382 which is controlling the blocks.

3.17.30.9.1.2  (01-01-2010)
Summary by Master File

  1. The summary at the end of each Master File provides a count of documents and blocks by from code and source for each type of record.

    1. Error block proof records are counted as coming from raw or from BOBs.

    2. Reject records can come from raw, BOBs, GMF errors, or ERS errors.

    3. Good records come from raw, BOBs, GMF errors or rejects, or ERS Errors or rejects.

    4. The primary purpose of these summary counts is to simplify balancing of error and reject counts on the SCCF to the counts on the error and reject systems. See IRM 3.17.30.9.4.

    5. The summary also provides count and amount totals for balancing to the TEP.

3.17.30.9.1.3  (01-01-2010)
Other Records

  1. Along with the Block Proof Records listing come the following:

    1. Revenue Receipts Control Sheet (RRCS)—a breakout by tax classes of all amounts converted to tape to be transmitted to ECC. (See IRM Figure 3.17.30-104)

      Figure 3.17.30-104

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    2. SCF0142, Block Sequence List (BSL)—A listing of DLNs for all blocks converted to good tape in the sequence in which they appear on good transaction tape. This listing is to be used for deletions due to tape "read fail" and other error conditions. The BSL may also be used to identify discrepancies between the TEP and SCF1152, Good Block Proof Records list. (See IRM Figure 3.17.30-105)

      Figure 3.17.30-105

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    3. Control Date Recap, Good Block Proof Records—A summary by DLN Control Date of all documents and amounts converted to good tape and listed on the corresponding Block Proof Record list. (See IRM Figure 3.17.30-106)

    Figure 3.17.30-106

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

3.17.30.9.1.4  (01-01-2010)
Tape Control Record

  1. Process the Tape Control Record List as follows:

    1. Summarize the totals in the "good tape" column of the Block Proof Record list and compare to the sum of the Good Block Proof Control Date Recap.

    2. Summarize the "Current" , "Future" , and "Other Prejournalized" Debits and Credits on the Revenue Receipts Control Sheet and balance the totals of the released good tape totals on the Tape Control Record List. Balance the total of the CRL—Good Block Proof Record Recaps to the RRCS and the totals of the CRL—Good Block Proof Records. (See IRM Figure 3.17.30-107)

      Figure 3.17.30-107

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    3. When notified of a block or blocks to be deleted, adjust the totals on the Tape Control Record List, Good Block Proof Record Date Recap, Block Sequence List, and daily RRCS.

    4. When the Tape CRL has been balanced and the SCFDL file worked, notify the Enterprise Computing Center so that the TEP (SCF15 and GMF15) can be run.

    5. See IRM 3.17.30.10 for Delete Operations and IRM 3.17.30.11 for ECC Tape Releases.

    6. Keep a control on the documents deleted and when put back into the system. Deleted documents should be put back into the system within two weeks.

3.17.30.9.2  (01-01-2010)
Revenue Receipts Control Sheet

  1. A daily RRCS is received with the Tape CRL. The summaries are broken into tax class on BMF and into tax class 2 and 4 for IMF.

    1. "Current" includes those Revenue Receipt items which contain a DLN date which falls within the current report period.

    2. "Future" includes those Revenue Receipts items which contain a DLN date which is later than the current report period.

    3. "Other" includes those Revenue Receipts items which have a DLN date which is earlier than the beginning of the report period. It also includes prejournalized amounts which are not Revenue Receipts or adjustments affecting deposits. The non-revenue receipt document codes are 45, 48, 51, 58 and 74.

3.17.30.9.2.1  (01-01-2010)
Manual Adjustments on the Daily RRCS

  1. When money is deleted from the Tape CRL by a Submission Processing Campus deletion, manually adjust all totals affected by the delete. Hold a copy of the daily RRCS to balance to the weekly.

    1. Weekly, at the end of the cycle, request the Enterprise Computing Center to run a weekly RRCS. The SCF83 file is modified to include a "W" in the Revenue Receipts Frequency Indicator when the weekly RRCS is run. This file is updated by the Enterprise Computing Center upon request.

    2. The weekly RRCS is a summation of all Revenue Receipts transferred to ECC on the transaction tapes. (See IRM Figure 3.17.30-108)

    Figure 3.17.30-108

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

3.17.30.9.2.2  (01-01-2010)
Weekly Revenue Receipts Control Sheet (RRCS) and Tape Edit Processor (TEP)

  1. The weekly RRCS may be produced as soon as the final TEP is run and the cycle closed, or it may be run with the following day's cycle.

    1. If no deletes of revenue receipt items have been processed to the final daily TEP, the weekly SCF13 can be run on the same day with no special procedures. Just be sure that the "W" has been entered in the Revenue Receipts Frequency Indicator on the SCF83 date file.

    2. If revenue receipt deletes have been processed to the final TEP, the weekly SCF13 can only be run on the same day if a dummy SCF01 run has processed the GMF15 CYNN file.

    3. The weekly SCF13 can be run with the following night's batch processing if the nightly SCF01 includes a T setting of 100. This setting will allow the weekly RRCS for one week plus the daily RRCS for the first day of the following week to be produced from the same SCF13 run.

3.17.30.9.2.3  (01-01-2010)
Weekly RRCS Balancing

  1. When the weekly RRCS is received, balance to the sum of the daily Grand Total debit and credit figures. If an imbalance exists and the daily figures are correct, contact the Enterprise Computing Center for a possible rerun.

    1. Compare the weekly delete RRCS (labeled as daily) with the sum of deletes for each day. (See IRM Figure 3.17.30-109)

      Figure 3.17.30-109

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    2. Attach a copy of each RRCS to the Tape CRL for that cycle.

    3. After the adding machine tape of the daily RRCS balances with the weekly RRCS, associate the original with the tape release for shipment to ECC.

3.17.30.9.3  (01-01-2010)
Control File Summary

  1. The Control File Summary, SCF0742, is printed for each Master File with a total summary of all Master Files.

  2. The summary provides various information relative to the modules on the current SCCF data base.

3.17.30.9.3.1  (01-01-2011)
Block, Document, Counts and Net Amount

  1. The summary provides total in process block count, document count, and net amount.

    1. Manual, Error, and Reject counts and amounts making up the total in process are listed individually.

    2. The prejournalized and non-prejournalized components of the in process are listed separately by block count, document count, and prejournalized amount.

  2. The summary provides the block counts for Active, Inactive, and Shelved blocks.

    1. Active blocks are those with an in process balance.

    2. Inactive blocks are those with no in process balance and are subject to removal to the historic file.

    3. Shelved blocks are those which are not currently being processed. These are IMF return document codes 06, 08, 10, 12, 22, 26 and 27 with full paid blocking series with no activity other than From–To Codes 7–0, 8–0, and 9–9 following the From–To Code 0–0 for the MCR. Shelved blocks are automatically unshelved on July 1 of each year.

  3. The summary provides information when other transcripts are processed (Aged, Historic, Special) with respective block counts.

  4. The summary provides an automated balancing worksheet of the current input to the SCCF account to facilitate timeliness of TEP request. Document counts and money amounts from valid records are analyzed for the net impact on the in process totals. The system performs the indicated processes to provide a current in process total worksheet.

3.17.30.9.3.2  (01-01-2010)
Total Process Count

  1. Based on the previous days total in process count and net amount, the system will consider all valid control records from the current days SCF reports.

    1. Each component of the SCF11 series will be identified with its net impact on the in process count and amount.

    2. In process counts/amounts deleted during the posting run (from–to code 8–2) will be identified and considered in the worksheet balance section process.

    3. Neither the generated deletes nor the restorations (From–To Codes 0–2 and 2–0) for SCRIPS returns are counted in the WORKSHEET section of the Control File Summary.

3.17.30.9.3.3  (01-01-2010)
Invalid Transcript

  1. Invalid transcripts from SCF0743 are identified and listed by record type and by impact/non-impact on the in process count and amount.

    1. Invalid transcripts with in process impact (such as 0–0, 0–5, etc.) are reversed in the worksheet balancing process, since these are listed on SCF11 reports but were inconsistent for posting to SCCF.

    2. Invalid transcripts with no impact on in process balancing (such as from–to codes 0–3, 3–4, etc.) are listed as "Non-Add."

    3. All invalid transcripts are resolved in accordance with IRM 3.17.30.7.

3.17.30.9.3.4  (01-01-2010)
In Process Worksheet

  1. The Worksheet In Process Total (count and amount) represents the results of posting to SCCF all valid control records on the current days SCCF reports. (See IRM Figure 3.17.30-110)

    Figure 3.17.30-110

    This image is too large to be displayed in the current screen. Please click the link to view the image.
    1. Compare this worksheet total to the actual In Process Total count and amount on line 4 of SCF0742.

    2. Any difference should be identified and appropriately reconciled.

    3. The error coded control records from the CRL components of SCF11 are itemized separately with block counts, document counts, and net amounts.

    4. These control records are considered to be pending and require individual analyses and appropriate manual adjustments to SCCF.

    5. Error coded good block proof records on SCF1151, Tape CRL, require priority analysis since, if deletion is necessary, the DLN must be added to the daily delete file with SCFDLA prior to running GMF.

3.17.30.9.3.5  (01-01-2010)
In Process and Worksheet Total

  1. To facilitate the timeliness of the TEP request, compare the Control File Balance, In Process Total (line 4), to the Worksheet In Process Total (line just above the CRL error code portion), adjusted by any error coded counts and amounts except the Non-Add Amounts. When these lines are equal, SCCF has been updated by all valid control records represented by each CRL component as indicated in the Worksheet Section; the preliminary daily SCCF balancing has been systemically calculated.

    1. Balance the actual In Process total amount to General Ledger SC Suspense Accounts (RRACS) 4120, 4220, or 4420 by consideration of pending and/or outstanding adjustments. See IRM 3.17.30.14.2.

    2. Balance the Error and Reject counts to the error and reject work inventories. See IRM 3.17.30.9.4.

3.17.30.9.4  (01-01-2010)
Error and Reject Balancing

  1. Raw and Correction GMF and ERS run controls should be balanced to the error and reject counts on the TCRL and the SCCF to ensure that GMF and ERS tapes have been input properly.

  2. The Raw Run Control Report (GMF0740), Correction Run Control Report (GMF0840), Error Resolution Inventory Control Report (ERS1747), F1040 Doc Perfection Run Control Report (GMF3740), and the Unpostable Controls (GUF5340) should provide the necessary tools for this balancing. Campuses may also refer to BAL0240 for a quick count balance of inventories.

    Note:

    For Campuses that process electronic returns an additional report, GMF2740, Run Control Report, will be required to balance new records and inventories.

3.17.30.9.4.1  (01-01-2010)
Daily Balancing of New Error Records

  1. Daily balancing of new error records.

    1. Add the Error Count for all Tape CRLs (SCF1151). The total should equal the sum of "Raw Documents to GMF Error Status" and "Raw Documents to ERS File" on the Raw Run Control Report (GMF0740, page 5), less the "GUF records to ERS" (GMF0740, page 4, plus "MEF Documents to Error Status, AWF" (GMF2740, page 3), less "GUF Records to ERS" (GMF3740, page 4), plus "Raw Docs to Error Status" (GMF3740, page 2). (See IRM Figure 3.17.30-111)

    Figure 3.17.30-111

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

3.17.30.9.4.2  (01-01-2010)
New Reject Records

  1. Daily balancing of new reject records.

    1. Add the Reject Block Proof Record document counts for all Master Files "from Raw" and "from BOB" from the summaries of (SCF1151). The total should equal the "Raw Documents to Reject Status" , less "Unpostable Documents to Reject Status" (both on GMF0740, page 5), plus "Raw Documents to Reject Status" (GMF3740, page 2).

    2. Add the Reject Block Proof Record document counts for all files "from GMF errors" on the SCF1151. The total should equal the count of Error Documents to Reject Status on page 9 of the GMF0840.

    3. Add the Reject Block Proof Record document counts for all files "from ERS errors" on SCF1151. The total should equal the sum of the "Returns Analysis Records Added" to the Workable and Unworkable Suspense Inventories and the "Records Suspended" and "Duplicate Block Records moved to Suspense" from the Error Inventory, all shown on the Error Resolution Inventory Control Report, ERS1747. (See IRM Figure 3.17.30-112)

    Figure 3.17.30-112

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

3.17.30.9.4.3  (01-01-2010)
Unpostables

  1. Add the "Reject" counts from the GUF5340, Unpostable Control Reports, for all Master Files. This total should equal the "GUF Records Input from mainline Data File" (GMF0740, page 4, plus the "GUF Records to ERS" (GMF3740, page 4) totals. The GMF0740 and the GMF3740 may be dated one day later than the GUF Unpostable Control.

    1. If the GMF07 and the GMF37 count is less than the GUF5340 count, check GMF0640, page 5, Mainline Block Run Control Report, for a dropped record or a "problem" alert.

    2. The SCCF and the Block Proof Summary will be updated by the GUF tape, but the GUF records dropped in GMF06 will not update the Reject/ERS inventories and will be a pending adjustment for balancing reject inventories for both SCCF and PCD.

    3. Resolution of the pending adjustment should include Command Code SCFAJ From–To Code 4–0 to move the record from reject status on SCCF to manual status. Be sure to use Control Record Source Code R on the SCCF adjustment so that the reject inventory on the Block Proof Summary will be corrected.

    4. Coordinate resolution of the nullified unpostable case with the GUF or Reject/ERS function.

  2. Verify that the "GUF Records to ERS" (GMF0740, page 4), plus "GUF Records to ERS" (GMF3740, page 4), is equal to the ERS1747, Workable Suspense Inventory, "GUF Records Added."

  3. Add the "Raw Documents to ERS File" (GMF0740, page 5), the "MEF Documents to ERS File, AWF" (GMF2740, page 5), and the "Raw Documents to ERS File" (GMF3740, page 5), then compare to the "Total Records Added from GMF" on the ERS1747. Normally, the ERS1747 will be dated one day later than the GMF report.

  4. All of these counts should balance exactly. If any do not balance, look for invalid control records that may not have been included in the CRL counts. If imbalances cannot be corrected from available listings, contact a CSA.

  5. Contact a CSA if GUF records are dropped in GMF06 and not passed to GMF07 or GMF37. Depending on the volume of dropped records, the CSA may determine that a re-run would be appropriate. If not, these records must be identified by a filecracker of the GUF tape.

  6. If a discrepancy exists at this point, compare the "Program Total" count on ERS1740, Error Resolution New Suspense List, to the Error count for all TCRLs, SCF1151. This may help clarify the source of the difference.

  7. GMF1141, Reject Reinput Transmittal, and ERS1940, Error Resolution Duplicate Document DLN Report By Inventory Source, may be useful for comparison purposes, in some instances, to resolve count differences.

3.17.30.9.4.4  (01-01-2010)
Balancing Error and Reject Records

  1. Daily balancing of corrected error and reject records

  2. Add the document counts for Good Block Proof Records from each GMF and ERS status in the summaries from SCF1151.

    1. The total "from GMF errors" should equal the "Error Documents to Good status" on page 8 of GMF0840.

    2. The total "from GMF rejects" should equal the "Reject Documents to Good Status" from page 9 of GMF0840.

    3. The total "from ERS errors" should equal the "Error Inventory Records Corrected" from ERS1747.

    4. The total "from ERS rejects" should equal the "Workable Suspense Inventory Records Corrected" from ERS1747.

  3. Any imbalance that cannot be explained by other available listings should be reported, via KISAM, to ECC.

3.17.30.9.4.5  (01-01-2010)
Balancing Error and Reject Inventories

  1. Daily balancing of error and reject inventories

    1. Each day, balance the error and reject counts on the SCCF to the Raw Run Control Report (GMF0740), the Correction Run Control Report (GMF0840), the Electronic Run Control Report (GMF2740), the F1040 Doc Perfection Run Control Report (GMF3740), and the Error Resolution Inventory Control Report (ERS1747).

3.17.30.9.4.6  (01-01-2010)
Balancing SCCF Errors

  1. Balancing SCCF error count to the error work inventory

    1. Add the SCCF error counts from the SCF Summaries (SCF0742) for all files except NMF. The total is the unadjusted SCCF error count. (See IRM Figure 3.17.30-113)

      Figure 3.17.30-113

      This image is too large to be displayed in the current screen. Please click the link to view the image.
    2. Add the "Intermediate Error File-Total Documents" (GMF0840, page 8), plus the "Raw Documents to GMF Error Status" and the "Raw Documents to ERS file" (both from GMF0740, page 5), plus the "MEF Documents to Error Status, AWF" (GMF2740, page 3), plus "Raw Documents to Error Status" (GMF3740, page 2), plus the "Error Inventory Ending Inventory" (ERS1747). Subtract the "GUF Records to ERS" (GMF0740, page 4) and the "GUF records to ERS" (GMF3740, page 4). The total is the Total Unadjusted Control count.

    3. Any "Unadjusted Difference SCCF Long/Short*" should be resolved by the method described in item 4 and 5.

    4. Add or subtract all pending SCCF adjustments related to error status (From/To Code 3). Subtract any items which have been deleted from SCCF but are pending deletion from the work inventory, both ERS and SCRS.

    5. It may be necessary to use the "Unselected ERS–ERR–REC–FILE" (ERS0149) or the "Selection Inventory, Ending Inventory" (ERS1747), "Total New Suspense Records" (ERS1749), less "GUF Records Added" (ERS1747), depending on how the ERS runs are scheduled.

    6. If there is a count on the "Total New Suspense Records" (ERS1749), the "Duplicate DLN Register" (ERS1742), should be used to identify duplicate DLNs. Resolve the duplicate DLNs according to local procedures.

3.17.30.9.4.7  (01-01-2010)
Balancing SCCF Rejects

  1. Balancing SCCF reject count to reject work inventory.

    1. Add the SCCF reject counts from the SCCF Summaries (SCF0742) for all Master Files.

    2. Add the sum of the "Intermediate Reject File—Total Documents" and the "Error Documents to Reject Status" (both from GMF0840, page 9), "Raw Documents to Reject Status" (GMF0740, page 5), the "Ending Inventory" from both the Workable and Unworkable Suspense Inventories (ERS1747), the "GUF Records to ERS" (GMF0740, page 4), the "Raw Documents to Reject Status" (GMF3740, page 2), the "GUF Records to ERS" (GMF3740, page 4), and the GUF Reject Count from GUF5340 (or GUF5149, Line 51–08, GUF Reject Doc File).

    3. Any "Unadjusted Difference SCCF Long/Short*" should be resolved by the instructions described in (d) and (e) below.

    4. Add or subtract all pending SCCF adjustments related to reject status (From/To Code 4). Subtract any items which have been deleted from SCCF but are pending deletion from the work inventory, both ERS and SCRS.

    5. It may be necessary to add "GUF Records Added" (ERS1747), less "Total New Suspense Records" (ERS1749), depending on the schedule of the ERS run.


More Internal Revenue Manual