Skip to content
TDR Prep

Catch-up

Months you have not reported, built in the order SRP takes them.

Transactional Data Reporting has applied to every MAS contract since , and SRP will not take a period while an earlier one on the same contract is unreported. That is the whole shape of the problem: the months only go in forwards, one at a time, starting from the first one missing.

Opening soonHow a month is built

Why order matters

SRP takes periods in sequence

Every earlier period on the contract has to be reported before this one.

Upload August 2026 while July 2026 is still unreported and the portal declines it and names the earlier period. So a single skipped month — including a month in which nothing sold — holds up every month behind it, and the fix is always the same fix: start at the first missing period and work forward.

That is also why this product exists as more than a validator. Building one clean month is a mapping problem. Building five, in order, each validated before the next, is a sequencing problem — and the mapping you do on the first month is already done for the four behind it.

ICD §2.6 Scenario 1; UG §2.2

The dates, as dates

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

The sequence

Every period the mandate covers, and when each was due

The months from the effective date to the end of the grace period, in the order SRP reads them. Which of these are yours depends on your contract; the order does not.
PeriodSRP periodReport dueOrder
July 202607-2026First period under the mandate
August 202608-2026Waits on July 2026
September 202609-2026Waits on August 2026
October 202610-2026Waits on September 2026
November 202611-2026Waits on October 2026
December 202612-2026Waits on November 2026

A due date that has passed is a date that has passed. It is not a verdict about the holder, and nothing on this site counts down to one.

What the product does

One month at a time, in order

The same four steps as a current month, run back to front through the calendar.

It does

  • Opens a reporting period for each back month on the contract and holds them in the order SRP will accept them.
  • Imports each month’s sales from the same QuickBooks connection or CSV source, with the catalog mapping already built by the first month you do.
  • Validates each month on its own, so a rejection in September never hides behind one in July.
  • Emits each file in sequence, under its own period’s filename, and archives each as an immutable snapshot with its inputs frozen on the row.
  • Tracks a month with no sales as a period of its own. There is no file for it — it is a confirmation you enter in SRP’s form — and the period is not marked reported here until you have.

It does not

  • Upload anything to SRP. There is no third-party submission surface here and there will not be — SRP’s web service is onboarded per contractor.
  • Certify anything. SRP asks the holder to certify the data is true and accurate; that is your statement about your own sales.
  • Promise an outcome. The validator applies SRP’s file rules; what a contracting officer does about a late period is between you and them.
  • Decide what is reportable. It applies the file format’s rules to the transactions you give it, and makes no determination about your contract.

Worked sequence

Harlan Office Interiors (Demo), starting from the first missing month

The repo’s fixture holder, on a made-up contract, catching up from the first period the mandate covers. Every figure below is fixture data.

  1. July 2026

    Due

    Import the month, map every item in it once, and read the findings. This is the month that builds the catalog: 40 lines on contract 47QSHA22D0031, 3 lines SRP would have sent back, clean after the fixes.

    Reviewed

  2. August 2026

    Due

    Import the month. The catalog mapping from the first month already covers every repeated item, so only genuinely new SKUs come up unmapped.

    Open

  3. September 2026

    Due

    Same again. By the third month the mapping work is close to nothing and the month is mostly reading findings.

    Open

  4. October 2026

    Due

    And so on, forward, one period at a time until the current month is the next one due.

    Open

Each file comes out of the same emitter; you upload them to SRP in that order and certify each one there. The archive keeps every version of every month, and keeps it readable and exportable whether or not the subscription is running.

GSA — Multiple Award Schedule TDR User Guide (PDF)GSA — Help with TDR