--- title: "Part XIV, Chapter 5" document: "M-21-1" section: "Part XIV, Chapter 5" canonical: "https://veteranai.co/va-regulations/m21-1/xiv.5" source: "https://www.knowva.ebenefits.va.gov/system/templates/selfservice/va_ssnew/help/customer/locale/en-US/portal/554400000001018/content/554400000173309/M21-1-Part-XIV-Chapter-5-Matching-Programs-That-Identify-Veterans-That-Returned-to-Active-Duty" updated: "2026-09-07T14:38:16.764854Z" --- January 19, 2022 ### XIV.5.1.a. VADIR Activation Match Approximately two months after the end of a specific month, a _VA/DoD Identity Repository (VADIR) Activation Match_ is released to the Department of Veterans Affairs. This match identifies reservists and members of the National Guard that were called to active duty. Effective October 1, 2020, the match includes non-training Guard/Reserve Active Service (GRAS) periods in the Veterans Information Solution (VIS). These service periods are identifiable in VIS by the presence of _No_ in the TRAINING column on the MILITARY HISTORY page. The results of the match are sent to the Hines Information Technology Center (ITC) for screening and end product (EP) establishment. **Reference:** For more information on a waiver of disability benefits during National Guard/Reserve training duty, see [M21-1, Part VI, Subpart ii, 3](). ### XIV.5.1.b. Automated Processing of the Activation Match The Hines ITC establishes an EP 600 - _Return to Active Duty_ on matched cases. Corresponding notices of proposed adverse action are issued on all EPs 600 established by the batch process. In these cases, the system will * set the suspense date for 65 days * create contentions titled * _Return to Active Duty_ followed by the begin date and termination date (if known), and * _Return to Active Duty Proposal_ , and * create a tracked item titled _Return to Active Duty Proposal._ **Exception:** For cases in which there was more than one non-sequential active duty/activation period, an EP 290 - _Return to Active Duty_ is __ automatically established for all remaining active duty/activation periods. These cases are not eligible for automated processing. Claims processors must follow the steps outlined in [M21-1, Part X, Subpart v, 2.B.1.b]() to manually process the notice that the Veteran has returned to active duty. ### XIV.5.1.c. Required Actions After Initial Automated Processing After the initial automated processing described in M21-1, Part XIV, 5.1.b, use the table below to determine the next steps.| **If the Veteran ...**| **Then …** does not respond after 65 days | no regional office action is required. The adjustment will be made through automated processing. responds within 65 days and agrees with the proposed action | * close out the _Return to Active Duty Proposal_ tracked item with the date the Veteran provided the response, and * the adjustment will be made through automated processing. **Note:** A manual adjustment may be made to reduce the amount of the overpayment. responds within 65 days and disagrees with the proposed action | * close out the _Return to Active Duty Proposal_ tracked item with the date the Veteran’s response was received * create a new tracked item titled _Other Request_ and enter _Return to Active Duty – Manual Process_ as free text and enter a suspense date that is 30 days from the current date, and * no automated action will be taken. Manually adjust the Veteran’s benefits. responds within 65 days and requests or claims a waiver of military pay and allowances for a specific active duty/activation period(s) | * send an encrypted e-mail to [VAVBAWAS/CO/MILPAY]() * in the body of the e-mail message, include the * Veteran’s name * file number * date the waiver was received * period(s) of the waiver, and * document identification number assigned to the waiver * save a copy of the e-mail in portable document format (PDF) and upload the PDF into the Veteran’s electronic claims folder, and * take no further action until the Military Pay Staff responds with further instructions. responds within 65 days and requests a hearing | follow the instructions in [M21-1, Part X, Subpart ii, 3.B.3]().