Pending SCCF adjustments represent items which are included in the work inventory but are not reflected in the appropriate count on the SCCF Summaries (SCF 07–42).

Pending deletions from work inventory represent items which have adjusted the appropriate SCCF balances but have not been deleted from ERS, error or reject inventories.

If a large imbalance is identified, report the problem immediately to the CSA as records may have been dropped, omitted, or loaded twice on the files.

Because of differences in individual Submission Processing Campus scheduling, it will be necessary to consider cut-off times for GUF, ERS, etc., adhered to by your campus and to consider these as possible variables to the above procedures.

Enter an 8–2 SCFAJ adjustment as the 150th control record to delete the block in the next posting run. (See figure 3.17.30-116)

Figure 3.17.30-116

The block will then be deleted from the SCCF and printed on the next Invalid Transcript with Transcript Code 82. (See figure 3.17.30-117)

Figure 3.17.30-117

If an on-line SCCF adjustment attempts to post the 150th record with other than From-To Code 8–2, the control record will display as an Invalid Transcript with code MX. Any on-line adjustment with From-To Code 8–2 posts to the SCCF immediately and deletes the module from the SCCF during the next SCF–05 posting run for printing on SCF 07–43 as invalid with Transcript Code (TC) 82.

Combine any control records with the same From Code, To Code, Posting Date, and cross-reference DLN (if any). Add the document count and money amount of these records to form single control records. If this does not sufficiently reduce the number of records, other consolidations may be necessary.

Reestablish the record on the SCCF using Command Code SCFAJ. Enter each control record, providing as much documentation as possible in the Remarks field, including cross-reference DLNs and the cycles of the original postings. (See figure 3.17.30-118)

The error and reject balances on the SCCF have been reduced to zero, or

A SCCF adjustment with From-To Code 8–7 has posted to turn off the ADSI.

This will reverse the Good Block Proof Record and place the count and amount back into a suspense balance.

If the Delete Source Code is "S" , no from-to code will post with the Trans Deletion Control Record. If an adjustment is required, input Command Code SCFAJ.

When the previous delete file has been released by the running of SCF 15, any blocks to be deleted in TEP from the new SCF runs must then be added manually to the delete file using SCFDLA.

If there is a large volume of deletes to be added to the delete file because the previous delete file was not downloaded on time, it may be appropriate to rerun SCF 03 to create the proper delete file.

Code R—Remove a record from the delete file. If an error coded Good Block Proof Record should not be deleted in TEP, Code R will code the record for removal from the delete file. If the record was coded for removal by mistake, overlay the R with a D to indicate that the record should be deleted.

Code D—This code is used to indicate that the record should be deleted in TEP. This is for information only, since every record on the delete file not marked with an "R" is passed against the transaction file in TEP, whether coded with A or D or not coded at all. If Code D is present, this merely indicates that the record has been worked.

To transmit the SCFDL screen use the down arrow key to get to the bottom line of the screen (line that contains employee and page number) and thentab twice to move to the bottom far right corner of the screen before transmitting.

Terminal response will be Request Completed . It is recommended that the user access SCFDL after transmitting and receiving the Request Completed message, to ensure the coding input by the user was maintained in the screen.

MFC is the master file code (1 = IMF, 2 = BMF, 3 = EPMF, 5 = IRP, 6 = NMF).

Enter the block DLN with year digit (no hyphens).

Enter the Delete Source Code (DSC). Enter code M if a 5–0 control record should post to the SCCF, or code S if the SCCF status should not be updated.

Enter the 14–numeric tape sequence number from the Tape Control Record List (SCF–11–51). Not applicable for NMF.

The Alpha Block Control (ABC) is optional.

If more than 12 deletion records need to be added, then a new SCFDLA screen request must be entered. The SCFDLA program does not have multiple pages.

Terminal response will be Request Completed. It is recommended that the user access SCFDL after transmitting and receiving the Request Completed message, to ensure the coding was maintained in the screen.

The entire screen is retained until the error is corrected or the invalid record blanked out and the screen has been successfully transmitted.

The action code, master file code, block DLN, delete source code, and tape sequence number are validity checked.

Use of the alternate method (Form 4028 through ISRP) will result in invalid records appearance on the daily delete file with blank tape sequence number. These should be worked in the normal manner on the Invalid Transcripts, SCF 07–43.

NMF records may be added to the delete file using SCFDLA. Leave the tape sequence number blank. SCF–15 will create a file which is passed through SCF–01 to correct NMF revenue receipts in SCF–13. No NMF records are passed to the TEP, GMF–15.

Adjust the CRL in green if SPC requested, blue when ECC initiated, and/or attach a copy according to local procedures.

Forward the voucher to IRACS for adjusting journal entry.

