GSA TDR data elements: control the current 18-field SRP upload model
The hard part is not naming fields—it is proving population completeness, mapping consistency and source traceability every month.
Current MAS SRP upload model
The current standard MAS Transactional Data Reporting upload profile contains 18 fields. Saxum's GSA TDR engine uses that same 18-field profile rather than an obsolete field-count description that appeared in an earlier resource page. Requiredness can still depend on whether the row represents a product or service and on the current SRP instructions, so the latest GSA template remains authoritative.
The profile covers contract and order identifiers, manufacturer and product identifiers where applicable, item description, quantity and unit of measure, unit price and totals, non-federal entity information where applicable, dates, invoice number, Special Item Number, Unique Charge ID and Cloud Service Type.
Field-control model
For every field, document the source column, transformation rule, allowed blank condition, evidence owner and reconciliation dependency. Re-check the current SRP template each reporting cycle instead of preserving a stale local header list.
Common failure patterns
- Header drift after an ERP export change
- Credits and cancellations treated inconsistently
- Contract or order identifiers lost during joins
- Dates reformatted without preserving source evidence
Fail-closed handling
Missing required facts should become review items rather than guessed defaults. A clean file requires both structural validity and a reconciled source population.
GSA FAS SRP — MAS File Upload Instructions