60% VA Disability Increase 2027 Is Unconfirmed: Why Two Drill Days Can Mean Four Days of Withheld Compensation

VA compensation · Current as of October 5, 2026

The 60% VA disability increase for 2027 is unconfirmed as of October 5, 2026. The published 2026 amount for a veteran rated 60% with no dependents is $1,435.02 a month, effective December 1, 2025. A hypothetical 3% increase would make that $1,478.07, an illustrative gain of $43.05 a month. It is not an official 2027 rate, and it does not tell a reservist or National Guard member how much a future deposit will contain.

For someone receiving both VA disability compensation and military training pay, the important second calculation is often a count of paid training units. A two-day drill weekend can produce four training-pay days. If the member keeps that training pay and waives VA benefits for the corresponding days, the count can therefore be four, even though only Saturday and Sunday were spent at drill. A calendar and a pay record are counting different things.

This article keeps those two questions separate: what is known about the next rate increase, and how training-pay days affect a VA waiver. The interactive examples use fictional schedules. They do not calculate an actual debt, recommend a pay election or ask for military, medical or financial identifiers.

Start with $1,435.02, then keep the 2027 percentage open

The veteran-alone figure comes from VA’s current compensation table. The 60% spouse-only row, with no children or parents, is $1,566.02. With a spouse and one child, but no parents, the row is $1,663.02. Those amounts all describe the same rating column, but different recognized household circumstances. A headline that lists only the veteran-alone figure is not a complete household rate table.

The current table also lists additional amounts at 60%: $65 for each additional child under 18, $211 for each additional child over 18 in a qualifying school program, and $121 for a spouse receiving Aid and Attendance. The correct first-child row and the conditions for an additional allowance still matter. A relative’s presence in the household does not by itself establish that VA has included that person in an award.

The illustration below starts with the veteran-alone row and no percentage assumption. Its deliberately narrow job is to show what an assumed percentage would do to that published baseline. It does not combine dependent components, special monthly compensation, a drill adjustment or any other change to an award. The official 2027 table will be needed for the final rate, including the actual published rounding.

At 3%, multiplying $1,435.02 by 1.03 gives $1,478.0706, or $1,478.07 when this arithmetic illustration is rounded to cents. The $43.05 difference would add up to $516.60 across twelve unchanged monthly payments. That annual figure assumes the same fictional circumstances for every month. It is not retroactive compensation, an award effective date or a prediction of a reservist’s net deposits.

A bill’s date and a payment calendar do not confirm the increase

The introduced versions of H.R. 8552 and S. 4487 propose a veterans’ compensation adjustment effective December 1, 2026, tied to the Social Security COLA. The official bill-status records checked for this article did not show enactment. The latest listed House action was advancement from subcommittee to the full committee on June 30; the Senate record showed committee referral on May 11.

The SSA latest-COLA page still described the 2.8% adjustment for 2026 on the research date. A news forecast for the following year cannot replace the official percentage, the veterans’ legal authority or the published VA table. The word “increase” in a proposed law’s title is not evidence that a particular 2027 dollar amount has been approved.

Treasury’s published settlement calendar does establish that the January 2027 VA payment is scheduled to settle on December 31, 2026. That is a calendar fact, not a rate announcement. It also does not predict when a bank will make an individual deposit visible, or settle a separate adjustment for training pay. Rate, settlement and withholding records have to be matched rather than treated as one announcement.

Why a two-day weekend can produce four waiver days

The current VA Form 21-8951-2, dated January 2026, explains the counting rule directly. The National Guard and Reserves report one full day of duty pay for each four-hour unit training assembly attended. Two assemblies on Saturday and two on Sunday can therefore produce four days’ worth of inactive-duty training pay. The physical calendar still contains only two dates.

The form also explains the consequence: a member who keeps military training pay must waive VA benefits for the same number of days for which training pay was received. That is why simply counting weekends, or multiplying weekends by two calendar days, can miss the relevant number. The waiver follows the paid training units reported in the process. It does not necessarily follow the number of dates crossed off on a kitchen calendar.

In the fictional weekend above, switching from one paid assembly on each day to two doubles the training-pay count from two to four without adding another calendar date. The movement makes the unit conversion visible. It does not claim that every real weekend has four assemblies or that every recorded event was paid. Actual duty and pay records decide which units belong in the count.

The form’s list of inactive-duty activities is broader than weekend drill. It includes examples such as schooling, conferences, preparation for inspections, additional flight training, muster duty and funeral honors duty. A reconstruction that looks only for familiar Saturday-and-Sunday dates may therefore leave out reported paid activity. Conversely, attendance remembered from a calendar is not proof of the exact pay classification or the number ultimately reported.

The familiar 63-day example is a paid-unit total, not 63 days away

The January 2026 form says most members are paid for about 48 inactive-duty training days and 15 annual active-duty training days per fiscal year. Combining those figures gives 63 training-pay days. In a simple fictional schedule with four paid assemblies per two-day weekend, twelve weekends account for the 48 inactive-duty days, even though those weekends occupy only 24 calendar dates.

Add a separate 15-day annual training period and that fictional calendar has 39 training dates while the pay ledger has 63 days. The difference, 24, is not missing service or an extra annual training period. It comes from counting two paid assemblies on each of the 24 weekend dates. This is the article’s central reconstruction: the same schedule can legitimately have two totals because the units differ.