If needed, prepare Form 2275 to get the documents for input from Perfection Branch or Files.

Input SCFAJ with From-To Code 5–0 and Source Code D to place the deleted block back into suspense if the documents will be reinput with Form 3893.

For NPJ IDRS records, no SCCF adjustment is necessary. Route a copy of the listing to the IDRS coordinator, who will determine if reinput is necessary.

An attachment to the acceptance voucher also lists any Submission Processing Campus cartridge that may have been returned as unprocessable.

Whenever the acceptance voucher indicates that a cartridge has not been processed, contact the Help Desk to ensure that a recovery effort has been initiated. The initial contact from ECC may have been received by telephone.

If any returned cartridges have not been resubmitted and processed within three cycles, be sure to notify the Computer Site contact with the date of the original transmission and any details that are available.

At Submission Processing Campus option, every document deleted for reinput may be referred to Collection for determination and input of action to suppress erroneous notices.

If the action is to be input by Accounting, every BMF return that is more than ten weeks past the due date or IMF return more than six months past the due date requires prompt input of Command Code FRM49 with Transaction Code 599, closing code 18.

Every document code 17, 18, or 19 payment transaction requires input of Command Code STAUP for six cycles.

Be sure to annotate "599–18" or "STAUP–6" and the date on each document.

Box 1—Blank

Box 3—Blank

After preparing Form 3893, attach it to the first document and route to Data Conversion to be reinput, or leave boxes 1 and 3 blank and route to Batching.

Edit the documents for proper input. The documents normally will not go to Returns Analysis.

Route the documents which cannot be reinput through mainline to the IDRS Control Staff, the originating function, or an area designated by the Control Staff.

For read failed documents not to be reinput through Data Conversion Branch, prepare a SCCF adjustment with From-To Code 0–2 and CR Source Code D.

Document Code 64 deleted documents should be routed to the Refund Inquiry Group, Taxpayer Relations function.

Data Control should provide User Support function with list of deleted records for IDRS transactions deleted in TEP. Annotate the list with the method of resolution for the deleted records, e.g., reinput through IDRS, reinput through mainline processing, etc.

Prepare Form 3244 for each item from the Archive Research with a primary TC 670 and a secondary TC 570.

Route to Batching for reinput.

If the documents still being processed are valid and need not be deleted, input Command Code SCFAJ with From-To Code 8–7 to turn off the ADSI. Then pull only the documents that have been deleted and reinput with Form 3893. (See figure 3.17.30-128)

If the block should be voided, input an SCFAJ adjustment for the documents on the Deleted Records list using To Code 2. The From Code will match the current status on the SCCF.

Notify Input Correction to delete the items still open in the Error or Reject inventory. If ERS code 640 is used, a From-To code of 3–0 or 4–0 will post to the SCCF database.

For ERS, Action Code 660 is entered with Command Code RJECT. At Submission Processing Campus option ERS deletes may be entered on the terminal by Data Controls personnel. When all documents have been deleted from rejects, adjust the SCCF as necessary and establish the new DLN with From-To Code 0–0.

Documents on error or reject registers from the same block may be returned to Document Perfection for normal resolution.

No SCCF adjustment is needed if the deletes had source code C or M, other than the From-To Code 8–7 to turn off the ADSI. If source code S, also prepare an adjustment with To Code 0.

The ADSI will prevent erroneous records from posting.

Box 1—Alpha/Numeric Block Control Number—Leave blank if routing to Batching in the Receipt and Control Branch. If routing directly to Data Conversion, enter the designated alpha.

Box 2—Document Locator Number—Enter the eleven digit block DLN. The complete DLN may be entered, but only eleven digits are transcribed into the block header.

Box 3—Enter the batch number if routed directly to Data Conversion.

Box 4—Document Count—Enter the number of documents attached to Form 3893.

Box 5—Credit Amount—Enter the amount of the credit transaction. If more than one document, enter the sum of the credit amounts. Amounts may be from payment transactions, transfer documents, or adjustments.

Box 6—Debit Amount—Enter the total amount of the debits. This box must be blank if a credit amount is present. Debit amounts may be present only with document code 24, 45, 48, 51, 54, 58, and 87.

Enter only when block header transaction code is required.

For IRP, enter the Account Type Code, followed by the Record Identification Code (F or G) followed by the Payer Count. See 3.10.80 for details.

Always enter the received date for Forms 1040ES and 1040C.

Enter received date for returns received after the tax period due date.

Mark "R" for Reprocessable if the return has already posted to the master file. Also complete box 19.

Mark "N" for Nullified if the reinput document was previously an unpostable. Also complete box 18.

Mark "4" for Reinput if the reinput block/document has neither posted nor unposted at the master file. The "4" should always be used when issuing and processing a new DLN. Also complete box 18. When processing a new DLN, mark "Other" in box 18 and write "New DLN."

