These instructions provide for use by the Data Controls function, also known as the Balancing function, in the Submission Processing Campus Accounting Operation. The balancing of daily, weekly and monthly reports are a mission critical function and must be completed timely.

The Service Center Control File (SCCF) is a real time file designated to control all documents and revenues while accountable to the Submission Processing Campus. Each control is verified prior to being processed by the SCCF. Instructions within this IRM will explain and guide technicians on the balancing steps.

Instructions on balancing the Form 3996, Revenue Receipts Recap, also included in the proceeding sections.

The Director, Submission Processing, oversees the policies in this IRM and approves and authorizes the issuance of this Internal Management Document.

The Operations Manager and Department Manager secure, assign and providing training for the staff needed to perform the task required throughout this instruction.

The Frontline Manager assigns cases and controls the workflow. Accurate recording of hours and volume is required. Task of balancing and reporting is rotated periodically to mitigate the risk of fraud.

The employee must ensure that the CRL, SCCF, and Tape Edit Processing (TEP) runs is properly balanced before succeeding runs get initiated or tapes get released to the Enterprise Computing Center.

NOTE: While working assigned cases, SP employees may come across blocked accounts on IDRS. These accounts can be identified by an IDRS security violation message: "Unauthorized Access to This Account". Forward the transcript to your manager. Managers will notify the local Planning & Analysis Staff who will scan the transcript and send encrypted information to the ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ ≡ mailbox to request access to the account. Managers will keep the original case in a file awaiting access (can take up to 5 business days). Once notified access is granted, the case can be processed following applicable procedures.

Below is reference to the definitions of words/terms used while working with SCCF.

A list of acronyms found throughout this IRM follows:

The following manual sections, websites, or documents frequently used in conjunction with this IRM:

The following SCF runs to use with the on-line SCCF.

SCCF control can be established in different ways.

The following information pertains to processing of MCR source documents.

The Submission Processing Campus Accounting function receives Accounting Control packages for all deposits from the Receipt and Control Branch.

Data Control uses parts of the package for SCCF balancing after Accounting Control balancing is completed.

Master Control Records (MCR) established via BBTS will appear on the SCF1144. BBT0103 is the BBTS output file that is processed through GMF04 to establish the MCRs on SCCF. Verify input of the BBT0103 input file daily by reviewing the GMF0440 run control. The Master Control Records also appear on the BBTS report titled Sorted MCR Report in the report menu of BBTS.

Most IMF and BMF payments process through the ISRP Residual Remittance Processing System (RRPS) and Lockbox. RRPS run ISR05 and Lockbox RPS01 generates a tape of master control records which process to the SCCF through RPS01, GMF04 and GMF06. On the same day, RPS 05 and RPS 07 creates blocks of transaction records which process through the regular series of GMF runs.

The Remittance Transaction Research (RTR) System is a database which stores information from the Remittance Register Report (Form 813) and the EndPoint Master Listing Report. This system replaces the printing process of these reports produced by ISRP and allows research to be done on-line. (See IRM Figure 3.17.30 -14).

Figure 3.17.30-14

Shown is a screen shot of the RRPS Document Remittance Register and the End Point Master Listing from the RTR System. The text explains each of the data fields shown in the screen shot, in sequence, same as in the reports shown.

Please click here for the text description of the image.

The RTR System allows the user to query for specific records. It is important to enter as much information as possible to narrow your query request. Information that may be used includes:

See the RTR Quick Reference Guide Version 1.1.0, for more information on this application.

A copy of every Form 9382, Batch Transmittal, that is corrected or voided because of an error found by Data Conversion or Receipt and Control should be routed to Data Control.

Be sure that the Transmittal provides sufficient audit trail information to document the change.

Submission Processing Campuses processing Modernized Electronic Filed (MeF) returns should assure that SCCF control is established for all returns accepted by MeF that all transactions get verified in the system. Manual balancing procedures will need to be followed whenever the automated MeF balancing is turned off or whenever the BAL6240 and the GMF2545 do not complete successfully.

BAL6040 and 6140 are run control reports implemented in 2007. They generate through automated programming that total the MeF transmission, balance MeF to SCCF and scan for error code and invalid conditions. If any discrepancies (balancing or error codes) get identified, the automation will abort and the process will have to be completed manually, see IRM 3.17.30 3.8. These output records must be handled as a daily priority and verified prior to requesting the regular consolidated TEP. During the first week of the new year the MeF TEP runs will need to be balanced manually until the initial MeF runs can be verified as correct. BAL62 is the automated MeF TEP programming, refer to IRM 3.17.30.12.9.1.

