Sixteen months of full disability payments kept arriving after a Department of Veterans Affairs employee proposed cutting a veteran’s rating for lung cancer from 100 percent to 30 percent, citing improvement. The proposal never turned into a final decision. Before the case could be resolved, a different claims processor canceled the paperwork tracking it — an internal record VBA calls an “end product” — and the file simply closed without a ruling.
The Veterans Affairs Office of Inspector General uncovered the mistake while reviewing how the Veterans Benefits Administration processes proposed cuts to disability compensation. It is one of two detailed case files auditors used to show how the system can pay out money nobody actually decided was owed.
A proposed cut that was never carried out
Ordinarily, a proposed reduction moves toward a final decision once a veteran’s response window closes, whether or not the veteran replies. In this case, that never happened. The end product tied to the proposal was canceled instead of carried to completion, which meant no final rating decision was ever issued and the original 100 percent payment continued as if nothing had been proposed at all. Nothing in the case file suggests the veteran did anything wrong; the break happened entirely on VBA’s side of the paperwork.
A canceled file does not undo an overpayment: When a proposed reduction never reaches a final decision, the payment record and the paperwork trail can drift apart for months without anyone reconciling them. A claim tracker built for following a case number and its status sits inside The Veterans Benefits Action Kit.
How a canceled file let extra payments keep going
The inspector general’s report ties the breakdown to a specific step: someone canceled the end product associated with the proposed reduction before it produced a decision. Once that record was gone, there was no open case left to finalize, and no internal flag to catch that a proposed cut had simply vanished from the workflow rather than being resolved one way or the other. An end product is ordinarily supposed to close only once a claim is finished or found to be a duplicate; using it to close out a live proposed reduction left the case in an in-between state that nobody was tracking.
The size of the gap: $43,000 already paid, $2,700 a month more
By the time auditors reviewed the file, VBA had overpaid the veteran about $43,000 over 16 months, according to the inspector general’s report. The overpayment was not a one-time event that had since stopped. The report says an ongoing monthly overpayment of about $2,700 was still going out as of the review, because the reduction that should have ended it had never been carried through to a final decision.
A smaller case shows how one wrong date adds up
A separate file in the same review shows the opposite failure produces the same kind of result. A final notification letter went out on November 5, 2024, which — under the same 60-day due-process window set by 38 C.F.R. § 3.103 — should have discontinued the veteran’s service connection by February 1, 2025. Staff instead applied the discontinuance a month late, on March 1, resulting in an overpayment of about $300 — a small amount next to the lung-cancer case, but evidence that even a single miscalculated date routinely turns into money paid that should not have been. Both errors point the same direction: once a proposed action’s timeline slips, whether by a canceled end product or a mis-set date, the extra payment tends to keep flowing until someone outside the original case catches it.
The scale of errors behind both files
Neither case was isolated. Reviewing a sample drawn from 27,136 adverse-action cases VBA processed in 2024, auditors found errors in about 34 percent of files examined and estimated at least $16.9 million in improper payments tied to the population, with roughly $964,000 a month continuing to go out incorrectly, according to the report’s published summary. J. Margarita Devlin, VA’s principal deputy under secretary for benefits, concurred with the inspector general’s four recommendations in a July 15, 2026 response, including a recommendation to build an automated report that flags proposed adverse actions that never reach a final decision — the exact gap that let the lung-cancer overpayment run for 16 months.
Following an overpayment case to its end
An overpayment tied to a proposed reduction does not resolve itself once the mistake is found. Someone still has to track the case number, the dates involved and whatever correction VA eventually issues, and that paperwork trail is easy to lose partway through.
The Veterans Benefits Action Kit includes a claim tracker and how to file for free, built around keeping a VA case’s dates and documents in one place from notice to resolution.
Open the free-filing steps in The Veterans Benefits Action Kit.
This article was produced with AI assistance and reviewed by a human editor. Figures are linked to their primary sources.
