May 10, 1971 M29-1, Part II\
Change 1

CONTENTS\
CHAPTER 18. TRANSACTION HISTORY LISTS\
PARAGRAPH PAGE\
18.01 General 18-I\
18.02 Requesting Transaction History Information 18-1\
18.03 Transaction History Lists on Certain Special Computer Runs 18-3\
18.04 Guidelines for Requesting Transaction History Information 18-4\
18.05 Transaction History Information Received 18-5

18-i

September 30,1977 M29-1, Part II\
Change 14

CHAPTER 18. TRANSACTION HISTORY LISTS

18.01 GENERAL

**a. The insurance** master record maintained on tape contains current
information. To retain the history of all insurance transactions, with
the exception of \[those listed below, **a** daily\] computer-produced
listing \[is prepare d showing **all transactions** processed.\] They
are microfilmed daily for security purposes **and** the original of the
listing is stored in the Finance Division. The copies are filed in the
Administrative Division. \[Transactions that will not appear on daily
listings after October **1974,** are **as** follows:

\(1\) TT 008-which apply to non monetary pending transactions, except
the insertion of **a** nonfreeze waiver diary, when **an** application
for waiver is received, or the insertion of **a** review diary when the
premium is how paid code 5 (waiver) and there is no review diary on the
pending transaction tape.

NOTE: Transaction lines will be generated for TT 008, insertions of
dividend information, TT 026 and the IXX series, deduction
establishments and discontinuance\'s.

**(2) TT** 078-which applies to **a** change of an underwriting diary,
change or correction of **a** waiver diary, **and** Policy Service
nonmonetary diaries.

\(3\) TT 083-which applies to how paid 5 (waiver) cases.

**(4) TT** 087-which applies to how paid 5 (waiver) cases.

\(5\) TT 098-which applies to the deletion of **a** non monetary pending
transaction; and, the deletion of a waiver diary from the pending
transaction tape when an application for disability waiver is
disapproved or when **a** duplicate diary exists.

*(6)* **TT** 700-billing.

NOTE: Transaction lines will be generated for TT 098, deletion of
dividend information and the IXX series, deduction establishments and
discontinuance\'s.

**(7)** Transaction types 033, 040, 050, 080, 501, 603, 700, 800, 810,
**820** and **944.\]**

b\. The listings show **a** single line entry for each transaction
processed, showing identification data and transaction type. The sheets
are divided into 500 equal segments with 20 secondary digits to each
segment based on the terminal digit filing system. Each line of history
contains two processing day numbers. One is for the date of transaction
shown on the listing. The other processing day number is for the date of
the last previous transaction for this master record. lf the history
relates to premium, loan, lien, dividend credit or deposit, **a** third
processing day number will indicate the date the last transaction
**was** processed for premium, loan, lien, dividend credit or deposit.
Data are obtained from the listings by the use of thermofax prints which
are prepared by personnel of the History Retrieval Group.

c\. The listings are retained for 12 months, at which time they are
microfilmed again and discarded. History required prior to the 12-month
period must be obtained from the microfilm files.

18.02 REQUESTING TRANSACTION HISTORY INFORMATION

**a.** When transaction data are required, **a** current VA Form
**29-5886** \[b, Insurance\] Record Printout, will be used to request
the information.

b\. The RPO \[record printout\] must show the earliest PDN (processing
day number) and the last two digits of the year history is needed, the
transaction type(s) desired and **a** correspondence symbol. After
determining what history is needed, the clerk will enter positive
entries in the upper right corner of the RPO or use **a** stamp
impression -

18-1

M29-1, Part ll September 30, 1977

change 14

**c.** Effective with DN 317/62 (November 13, 1962), all transactions
processed against the loan, lien, premium and dividend credit and
deposit segments and recorded on the transaction history lists will
reflect the day number **of** the last **prior** transaction affecting
the segments. The year will also be shown in the loan and lien segments.

**d. On PDN 153/68 (June** 1, 1968), **all** NSLI, (National Service
Life Insurance) VSLI (Veterans Service Life **Insurance) and** USGLI
(United States Government Life Insurance) master records were combined
for the **same** insured under the governing file number.

**(1) Good judgment** must be exercised when requesting history on
**cases** when multiple life segments for one insured have been
**merged** under the same file number. The clerk must determine if
history **is** required on **all contracts or if** history transactions
for one particular account only will suffice to complete the required
action. The request **should be made accordingly.**

\(2\) When the history trail required will extend prior to PDN 153/68
(June I, 1968) on one or all of the insured\'s contracts, it will be
more expedient to split the request. The RPO\'s (record printouts) will
be used for this purpose **and** the notation thereon **specific** as to
the intent.