SCRIPS is an input processing system which replaced the OCR (REI/Scan-Optics) systems in the Submission Processing Campuses. SCRIPS will process Form 941 and Form 940, Schedule K-1 and IRP. These forms will be scanned by SCRIPS and processed through DED, GMF, and SCCF.

SCRIPS is an image capture and data processing system. Capturing images allows the system to use labor savings technologies, such as character recognition (both image and optical). Using these combined technologies, SCRIPS can offer a system that will reduce labor associated with handling paper and performing data entry.

SCRIPS will be able to store and retrieve digitized images of Form 941, Form 940 and Form 1096 and Schedule K-1. SCRIPS will interface and be integrated into other input initiatives.

The Block Header control data is recorded on computer tape. The information on the tape is then transferred to the SCCF. This process sets up or "establishes" the blocks on the SCCF. The information includes the block DLN, block control identification, batch control number and total volume in the block. The Accounting Function has the responsibility for the SCCF information. If the SCCF computer program detects an error in the information that is input to the file, the Block Header data will print out on an Invalid Listing that is worked primarily by the Accounting Function.

To access any DLN on the SCCF, enter Command Code SCFTR, followed by the Master File System Code and the Block DLN, with a space only between the command code and the MFID code. (See IRM Figure 3.17.30-15).

Figure 3.17.30-15

Shown is a screen shot of the SCFTR screen with the data entered as stated in the text.

Please click here for the text description of the image.

The Master File system codes:

The DLN must be entered as 12 numbers without hyphens or spaces.

Use Tax Class 6 or the true tax class for NMF. If Tax Class 6 is used, the true tax class will be determined, validated, and displayed in the DLN of the transcript response, if needed.

If the DLN is not on the SCCF for the requested Master File, the message "No Record of DLN" is displayed. (See IRM Figure 3.17.30-17).

Figure 3.17.30-17

Shown is a screen shot of SCFTR. As explained in the text, the DLN on the first line is not found in the database, hence, NO RECORD OF DLN, is on the second line.

Please click here for the text description of the image.

If the DLN is open on the SCCF, the complete transcript is displayed. (See IRM Figure 3.17.30-18).

Figure 3.17.30-18

Shown is a screen shot via SCFTR of an IMF Individual Control File Transcript. This Transcript provides the from-to history of the block and the block's current status, and Module Balances.

Please click here for the text description of the image.

If multiple research attempts performed from the same Master File, the operator may tab twice after initial request to place the cursor on the first position of the DLN for overlaying the subsequent DLN.

If the block is removed to the Historic transcript after conversion to the on-line SCCF, the response is an abbreviated record having only the block DLN and the latest historic cycle, plus a pre-formatted SCFTRH record to request reactivation of the historic transcript. If more research is necessary, transmit the SCFTRH request. See IRM 3.17.30.4.6 for more instructions.

The on-line control file is updated continually for on-line SCCF adjustments and updated daily for batch processing at the conclusion of the SCF03 run.

SCFTR displays up to 10 pages, with 15 control records per page. If more than 150 records input, some of the records would consolidate to prevent an overflow condition.

Use the print option to get a copy of the transcript. For multi-page transcripts, this is the only way to see the entire record at one time. However, print the transcript only when necessary.

All SCCF transcripts print or display in the same basic format. The top part identifies the current status of the block. (See IRM Figure 3.17.30-19).

Figure 3.17.30-19

Shown is an individual Control File Transcript. Refer to the 14 alphabetized arrows pointing to the various data listed at the top of the transcript. These alphabet items get identified in the text.

Please click here for the text description of the image.

Each SCCF transcript displays six different count and amount balances. The total in-process balance is the sum of the Manual, Error, and Reject balances. The following paragraphs match the letters on IRM Figure 3.17.30 -19.

The manual balance represents items that set up on the SCCF but have not yet transcribed. This includes reinputs and reprocessables that have yet to be re-transcribed. (d)

The Error balance represents items in the Input Correction inventory, including both error registers and Error Resolution System error items. The Error balance is increased with from-to codes 0–3 and 1–3 or decreased with codes 3–0, 3–2, 3–4, and 3–5. (e)

The Reject balance represents items in the reject or ERS suspense inventories. (f)

The Delete balance is not an open balance but is provided for informational purposes to show items and money that deleted from the block. The Delete balance is increased with Codes 0–2, 1–2, 3–2, 4–2, or 6–2 and decreased with code 2–0. (g)