Enter the 14th digit of the DLN from the source document.

If the year digit is not shown on the document, determine the correct year from the DLN color or from other information on the document.

GMF 15–45, Trans Release Summary for each file containing data, e.g., Mainline, IDRS, Unpostables Auto-LIEN, etc.

GMF 15–45, Trans Release Summary, Other Total Summary, annotated by Releasing Officer. (See figure 3.17.30-130)

Figure 3.17.30-130

For Submission Processing Campuses processing and exercising the option to separate ELF in TEP, GMF 15–45, Trans Release Summary, ELF Total Summary, annotated by Releasing Officer. Be sure the reel number is annotated on the ELF Total Summary. (See figure 3.17.30-131)

Figure 3.17.30-131

The GMF 15–45, Grand Total Summary, should be annotated by the releasing officer since it reflects the total of all records included in the TEP. Additional records shown on the Grand Total Summary which are not shown on either the Other Total Summary or the Elf Total Summary are "generated records added" as indicated on the GMF 15–43, Transaction Release Adjustment Report.

SCF 13–40, RRCS (daily, plus weekly at close of cycle)

GUF 53–40, Unpostable Control Report

GUF 53–42, GUF RRCS—Nullified Unpostables

Promptly coordinate with IRACS on any GMF 15, TEP, that is re-run and/or not released for shipment to ECC.

GMF 15–45 paper documentation should be sent to IRACS for confirmation and comparison with the Daily Posting Summary.

Deleted Records List, GMF–15–42.

Transaction Release Adjustment Report.

Trans Release Summary.

Unmatched Deletes List, GMF–15–41.

Code 1 indicates that the block DLN contains other than 12 numerics.

Code 2 indicates that the Trans Tape Sequence Number is invalid. The number must contain 14 numerics and be greater than the prior number.

Code 3 indicates that the Delete Source code is other than S or M.

Code 4, indicating a Record Type ID Code other than D, and Code 5, indicating an invalid master file literal, should no longer be possible.

Delayed re-entry may cause erroneous balance due and delinquency notices to be generated.

If re-entry is delayed, erroneous notices should be suppressed.

Line out and note "duplicate" for any transactions on the Deleted Records List which were deleted because of duplicate processing.

Subtract any Mainline deletes listed on the Deleted Records List, GMF 15–42, from the totals on the Tape CRL and annotate the resulting totals.

Balance the annotated good tape record count, document count, total debits, and total credits from the Tape CRL to the "SCCF Released" totals on the appropriate Trans Release Summary. (See figure 3.17.30-138)

Figure 3.17.30-138

IMF ELF Submission Processing Centers-When the computing centers are running the automated BAL62 and a separate TEP (GMF25) for a "clean" error free ELF (passed all GMF27 validity checks and ready for Good Tape), verify the BAL62 completed successfully and is available for viewing and retention on Control/D. This verification process must be completed and verified as correct prior to requesting the regular daily consolidated TEP (GMF15). The BAL62 will compare the Released Document Totals on the ELF Total Summary, Grand Total Summary, and IMF Mainline back to the BAL6140 total that read the input from GMF27 (ELF Docs to Good Status). The BAL62 will also scan for GMF25 TEP deletes. There is a zero tolerance for GMF25 TEP deletes, if the scan program identifies a DLN is present on any of the GMF25 TEP Delete reports (GMF 2540, 2541 or 2542), the job will abort and will have to be completed manually by the computing center. Any discrepancies with the BAL62 and the ELF Only GMF25 TEP must be reported immediately to the assigned computing center Computer System Analyst (CSA)staff.

Neither the AUTO—UNDERRPT nor the AUTO—LIEN—FILE Trans Release Summary will have money amounts, but will have record and document counts only.

IDRS deletes in TEP with Trans Source Codes B and L can not be perfected and reinput through mainline processing.

From the GUF 53–40, the Total Corrected, the Reclassified the Total Nullified, and the Purged Unpostables should balance with the corresponding category on the Trans Release Summary for Unpostables for record counts, PJ credit and debit, and net PJ amounts.

Subtract any TEP deletes from the appropriate category (e.g., corrected, reclassified, etc.) on the GUF 53–40.

Add the record counts, PJ credit and PJ debit amounts of the Corrected, Reclassified, Nullified, and Purged Unpostables (minus any TEP deletes) on the GUF 53–40.

The result should equal the "SCCF Released" totals on the Unpostable Trans Release Summary. (See figure 3.17.30-139)

Figure 3.17.30-139

If unable to reconcile an imbalance, do not release the transaction tape. Notify the Computer Branch of a possible read fail and request a rerun of the TEP.