Example 1:

Insured has active V and active J contracts and history **is** required
on both, from the current PDN back to **000/67.**

FV30IOOOO FV 3010000\
3010000 J81000090

Action:

**On** the V RPO, request history from the current PDN to PDN I 53/68 on
both contracts and from PDN I 53/68 to **PDN 000/67 on** the V
**contract** only.

**On** the J RPO, request history from PDN 153/68 to PDN 000/67 on the J
policy only.

Example 2:

Same two contracts; history is required on the J contract only, from
current PDN to PDN 000/67.

Action:

Show the J number in red in the upper right margin of the V RPO and
request history from the current PDN to PDN l 53/68 on the J contract
**only.**

**Use** the J RPO to request history from PDN 153/68 to PDN 000/67 on
the J contract only.

Example 3:

**Same two contracts; history is** required on the V contract only from
current PDN to PDN 000/67.

Action:

**Use** the V RPO to request history **from** the current PDN to PDN
000/67 on the V contract only.

e\. **When** history **on a** particular transaction type is needed,
enter the letters **TT** followed by the code number **of that
transaction on** the RPO adjacent to the PDN requested. The approximate
PDN is shown to prevent the history **clerk from looking back any**
further than necessary.

f\. When history to February 3, 1969, is required on **a** certain
transaction type series, note the code number **on** the **RPO. For
example:**

\(l\) TT 200 series-034/69.

\(2\) TT 400 series-034/69.

\(3\) TT 500 series-034/69.

18-2

September 30, 1977 M29-1, Part ll\
change 14

The history will include all transaction types with the first digit
(high order) of the series requested. **For** example, if the request
**shows TT** 200 **series,** the history will include all 200 (200
through **219) items. The** same rule applies to a\" such transaction
type series requested.

**g.** The transaction type series **may** also be **shown** as 0-2,
0-3, 0A, **0-5, 0-6,** and 0-7. when there is a question of status **on
a** direct **pay** or payroll deduction account, request only the
transaction **series that** are involved. **For** example:

\(I\) TT200 series-034/69.

\(2\) **TT** 0-3 series-034/69.

\(3\) TT0-4 series-034/69.

**(4) TT 0-8** series-034/69.

The history prints will include **any** dividend credit automatically
applied under the dividend credit or premium options which would be
reflected in the 200 **series.** If there is **a loan,** lien, and/or
**TDIP** (total disability income **provision)** segment on **a**
policy, the request should include 300, 0-5, 0-6, and/or **0-7** series.
In addition to the **200 and/or 300** series, prints are also made on
a\" transaction types beginning and ending with the other numbers
**shown.** The dash between the numbers includes **any** number **0**
through **9.**

h\. When premium status on how paid **8** and **9** accounts is needed,
the lookup period **may** be reduced by lining through the last life
transaction day number and inserting in red the earlier **day** number,
if applicable, from the last premium processing **day** number. A
stamped impression **may** also be used **for** these entries. In
Philadelphia, this will not apply if the earlier day number is before DN
230, August **18, 1961. This** was the effective date that clerical
processing of VA Form **29-5893a,** Premium Input Card-ADP, caused
**the** system to enter that processing **day** number in the **LAST
PREMIUM** PROCESSING **DAY NUMBER** field.

\-
•Transactionhistoryprintsarenotfurnishedforaddresschanges,lifesegmentinsertsorchanges(transaction

**types ending** with **0),** and/or most diary inserts and deletes
(pending **transaction** type **978),** unless specifically requested.
If prints of these items are needed, **note** the RPO accordingly.

**j.** Whenever long and comprehensive history prints **are** used to
review an account, consideration should be given **to filing** certain
histories in the insurance folder for utilization in subsequent actions.
Filing of these prints will be restricted to situations when it **may
be** necessary to recapture this information as indicated by repetitive
inquiries in the insurance folder. Filing of extensive histories will be
based strictly on **good** judgment.

\(1\) History prints to be filed in the insurance folder will be stamped
Ready for File **and** dated.

\(2\) **In** future review of folders, histories over l year old from
date of filing will be removed and reported for **disposal.**

\(3\) Transaction prints on routine cases will continue to be disposed
of in accordance with Records **Control** Schedule VB-I, part **1.**

18.03 TRANSACTION HISTORY LISTS ON CERTAIN SPECIAL COMPUTER RUNS

**a.** Special Computer Run **on** September 24, *1966* **(PDN** *267)*