The Good balance, also not an open balance, shows the count and amount sent to Enterprise Computing Center (ECC) for posting. The Good balance is increased with codes 0–5, 1–5, 3–5, and 4–5. The Good balance is always decreased with 5–0 and may be decreased with codes 0–0R, 6–0, 6–4, and 6–2. (h)

The batch and program numbers (BP) are shown on most non-remittance blocks. (i)

The Action Delete Status Indicator (ADSI) is off (0) unless a Trans Deletion Control Record or 7–7 SCCF adjustment is posted to the module. If the indicator is on (1), no Good Block Proof Record can post to the module. (j)

The Block Status Code (S) identifies the current status of the Block on the SCCF. (k)

The Block Out of Balance Indicator (B) is 1 if the block is in BOB status or 0 for all other blocks. The indicator is turned on with a 0–1 control record or off with code 1–0, 1–2, 1–3, 1–4, or 1–5, or whenever the SCCF manual balance is reduced to zero. (l)

The Age Counter (A) shows the number of times that a block is selected for the monthly SCCF age review. Each time the block is printed on the monthly age transcript, the indicator is increased by one. The indicator is never decreased, unless a Historic block is reactivated as a reprocessable. (m)

The Historic Cycle (HC) is filled with zeros when the original block has never pulled off to a Historic. HC with a cycle number represents the latest cycle that a block has gone to the Historic file. (n)

Each control record that posts to the SCCF is shown in the control record section of the transcript. (See IRM Figure 3.17.30-20).

Figure 3.17.30-20

Shown is the same transcript as figure 19. Where as figure 21 identified the data at the top of the transcript, this figure shows the body of the transcript with 14 different alphabetized arrows stating what the item is in the transcript.

Please click here for the text description of the image.

The on-line transcript displays one control record per line, while the printed transcript normally displays two, reading across.

This section prints only for the Invalid Transcript, SCF0743, and is displayed for on-line SCCF adjustments.

Each control record that does not post to the SCCF is printed at the bottom of the transcript. For NR (no record) transcripts, this is the only section except for the DLN and transcript code.

The standard elements of the invalid record is as follows: (See IRM Figure 3.17.30-21).

Figure 3.17.30-21

Shown is an IMF Individual Control File Transcript. The elements of this invalid transcript is listed on one line at the bottom of the page with alphabetized arrows identifying the items on the line listed in this figure.

Please click here for the text description of the image.

The remaining elements vary with the type of control record. See IRM 3.17.30.4.5 for more information on the record formats.

Frequently, when working the Invalid CRL or the SCCF Invalid Transcript, it is necessary to examine the complete invalid record.

All control records have 92 characters. Positions 1–61 and 89–92 is standard, although some of the positions may be blank for some types of records.

Position 1—Record Type ID Code—a

Positions 2–4–SC Block Control Number. The alpha may be blank or present for any type of control record.—b

Position 5—From Code. Must be 0–9 and a valid combination. See IRM 3.17.30.5.2. The From and To codes may be blank only for a Trans Deletion Control Record.—c

Position 6—To Code. Must be 0–5, 7, 9, or blank and a valid combination. See IRM 3.17.30.5.2.—d

Position 7—Reinput Source Code. This position must be blank, 4, E, H, N, R, or U.—e

Position 8—Master File System ID Code—f

Positions 9–19—Block DLN—g

Position 20—DLN Year Digit—h

Positions 21–24—Document Count—i

Positions 25–28—Batch Number—j

Positions 29–33—Program Number—k

Positions 34–46—Credit Amount—l

Positions 47–59—Debit Amount—m

Positions 60–61—DLN Serial Number—n

Positions 90–92—Control Record Error Codes—o

Any module that has removed to the Historic Database in the current year or prior six years may be reactivated.

Historic reactivation requests generate whenever a 0–0 R (reprocessable) or 6–4, 6–0, or some 6–2 (nullified) control record is posted to a SCCF module where only an abbreviated historic Database record is present.

Blocks reactivated by SCFTRH request for historic research get created in Inactive status on the control file.

Adjustments to the SCCF get prepared because of SCCF posting errors, age review, and other problems identified during processing.

Most adjustments to the SCCF get entered with Command Code SCFAJ. With SCFAJ, each adjustment is input, validated, and posted in real time.

Every transaction that posts to the SCCF has a From Code and To Code.

When the From and To Codes is in the range of 0 to 6, the standard meanings apply.

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

The Control Record Source Code is required for every SCCF adjustment, including renumber adjustments. The code should show 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:

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

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

Adjustments made from the CRL to correct error codes; to correct erroneous MCRs; and to create MCRs normally created on the Master CRL get assigned a source code C.

