Transactional Data Reporting Guide: Monthly TDR, FCP Values, Sales Records, and IFF

A practical guide to GSA Transactional Data Reporting: monthly line-item reporting, approved FCP/PPT values, reporting errors, sales data ownership, and IFF reconciliation.

Built for

GSA MAS offer teams, pricing leads, contract administrators, and founders building a Schedule package

By the end

Turn TDR from a vague compliance phrase into a monthly data process.

Field guide

TDR decision map

Monthly data

TDR should not wait for quarter-end cleanup.

Signal

Sales are directly linked to the MAS contract.

Response

Export line-item records, review exceptions, and submit through SRP within the required cadence.

Approved file values

Small spelling differences can cause reporting errors.

Signal

Line items include part numbers, labor category titles, UCIDs, or catalog values.

Response

Match reporting values to approved FCP Product File, Services Plus File, or approved PPT values.

IFF

Monthly reporting and quarterly payment need the same source of truth.

Signal

Sales are reported and the fee must be remitted.

Response

Reconcile reported sales with IFF payment timing and internal finance records.

Part 1

TDR is a data process

GSA describes TDR as collecting transactional data about prices paid for products and services sold through MAS. That makes the real contractor job data discipline, not just knowing the acronym.

The company needs an owner, source system, review checklist, submission calendar, and backup.

Part 2

Approved-file consistency matters

GSA's TDR help page notes that values should match approved FCP Product File, Services Plus File, or approved PPT values where applicable. This is why product and services files need clean names and stable identifiers.

Part 3

TDR and IFF are connected but not identical

TDR is the reporting requirement. IFF is the fee payment obligation. The records should reconcile, but the team should understand the timing and ownership of each.

Examples

What this looks like in practice

In practiceA simple monthly TDR close

On day one, finance exports MAS sales. On day two, contracts checks the line items against approved catalog values. On day three, exceptions are fixed or documented. The submission owner files the report and records the confirmation.

The rhythm is intentionally boring. Boring is good for recurring reporting.

Export
Match approved values
Review exceptions
Submit
Reconcile IFF

Frequently asked questions

How often is TDR reporting due?

GSA's help page describes monthly TDR reporting through SRP, with reports due within 30 calendar days from the last calendar day of the month.

Does TDR replace traditional FAS sales reporting?

GSA's TDR help page says TDR is monthly line-item transactional reporting, while traditional FAS reporting is quarterly and does not require line-item detail.

What causes TDR errors?

Common issues include values that do not match approved FCP or PPT records, such as part numbers, labor category titles, or UCIDs.