\(l\) As **a** result of this run, to reduce the premium rate on **NSLI
TDIP Age 60 (\$5** and **\$10)** permanent plan riders, **a**
transaction history list of a\" the reduction and refund actions was
established. This list contains **a** line entry for each policy **on**
which the **TDIP** premium was reduced and **a** line entry for each
refund as a result of the reduction calculation. These line entries are
the same as those for the regular **027** and **609** transaction types.
If required, VA **Form** 29-5935 **or 29-5935b, Transaction Print**
Templates, may be use d **to aid** in reading the data.

18-3

M29-1, Part 11 September 30,1977

Change **14**

\(2\) Clarification concerning the calculation dates, shown as a month
number in the Next Premium Due field, are as follows:

**(a) Reductions of** the **TDIP** premiums for a\" allotment (how paid
*6)* and deduction **from** VA benefits (how **paid 3) accounts** were
made **as** of the October 1966 premium **due date.**

\(b\) **Reduction of** the **TDIP** premiums for a\" direct **pay (how
paid 9) and** employee **payroll** deduction **(how paid 8) accounts**
were made effective with the October 1966 premium **due date** if the
month number shown is **574 (October** *1966)* **or** higher. If the
month number **shown is** higher than **574,** the calculation included
**any premiums paid beyond** that **date** and **the credit is**
included in the refund. If the month number is lower than 574, the
calculation was **made** through the month that premiums were paid.

**(c) Reduction of** the **TDIP** premiums for the total disability
waiver (how paid 5) **accounts was made as** of the **October** *1966*
premium **due date.**

**(d) Reduction of** the **TDIP** premiums for the paid-in-full limited
pay life policies (how paid 0) **was made** effective **as of** the
October *1966* **date. The** month number shown on the transaction
history list represents the **premium** month in which **the policy
became paid-up.**

b\. Special Computer Run on September **27, 1970 (PDN 270)**

**(1) As a result of** this run, to **reduce** the premium rate on
**NSLI TDIP** Age 60 **and 65 (\$5** and \$10) riders on certain term
policies **and** premiums on J policies, transaction history lists of
a\" the transactions **processed and pending** diaries **created** were
established. **The reduced** premiums were effective with the October
**1970** premium **due date.**

\(2\) A **transaction** history list of all transactions, when the
reduced **NSLI** TDIP term or J premium **was entered** into the master
**record,** was established. **The** reduced premium **was** entered if
the September **1970** premium was **paid and** there was no life or
policy freeze. However, on deduction **from VA** benefits (how paid 3)
**and allotment (how paid** *6)* **accounts the** reduced premium
**was** entered in the master record even though there was **a** life or
**policy freeze.**

\(3\) **A** transaction history list of pending diary **transactions**
when the **reduced** premium **could** not be entered into the master
**record because the** September **1970** premium **was** not paid or
**because there was a life** or policy **freeze,** was established. This
transaction shows the **reduced TDIP monthly rate** per \$1 ,000 or the
reduced J premium **(including administrative cost) for the mode of
record.**

\[c. Special Computer Run on September 30, 1976 PDN 27D

\(1\) **Transaction** lists of all of **the** transactions processed
**and pending** diaries **created, as a** result of this run, **were
established to reduce the** premiums on J and JR policies. **The
reduced** premiums were effective with the **October 1976** premium
**due date.**

\(2\) **A** transaction history **list** was established when all
pending transactions were **processed** through **a subroutine known as
2 POST PENDING; transactions** to **reduce the** premium (TT 082),
**transactions** to insert **refund diaries (TT 008-609) and
transactions** increasing the monthly loan repayment amounts (TT 025).

\(3\) **The reduced** premiums were **entered** into the master records
for a\" of the J **and** JR **policies except** for the **following
cases:**

\(a\) How paid 2 and 4,

\(b\) Policies maturing during October 1976, and

\(c\) Pending death claims

18A

September 30, 1977 M29-1, Part II\
Change 14

18.04 GUIDELINES FOR REQUESTING TRANSACTION HISTORY INFORMATION

**a. The** following guidelines apply when requesting history lookups:

\(1\) Reason code 012 on the RPO, indicating that a pending posting item
was \[deleted and therefore\] rejected because it did not match the
pending transaction.

**(a)** Arrange the reject cards representing the pending transactions
which are no longer on tape, in chronological order.

\(b\) Request transaction history lookup to the latest unit number
involved.

**Example:** Rejected pending transactions no longer on tape: Unit
#1300, PMD lO- 1-69, \$13.20 Unit #1328, PMD 11-16-69, \$13.20 Unit \#
1039, PMD 2. 1-70, \$13.20 Show PDN 039/70 on the RPO.

\(2\) Reason code **277** on the RPO indicating the postmark date of the
payments is before the date of the last premium transaction in the
master record. Request lookup to day number and year indicated by the
last premium PDN. If status code block indicates a U, this item was
inserted by Miscellaneous Accounts and Service Unit. History lookup is
not required.

**(3) Reason** code 874 on the RPO indicating renewal was processed, but
the deduction has not been received or the deduction was made pending by
the system because it could not be posted automatically.

\_\_\_\_ (a) lf the allotment information is not in the pending
transaction area, transaction history lookup is needed

to find out when the system released either VA Form 29-\[483a\],
Certificate of Renewal, (Philadelphia), or VA **Form 29-5926,** Request
for DFB Action, (Philadelphia). This information is shown in the
transaction history list

under transaction type 810.

\(b\) Enter in the reason code block, transaction type 810 and the year
involved.

Example: TT 810/69

**(4)** Reason code **957** on the RPO, indicating a TDIP transaction
was processed, but clerical action is necessary. The system uses this
reason code when the edit regarding a current transaction discloses one
of the following erroneous conditions:

\(a\) Effective date of TDIP is earlier than effective date of life
contract.

\(b\) Next month due and/or how paid code on TDIP is different from that
on life contract.

\(c\) TDIP fund code or action type and date are wrong.

18-4a

May 10,1971 M29-1, Part II\
Change 1

1\. Refer to miscellaneous input and terminal digit (input) listing and
reject listings for the day number on which the RPO was generated, to
find what caused the erroneous condition.

**[2]{.underline}.** lf neither of the listings show how the differences
occurred, request transaction history lookup to the day number shown in
the block entitled Last Prem. Proc. Day No.

\(5\) Dividend Information Needed

\(a\) Prepare VA Form 29-5720, Request for Paid Dividend Information,
for the years involved, and refer the form to the unit maintaining the
paid dividend files.

\(b\) lf the VA Form 29-5720 is returned No Record, request transaction
history lookup by entering the transaction type involved and the
earliest day number and year in the reason code block of the RPO.

For example:

TT 606-Enter PDN **296/69** on the RPO.

\(c\) The VA Form 29-5720 may indicate an offset of indebtedness.

l - lf the legend **CTL** is shown in the Indebtedness block, obtain a
**TT** *606* transaction line print to determine the-gross dividend and
any offset.

**2.** lf the amount of dividend is not compatible with the amount
earned, obtain a **TT** *606* transaction line print to determine if an
offset was made.

\(d\) Since the face amount of insurance does not appear on the **TL**
line which is generated when the dividend is paid, the dividend rate
that is to appear in the TL line will be doubled for plan **9.**

W NOTE: With an assumed dividend rate of \$0.50, that figure will appear
on the record printout in the Rate Per Thousand block. However, the rate
will appear as \$1 in the miscellaneous listing, transaction line.

*(6)* Itemized List of Premium Payments Needed to October **27, 1969.**
Enter transaction type and earliest day number in reason code block of
the RPO.

Example:

TT 200 series-300/69.

\(7\) UNCOL in lower right corner of the reason code block of the RPO
indicates an uncollectible item was not processed by the system.
Clerical action is necessary to prepare input documents.

NOTE: If the uncollectible item cannot be identified and processed from
information shown on the RPO, use the RPO to request transaction history
through the original processing day number (same as unit number) on the
uncollectible item.

18.05 TRANSACTION HISTORY INFORMATION RECEIVED

a\. When thermofax are prepared from the transaction history lists for
the information requested on VA [Forrn 29 5886a, InsuranceRecord
Print]{.underline} Out, or other requesting document, the prints are
returned stapled to the requesting RPO or document.

b\. VA Form **29-5935,** Transaction Print Template, is used to read
thermofax prints of transaction history lists prepared prior to PDN
153168, June l, 1968.

c\. VA Form **29-5935a,** Transaction Print Template, is used to read
prints of transaction i\~istory\~rep\~red prior to PDN 153/68, June
1,1968, reproduced from the microfilm.

18-5

M29-1, Partii May 10, 1971\
Change 1\
w\~6

d\. VA Form 29-5935b, Transaction Print Template, is used to read
thermofax prints of transaction history hsts\~i\~a\~\~d\~n\~nd-aft\~rPDN
[j \~3I6\~, June i]{.underline} ;4\~6\~:

e\. VA Form 29-5935c, Transaction Print Template, is used to read prints
of transaction history prepared on and after PDN 153/68, June I, 1968,
reproduced from the microfilm.

18-6