Source Code D is used for ECC deletes.

Source Code E is used by the Input Correction Operation.

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

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

Source Code K identifies adjustments originating from BBTS.

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

Source Code N is used for adjustment to Nullified Unpostables.

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.

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

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

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

Other codes may be established locally with designated special meanings.

Enter Command Code SCFAJF to display a SCCF adjustment screen. (See IRM Figure 3.17.30-28).

Figure 3.17.30-28

Shown is the SCFAJ screen described in the text. It has the following fields to be populated, listed from top to bottom of the screen: BLOCK DLNMASTER FILEFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

If the SCFAJ record fails a CRL validity check, it is re-displayed with an error message. (See IRM Figure 3.17.30-30).

Figure 3.17.30-30

Shown is the SCFAJ screen described in the text. It has the following fields to be populated, listed from top to bottom of the screen with the last row being populated with a systemic generated Error Code message : BLOCK DLNMASTER FILEFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKSError Message (System generated)

Please click here for the text description of the image.

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

The valid error messages:

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.

Move the cursor to the bottom of the screen and retransmit. (See IRM Figure 3.17.30-31).

Figure 3.17.30-31

Shown is the SCFAJ screen described in the text. It has the following fields to be populated, listed from top to bottom of the screen: BLOCK DLNMASTER FILEFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

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 IRM Figure 3.17.30-34).

Figure 3.17.30-34

Shown is a Form 4028 with a box superimposed on part of the figure listing the fourteen columns as explained in the text: Serial NumberSC or Alpha Block Control NumberFrom CodeTo CodeReinput Source CodeMaster FileBlock DLN (the following five bullets is a listed subset of this on the line below this header)Service Center or District OfficeTax Class and Doc. CodeJulian DateBlock NumberYear Document CountAdjustment Credit AmountAdjustment Debit AmountDLN Serial NumberControl Record Source CodeNMF Abstract NumberReason for Adjustment

Please click here for the text description of the image.

Adjustment Code

Reinput Source Code

Prepare Form 4028-A to delete one DLN and simultaneously establish a renumber DLN on the SCCF. (See IRM Figure 3.17.30-35).

Figure 3.17.30-35

Shown is a Form 4028-A with a box superimposed on part of the figure listing the fifteen columns as explained in the text: Serial NumberSC or Alpha Block Control NumberFrom CodeTo CodeReinput Source CodeMaster FileBlock DLN (the following five bullets is a listed subset of this on the line below this header)Service Center or District OfficeTax Class and Doc. CodeJulian DateBlock NumberYear Document CountAdjustment Credit AmountAdjustment Debit AmountDLN Serial NumberControl Record Source CodeNew DLN (the following five bullets is listed below this header to be populated)Service Center or District OfficeTax Class or Document CodeJulian DateBlock NumberYearNew DLN Serial NumberNew Master File CodeRemarks

Please click here for the text description of the image.

Serial number—An assigned, consecutive two-digit number assigned later.

SC or ABC number—the document ABC number or Julian date of the CRL.

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

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

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

Original DLN—DLN of block being deleted.

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

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

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

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

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

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

New Master File—Enter the number 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.

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

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. Form 4028 and Form 4028-A must be blocked separately.

Figure 3.17.30-36

Shown is a Form 4028-A with a box superimposed on part of the figure listing the fifteen columns as explained in the text: Serial NumberSC or Alpha Block Control NumberFrom CodeTo CodeReinput Source CodeMaster FileBlock DLN (the following five bullets is a listed subset of this on the line below this header)Service Center or District OfficeTax Class and Doc. CodeJulian DateBlock NumberYear Document CountAdjustment Credit AmountAdjustment Debit AmountDLN Serial NumberControl Record Source CodeNew DLN (the following five bullets is listed below this header to be populated)Service Center or District OfficeTax Class or Document CodeJulian DateBlock NumberYearNew DLN Serial NumberNew Master File CodeRemarksTwo rows get populated with data to show an original DLN and the renumber DLN.

Please click here for the text description of 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 get skipped, the serial number is required only on the first and last entries on each page.

2. No sort by Master File is required.

Verify the source document against the corresponding CRL list to assure that all SCCF adjustments is transcribed. (See IRM Figure 3.17.30-37).

Figure 3.17.30-37

Shown is a Renumber Control Record List. The record has the following columns with the rows populated with data, as described in the text: ERR CODEDELETED DLNSER NUMRCFCTCDOC CTAMOUNTNEW DLNSER NUMDOC CTNEW MFRC

Please click here for the text description of the image.

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

