The Integrated Submission and Remittance Processing (ISRP) System transcribes and formats data from paper returns/documents/vouchers for input into the Generalized Mainline Framework (GMF) and other systems by key entry operators. It also captures check images for archiving. Transaction Management System (TMS) is a COTS product that is an integral part of ISRP.

The following provides authority for the instructions in this IRM to be performed in support of completing compliance functions to make credits or refunds of any internal revenue tax, processing of non-revenue forms, and administrative support forms.

The Operations manager is responsible for securing, assigning and providing training for the staff needed to perform the task required throughout this instruction.

The Planning and Analysis Staff is responsible for providing feedback and support to local management to achieve and effectively monitor scheduled goals.

The team manager is responsible for assigning, monitoring and controlling the work flow to accomplish timely completion of the tasks required throughout this IRM.

The employee is responsible for applying the instruction present to the assigned task on the ISRP system to accurately convert paper data to electronic data record for proper posting for use by the Service.

Program Reports: Below are a list of reports to use to show receipts, production and inventory for the paper return to electronic data conversion process. These reports will be utilized to report and monitor daily and weekly status of the program to completeness.

Program Effectiveness: Goals will be measured utilizing standard managerial reports by documents processed per hour and completion of each function compared to the established schedule for completion each week. Each function is expected to retain or exceed schedule prior to the program completion date stated in IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates. Quality reviews are expected to be conducted and monitored by local management and corrective action taken to ensure quality products are released to the next function.

Annual Review: Review the processes included in this manual annually to ensure accuracy and promote consistent tax administration. This may be included under responsibilities for a manager.

The reports for the Control Data Analysis, Project PCD, are on the Control-D/Web Access server, which has a login program control.

The following terms or acronyms are utilized throughout this IRM:

IRM 3.24.37, ISRP System - General Instructions.

IRM 3.30.123, Processing Timeliness: Cycles, Criteria, and Critical Dates.

The Federal Managers' Financial Integrity Act (FMFIA) of 1982 requires each executive agency to conduct annual evaluations of its systems of control using guidelines set by the Office of Management and Budget (OMB).

In December 2004, OMB issued a revision of Circular Number A-123, Management's Responsibility for Internal Control, to provide guidance to federal managers on improving the accountability and effectiveness of federal programs and operations by establishing, assessing, correcting, and reporting on internal control.

For specific guidelines and responsibilities, refer to the Circular A-123, and to IRM 1.4.1, Management Roles and Responsibilities, and IRM 1.4.2, Monitoring and Improving Internal Control.

Input to the Data Edit and Validation (DED) System and ISRP is through ISRP Data Entry, Lockbox, SCRIPS, and magnetic tape. Coordination of data entry instructions is the responsibility of the ISRP analyst, and the analyst assigned to each individual project. These instructions will govern the format of the input into the Edits Processing system. Fields will be edited and output in the same order in which they are entered.

Since the systems are designed so that input can be in a variety of formats, the general requirements for input are minimal and correspond to the format requirements for ISRP.

Each block must contain a block header which consists of:

