This Section includes instructions for maintaining and balancing the Service Center Control File, balancing and releasing transaction tapes to the Enterprise Computing Center, and balancing the Submission Processing Campus (SPC) suspense accounts.

Instructions for maintaining the Federal Tax Deposit (FTD) control system are included in IRM 3.5.17.

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.

Provided below are the definitions to words/terms used while working with the SCCF.

CRL Outputs

SCCF Outputs

Revenue Receipts

Tape Edit Processor Outputs

Unpostables

Other SCF Listings

Error Resolution System

RPS Listings

ISRP-RRPS

DED Reports

Other GMF Reports

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.

See IRM 3.17.10 for balancing procedures for the Accounting Control packages.

Portions of the package are used by Data Controls for SCCF balancing after Accounting Control balancing has been completed.

Secure copies of BBTS Forms 6695, Batch Transmittal, for count verification of generated non-remittance MCRs.

Forms 6695 are returned from Data Conversion after the master control records have been established on SCCF.

Figure 3.17.30-4

Balance the total count from the SCF 11–44, Non-Prejournalized Batch Recap to the total count of Form 6695 for each master file. (See figure 3.17.30-4)

If a variance is discovered:

A list of Submission Processing Function Codes listed in the BBTS IRM, 3.10.5 are listed below:

Most IMF and BMF payments are processed through the Integrated Submission and Remittance Processing (ISRP) — Residual Remittance Processing System (RRPS) and Lockbox. RRPS run ISR–05 and Lockbox RPS-01 generates a tape of master control records which are processed to the SCCF through RPS-01, GMF–04 and GMF–06. On the same day, RPS–07 creates blocks of transaction records which are processed through the regular series of GMF runs, and DED for Lockbox.

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 figure 3.17.30–15)

The RTR System allows the user to query for specific records. It is important to enter as much information as possible in order 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 and 2345, Batch Transmittal, that is corrected or voided as a result of an error found by Data Conversion or Receipt and Control should be routed to Data Control with other Batch Transmittals.

These Batch Transmittals should be clearly labeled and withdrawn from the other transmittals for special processing.

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

Figure 3.17.30-16

See 3.17.30.2.4(3) for Batch Query procedures. (See Figure 3)

Submission Processing Campuses processing electronically filed (ELF) returns should assure that SCCF control is established for all returns accepted by ELF and that all transactions are accounted for in the system.

The ELF run to run balancing from multiple runs of ELF 02–48, through the ELF validity checks in ELF 04–48 and 05–48, to ELF 06–48 and ELF 06–49 will provide the grand totals of accepted returns from ELF.

Balance the ELF 06–48, returns accepted from ELF 06–49, verified by the total blocks accepted according to beginning and ending DLNs on the ELF 06–49, to the ELF MCRs on the SCF 11–42, Master CRL.

Verify that all MCRs have corresponding block proof records on the SCF 11–51, Tape CRL, or are controlled in the Block Out of Balance inventory.

Return blocks with ISS Code C (SCRIPS) on the SCF 11–51, Tape CRL, may be treated as exceptions to the ELF balancing techniques.

All discrepancies should be resolved immediately through coordination with the ELF staff.

BAL6040 and 6140 are run control reports implemented in 2007. They are generated through automated programming that total the ELF transmissions, balance Little ELF to Big ELF to SCCF and scan for error code and invalid conditions. If any discrepancies (balancing or error codes) are identified, the automation will abort and the process will have to be completed manually. 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 ELF TEP runs will need to be balanced manually until the initial ELF runs can be verified as correct. BAL62 is the automated ELF TEP programming, refer to 3.17.30.8.1 (c).

SCRIPS is an input processing system which replaced the OCR (REI/Scan-Optics) systems in the Submission Processing Campuses. SCRIPS will process the current scannable applications of FTD's, Forms 941 and 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). Through the use of 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 FTD's, and Forms 941, 940 and 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 Service Center Control File (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 figure 3.17.30-17)

Figure 3.17.30-17

The master file system codes are:

The DLN must be entered as 12 numerics 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 appropriate.

If the DLN is not on the SCCF for the requested master file, the message "No Record of DLN" is displayed. (See figure 3.17.30-19)

Figure 3.17.30-19

If the DLN is open on the SCCF, the complete transcript is displayed. (See figure 3.17.30-20)

Figure 3.17.30-20

If multiple research attempts are done 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 was removed to the Historic transcript after conversion to the on-line SCCF, the response is an abbreviated record containing only the block DLN and the latest historic cycle, plus a pre-formatted SCFTRH record to request reactivation of the historic transcript. If additional research is necessary, transmit the SCFTRH request. See 3.17.30.3.6 for additional 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 SCF–03 run.

SCFTR displays up to 10 pages, with 15 control records per page. If more than 150 records had been input, some of the records would have been consolidated 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 are printed or displayed in the same basic format. The top portion identifies the current status of the block. (See figure 3.17.30-21)

Figure 3.17.30-21

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 figure 3.17.30-21.

The Date is always the current date for on-line transcripts. For printed transcripts, the Date is the system date. (a)

Block Document Locator Number (b)

The Original balance normally reflects the figures on the block at the time it was established. (c)

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

The Error balance represents items that are in the Input Correction inventory, including both error registers and ERS 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 have been 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 has been 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 been 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 figure 3.17.30-22)

Figure 3.17.30-22

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, SCF–07–43, and is displayed for on-line SCCF adjustments.

Each control record that fails to 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 are as follows (See figure 3.17.30-23)

Figure 3.17.30-23

The remaining elements vary with the type of control record. See 3.17.30.3.5 for additional information on the record formats.

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

All control records contain 92 characters. Positions 1–61 and 89–92 are 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 3.17.30.4.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 3.17.30.4.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 been removed to the Historic Database in the current year or prior seven years may be reactivated.

Historic reactivation requests are generated 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 data base record is present.

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

Adjustments to the Service Center Control File are prepared as a result of SCCF posting errors, age review, and other problems identified during processing.

Most adjustments to the Service Center Control File are entered with Command Code SCFAJ. With SCFAJ, each adjustment is input, validated, and posted in real time.

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

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