Although the CRL is produced by a single computer run (SCF11), the control records get divided into five major segments and printed separately by Master File.

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 CRL-Invalid Control Records.

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

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.

The Invalid Records List is printed in the input format. (See IRM Figure 3.17.30-39).

Figure 3.17.30-39

Shown is the Control Record List - Invalid Control Records. It has the following five columns which provide the information stated in the text: ERROR CODESERROR CODESCONTROL RECORDNo header, just a column with the number 001 in each rowFILEThe bottom of the report lists the number of TOTAL INVALID RECORDS.

Please click here for the text description of the image.

The conditions included on this listing is:

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

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

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.

Error Codes T, U, V, X, Y, and Z is valid on this listing. See IRM 3.17.30.7.1.1 for procedures.

All SCCF adjustments that pass the initial validity checks get printed on the Adjustments part of the CRL. (See IRM Figure 3.17.30-40).

Figure 3.17.30-40

Shown is the top and bottom part of the IMF Adjustment Control Record List, as described in the text. The top part of the report has the report name and ten columns to be populated with data, from left to right the columns are: ABCDLN SER NUMFCTCCR CDRCDCDOC CTPRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)OTHER PRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS) The bottom part of the report lists the lines listed and described in the text.

Please click here for the text description of the image.

The records included on this listing include:

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

The "CR CD" field is the Control Record Source Code. The codes get explained in IRM 3.17.30.5.3.

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

The "DC" code is the Delete Source Code.

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

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

The summary of the Adjustment CRL provides separate counts for the different types of records on the listing.

The Control Record List-Master Control Records is a listing of blocks established on the SCCF. (See IRM Figure 3.17.30-41).

Figure 3.17.30-41

Shown is the top and bottom part of the IMF Master Control Record List, as described in the text. The top part of the report has the report name and ten columns to be populated with data, from left to right the columns are: ABCDLNSER NUMFCTCCR CDRCDCDOC CTPRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)OTHER PRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS) The bottom of the report lists the following headers in a column: FILE LOCATION CODETAX CLASS X SUBTOTALSTAX CLASS X TOTALSTOTALSTOTAL ERROR - CODEDGRAND TOTALSPAGE TOTALS

Please click here for the text description of the image.

The Renumber Control Record List has all renumber block proof records and renumber adjustment records input through IDRS by the Rejects function using Command Code NWDLN. Renumber adjustments may also be input through ISRP using the Form 4028-A. (See IRM Figure 3.17.30-44).

Figure 3.17.30-44

Shown is a Renumber Control Record List as identified in the text. The report has fourteen columns from left to right on the report is listed below: ERR CDABCDELETED DLNSER NUMRCFCTCDOC CTAMOUNTNEW DLNSER NUMDOC CTNEW MFRC

Please click here for the text description of the image.

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

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

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

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

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

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.

Renumbered transactions are also printed on a list sorted by new DLN. The New DLN Record List, SCF1148 allows cross-reference DLN research using either the new or the original DLN. (See IRM Figure 3.17.30-45).

Figure 3.17.30-45

Shown is a New DLN Record List as identified in the text. The report has thirteen columns from left to right on the report is listed below: ABCNEW DLNSER NUMNEW MFRCFCTCDOC CTAMOUNTDELETED DLNSER NUMDOC CTRC

Please click here for the text description of the image.

Any record that is rejected, reinput, or voided by the 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 IRM Figure 3.17.30-49).

Figure 3.17.30-49

Shown is the Nullified Control Record List identified in the text. The record lists the following information in columns read from left to right: ER CDABCDLNSER NUMFCTCCR CDRCDCDOC CTPRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)OTHER PRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)

Please click here for the text description of the image.

Rejected or reinput records is validated using standard CRL error codes.

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

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 IRM Figure 3.17.30-50).

Figure 3.17.30-50

Shown is a Control Date Recap - Nullified Unpostables as identified in the text. There is six columns listing from left to right the following headings: CNTRL DATEDOC COUNTPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PJ AMOUNTS DEBITSOTHER PJ AMOUNTS CREDITSTOTAL PJ AMOUNTS DEBITSTOTAL PJ AMOUNTS CREDITS

Please click here for the text description of the image.

See IRM 3.17.30.13.3 for instructions regarding the nullified listings produced by the GUF system.

The Tape Control Record List has the control records for all documents going to errors, rejects, or good tape. (See IRM Figure 3.17.30-51).

Figure 3.17.30-51

