On October 14, the Defense Department published two notices that connect military benefit records to the Treasury Department's Do Not Pay Working System. One covers applicants for and recipients of TRICARE West benefits. The other covers military retirees receiving Combat Related Special Compensation.
Both programs will compare the same categories of information: name, Social Security number or taxpayer identification number, address, date of birth, and payment or banking information. The stated purpose is to identify and prevent improper payments before money is awarded or paid.
That description makes the screening sound decisive. The documents describe something narrower. They establish data-matching programs, not automatic findings that a person is ineligible or has committed fraud.
The match happens before the decision
Do Not Pay is a Treasury-run service that lets agencies compare payment records with multiple government data sources. It is not one master blacklist. The sources have different purposes and update schedules, and a match can mean that a record needs another look.
Treasury's public guidance draws the line plainly: "Receiving a match or having an elevated risk does not stop a payment." Do Not Pay provides the result. The agency responsible for the benefit or payment must decide what that result means.
For TRICARE West, the participating Defense component is the Defense Health Agency. For Combat Related Special Compensation, it is the Defense Finance and Accounting Service. The two notices say the matching programs will run through September 10, 2029. The retirement-compensation comment period closes November 13, 2026. The TRICARE West period closes December 14.
The timing reflects a broader federal push to move payment checks earlier. Treasury says Do Not Pay helped agencies prevent, identify, or recover $11.7 billion in improper payments during fiscal year 2025. That is Treasury's program-level figure. It combines several kinds of payment-integrity action and does not tell us how accurately either new Defense program will handle an individual match.
Specialist reporting from GovCIO also shows how quickly the system is expanding. Treasury Executive Director of Financial Integrity Justin Marsico said the share of government programs fully able to use Do Not Pay was expected to rise from 4% to between 70% and 80% by the end of the fiscal year. More programs using a shared screening layer makes the quality of the follow-up decision more consequential.
Streamlined paperwork did not erase the safeguards
A 2025 Office of Management and Budget memo helped agencies connect to Do Not Pay without negotiating a separate traditional matching agreement in every eligible case. The four-year waiver reduces an administrative barrier, but agencies still need a written data-sharing agreement with Treasury. That agreement must cover the data being matched, verification procedures, security, limits on reuse, and what happens to records after the match.
The memo also preserves the protections that matter to an affected person. An agency must independently verify information produced by the match. Before taking an adverse action in a covered federal benefit program, it must provide notice of its findings and an opportunity to contest them.
This distinction is the center of the system. A shared database can surface a discrepancy at scale. It cannot know, by itself, whether the underlying record is current, whether two similar identities were confused, whether a program exception applies, or whether the paying agency has enough context to act.
Improper does not always mean fraudulent
The term improper payment covers more than fraud. It can include a duplicate payment, an agency mistake, a recipient mistake, insufficient documentation, or money sent to someone who does not meet a program rule. Treating every match as evidence of wrongdoing would collapse those different situations into one accusation.
A February 2026 Congressional Research Service report by Natalie R. Ortiz explains that matches found during payment processing are supposed to be adjudicated by the paying agency. That means verifying whether the payment is proper or improper and recording the determination.
CRS also identified a measurement problem. Public performance reporting does not make clear how counts of potential improper payments account for false-positive matches or for payments that agencies ultimately determine were proper. A large screening total shows reach. It does not reveal the error rate faced by the person waiting for a health-related benefit or military compensation.
What the evidence cannot establish
The October 14 notices do not report match counts, false-positive rates, payment delays, denials, savings, or completed cases. They do not show that either program has harmed a recipient. They also do not prove that the new screening will catch every improper payment.
The notices identify the records that will be compared and the legal structure around the programs. The OMB memo describes required safeguards. Treasury explains that a match is not a payment decision. None of those sources shows how quickly a disputed record will be reviewed, how clearly a notice will explain the problem, or how easy the correction process will be in practice.
Those are implementation questions. They can only be answered by observing decisions, corrections, appeals, delays, and outcomes after the programs begin.
Ask for the path from match to correction
If one of these programs questions your payment, begin with the decision trail. Ask which data source produced the match and what exact information conflicted. Ask whether the Defense agency independently verified that information before acting. If the source record is wrong, ask which office can correct it. If the agency still plans to reduce, suspend, terminate, or deny the payment, ask for the notice and the procedure for contesting the finding.
The practical test is simple: can the agency show how it moved from a database match to a verified decision, and can you see how to challenge an error before that decision becomes final?