The State of GSA TDR Data Quality in 2026
TDR is now mandatory for every MAS SIN. GSA's own watchdog says the data it collects is largely unusable. Both are true — and the gap between them is where your compliance risk lives.
Published July 15, 2026 · Updated September 10, 2026
General information, not legal advice. Requirements can depend on contract terms, modification status, effective dates, and current GSA guidance; confirm them with the relevant GSA source and your contracts, compliance, or legal adviser.
The number GSA doesn't put on a slide
In a June 2025 alert memorandum, GSA's Office of Inspector General reported that roughly 73% of the sales data reported under Transactional Data Reporting in FY2025 could not be used for meaningful price analysis. It wasn't a one-off: the OIG's earlier review of the TDR pilot found 87% of FY2022 reported sales similarly unusable. And all 23 contracting officers the OIG interviewed said they had never used TDR data in a price negotiation.[1]
Read that plainly: the government is collecting a monthly data feed that its own buyers don't use and its own auditors can't clean.
So why is it mandatory now?
Refresh 31 (April 2, 2026) made TDR mandatory for every MAS SIN and, in the same stroke, ended Price Reductions Clause tracking and the CSP-1 disclosure for TDR participants — the mechanisms that historically drove pricing-compliance enforcement.[2] GSA's bet is that a broad transactional feed will, over time, replace the old most-favored-customer machinery. Whether the data ever becomes usable is GSA's problem to solve.
What the data-quality problem means for your contract
Here's the trap: because the aggregate data is noisy, it's easy to assume your individual submission doesn't matter. It does — just not where you'd expect. The Sales Reporting Portal validates your file's format, rejects uploads that fail validation, and calculates the IFF due on what you report. What it will never flag is whether what you reported is complete and correct, whether a line carries TAA or country-of-origin exposure, whether you're on track for the $100K / $125K minimum-sales criteria, or whether a clause or modification applies to your contract.
Those are exactly the questions a Contractor Assessment Visit asks. TDR accuracy feeds your standing at an IOA review, your option-year exercise, and — if it's wrong enough, often enough — your contract's continuation. The enforcement hammer changed shape after Refresh 31; it didn't disappear.
What to do about it
Treat the SRP as your system of record, not your compliance check. Before you submit each month, verify the layer the portal doesn't: IFF accuracy per period, TAA and country-of-origin, thresholds and SIN mapping, clause applicability, and a defensible audit trail you can hand an IOA. That's the difference between "GSA accepted my file" and "I'm compliant." See the two layers, side by side →
Sources. [1] GSA Office of Inspector General, Alert Memorandum A140143-4 (June 27, 2025). [2] GSA, Transactional Data Reporting requirements (gsa.gov, updated July 31, 2026); Refresh 31 analysis — Holland & Knight, "Goodbye PRC, Hello TDR." Figures describe TDR data usability in aggregate for GSA price analysis; they are not compliance findings against any individual contractor.
Check the compliance layer before you submit.
TDR Guard and FAR Guard have not launched yet. Requesting access does not activate either module. Access is reviewed before activation.
Pricing is confirmed before activation.
MAS Pilot helps teams monitor and organize compliance-related information. It does not determine compliance, provide legal advice, or replace review by your contracts, compliance, or legal team.
Request access