Shown is a Tape Control Records List as identified in the text. The list from left to right has the following column headings: ABCDLNBAT NUMRCFCTIABS NUMTRANS TAPE AMOUNTREC CTDOC CTTRANS SEQDOC CTFCREJECT TAPE AMOUNT

Please click here for the text description of the image.

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

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 IRM Figure 3.17.30-52).

Figure 3.17.30-52

Shown is a Control Date Recap - Good Block Proof Records as identified in the text. There is six columns listing from left to right the following headings: CNTRL DATEDOC COUNTPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PJ AMOUNTS DEBITSOTHER PJ AMOUNTS CREDITSTOTAL PJ AMOUNTS DEBITSTOTAL PJ AMOUNTS CREDITS

Please click here for the text description of the image.

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 shows that the same block DLN appears twice. Normally, this is not an invalid condition as reprocessable block DLNs frequently get input twice on the same day. (See IRM Figure 3.17.30-53).

Figure 3.17.30-53

Shown is the BLOCK SEQUENCE LIST which is described in the text. The figure is listing the Tape Sequence Number and associated Block DLNs is listed.

Please click here for the text description of the image.

Some records get consolidated prior to posting to the SCCF.

Multiple control records for the same block DLN on the same day get consolidated in SCF01 when the following fields is the same on each record:

When records get consolidated, the item counts and money amounts get added together. The DLN serial number on the consolidated record is XX. (See IRM Figure 3.17.30-54).

Figure 3.17.30-54

Shown on the top line of this transcript is title, cycle, and date. The transcript has the following categories across the top of the report, below the title line: TCBlock DLNCountAmountCount (status of the block - in ORG, ERRS, REJ, DEL, MAN, GOOD Status) Amount (money in ORG, ERRS, REJ, DEL, MAN, GOOD Status)

Please click here for the text description of the image.

Although the record on the SCCF is consolidated, each record is listed separately on the CRL. (See IRM Figure 3.17.30-55).

Figure 3.17.30-55

Shown is the Control File Transcript identified in the text. The record lists the following information in columns read from left to right: ER CDABCDLNSER NUMFCTCCR CDRCDCDOC CTPRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)OTHER PRE-JOURNALIZED AMOUNTS (DEBITS, CREDITS)

Please click here for the text description of the image.

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

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

This error condition occurs whenever a character other than numbers 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 has significant data. (See IRM Figure 3.17.30-56).

Figure 3.17.30-56

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

Figure 3.17.30-57

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

Remember that amounts coded with Error Code 0 is 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.

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

A control record will print with error code 1 if any of the following condition(s) is present: (See IRM Figure 3.17.30-58).

Figure 3.17.30-58

Shown is a Master Control Record as identified in the text. The data listed is the output values that created the error condition. Listed from left to right is the column headers of this record: ERR CDABCDLNBAT NUMPROG NUMDOC CTRCISSER NUMPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PRE-JOURNALIZED DEBITSOTHER PRE-JOURNALIZED CREDITS

Please click here for the text description of the image.

Review the source document for transcription errors and prepare any necessary SCCF adjustments. (See IRM Figure 3.17.30-59).

Figure 3.17.30-59

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

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

The Submission Processing Campus identified in the link below is currently processing electronically filed documents. For these Centers, the Area Office codes listed in Section 4, Document 6209 is restricted for use as File Location Codes (FLC) in the DLN of electronically filed documents. SERP - IDRS Campus and File Location Codes - Section 4 - 6209 (irs.gov)

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 IRM Figure 3.17.30-60).

Figure 3.17.30-60

Shown is a Master Control Record as identified in the text. The data listed is the output values that created the error condition. Listed from left to right is the column headers of this record: ERR CDABCDLNBAT NUMPROG NUMDOC CTRCISSER NUMPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PRE-JOURNALIZED DEBITSOTHER PRE-JOURNALIZED CREDITS

Please click here for the text description of the image.

For every control record generated by the RPS, the program number and debit amount must be blank.

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

This condition occurs whenever the document code is not valid for any type of input. (See IRM Figure 3.17.30-62).

Figure 3.17.30-62

Shown is a Master Control Record as identified in the text. The data listed is the output values that created the error condition. Listed from left to right is the column headers of this record: ERR CDABCDLNBAT NUMPROG NUMDOC CTRCISSER NUMPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PRE-JOURNALIZED DEBITSOTHER PRE-JOURNALIZED CREDITS

Please click here for the text description of the image.

Because the program is unable to recognize the document code, any money amount cannot be accumulated as pre-journalized. For this error code only, the money is automatically counted as other Pre-journalized.

When an adjustment is prepared to establish the correct DLN, be sure to correct the PJ and OPJ totals. (See IRM Figure 3.17.30-63).

