Skip to content

What TDR is

Transactional Data Reporting, in the terms a holder meets it in.

A MAS contract holder reports what they sold under the contract, line by line, every month, into GSA’s Sales Reporting Portal. Not a total. Not a summary. The transactions.

Refresh 31

What changed, and when it started

TDR began as a pilot on a subset of Special Item Numbers, and holders outside it reported under the Commercial Sales Practices and Price Reduction clauses instead. Refresh 31 of the MAS solicitation ended the split.

TDR now applies across MAS rather than to a pilot list of SINs, and it applies to new offers as well as existing contracts. GSA then issued a unilateral mass modification setting the participation effective date, and published a grace period to let holders get their reporting started.

For a holder, the practical change is a cadence. Where the old regime asked for disclosure at negotiation and tracking against a basis-of-award customer, this one asks for a file every month, on a fixed clock, whether or not anything sold.

What TDR participation means for the price-reduction and commercial-sales- practices obligations on a given contract is a question about that contract. This product makes no determination about it; the source below and your contracting officer do.

The dates

Applies since
Grace period ends
Enforcement
A contracting officer may take enforcement action after December 31, 2026
Reporting cadence
Monthly, within 30 calendar days of the last calendar day of the month

GSA — Help with TDRGSA — Multiple Award Schedule TDR User Guide (PDF)GSAM 552.238-80 — Industrial Funding Fee and Sales Reporting

The monthly report

One line per transaction, in a fixed set of columns

A MAS transactional line carries 18 columns: 9 that must have a value on every line and 9 that may be blank. This list is generated from the same field data the validator and the emitter run on.

The columns, in the order the file reads them

  1. 1Contract/BPA NumberRequired
  2. 2Order Number/PIIDRequired
  3. 3Description of DeliverableRequired
  4. 4Manufacturer Name
  5. 5Manufacturer Part Number
  6. 6Unit MeasureRequired
  7. 7Quantity of Item SoldRequired
  8. 8Universal Product Code
  9. 9SIN NumberRequired
  10. 10Price Paid per Unit (US$)Required
  11. 11Total Price (US$)Required
  12. 12Non-Federal EntityRequired
  13. 13Federal Customer
  14. 14Order Date
  15. 15Ship Date
  16. 16Zip Code Shipped To
  17. 17UCID
  18. 18Cloud Service Type

Most of it comes out of an accounting system unchanged. What does not is the part that identifies the item as a schedule item — the SIN it was awarded under, SRP’s unit-of-measure abbreviation, the manufacturer and part number — and that is the part this product maps once per item and reuses every month.

The list above is the whole of it. A field that is not on it is not part of this report, however familiar it is from other federal reporting.

Getting it there

The lanes SRP offers

Five ways in, and they are not equivalent. This product prepares the file for the CSV lane.

Form entry

Type each transaction into the portal. Fine for a handful of lines, and it is what GSA points a holder at for a month with no sales, where the submission is a confirmation rather than a file.

Excel upload template

GSA publishes a workbook with the columns laid out and stars on the ones its own template treats as required. You fill it in and upload the workbook. The star set is slightly wider than the file specification’s required set, which is why this product raises an advisory finding on those columns rather than a rejection.

CSV upload — the lane this product prepares

One text file per contract per month, one line per transaction, values separated by a pipe character. SRP validates it on ingest and either accepts the period or returns the rows it will not take. That validation is the one this product runs first, on your machine, before anything is uploaded.

EDI and the web service

Both exist and both are onboarded per contractor: a holder arranges access with GSA directly. There is no lane through which a third party submits on a holder’s behalf, which is why this product does not have one and will not claim one.

Whichever lane a holder uses, the last two acts are the same and they are the holder’s: submit the period, and certify that the data is true and accurate. That is true of a month with no sales too — the confirmation is still a submission, and it is still certified.

Where SRP problems go

An SRP account problem, an upload that will not go through, or a question about your contract’s status goes to GSA’s Vendor Support Center, not to us.

vendor.support@gsa.gov

(877) 495-4849

SRP user manual — data reporting optionsSRP — frequently asked questions