Each block must contain at least one document with a document breaker ([).

Each block must contain at least one section with a section breaker (@).

Each block must contain at least one field per section.

Each block must contain an end of block indicator (EOB).

When preparing parameters for an input document, comments can be placed on each parameter entry line by separating the end of the parameter and the beginning of the comment with at least three spaces.

The operator class is a one-digit field which may provide additional information on the type of document being entered. Operator class assignment for a given document is obtained from the ISRP analyst along with the Format Code. Generally, the Operator Class is assigned as follows:

A three-digit Format Code must be assigned by the ISRP analyst to each type of input document. While the sections within a document may have various formats on both input and output, all documents entered under one Format Code must have like formats.

The SC Block Control Number (formerly ABC) is a three-digit/character Submission Processing Site generated code assigned to each block of documents for control purposes.

Four problem code fields (one character each) are established by the edits program for every section, immediately in front of the section number. They are in order of occurrence:

These fields will be zero-filled if the problem code checks are successfully passed. More information on problem code checks may be found in Functional Specification Package (FSP) documentation (1.35.00 Part 1, Subpart 2, SC Data Edit Prep).

The Data Edit and Validation (DED) System also performs certain validation checks to ensure logical processing integrity of all input data blocks. Failure of any of these checks will result in the subject block being dropped from further processing. At the same time a line entry will appear on the EDIT REJECT LIST with identifying information, including the block Document Locator Number (DLN) for machine data. For further information on the EDIT REJECT LIST, check FSP 1.35.00 Part 1, Subpart 2, SC Data Edit Prep.

The documentation of user Non-Pipeline programs (programs that receive data from Generalized Main Frame (GMF) 02) must include a File Identification starting with other than GMF in their parameters. All Non-Pipeline output will be in interchange format, odd parity, 6250 Bits per Inch (BPI) and have American National Standards Institute (ANSI) labels.

The first field, (four numerics), of each output record will always be a record length character count (not including the field itself). The receiving program File Description (FD) must have the following:

Multiple Format Codes will be placed on the same Non-Pipeline output file when:

There are three types of parameters:

Parameters must be entered on the UNISYS system and stored as a symbolic element in a shared program file. See IRM 3.24.159.6.1, Initial Transmittals, for transmittal instructions.

As many parameters and types of parameters as desired can be included in the shared program file.

Parameters cannot be split between line entries. Entry is limited to 80 characters.

Three consecutive blanks will cause the remainder of the parameter entry to be treated as a comment.

The character "@" can never be the first character of an entry.

Only requirement parameters need be entered.

If a parameter is not required to be present and no entry has been made for that parameter, in general, the default value generated will produce record formatting in GMF format.

One set (and one set only) of document parameters must be prepared for each Format Code.

For initial transmittal, at least one set of parameters for a section must be prepared for each document. As many as ninety six document specific sections can be present. Each section must be followed by as many sets of parameters for fields as are necessary for that section. Sets of parameters for sections and fields should be in sequential, ascending order.

For initial transmittal, at least one set of parameters for a field must be prepared for each section. The Edit System requires a set of field parameters for every field on input. As many as sixty fields per section can be output from the Edit System. Field parameters must follow the associated section parameters in their sequential order of occurrence.

Each format code requires a set of parameters. These parameters must be prepared by the analyst assigned to the project which processes the documents associated with that format code. A file of parameters for all format codes will be maintained by the Operation Support: Information Technology: Applications Development: Submission Processing: Paper Processing Branch (OS:IT:AD:SP:PPB), the responsible section.

Analysts must ensure that the OS:IT:AD:SP:PPB responsible section has received the parameters for each project.

Parameters must be received by OS:IT:AD:SP:PPB with enough lead time for implementation prior to System Acceptability Testing (SAT) and production transmittal dates.

Normally transmittals will be made no more than once a week, on Wednesday.

Analysts should provide a memorandum to the OS:IT:AD:SP:PPB responsible section listing the following:

The detailed name of the UNYSIS program file, including all qualifiers, read/write keys, etc., must also be included. Element name(s) to be used will be the Operator Class/Format Code(s) of the parameter set(s) contained in the element(s). See Exhibit 3.24.159-5, Example of Parameters Transmittal.

When updating any of the parameters for a particular document, it is necessary to resubmit the entire set of parameters (document, section, and field) as the complete set of parameters for the identified Operator Class/Format Code to be replaced on the on-line parameter file. Project analysts are responsible for reviewing the correctness of all updates as well as initial transmittals.

Project analysts are responsible for timely deletion of parameters for obsolete documents. Deletions are accomplished by parameter input as follows:
Operator Class Format Code DELETE>\.

The Operation Support: Information Technology: Applications Development: Submission Processing: Paper Processing Branch (OS:IT:AD:SP:PPB) section responsible for maintaining the SC Edits parameter file should be notified via memorandum when a set of parameters for a document is to be deleted, including the date of obsolescence. Section personnel maintaining the parameter file will affect the necessary deletion.

The DELETE capability should not be used when updating existing parameters. If updating parameters with the same Operator Class/Format Code, the update will overlay the old parameters and deleting is not necessary.