January 10, 1972 M29-1, Part II\
Change 5

CONTENTS

CHAPTER 17. REJECTS

PARAGRAPH PAGE\
17.01 General 17-I

17.02 Re submission of Certain Rejected\
Input Documents 17-I

17.03 Reinserting Rejected input Documents 17-2

17.04 Routing Processed Rejected input

Documents 17-2

17.05 Address Change Rejects 17-3\
17.06 Correction of a Diary Message 17-3

17-j

January 10, 1972 M29-1, Part ll\
Change 5

CHAPTER 17. REJECTS

17.01 GENERAL

a\. **All** input documents introduced into the computer system are
subject to certain preedits during the daily processing runs.

b\. Run 130 is the preedit program for all file maintenance
transactions. This run checks the input for validity, format, related
fields, certain calculations and sequence if the input is coded with
transaction types used for inserting a new master record on tape. When
the edit routine of a run 130 detects an error condition in connection
with the input data, the name code is replaced by a three-digit numeric
code or a special three-character code. This code denotes the type of
discrepancy found during the edit. The field which does not meet the
edit requirements will be identified by an asterisk in the last position
of the field containing the invalid data.

c\. MTC (Miscellaneous Transaction Control) accounts are edited for
out-of-balance situations. Debits and credits to the MTC account for
each file number are checked. When an out-of-balance condition is found,
an MTC reject card is created. Run 130 will continue to edit all inputs
and each transaction meeting the edits will be coded 888 in the name
code field. Those transactions not meeting edit requirements will be
coded individually with other reject codes which will be used to
identify each type of edit error.

d\. Rejected transactions from previous day numbers which have been
corrected and resubmitted are coded to bypass the MTC edit. An X is
gang-punched in the file prefix field to identify these transactions.
This insures proper control of documents posted to the general ledger
accounts.

e\. Rejects appearing on the reject list with an alphabetical character
in the left column of the list indicates that the input has rejected
more than one time.

f\. The daily processing run 140 edits the information furnished on the
input tape with the logic of the specific program function and data in
the master record before processing is accomplished. All transactions
meeting the logic of the program are processed, and transactions
continue to process until an error condition is detected by the program
or has been coded as a reject in run 130.

g\. Reject cards, reproduced input documents, **VA** Form 29-5886a,
Record Print Out, (RPO) or **VA** Form 29-5886b, Insurance Record
Printout, and a reject listing will be received for transactions that do
not meet edit requirements.

h\. Rejects identified by a dash (-) between the file number and
transaction type on the reject card; e.g., 1000 00 00-8I, with no reason
code shown on the reject card indicates there is no master record on
tape under that file number.

i\. Second-day releases will be identified by the letter **R** and
third-day by the letter X printed between the file prefix and the file
number on the daily reject list.

j\. The descriptions of reject reason codes are outlined in MP-6, part
II, supplement No. 1.4, chapter l.

17.02 RE SUBMISSION OF CERTAIN REJECTED INPUT DOCUMENTS

a\. Reject cards, reproduced input documents and RPO\'s must be reviewed
to determine the cause of the reject before re submission. **All** other
entries on the input document, corresponding to the reject card with the
error condition, must be examined for correctness and/or completeness.

17-1

M29-1 , Part ii January 10, 1972

Change S

b\. When the error condition is in connection with one of the following
input documents, a new input document must be prepared:

\(I\) **VA** Form 29-322 Disbursement Address or Trailer Input

\(2\) **VA** Form 29A97 Request For Transfer Insurance Records

\(3\) **VA** Form 29-5899 Request For Record Print Out

\(4\) **VA** Form 29-5899a Reinstatement Input Card

\(5\) **VA** Form 29-5934 Change of Address For Insurance Purposes

17.03 REINSERTING REJECTED INPUT DOCUMENTS

a\. Corrections may be made on the reproduced input documents provided
the transaction code type is valid for the action to be taken and is on
the proper form for the segment being inserted or changed.

b\. If the rejected input card can be reinserted without a change, a
large R in red must be placed on the right side of the face of the card
to indicate that no correction is necessary before re submission, except
for punching the name code. No other entries are required.

c\. If the rejected input card requires a change before re submission,
it must be corrected clerically as follows:

\(l\) The corrected information must be entered with red ink in the
blocks on the reproduced input card immediately below the blocks
containing the incorrect data.

\(2\) Corrected information must be block printed. The entire field
involved must always be completed even though only one character is
wrong.

