Transactional Data Reporting (TDR) replaced the cumbersome Commercial Sales Practices (CSP) and Price Reduction Clause (PRC) requirements for many GSA contractors.
Under TDR, contractors must submit detailed monthly reports on every sale made through their GSA Schedule, including transaction-level data such as pricing, quantity, and customer information.
This shift simplifies pricing compliance on one side, but introduces more frequent reporting requirements and ongoing administrative work that many contractors underestimate.
GSA Transactional Data Reporting is a reporting method introduced in 2016 as part of GSA’s Federal Marketplace Strategy. This program collects standardized transaction-level data about purchases made through GSA contracts.
Here’s the basic idea: every month, you tell GSA exactly what you sold through your GSA contract: what product or service, how many units, what price, which agency bought it, where it went.
Why does GSA want all this information?
A few reasons:
TDR started as a pilot program in 2016 with IT Schedule 70 contractors. The GSA had been working on modernizing their approach to pricing and sales practices for years. The old Commercial Sales Practices (CSP) format required contractors to disclose their commercial pricing structures and identify their “most favored customer.”
This system had problems. It was administrative-heavy for contractors, difficult to audit, and didn’t provide GSA with actionable market intelligence. So they tested TDR as an alternative.
The pilot was successful enough that GSA expanded it. Now TDR is mandatory for some contract categories and optional for others. The goal is to eventually move most GSA contractors to this model.
TDR sounds straightforward until you are doing it every month. Here is what the GSA TDR reporting process involves.
Contractors must capture detailed data for every GSA sale, including contract number, SIN, quantity, price paid, and customer information. This data typically comes from internal accounting, ERP, or sales systems.
Before submission, every required field needs to be complete and accurate. Incorrect SIN mapping, missing customer details, or pricing discrepancies can create compliance risks that compound over time.
TDR reports must follow GSA formatting requirements, typically submitted as a structured CSV or Excel file, or entered directly into the FAS Sales Reporting Portal.
Reports are due every month, even when no sales occurred during that period. Submissions must go in within 30 days after the end of each reporting period.
A single accurate submission is not enough. TDR reporting is ongoing, and gaps or inconsistencies between reporting periods create audit risk. Contractors need a repeatable internal process that holds up every month, not just the first one.
TDR offers several advantages for GSA contract holders:
The downside?
You’ve got to report every single month, even if you had zero sales. And you need systems in place to capture all the required data elements. But for most contractors, the trade-off is worth it.
Not all GSA contractors must participate in TDR. Currently, the program operates under both mandatory and optional participation models:
To know your status, look at your contract. Section I-FSS-969 is the TDR clause. If it’s in your contract, you’re required to report. If it’s not there, check with your GSA Contracting Officer about whether TDR is available for your category.
When you choose TDR, you’re trading one set of requirements for another. Here’s what that means:
Consider your sales volume. If you process hundreds of transactions monthly, you need good systems to aggregate TDR data. If you only do a few large contracts per year, manual reporting might work fine.
Also consider your commercial pricing structure. If you offer lots of different discounts to various commercial customers, the Price Reduction Clause is complicated to manage. TDR eliminates that headache. But if you have simple, consistent commercial pricing, the Price Reduction Clause might not be that burdensome.
Transactional Data Reporting shifts how GSA contractors handle pricing and compliance, moving away from the traditional Commercial Sales Practices (CSP) and Price Reduction Clause (PRC) requirements.
The table below highlights the differences between TDR and traditional GSA reporting requirements.
| Aspect | TDR | Traditional (CSP/PRC) |
|---|---|---|
| Reporting Frequency | Monthly | Quarterly, sales totals only |
| Price Reduction Clause | Eliminated | Required |
| Commercial Sales Practices | Eliminated | Required |
| Basis of Award | Not applicable | Must maintain pricing relationships |
| Price Adjustments | Streamlined process | More documentation required |
| Administrative Burden | Moderate | Higher |
| Level of Detail Required | Transaction-level (every line item) | Summary totals by contract |
| IFF Calculation | Separate quarterly report still required | Based on quarterly sales report |
Now let’s get into the specifics of monthly TDR reporting requirements and what you actually need to report. GSA has defined required data elements and optional elements. You must include all required elements for every transaction. Optional elements are nice to have but not mandatory.
GSA requires contractors to submit specific transaction-level data for every sale as part of TDR reporting. The table below covers every required field.
| Required Data | Description |
|---|---|
| Contract number | Your GSA contract identifier |
| Task/Delivery Order Number or PIID | Specific order identifier |
| Non-Federal Entity | If applicable to transaction |
| Special Item Number (SIN) | Contract category code |
| Description of Deliverable | What was provided |
| Manufacturer Name | Who made the product |
| Manufacturer Part Number | Product identifier |
| Unit Measure | How quantity is measured |
| Quantity of Item Sold | Amount provided |
| Universal Product Code (UPC) | If applicable |
| Price Paid per Unit | Cost per item or service unit |
| Total Price | Complete transaction amount |
| Order Date | When order was placed |
| Ship Date | When order was fulfilled |
| ZIP Code of Destination | Where order was delivered |
GSA also allows contractors to include optional data elements alongside required fields in their TDR reporting. Including these can strengthen reporting accuracy and give GSA a clearer picture of your sales activity.
| Optional Data | Description |
|---|---|
| Federal Customer | Specific agency information |
| Invoice Number | Billing reference |
| Invoice Paid Date | When payment was received |
Managing GSA transactional data reporting can get complicated fast. You need systems to capture all the required data, processes to ensure accuracy, and discipline to meet monthly deadlines.
Road Map Consulting specializes in helping federal contractors navigate TDR compliance:
Michael Perch is the Founder and Principal of Road Map Consulting. With over 30 years of experience in financial management, sales, and contract management, Michael specializes in helping businesses navigate federal procurement processes.
32 criteria GSA will audit – know exactly where you stand before you submit.
Our clients don't just compete—they thrive. Backed by certified processes and decades of experience, we deliver clarity, compliance, and confidence. Schedule your consultation today and see why organizations trust Road Map Consulting.
Our clients don’t just compete—they thrive. Backed by certified processes and decades of experience, we deliver clarity, compliance, and confidence. Schedule your consultation today and see why organizations trust Road Map Consulting.
SCHEDULE A CONSULTATION