Breadcrumb

Review of Alleged Use of Incorrect Effective Dates at VBA's VARO in Chicago, IL

Report Information

Issue Date
Closure Date
Report Number
16-02806-182
VISN
State
Illinois
District
VA Office
Veterans Benefits Administration (VBA)
Report Author
Office of Audits and Evaluations
Report Type
Audit
Recommendations
3
Questioned Costs
$0
Better Use of Funds
$0
Congressionally Mandated
No

Summary

Summary
We assessed the merits of a December 2015 Office of Inspector General (OIG) Hotline allegation that claims processors at the Chicago VA Regional Office (VARO) assigned incorrect effective dates when processing claims associated with “intent to file” (ITF) submissions. An ITF provides claimants the opportunity to submit minimal information related to their claim for benefits and allows up to one year for the claimant to provide additional information and evidence necessary to complete the claim. If benefits are subsequently established, VA may use the date the VARO received the ITF as the basis for an earlier effective date for benefits payments. We substantiated the allegation that Rating Veterans Service Representatives (RVSRs) at the Chicago VARO did not always assign the correct effective dates when they received an ITF. Overall, RVSRs established incorrect effective dates for 15 of the 30 disability claims (50 percent) we sampled from a universe of 616 claims. Five of the errors resulted in 15 improper benefits payments totaling approximately $5,700; 10 of the errors had incorrect effective dates but did not affect benefits payments. The majority of effective date errors occurred when the claimant submitted an ITF electronically. In these cases, the Veterans Benefits Administration (VBA) automatically updates the corporate database; however, there is no standardized form within the electronic claims folder, which increases the likelihood the VARO overlooks the ITF. Although a notification letter is generated, it is stored in a separate VBA system. Generally, we attributed the errors to a lack of guidance within VBA policy on how to identify ITF filings and insufficient analysis of effective date errors, which led to weaknesses in training. Using incorrect effective dates may result in incorrect benefits payments. However, subsequent to our review, VBA updated its policy to include instructions on identifying ITFs and made additional ITF training available nationwide. We recommended the Chicago VARO Director conduct a review and take appropriate actions on the 586 claims associated with ITFs remaining from our universe. In addition, we recommended the Director implement a plan to ensure sufficient analysis is completed to identify effective date errors related to ITFs. Furthermore, we recommended the VARO Director ensure claims processors receive training on how to identify ITFs. The VARO Director concurred with the recommendations and provided sufficient evidence to close the recommendations.

Open Recommendation Image, SquareOpenClosed and Implemented Recommendation Image, CheckmarkClosed-ImplementedNot Implemented Recommendation Image, X character'Closed-Not Implemented
No. 1
Closed and Implemented Recommendation Image, Checkmark
to Veterans Benefits Administration (VBA)
Closure Date: 3/31/2017
We recommended the Chicago VA Regional Office Director conduct a review of the 586 claims with intent to files remaining from our universe, completed from October 1, 2015 through March 31, 2016, and take appropriate actions and report results back to OIG.
No. 2
Closed and Implemented Recommendation Image, Checkmark
to Veterans Benefits Administration (VBA)
Closure Date: 3/31/2017
We recommended the Chicago VA Regional Office Director implement a plan to ensure sufficient analysis of quality reviews is completed to identify effective date errors related to intent to files.
No. 3
Closed and Implemented Recommendation Image, Checkmark
to Veterans Benefits Administration (VBA)
Closure Date: 3/31/2017
We recommended the Chicago VA Regional Office Director ensure claims processors receive training on how to identify intent to files.