NOTE: A field is a group of common data, such as, an amount of money, a
fund code, a file prefix, a file number, a control account number, a
name code, etc. Normally, fields on input cards are divided by solid
lines, but in some instances, broken lines are used, particularly when a
field is used for more than one purpose. In other words, a field is any
block or group of blocks on any input card that has a specific title.

d\. If data are to be deleted and the field is to be left blank, an
encircled lowercase(b) must be printed in the first block of the field
and a line drawn from the-through the remaining blocks of the field.

e\. **A** new input document must be prepared if the reproduced card
cannot be used. **A** large C in red must be placed on the right side of
the face of the new input card to bypass certain edits to indicate that
the input is part of a previously rejected case.

f\. Any additional or replacement input documents which may be required
to complete the case must be clerically prepared. The batch number from
the related input cards must be shown, unless a B or T batch number is
to be assigned in lieu of the number shown.

17.04 ROUTING PROCESSED REJECTED INPUT DOCUMENTS

a\. Corrected rejects will be released in one group to the Input/Output
activity, except when the batch number must be changed to a B or T
number.

b\. When input cards, other than **XC-** and matured endowment cases,
are rejected because a B, K or T batch number was not assigned to the
input documents with one or more control account numbers 01,, 05, 09, 20
and 52, the corrections must be resubmitted through the Accounting
Section, Finance and Data Processing Division, for assignment of a B or
K batch number or to Voucher Audit for a T batch number.

17-2

January 10,1972 M29-1, Part ii\
Change 5

c\. Label the XC- and matured endowment corrections, which can be
identified by the accounting transactions involving control accounts 13
and 51 and assign an XB and/or T batch number on the corrected input and
related cards, where necessary, for delivery to the Input/Output
activity.

d\. When deletion of a pending transaction involving a money item was
rejected for RPO, reason code 012, No Matching Pending Transaction on
Tape, check for an erroneously updated insurance account, as well as an
out-of-balance MTC transaction. A dual correction of this type may be
needed where duplicate actions were taken to post a pending transaction
and the second transaction type 098 was rejected or the system accepted
an 083 transaction, but rejected the related 098 transaction and the
pending transaction was automatically posted.

e\. Input documents will be used wherever possible to correct an MTC
out-of-balance. For example, if the Premium-Offsets account (32) is
overstated because of duplicate actions to delete and post a pending
transaction, the corrective action will consist of **VA** Form 29-5893a,
Premium input Card, with transaction type 083, showing a debit to the
Premium-Offsets account (32) and credit to Miscellaneous Transaction
Control account (39).

17.05 ADDRESS CHANGE REJECTS

a\. Run 140 address change rejects which did not match on name code must
be returned to the Input/Output activity for processing. These rejects
will be further processed as follows:

\(I\) Policy Service Technicians will associate the record printouts
with the reject cards and process in the regular manner.

\(2\) In requesting source documents for address change rejects, the
Policy Service Technician will enter in large red letters in the upper
right corner of **VA** Form 29-5891a, Address or Trailer Input, SD
(Source Document Requested). The **VA** Form 29-5891a will be released
to the General Clerk.

\(3\) The General Clerk will accumulate **VA** Forms 29-5891a and
release daily to the Data Control Section by **VA** Form 3230, and the
Remarks block noted Source Document Requested.

NOTE: Do not staple reference slip to VA Forms 29-5891a. These will be
machine-sorted in the Data Control Section if volume permits.

\(4\) Data Control Section will assemble the **VA** Forms 29-5891a with
the source documents attached and send to the Policy Service sections
properly identified by **VA** Form 3230.

\(5\) Any cases remaining uncorrected will be forwarded to Index with
the source document.

b\. The following types of address change rejects must be processed by
the originating element:

\(l\) **All** address change rejects where there is other input rejected
for the same file number.

\(2\) Run 140 address change rejects which match with a record printout
(other than reason code 988).

\(3\) Run 140 address change rejects (identified by a dash (-) on the
reject card between the file number and transaction type; e.g., 1000 00
00-081) with no other type rejects, or accompanying record printout,
must be processed by the appropriate insurance activity or Record group.

17.06 CORRECTION OF A DIARY MESSAGE

When deleting a diary, the message must be written exactly as it appears
on the record printout. if a reject is received because the input card
did not match the transaction on tape, it will be necessary to prepare a
corrected input document.

17-3