The model deliberately assumes the annual training dates do not overlap the weekend dates. It also assumes every selected assembly is paid and that each selected annual training day counts once. Real schedules can contain different duty categories, corrections and overlaps; the tool does not reconcile those records. Its “calendar dates” total is therefore a description of the fictional schedule, not a substitute for the government’s reported count.

There is a year boundary to watch as well. The form defines a fiscal year as October 1 through September 30. Fiscal year 2026 therefore runs from October 1, 2025, through September 30, 2026. A notice naming FY 2026 is not asking only about service performed between January and December 2026. Pulling the wrong twelve months of records can create an apparent disagreement before any assembly has been counted.

The published compensation rate year is a separate clock. The current 2026 rate became effective on December 1, 2025, which falls inside FY 2026 rather than at its start. That mismatch is one reason the tools here do not multiply all days on an old notice by today’s monthly rate. A present-day rate table can be correct while still being the wrong source for reconstructing a past adjustment.

The election notice asks about both the count and the pay to waive

Form 21-8951-2 separates the reported fiscal year and training-pay days from the member’s response. In Section III, the member can agree or disagree with the day count. If it is wrong, the form provides a field for the corrected number. The election then identifies which pay is being waived. These are related choices, but agreeing that the count is right is not the same question as choosing which benefit to keep.

The current instructions matter if the form is left incomplete. They say that if neither count box is selected, VA will assume agreement with the reported training-pay days. They also say that if the election is not marked, VA will assume the member wishes to waive VA pay for the indicated number of days. An unanswered field therefore is not a reliable way to put the issue on hold.

The form instructs the member to return it within 30 days and to secure a commander or designee signature when required. It specifically calls for that signature when a corrected count entered in the election is lower than the reported count; the signature section also describes disagreement with the count more broadly. A member facing a correction should follow the current form and accompanying notice, rather than assume that a calculator’s number is sufficient evidence.

Another line deserves attention: the current form says an election to waive VA pay results in automatic adjustments for future training pay. That does not mean future notices or counts should be ignored. It means a choice can have an ongoing administrative consequence. The article’s notice inspector only explains these printed provisions; it does not submit a response, make an election or tell the reader which option is financially better.

The form notes that waiving military pay generally produces less money for most veterans. That general observation is not a personal comparison for a particular rank, longevity, duty type, allowance situation and VA award. The article does not collect those details or recommend an election based on the 60% rating alone. An individual decision needs the actual pay records and the applicable notice.

The unknown fields in this article behave differently from blank fields on the actual election form. Here, leaving a scenario empty stops the arithmetic and clears its result. On the form, the printed instructions describe assumptions VA may make when particular boxes are left unmarked. The tool’s neutral state is a safeguard for an explanation, not advice to leave official correspondence incomplete.

Keep a copy of the actual notice and the records used to check it. If the issue is a wrong number of paid assemblies, a calendar alone may not resolve it; if the issue is the elected pay, correcting the count alone may not resolve that either. Identify the specific disagreement before responding so the evidence addresses the question the notice is asking.

A correct gross rate can coexist with a smaller deposit

A cost-of-living increase changes the gross compensation rate. A training-pay adjustment can separately change what is released in a particular payment. Those processes do not cancel each other conceptually. A member can have a higher published monthly entitlement and, during an adjustment, see a deposit that does not look like the expected percentage increase.

That is why the scenario summary keeps its two outputs in different units. The rate illustration is dollars per month at the veteran-alone 60% baseline. The training ledger is paid training days in a fictional fiscal-year schedule. The interface does not subtract the second from the first as if “63” were dollars, and it does not turn the day count into an official debt. A rate, a number of days and the agency’s period-specific adjustment are different inputs.

If a notice concerns an earlier fiscal year, compare it with the records for that fiscal year. Check the reported paid assemblies and annual training, the effective dates of the VA award, any recognized dependent changes and the explanation of the adjustment. The fact that the current table says $1,435.02 does not prove an older notice should use that amount. Nor does a forecast for 2027 prove what should be withheld for past service.

Similarly, a change from a 60% rating to a different rating would be a separate award change, not the annual percentage adjustment described here. A dependent added to an award could also change a payment without changing the rating. Separating those events helps explain why comparing two bank deposits is not enough to measure the COLA or verify a training-pay adjustment.

The useful check is a three-way match

First, match the VA award to the current official rate table: rating, recognized dependents and any other compensation components. Second, match the training notice to the correct fiscal-year military pay records. Count paid training units, not just dates attended. Third, read the election and adjustment instructions to understand what VA proposes to do and what response is due.

If the reported day count is wrong, use the correction procedure and supporting records identified by the notice and current form. If the amount or timing remains unclear even though the days are right, ask VA for the adjustment explanation rather than reverse-engineering it from a news article’s monthly figure. VA’s Ask VA service is one official contact route printed on the form. Do not send personal identifiers through a public comment or an unofficial calculator.

When the 2027 amount becomes official, it will update the rate side of this comparison. It will not change two calendar dates into two paid units when the record contains four assemblies, or turn a fiscal-year notice into a calendar-year one. Until the official announcement, enactment and VA table are available, $1,435.02 remains the confirmed veteran-alone 60% baseline and every future amount in this article remains illustrative.

For the inflation evidence behind the still-unconfirmed adjustment, see our 2027 COLA forecast analysis.

The broader 2027 VA disability increase guide explains how the announcement and official rate tables fit together.