On October 14, the Defense Department published two notices establishing new computerized matching programs with Treasury's Do Not Pay system. One covers applicants for or recipients of funds through the TRICARE West Region program, administered by the Defense Health Agency. The other covers Combat Related Special Compensation, administered by the Defense Finance and Accounting Service. In both cases, DoD plans to compare its program records against Treasury records before a payment or award in order to identify and prevent improper payments.
What changed
This pairing connects separate DoD record systems to the same Treasury screening layer. For TRICARE West, the Defense Health Agency will draw on Medical/Dental Claim History Files. For Combat Related Special Compensation, the Defense Finance and Accounting Service will draw on records in the Defense Military Retiree and Annuity Pay System.
The notices list five shared field groups: name, Social Security number or taxpayer identification number, address, date of birth, and payment or banking information.
The common legal frame is the Payment Integrity Information Act of 2019 and OMB Memorandum M-25-32. Both notices state that Treasury authorized a four-year waiver of the usual matching-agreement requirement for programs meeting the memorandum's criteria, and that DoD determined both programs qualify. The waiver removes one administrative layer from the process. A data hit still does not determine that a person is ineligible or that a payment was improper.
The comment calendars then diverge. Comments on the Combat Related Special Compensation notice close November 13, 2026, while the TRICARE West notice remains open until December 14. Each program is scheduled to take effect the day after its comment period closes unless comments require modification and republication. Both are slated to run through September 10, 2029.
Why it matters
The screen therefore sits upstream of consequential decisions about health-related benefits and military compensation. The straightforward case is one where a comparison surfaces a record that should stop or redirect a payment the program was not authorized to make. The harder case arises when identity data are stale, incomplete, or associated with the wrong person, or when a valid benefit circumstance looks anomalous because two systems describe it in incompatible terms.
The notices also expose the limits of what is known today. They name the participating systems and data categories, yet report no match volumes, expected savings, completed denial counts, or specific path for resolving a disputed result. They do not describe automatic denials. A match is an input to eligibility screening, not a self-executing finding.
Verification bottleneck
That missing detail is where the operational difficulty begins. After two records appear to correspond, a reviewer or downstream system must determine whether they refer to the same person, whether the underlying data are current and accurate, what the correspondence means within the named program, and what evidence would clear a discrepancy before it affects payment.
Because the match crosses systems, the audit trail becomes more consequential than the initial comparison. A defensible process would preserve which records were compared, which field produced the result flagged for review, what rule governed the evaluation, who or what made the determination, and how any correction reached every system that acted on the original result. The two notices do not supply that implementation detail. They cannot confirm that those controls are already designed and operating.
The four-year waiver sharpens the same question. It streamlines the administrative path when the OMB criteria are satisfied, while the public notices still identify participating agencies, record systems, data categories, stated purpose, effective dates, and comment routes. Whether that leaner structure preserves enough evidence to test match quality and support corrections remains open.
Watch next
The open questions make the comment periods worth watching. Comments may surface concerns about data currency, dispute procedures, or gaps the notices do not address. After each program takes effect, the stronger evidence will be operational: how potential matches are evaluated before payment is affected, what notice if any reaches the individual whose records were compared, how quickly a disputed record can be corrected, and whether a correction propagates across DoD and Treasury systems.
This is a bounded change covering two named DoD programs with specific record systems and populations. The notices do not document individual eligibility decisions, establish findings about improper payments, or describe every application of the Do Not Pay system across the federal government. This card is general orientation, not legal or benefits advice.
Sources
- Department of Defense, "Privacy Act of 1974; Matching Program," FR Doc. 2026-20951, October 14, 2026. https://www.federalregister.gov/documents/2026/10/14/2026-20951/privacy-act-of-1974-matching-program
- Department of Defense, "Privacy Act of 1974; Matching Program," FR Doc. 2026-20952, October 14, 2026. https://www.federalregister.gov/documents/2026/10/14/2026-20952/privacy-act-of-1974-matching-program