Figure 3.17.30-63

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

This condition occurs in the following situations: (See IRM Figure 3.17.30-64).

Figure 3.17.30-64

Shown is a Master Control Record as identified in the text. The data listed is the output values that created the error condition. Listed from left to right is the column headers of this record: ERR CDABCDLNBAT NUMPROG NUMDOC CTRCISSER NUMPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PRE-JOURNALIZED DEBITSOTHER PRE-JOURNALIZED CREDITS

Please click here for the text description of the image.

Review the source documents for transcription errors or duplicate input. Prepare an adjustment to correct the record. (See IRM Figure 3.17.30-65).

Figure 3.17.30-65

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

Coordinate the Renumbered duplicate DLN with the rejects function, if needed.

This condition occurs in the following situations.

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

Figure 3.17.30-67

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

This condition occurs in the following situations: (See IRM Figure 3.17.30-68).

Figure 3.17.30-68

Shown is a Renumber Control Record List identified in the text. This list has the following column headers, read from left to right: ERR CDABCDELETED DLNSER NUMRCFCTCDOC CTAMOUNTNEW DLNSER NUMDOC CTNEW MFRC

Please click here for the text description of the image.

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

The new DLN has other than twelve numbers or other than one of the following literals:

The original DLN and new DLN is incompatible on revenue receipts.

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

Figure 3.17.30-69

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

Figure 3.17.30-70

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

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.

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.

This condition occurs in the following situations (See IRM Figure 3.17.30-71).

Figure 3.17.30-71

Shown is a Master Control Record as identified in the text. The data listed is the output values that created the error condition. Listed from left to right is the column headers of this record: ERR CDABCDLNBAT NUMPROG NUMDOC CTRCISSER NUMPRE-JOURNALIZED DEBITSPRE-JOURNALIZED DEPOSIT CREDITSPRE-JOURNALIZED NON - DEPOSIT CREDITSOTHER PRE-JOURNALIZED DEBITSOTHER PRE-JOURNALIZED CREDITS

Please click here for the text description of the image.

Review the source document or block. Determine the correct count. Create the correct record with a SCCF adjustment. (See IRM Figure 3.17.30-72).

Figure 3.17.30-72

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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 IRM Figure 3.17.30-73).

Figure 3.17.30-73

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKSListed at the bottom of the record is the Error Code with written description.

Please click here for the text description of the image.

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

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.

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

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

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

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

Use of Reinput Source Code E overrides this error check. Use this rarely.

This condition occurs on the Invalid Control Record List or SCFAJ adjustment whenever a tax class is input that is not numbers or not valid for the Master File. (See IRM Figure 3.17.30-75).

Figure 3.17.30-75

Shown is an Adjustment Control Record as identified in the text. The Error Code(s) is listed at the bottom of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

Compare the DLN and Master File code of the record with the source document. When the reason for the error is determined, input a SCCF adjustment on SCFAJ to correct the record.

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

Shown is an Adjustment Control Record as identified in the text. The Error Code(s) is listed at the bottom of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

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

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

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

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.

Only the following record type codes is valid in SCCF processing:

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

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

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

Shown is an Adjustment Control Record as identified in the text. The Error Code(s) is listed at the bottom of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

See IRM 3.17.30.5.2 for a list of the valid code combinations.

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

Every valid control record must have one of the following Master File codes:

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

Shown is an Adjustment Control Record as identified in the text. The Error Code(s) is listed at the bottom of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

Review the invalid record and the source document to determine the correct Master File. Then input the corrected record using Command Code SCFAJ.

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.

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

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.7.7 and IRM 3.17.30.6.6.

Each validated control record is systemically analyzed to assure compatibility for posting to the correct module on the SCCF Database.

Invalid transcripts get coded to identify the condition which makes the control record incompatible with SCCF. These codes is called transcript codes and apply to both on-line and printed transcripts. See IRM 3.17.30.9.

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

Invalid transcripts on SCF0743 get printed with the correct SCCF module.

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

Figure 3.17.30-79

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)

Please click here for the text description of the image.

Correction of the MCR record type depends on the type of error condition encountered.

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

Record type code ADJ shows a record causing the transcripts is 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

Shown is a Individual Control File Transcript as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)Listed in the transcript is an adjustment which is described in the text.

Please click here for the text description of the image.

The type of error condition encounter determines the correction.

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

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.

Coordinate any corrective action with the BOB Function.

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 proper BCRs with the audit trail postings.

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

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This transcript lists an E/R as described in the text.

Please click here for the text description of the image.

