**CONTENTS**

**CHAPTER 5. NOTICE OF EXCEPTION PROCESSING**

PARAGRAPH PAGE

5.01 Chapter 32 NOE Processing - General 5-1

5.02 Chapter 32 NOE Messages, Legends, and Explanations 5-2

**CHAPTER 5. NOTICE OF EXCEPTION PROCESSING**

**5.01 CHAPTER 32 NOE PROCESSING - GENERAL**

a\. After chapter 32 awards or other transactions are processed, they
are sent to the TCS (Target Central System) for further editing and
storage. TCS generates chapter 32 reject, action, and informational NOE
(Notice of Exception) messages upon completion of benefit update
processing. These messages are transmitted to the appropriate BDNC
(Benefit Delivery Network Center). After further processing, the
messages are available for regional office retrieval. Regional office
personnel should obtain NOE messages on a daily basis. See part II,
chapter 8, for procedures for using the NOES (Notice of Exception
Subsystem) command to retrieve messages.

b\. Each BDNC only retains NOE messages for 30 processing days. These
centers also compare every message against the PIF (Pending Issue File)
to determine whether affected pending issues should be cleared or
updated (to reflect a reject).

\(1\) If a pending issue exists and it is \"pending acceptance\" and
[no]{.underline} message is posted for that master record when Target
completes update processing and produces messages, Target will clear the
pending issue.

\(2\) If a pending issue exists and it is \"pending acceptance\" and a
message [is]{.underline} posted for that master record, Target will
determine whether to clear the pending issue based on the message
number.

\(a\) If the message is in the 8000-series range, Target clears the
pending issue as these messages do not indicate a rejected transaction.

\(b\) If the message is not in the 8000-series range and was generated
by award processing, Target updates but does not clear the pending
issue. The regional office must either cancel the pending issue or clear
the pending issue through generation of a corrected transaction.

*NOTE 1: Some of the messages in this chapter cannot be issued as the
result of input from a Target terminal; however, these messages can be
issued as a result of DOD (Department of Defense) changes to a
claimant\'s Contributions Account.*

*NOTE 2: Corrections (02V transactions) to some fields in master records
can be made directly on a Target screen. See part II, paragraph 8.13,
for allowable entries.*

**5.02 CHAPTER 32 NOE MESSAGES, LEGENDS, AND EXPLANATIONS**

Only the chapter 32 messages shown in this chapter should be generated
at the regional offices. If any other chapter 32 message is generated at
a regional office, contact VA Central Office by sending an inquiry via
E-Mail to MAIL VBA CH 32 PROBLEM.

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **1005**      REJECT - NO UNASSOCIATED RECORD FOUND

                

                [Explanation]{.underline}: This message is generated by
                fiscal processing.

                

                [Action]{.underline}: Route this message to the Finance
                activity.

                

  **1300**      (Various Legends)

  **through**   

  **1399**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                

  **1400**      ACTION - COD NOT RECEIVED/CONFIRM ENROLLMENT

                

                [Explanation]{.underline}: Target issues this one-time
                message when 2 months have elapsed since the beginning of the
                advance pay enrollment in an IHL (Institution of Higher
                Learning) case and the enrollment has not yet been confirmed
                by a COD (Certificate of Delivery) transaction.

                

                [Action]{.underline}: Send the message to VSD (Veterans
                Service Division) to obtain confirmation of school
                attendance. After obtaining school attendance information,
                VSD will annotate the message appropriately and return it as
                follows:

                

                If there is no change in school attendance, VSD will return
                the message to the Finance activity to prepare a
                certification transaction to lift the COD bar.

                

                If there is a change in school attendance, VSD will return
                the message to the Adjudication Division for appropriate
                award or stop pay action. Any award prepared will also lift
                the COD bar.

                

  **1401**      ACTION - COD NOT RECEIVED/CONFIRM ENROLLMENT - 2ND NOTICE

                

                *NOTE: Target does not generate 1401 messages if the field
                station has previously confirmed school attendance and lifted
                the COD control.*

                

                [Explanation]{.underline}: Target issues this one-time
                message when 3 months have elapsed since the beginning of the
                advance pay enrollment in an IHL case and the enrollment has
                not yet been confirmed by a COD transaction.

                

                [Action]{.underline}: Follow the procedures specified in the
                action paragraph shown for message 1400.
  ------------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **1402**   ACTION - COD NOT RECEIVED/CONFIRM ENROLLMENT - PRIORITY

             

             *NOTE: Target does not generate 1402 messages if the field
             station has previously confirmed school attendance and lifted
             the COD control.*

             

             [Explanation]{.underline}: Target issues this recurring
             message when 4 or more months have elapsed since the
             beginning of the advance pay enrollment in an IHL case and
             the enrollment has not yet been confirmed by a COD
             transaction.

             

             [Action]{.underline}: Follow the procedures specified in the
             action paragraph shown for message 1400.

             

  **1410**   ACTION - NEED VERIF OF PURSUIT FROM MM-DD-YY, DLC

             

             [Explanation]{.underline}: Target issues this one-time
             message approximately 3 months after an IHL verification of
             pursuit form has been released to the school and a
             certification transaction has not yet been submitted.

             

             [Action]{.underline}: Stations may take action as specified
             in message 1412. However, stations may also defer action
             until message 1412 is received.

             

  **1411**   ACTION - NEED VERIF OF PURSUIT FROM MM-DD-YY, DLC/2ND NOTICE

             

             *NOTE: Target does not generate this message if the field
             station has previously verified attendance and entered a
             certification transaction.*

             

             [Explanation]{.underline}: Target issues this one time
             message when a certification transaction has not been
             received by 4 months after the verification of pursuit form
             is released to the school.

             

             [Action]{.underline}: Stations may take action as specified
             in message 1412. However, stations may also defer action
             until message 1412 is received.

             

  **1412**   ACTION - NEED VERIF OF PURSUIT FROM MM-DD-YY, DLC/PRIORITY

             

             *NOTE: Target does not generate this message if the field
             station has previously verified attendance and entered a
             certification transaction.*

             

             [Explanation]{.underline}: Target issues this recurring
             message when a certification transaction has not been
             received by 5 or more months after the verification of
             pursuit form is released to the school.

             

             [Action]{.underline}: Upon receipt, route the message to VSD
             for verification of school attendance. After obtaining school
             attendance information, VSD will annotate the message and
             return it as follows:

             

             If there is no change in school attendance, VSD will return
             the message to the Finance activity. The Finance activity
             will prepare a certification transaction.

             

             If there is a change in school attendance, VSD will return
             the message to the Adjudication Division for processing an
             amended award or a \"quit\" certification as appropriate. Any
             award prepared should include a certification transaction.
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **1417**   ACTION - LUMP SUM 51B A/R ESTABLISHED - REVIEW ACCT,
             ESTABLISH CONTROL

             

             [Explanation]{.underline}: This message is generated by
             fiscal processing.

             

             [Action]{.underline}: Route the message to the Finance
             activity.

             

  **1500**   ACTION - MASS ENDING DATE NOT CHANGED - COD PENDING

             

             [Explanation]{.underline}: A mass ending date change was
             processed for a specific school. For the file number shown on
             the message, the revised ending date was not changed as an
             advance payment was issued and the COD control had not yet
             been lifted.

             

             [Action]{.underline}: Upon receipt, route the message to VSD
             for verification of school attendance. After obtaining school
             attendance information, VSD will annotate the message and
             return it to the Adjudication Division for an amended award
             to include the revised ending date. If necessary, contact the
             ELR (Education Liaison Representative) for the revised ending
             date. Any award prepared should lift the COD bar.

             

  **1502**   REJECT - CANNOT EXTEND ENDING DATE IN THIS RECORD

             

             [Explanation]{.underline}: A mass ending date change was
             processed for a specific school. For the file number shown on
             the message, the ending date was not extended because the
             award ending reason indicates that an extension might not be
             appropriate. The transaction was rejected.

             

             [Action]{.underline}: Contact the ELR and obtain the
             school\'s new ending date. Compare this extended ending date
             with the ending date shown in Target. Review the reason
             associated with the claimant\'s current ending date. If
             appropriate, process an amended award with the extended
             ending date.

             

  **2001**   REJECT - TRANS VALUE NOT EQUAL TO M/R VALUE

             

             [Explanation]{.underline}: A correction transaction was
             submitted but rejected. When a correction is submitted, the
             transaction includes both the existing value of the field (to
             be changed) and the new (corrected) value. The transaction\'s
             existing value and the value stored in Target should be the
             same. If the existing value is not the same, Target may have
             processed an intervening action and a correction may not be
             appropriate.

             

             [Action]{.underline}: Review the claimant\'s folder and the
             correction. Determine whether the correction remains
             appropriate. If the correction is still appropriate, submit a
             new transaction.
  ---------- -------------------------------------------------------------

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **2002**      REJECT - ENTRIES INCONSISTENT WITH AWARD DATA

                

                [Explanation]{.underline}: A master record correction
                attempted to make a change to the service information. Based
                on the change, however, the veteran\'s delimiting date would
                be earlier than the latest award ending date. The transaction
                was rejected.

                

                [Action]{.underline}: Review the veteran\'s folder and the
                attempted correction. Determine whether the correction
                contained accurate service dates. If the correction contained
                accurate service dates, process an amended award or stop pay
                action, as appropriate. If the correction contained erroneous
                service information, submit an amended award or a correction
                with the correct dates, whichever is appropriate.

                

  **2003**      REJECT - SCHOOL CODE INCONSISTENT WITH TYPE TRAINING

                

                [Explanation]{.underline}: A correction attempted to change
                the facility code. The new facility code is incompatible with
                other information in the master record. The transaction was
                rejected.

                

                [Action]{.underline}: Review the claims folder and the
                submitted correction. If necessary, contact the ELR for the
                current facility code as he or she may have submitted a
                revised facility code for the claimant\'s school or training
                establishment. Determine whether any adjustment in the
                facility code is needed. If an adjustment is needed, submit
                the correct facility code.

                

  **2004**      (Various Legends)

  **through**   

  **2012**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                

  **2016**      REJECT - OVER 16 TRANSACTION AWARD LINES

                

                [Explanation]{.underline}: An award processed which either
                contained more than 16 award lines, or created more than 16
                \"future\" lines. Target processing cannot handle more than
                16 lines in a single action. The award was rejected.

                

                [Action]{.underline}: Review the claims folder and the award.
                Resubmit the award in increments which will not cause
                excessive lines. This may require sequential submission of
                two or more awards. Also see part IV, paragraph 13.19.

                

  **2020**      REJECT - NO ADDRESS IN TRANSACTION

                

                [Explanation]{.underline}: This message is generated by
                fiscal processing.

                

                [Action]{.underline}: Route the message to the Finance
                activity.

                
  ------------- -------------------------------------------------------------

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **2022**      REJECT - BANK ALLOTMENTS OUT OF BALANCE - CORRECTION REQUIRED

                

                [Explanation]{.underline}: The bank record of the claimant is
                \"Out-of-Balance.\" The sum of the individual allotments does
                not match the amount stored in the original amount fields.
                The transaction was rejected.

                

                [Action]{.underline}: Review the claimant\'s folder and
                master record. If the M27 CH 32/903 Participant Contribution
                History screen shows \"Out-of-Balance\", the chapter 32
                coordinator should contact the Hines PPU (Payment Processing
                Unit) to make the necessary corrections to the bank record.
                After PPU notifies the chapter 32 coordinator that the bank
                record is in balance, resubmit the rejected transaction. If
                the M27 screen does not initially show \"Out-of-Balance\",
                bank adjustment is not necessary; however, resubmit the
                rejected transaction.

                

  **2023**      REJECT - DOD CONTRIBUTIONS OUT OF BALANCE - CORRECTION
                REQUIRED

                

                [Explanation]{.underline}: The bank record of the claimant is
                \"Out-of-Balance\" concerning DOD contributions. The
                transaction was rejected.

                

                [Action]{.underline}: Review the claimant\'s folder and
                master record. If the M28 CH 32/903 DOD Contribution and
                Miscellaneous Data screen shows \"Out-of-Balance\", the
                chapter 32 coordinator should contact the Hines PPU to make
                the necessary corrections to the bank record. After PPU
                notifies the chapter 32 coordinator that the bank record is
                in balance, resubmit the rejected transaction. If the M28
                screen does not initially show \"Out-of-Balance\", bank
                adjustment is not necessary; however, resubmit the rejected
                transaction.

                

  **2024**      (Various Legends)

  **through**   

  **2078**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                

  **2079**      REJECT - INVALID TRANSACTION CODE

                

                [Explanation]{.underline}: A transaction was submitted with
                an invalid transaction code. The transaction was rejected.

                

                [Action]{.underline}: See part II, chapter 2, for transaction
                codes. Review the claimant\'s folder and the transaction
                submitted. If the transaction was submitted incorrectly,
                submit a corrected transaction.

                

  **2080**      (Various Legends)

  **through**   

  **2099**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                
  ------------- -------------------------------------------------------------

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **2100**      REJECT - ELIGIBILITY NOT INDICATED BY ENTRIES

                

                [Explanation]{.underline}: A master record correction
                attempted to change the service information. The correction
                would have had the effect of canceling the veteran\'s
                eligibility for chapter 32 benefits. The transaction was
                rejected.

                

                [Action]{.underline}: Review the claim. If the service
                information was submitted incorrectly (on the correction),
                submit an adjusted action. If the veteran does not have basic
                eligibility because of inadequate service, an amended award
                may be required. If the veteran does not have basic
                eligibility but no award adjustment is needed, set the folder
                pull indicator to \"Y\" and properly annotate the claims
                folder.

                

  **2111**      REJECT - ADJUSTMENT DATE NOT FOUND IN AWARD LINES

                

                [Explanation]{.underline}: This message is generated by
                fiscal processing.

                

                [Action]{.underline}: Route this message to the Finance
                activity.

                

  **2120**      REJECT - ADVANCE PAYMENT CANNOT BE PAID - OVER 30 DAYS OLD

                

                [Explanation]{.underline}: An advance pay was submitted. At
                the time that Target attempted to generate the advance
                payment, the effective date of the award was 30 or more days
                in the past. The transaction was rejected.

                

                [Action]{.underline}: Send the message to VSD to obtain
                confirmation of school attendance. After obtaining school
                attendance information, VSD will annotate the message
                appropriately and return it to the Adjudication Division for
                submitting a confirmed award.

                

  **2900**      ACTION - NO AWARD SEGMENT IN M/R

                

                [Explanation]{.underline}: This message is generated by
                fiscal processing.

                

                [Action]{.underline}: Route the message to the Finance
                activity.

                

  **2901**      ACTION - AWARD EXCEEDS 16 LINES - NOTIFY PAYEE OF LINES
                BEYOND MM/DD/YY

                

                [Explanation]{.underline}: An award was submitted which
                affected more than 16 award lines. Target cannot print a
                letter with more than 16 lines, so only 16 award lines were
                included in the Target generated letter.

                

                [Action]{.underline}: Send the claimant a dictated letter
                explaining the situation. Include both the old and new award
                lines.

                

  **2902**      (Various Legends)

  **through**   

  **2906**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                
  ------------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **2950**   ACTION - REVIEW AWARDS - CONTRIBUTIONS ADJ FOR MMM-YY

             

             *NOTE: MMM = a three-letter abbreviation for a month; Y = the
             year.*

             

             [Explanation]{.underline}: Bank file processing has caused a
             change to the master record. One or more allotments have been
             changed. The month and year shown in the NOE legend reflect
             the earliest allotment affected. The master record contained
             award lines which extended beyond adjusted allotment
             month(s), so the master record\'s monthly rates may require
             adjustment. Target could not automatically adjust the
             rate(s).

             

             [Action]{.underline}: Carefully review the claimant\'s folder
             and master record. Award action may be necessary to adjust
             the monthly pay rates in existing periods. (See par. 4.18g.)
             Identify the changes to the Contributions Account and compare
             the affected allotment months to the claimant\'s award
             periods. If the allotment adjustment changes the monthly rate
             payable in any award line, process an amended award,
             repeating the affected award line and all subsequent award
             lines (with the same award information). Target will then
             recalculate the monthly rates. The rates are likely to
             require adjustment in the following instances:

             

             The allotment adjustment increased the claimant\'s original
             number of monthly contributions (from less than 36 to more
             than 36); or

             

             The allotment adjustment decreased the claimant\'s original
             number of monthly contributions (from more than 36 to less
             than 36); or

             

             The allotment adjustment causes the Contributions Account to
             include allotments of differing amounts (e.g., before
             adjustment all allotments were \$50 and after adjustment
             there are three new allotments of \$65); or

             

             The Contributions Account previously contained allotments of
             differing amounts, and the adjustment changed the total
             number of allotments.

             

             If the allotment adjustment does not change the existing
             monthly rate of any award line, no action is necessary.

             

             See footnote 1.
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **2951**   ACTION - AWARD SUSPENDED FOR CONTRIBUTIONS ADJUSTMENT

             

             [Explanation]{.underline}: The claimant had an active award,
             and bank file processing changed the master record. Either
             the number of months or the amount of money available has
             been reduced. As a result of the adjustment, the claimant\'s
             entitlement may be exhausted before the end of the award.
             Target suspended the award to prevent erroneous payments.

             

             *NOTE: This message can be issued when due process must be
             followed as provided by Public Law 100-203, The Computer
             Matching and Privacy Protection Act of 1988. This legislation
             provides that VA may not take adverse action to a benefit
             recipient based on information received by an agency from an
             automated system of another agency until VA notifies the
             recipient of the pending action and the information received
             from the automated system is verified independently. (See
             pt. IV, par. 13.14.)*

             

             [Action]{.underline}: Process an amended award to remove the
             suspense [only after]{.underline} carefully reviewing the
             claimant\'s record to determine the proper enrollment period
             (or periods) to be included in the amended award. If the
             allotment months which have been adjusted fall within an
             award period, resubmit that award period and all subsequent
             award periods. If the allotment months which have been
             adjusted do not fall in an award period, all later award
             periods should be resubmitted. If school changes or course
             objective changes are involved, multiple award actions will
             be required. The processing of the amended award action will
             allow Target to recalculate the monthly rates and adjust the
             ending date so that the claimant does not use excessive
             entitlement.

             

             See footnote 1.

             

  **2952**   ACTION - ALLOTMENT RECD - AMENDED AWD REQUIRED

             

             [Explanation]{.underline}: Bank file processing has added one
             or more allotments to the claimant\'s Contributions Account.
             Before the bank file processing, the claimant\'s last award
             had been terminated due to exhausted entitlement (ending
             reason 65). Target changed the latest ending reason in the
             master record from 65 to 61 to indicate that entitlement will
             no longer be exhausted on that date.

             

             *NOTE: Although 38 CFR 5.064(a) requires that the individual
             only contribute for 12 continuous months, a serviceperson may
             resume making contributions after suspending such
             contributions.*

             

             [Action]{.underline}: Associate the message with the
             claimant\'s folder. Review the claimant\'s latest enrollment
             certification. If the claimant\'s enrollment has been
             certified beyond the current award ending date, process an
             amended award to extend the ending date. If the ending date
             on the latest enrollment certification matches the current
             award ending date, notify the claimant of his or her
             remaining entitlement by dictated letter. (See par. 4.18h.)

             

             See footnote 1.
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **2953**   ACTION - CONTRIBUTION ADJUSTMENT - AMENDED AWARD MAY BE
             NEEDED

             

             [Explanation]{.underline}: Bank file processing has
             generated, or should have generated, an amended award to
             reflect changes to the claimant\'s Contributions Account.

             

             *NOTE: Although 38 CFR 5.064(a) requires that the individual
             only contribute for 12 continuous months, a serviceperson may
             resume making contributions after suspending such
             contributions.*

             

             [Action]{.underline}: Carefully review the claimant\'s folder
             and master record to ensure that an amended award has
             processed and that the master record correctly reflects
             proper monthly rates based on the Contributions Account.

             

             See footnote 1.

             

  **2960**   ACTION - CONTRIBUTION ADJUSTMENT - AMENDED AWARD REQUIRED

             

             [Explanation]{.underline}: Bank file processing has caused a
             change to the benefit record. Because the record contains two
             different types of training NCD (Non-College Degree) and IHL,
             Target could not generate an amended award.

             

             *NOTE: Although 38 CFR 5.064(a) requires that the individual
             only contribute for 12 continuous months, a serviceperson may
             resume making contributions after suspending such
             contributions.*

             

             [Action]{.underline}: Process a stop payment action to remove
             all award periods that do not correspond with the claimant\'s
             initial training type. Amend the initial award to change the
             remaining award lines. Submit a reentrance award for the
             subsequent training type. For example, an NCD award and an
             IHL award appear in the master record in that order. A bank
             adjustment cannot generate an amended award. To properly
             adjust the record, terminate the IHL award effective its
             beginning date. After the termination action has processed
             (i.e., the pending issue file has cleared and Target reflects
             the termination action), amend the initial NCD award. After
             the amended NCD award has processed (i.e., the pending issue
             file has cleared and Target reflects the amended NCD award),
             submit a reentrance IHL award. Suppress all award letters and
             send a fully explanatory dictated letter to the claimant.

             

             See footnote 1.

             

  **3000**   (Various Legends)

  **and**    

  **3001**   [Explanation]{.underline}: These messages are generated by
             fiscal processing.

             

             [Action]{.underline}: Route any of these messages to the
             Finance activity.

             
  ---------- -------------------------------------------------------------

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **3006**      REJECT - RECORD CANNOT BE ADJUSTED BY VA

                

                [Explanation]{.underline}: A change of name action was
                submitted. Target did not have a Benefit Account but did have
                an active Contributions Account. When this situation occurs,
                VA may not change certain basic information in the
                Contributions Account, such as the participant\'s name. The
                transaction was rejected.

                

                [Action]{.underline}: If a change of name is appropriate, the
                chapter 32 coordinator should request the participant\'s
                military service department to submit a change of name.

                

  **3010**      REJECT - LESS THAN 3 MONTHS CONTRIBUTIONS

                

                [Explanation]{.underline}: An original or reentrance award
                was submitted for a serviceperson; the award\'s effective
                date is earlier than the first day of the month following the
                third allotment. The transaction was rejected.

                

                [Action]{.underline}: Review the claim. Verify the
                claimant\'s earliest eligibility date. Submit awards for any
                enrollment periods on or after the first day of the month
                following the claimant\'s third allotment. If the claimant is
                to be awarded benefits for a period before the first day of
                the month following the third allotment, complete an
                \"Out-of-System\" award and forward it to the Finance
                activity. The Finance activity will make payment and charge
                entitlement through fiscal transactions.

                

  **3011**      REJECT - NO CONTRIBUTIONS

                

                [Explanation]{.underline}: An original or reentrance award
                was submitted for a claimant; the award\'s effective date is
                earlier than the claimant\'s first allotment. The transaction
                was rejected.

                

                [Action]{.underline}: Review the claim. Verify the
                claimant\'s earliest eligibility date. A revised award may be
                required.

                

  **3021**      (Various Legends)

  **through**   

  **3035**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                

  **3040**      REJECT - COMPETENCY PAY STATUS INVALID

                

                [Explanation]{.underline}: A CFID (Change of Fiduciary)
                action was submitted. The transaction\'s Competency Pay
                Status code did not reflect an appropriate change from the
                existing Competency Pay Status code. The transaction was
                rejected.

                

                [Action]{.underline}: Review the claim. Verify fiduciary
                involvement. If there is no fiduciary involvement, submit the
                action as a change of address or a change of name. If there
                is fiduciary involvement, submit a corrected CFID action with
                a correct Competency Pay Status code. (See M21-1, pt. V, par.
                13.05.)

                
  ------------- -------------------------------------------------------------

+--------+-------------------------------------------------------------+
| **MSG  | **LEGEND AND EXPLANATION**                                  |
| \#**   |                                                             |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
| **     | INFO - CAN\'T ISSUE C/A FOR PERIOD BEG DATE MM-DD-YY END    |
| 8001** | DATE                                                        |
|        |                                                             |
|        | MM-DD-YY                                                    |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Explanation]{.underline}: Certification is needed for the  |
|        | claim, but the certification period involves more than the  |
|        | number of award lines that can be printed on the            |
|        | certification form.                                         |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Action]{.underline}: Send the message to VSD to obtain     |
|        | confirmation of school attendance. After obtaining school   |
|        | attendance information, VSD will annotate the message       |
|        | appropriately and return it to the Finance activity. The    |
|        | Finance activity will prepare a certification transaction.  |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
| **     | INFO - BENEFIT REC ONLY - NO ADV PAY OR RECURRING PAY MADE  |
| 8003** |                                                             |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Explanation]{.underline}: The message is generated by      |
|        | either advance pay processing or monthly recurring payment  |
|        | processing. Target found a record with only a Benefit       |
|        | Account (no Contributions Account). No chapter 32 payment   |
|        | is made for such a record.                                  |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Action]{.underline}: Associate the message with the        |
|        | claimant\'s folder. Determine if the claimant has a         |
|        | Contributions Account under [any]{.underline} number (even  |
|        | a different one). If a Contributions Account can be found,  |
|        | contact the Hines PPU and have them consolidate the         |
|        | Contributions Account and the Benefit Account under a       |
|        | single number. If no Contributions Account exists, and the  |
|        | claimant was paid in error, send the claimant\'s folder to  |
|        | the Finance activity to create an overpayment for all       |
|        | amounts paid.                                               |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
| **     | (Various Legends)                                           |
| 8004** |                                                             |
+--------+-------------------------------------------------------------+
| **thr  |                                                             |
| ough** |                                                             |
+--------+-------------------------------------------------------------+
| **     | [Explanation]{.underline}: These messages are generated by  |
| 8010** | fiscal processing.                                          |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Action]{.underline}: Route any of these messages to the    |
|        | Finance activity.                                           |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
| **     | INFO - RETURNED CHECK APPLIED TO ACCTS REC                  |
| 8011** |                                                             |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Explanation]{.underline}: A benefit payment check has been |
|        | returned. The returned check reason indicated \"death of    |
|        | claimant.\" The claimant\'s Benefit Account was active, and |
|        | there was an accounts receivable against which the returned |
|        | check amount was totally applied.                           |
+--------+-------------------------------------------------------------+
|        |                                                             |
+--------+-------------------------------------------------------------+
|        | [Action]{.underline}: Take action to determine whether the  |
|        | claimant is deceased. If the claimant is deceased, verify   |
|        | his or her training status through the date of death and    |
|        | adjust or terminate the suspended award. If a proceeds      |
|        | segment or any participant\'s contributions remain after    |
|        | the adjustment, solicit a claim for accrued benefits. If    |
|        | the claimant is not deceased, verify the current mailing    |
|        | address and enrollment status and adjust the master record, |
|        | as appropriate. (See ch. 7 for refund procedures in ch. 32  |
|        | death cases.)                                               |
+--------+-------------------------------------------------------------+

  ------------- -------------------------------------------------------------
  **MSG \#**    **LEGEND AND EXPLANATION**

                

  **8012**      ACTION - PROCEEDS ESTABLISHED - REVIEW CASE

                

                [Explanation]{.underline}: A benefit payment check has been
                returned. The returned check reason indicated either an
                undeliverable address or nonentitlement. Target placed the
                amount of the check in proceeds. If the claimant had a
                running award, Target suspended benefits.

                

                [Action]{.underline}: Send the message to VSD to verify the
                claimant\'s current address and enrollment status. VSD will
                verify the address and enrollment, annotate the message
                appropriately, and return the message to the Adjudication
                Division. If the claimant\'s enrollment has changed, the
                Adjudication Division will submit an award adjustment. If the
                claimant\'s mailing address has changed, the Adjudication
                Division will lift a suspended record and reissue the
                benefits in the proceeds by processing an amended award to
                include updating the claimant\'s address. If there is no
                change to the claimant\'s enrollment or mailing address and
                the returned check has suspended the award, lift the suspense
                by a resume pay action.

                

  **8013**      ACTION - PAYEE DECEASED - ACCRUAL SEGMENT ESTABLISHED

                

                [Explanation]{.underline}: A benefit payment check has been
                returned. The returned check reason indicated \"death of
                claimant\"; the amount of the check was placed in proceeds.
                If the claimant had an active running award, Target suspended
                the award.

                

                [Action]{.underline}: Determine whether the claimant is
                deceased. If the claimant is deceased, solicit a claim for
                accrued benefits. If the claimant is not deceased, verify the
                current mailing address and enrollment and lift the suspense
                by a resume pay action.

                

  **8014**      INFO - M/R SUSPENDED - RET CK FOR NON-ENTITL - REVIEW CASE

                

                [Explanation]{.underline}: A benefit payment check has been
                returned. The claimant\'s award was running, there was no
                accounts receivable, and the check was returned for
                \"nonentitlement.\" Target placed the amount of the check in
                proceeds and suspended the award.

                

                [Action]{.underline}: Verify the claimant\'s current address
                and enrollment status. If the claimant\'s enrollment has
                changed, submit an award adjustment. If the claimant\'s
                mailing address has changed, submit an amended award to
                include the claimant\'s current address. If there is no
                change to the claimant\'s enrollment or mailing address and
                the returned check has suspended the award, lift the suspense
                by a resume pay action.

                

  **8015**      (Various Legends)

  **through**   

  **8022**      [Explanation]{.underline}: These messages are generated by
                fiscal processing.

                

                [Action]{.underline}: Route any of these messages to the
                Finance activity.

                
  ------------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **8023**   INFO - A/R COMPUTER GENERATED - REVIEW DEDUCTION AGREEMENT

             

             [Explanation]{.underline}: An NCD certification has been
             processed. The certification processing has created an
             excessive absence situation, and an overpayment has been
             created in the account.

             

             *NOTE: Effective 12/18/89, VA regulations no longer require
             the reporting of absences. This message should only be
             generated for actions involving effective dates before
             12/18/89.*

             

             [Action]{.underline}: Route this message to the Finance
             activity.

             

  **8024**   ACTION - NAME CHANGED TO X X XXXXX

             

             [Explanation]{.underline}: Bank file processing has changed
             the claimant\'s name in the Contributions Account. Target has
             generated a transaction 88G to make the same name adjustment
             in the Benefit Account. See footnote 2.

             

             [Action]{.underline}: Review the name and address in the
             claimant\'s Benefit Account and compare it with the
             information in the Contributions Account. If the claimant\'s
             name is incorrect in the Contributions Account, contact Hines
             PPU to have them correct the name.

             

  **8025**   ACTION - FILE NUMBER CHANGED TO XXXXXXXXX

             

             [Explanation]{.underline}: Bank file processing has changed
             the file number in the claimant\'s Contributions Account.
             Target has generated a transaction 88G to update the Social
             Security number stored in the Benefit Account. See footnote
             2.

             

             [Action]{.underline}: Review the claimant\'s folder to ensure
             that the claimant\'s Benefit Account and Contributions
             Account both reflect the same file number [and]{.underline}
             the folder also reflects the correct file number.

             

  **8026**   ACTION - REVIEW CASE - POSSIBLE AMENDED AWARD REQ EFF DATE
             MM-DD-YY

             

             [Explanation]{.underline}: Bank file processing has merged
             two Contributions Accounts into one record. The master record
             includes one or more award periods, and the merging action
             may have an effect on the monthly rate(s) of the award
             period(s). Target did not automatically adjust the award
             period(s) in the Benefit Account. See footnote 2.

             

             [Action]{.underline}: Review the claimant\'s folder to
             determine whether the new composition of the Contributions
             Account will affect existing award rates. If so, submit an
             amended award, repeating any award periods that require
             adjustment.
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **8027**   ACTION - MAX ALLOWABLE ABSENCES RECOMPUTED - REVIEW FOR
             POSSIBLE O/P

             

             [Explanation]{.underline}: This message applies only to a
             retroactive adjustment of an NCD enrollment. As a result of
             the adjustment, the maximum number of allowable absences has
             been recomputed. Based on the number of absences previously
             reported, the claimant may now be overpaid.

             

             *NOTE: Effective 12/18/89, VA regulations no longer require
             the reporting of absences. This message should only be
             generated for actions involving effective dates before
             12/18/89.*

             

             [Action]{.underline}: Route the message to the Finance
             activity. The Finance activity will submit a fiscal
             transaction to establish any overpayment.

             

  **8028**   ACTION - MAX ALLOWABLE ABSENCES RECOMPUTED - REVIEW FOR
             POSSIBLE U/P

             

             [Explanation]{.underline}: This message applies only to a
             retroactive adjustment of an NCD enrollment. As a result of
             the adjustment, the maximum number of allowable absences has
             been recomputed. Based on the number of absences previously
             reported the claimant may now be underpaid.

             

             *NOTE: Effective 12/18/89, VA regulations no longer require
             the reporting of absences. This message should only be
             generated for actions involving effective dates before
             12/18/89.*

             

             [Action]{.underline}: Route the message to the Finance
             activity. If the adjustment increased the maximum number of
             allowable absences and the claimant was previously in an
             excessive absence situation [and]{.underline} after the
             adjustment the reported absences are no longer excessive, a
             fiscal transaction will be submitted to release the
             appropriate one-time payment to the claimant.

             

  **8029**   ACTION - VERIFY ELIGIBILITY - FILE ID CORR PURGED TYPE J M/R

             

             [Explanation]{.underline}: Bank file processing has changed
             the file number of the claimant\'s Contributions Account to a
             number which already has a disallowed (type J) benefit master
             record. The type J master record has been purged from Target
             and the other benefit master record has been retained.

             

             [Action]{.underline}: Carefully review the claims folder to
             ensure that the reason for disallowance in the purged type J
             master record is no longer appropriate based upon the
             present, corrected Contributions Account. If the disallowance
             is still in order, contact VA Central Office via E-mail to
             MAIL VBA CH 32 PROBLEM.

             
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **8030**   INFO - M/R AWARD LINES DELETED

             

             [Explanation]{.underline}: Target processing has caused a
             master record to contain more than 16 prior award lines.
             Since 16 prior lines is the maximum capacity of the system,
             Target deleted the earliest lines. Target calculates the
             amount of entitlement used for the deleted line(s) and prints
             a message showing the deleted line(s).

             

             *NOTE: This message is generated on wide green bar computer
             paper and forwarded to the regional office. Message 8030 is
             the only message printed in this manner. NOE processing does
             not generate a message at the regional office.*

             

             [Action]{.underline}: No action is necessary. Drop file the
             message printed by PPU for any future reference.

             

  **8033**   INFO - AWARD END REASON IS 65 - ADD\'L CONTRIBUTION REC\'D

             

             [Explanation]{.underline}: Bank file processing has increased
             the amount of contributions available in the claimant\'s
             record, and the ending reason for the claimant\'s last award
             is 65, indicating exhaustion of entitlement.

             

             [Action]{.underline}: Review the claimant\'s folder and the
             master record to determine whether an amended award is
             needed. With additional contributions available, take
             appropriate action as the claimant\'s monthly pay rate may
             require change, or an extension of the award ending date may
             be required.

             

  **8036**   (Various Legends)

  **and**    

  **8037**   [Explanation]{.underline}: These messages are generated by
             fiscal processing.

             

             [Action]{.underline}: Route any of these messages to the
             Finance activity.

             

  **8040**   INFO - ADVANCE PAY NOT PAID

             

             [Explanation]{.underline}: Target processed an advance pay
             award and computed the payment amount. The claimant had an
             accounts receivable which completely offset the advance pay
             amount, so no check was released. Also, no COD form was sent
             to the school.

             

             [Action]{.underline}: Upon receipt, route the message to VSD
             for confirmation of school attendance. After obtaining school
             attendance information, VSD will annotate the message and
             return it as follows:

             

             If there is no change in school attendance, VSD will return
             the message to the Finance activity. The Finance activity
             will submit the certification.

             

             If there is a change in school attendance, VSD will return
             the message to the Adjudication Division for processing an
             amended award or a \"quit\" certification as appropriate. Any
             award prepared should lift the COD bar.

             
  ---------- -------------------------------------------------------------

  ---------- -------------------------------------------------------------
  **MSG \#** **LEGEND AND EXPLANATION**

             

  **8901**   (Various Legends)

  **and**    

  **8902**   [Explanation]{.underline}: These messages are generated by
             fiscal processing.

             

             [Action]{.underline}: Route any of these messages to the
             Finance activity.

             

             

  **8909**   INFO - DISALLOWANCE PROCESSED BUT NO SYSTEM LETTER GENERATED

             

             [Explanation]{.underline}: Target did not generate a
             disallowance letter because of the entered reason code(s).

             

             [Action]{.underline}: Associate the message with the
             claimant\'s folder. Determine if a dictated letter was
             appropriate and whether one was sent to the claimant. If a
             letter has not been sent, send an appropriate dictated
             letter.

             
  ---------- -------------------------------------------------------------

[FOOTNOTES]{.underline}:

1 Messages 2950, 2951, 2952, 2953, and 2960 involve changes to a
claimant\'s Contributions Account. To properly review these messages, it
is necessary to determine which allotment months have been affected, to
what extent that the allotment months have changed, and whether an
adjustment (i.e., increase or decrease) is necessary. Maintain a current
copy of the M27 screen (and the M28 screen if the claimant has a DOD
contribution) in the claimant\'s folder as a normal part of the chapter
32 claim documentation. Review these screen prints during routine claims
processing. If the Contributions Account has changed or the existing
prints are more than 6 months old, print the appropriate screen(s) to
replace the screen(s) in the claimant\'s folder. In many instances, the
Contributions Account changes which generate the above-mentioned
messages will affect all award lines and rates. In such instances, any
amended award action must repeat all award periods.

When allotments are being made at a low monthly rate (e.g., \$25 per
month), the allotments can extend beyond a 6-year period. However,
Target has a 6-year maximum field for allotments. If additional
allotments are received (to exceed the 6-year maximum), Target posts
these allotments to retroactive months. A retroactive award should
[not]{.underline} be made in such a case because the new allotments only
affect remaining entitlement. Target automatically adjusts the award DLP
(Date Last Paid) and issues a message. File the message without action
provided that Target had properly adjusted the award DLP.

2 The transaction code for messages 8024, 8025, and 8026 will be 88G.
This code signifies a system-generated transaction which occurs when a
Bank file processing action adjusts a claimant\'s name or file number
(or merges two Contributions Accounts), and the master record also
includes a Benefit Account. The 88G transaction updates the Benefit
Account so it reflects the change(s) made during Bank file processing.