The E/R record type will be corrected according to type or error condition.

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

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.

Record Type Code GBP shows 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

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)A record type code GBP is listed which is described in the text.

Please click here for the text description of the image.

For each GBP transcript, a record is added to the on-line delete file. See IRM 3.17.30.11.2 for instructions for the on-line delete file and Command Code SCFDL.

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

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

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)Listed in the transcript is two BPRs as described in the text.

Please click here for the text description of the image.

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

Analyze the source documents and coordinate any corrective action with the function handling the input of the record.

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.

Blocks of documents that input without the DLN being established on the SCCF is identified with BOB Code P.

BOB P blocks get 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

Shown is a BOB P Code Block List as described in the text. The list has the following column headers read from left to right: RELEASE CODEBLOCK DLNBOB SEQ NUMPROGRAM NUMBERBATCH numberABCDOCUMENT COUNTMASTER FILEP-DATEBOB CODES

Please click here for the text description of the image.

The BOB P Block List has five types of Blocks in the order listed:

Resolve each block by ensuring that the Batch Transmittals is properly routed to Data Conversion. Review the CRL–MCRL to verify that adjustments have prepared for error coded records. If the wrong DLN is 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.

If the MCR is correct, but the wrong DLN is 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.

Any BOB P block that also has 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 is input.

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.

This transcript code occurs with any of the following conditions:

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

Shown is an Adjustment Control Record as identified in the text. The Error Code(s) is listed at the bottom of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

If the DLN is transcribed incorrectly, input Command Code SCFAJ with From–To Code 0–0 to establish the correct DLN. (See IRM Figure 3.17.30-86).

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.

Figure 3.17.30-87

Shown is a Individual Control File Transcript as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)

Please click here for the text description of the image.

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.

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.

Figure 3.17.30-88

Shown is an Adjustment Control Record as identified in the text. The error is listed in the remarks section of the record. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABC SERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

Figure 3.17.30-89

Shown is a Individual Control File Transcript as identified in the text. This has a Transcript Code error. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)

Please click here for the text description of the image.

Review the erroneous control record and the related source document.

Figure 3.17.30-90

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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

Figure 3.17.30-91

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This transcript has two errors as described in the text.

Please click here for the text description of the image.

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 is previously deleted.

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

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This is a Transcript Code error as described in the text.

Please click here for the text description of the image.

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

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 is sent to accounting to increase or decrease volume from Receipt and Control Branch.

Figure 3.17.30-94

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

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.8.5. Pull the block for future processing.

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

Figure 3.17.30-95

Shown is a Individual Control File Transcript as identified in the text. This has a Transcript Code error. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)

Please click here for the text description of the image.

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

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

Review the source documents.

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.8.5. Pull documents for future processing.

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.

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

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

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)

Please click here for the text description of the image.

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.

Review the source documents.

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

Figure 3.17.30-99

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This transcript reflects a delete action which is described in the text.

Please click here for the text description of the image.

This is not an invalid condition and requires no corrective action. However, the transcript should be kept for reference if more actions will be taken on the block. The 8–2 action is 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.10.5 for detailed instructions.

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

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.

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

Shown is an Individual Control File Transcript as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This transcript is listing transcriptions as described in the text.

Please click here for the text description of the image.

The Transcript Code MX condition occurs when the 150th record tries to post.

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.

See IRM 3.17.30.10.5 for correction procedures.

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

Figure 3.17.30-101

Shown is a Control File Transcripts Invalid Modules as identified in the text. This transcript has the following headers read in columns from left to right: TCBLOCK DLNABCISCOUNT AND AMOUNT (in these categories - Original, Error, Delete, Manual, Reject, Good)This transcript shows a no record as described in the text.

Please click here for the text description of the image.

From–To Codes that normally establish a block on the SCCF is 0–0R, 0–0, 6–0, and 6–4.

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

Shown is an Adjustment Control Record as identified in the text. This record has the following descriptions listed on the left side of the SCFAJ screen, from top to bottom of the record: BLOCK DLNFROM TO CODEREINPUT SOURCE CODECONTROL RECORD SOURCE CODEDOCUMENT COUNTCREDIT AMOUNTDEBIT AMOUNTABCSERIAL NUMBERNMF ABSTRACT NUMBERREMARKS

Please click here for the text description of the image.

These transcripts get 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.

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

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

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

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

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

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

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 rejected from normal processing. (See IRM Figure 3.17.30-103).

Figure 3.17.30-103

Shown is a Tape Control Records Listing which is described in the text.

Please click here for the text description of the image.

The listing shows: