GSA Schedule Accounting: Refresh 31 and What It Removed

A GSA Schedule holder runs a compliance track most government contractors never encounter. The obligations are not difficult. They are different, and in 2026 they changed more than they had in a decade.

Effective with MAS Refresh 31 in April 2026, GSA made Transactional Data Reporting mandatory for every Multiple Award Schedule Special Item Number [GSA, Transactional Data Reporting requirements]. That single change reversed the shape of Schedule compliance. Two obligations that had defined it for decades came off, and the central reporting duty moved from four times a year to twelve.

A contractor still running the pre-2026 playbook is tracking data GSA no longer asks for while missing reports that are now due monthly. The penalties for the obligations that remain start at $14,308 per false claim and scale to treble damages under the False Claims Act.

GSA Schedule accounting now carries four ongoing obligations beyond standard bookkeeping: monthly transactional data reporting, quarterly Industrial Funding Fee payments, Trade Agreements Act country-of-origin tracking, and records granular enough to reconcile all three. Commercial Sales Practices disclosure and basis-of-award tracking are not required under TDR. We walk through the chart of accounts modifications, reporting mechanics, and audit triggers below.

The Industrial Funding Fee: GSA Schedule Accounting’s Core Obligation

The Industrial Funding Fee (IFF) is GSA’s operating cost recovery mechanism. The IFF rate is set at GSA’s discretion. GSA has the unilateral right to change the percentage at any time, but not more than once per year. The current rate is 0.75% [GSA Vendor Support Center, IFF rates]. Before each filing, verify the rate at vsc.gsa.gov, which is where the clause requires GSA to post it. Payment is due within 30 calendar days after the last calendar day of the reporting quarter.

Check which version of the clause your contract carries. The codified text at GSAR 552.238-80 is the July 2020 clause. Contracts issued under Refresh 31 carry 552.238-80 (Dec 2025) (GSAR Deviation), which restates the clause around transactional data. The rate rule and the 30-day remittance deadline read the same in both. The reporting duties do not.

The fee applies to all sales made under the GSA contract, including task orders placed by federal agencies, state and local government purchases through cooperative purchasing, and orders placed through GSA Advantage.

The calculation at the current rate: total reportable GSA sales multiplied by 0.0075. A firm reporting $2 million in quarterly GSA sales owes $15,000 in IFF.

Read the consequence clause literally, because it is harder than it looks. Failing to remit the full IFF within 30 calendar days makes the shortfall a contract debt to the government under FAR subpart 32.6, collectible by withholding or offsetting payments, with interest under FAR 52.232-17. Failing to submit the required reports, falsifying them, or paying the IFF late is by itself sufficient cause for the government to terminate the contract for cause. The clause sets no threshold of repetition. One failure meets the standard.

The accounting treatment requires a dedicated accrual. Record the IFF liability monthly as GSA sales occur, not quarterly when the payment is due. A journal entry debiting IFF expense (or a GSA compliance cost account) and crediting IFF payable keeps the balance sheet accurate and prevents a quarterly cash surprise. When payment remits, debit IFF payable and credit cash.

Sales Reporting Through the GSA Portal

GSA collects this data through the FAS Sales Reporting Portal, the successor to the 72A system. Under TDR the two deadlines separate, and this is the detail contractors most often get wrong. Transactional data is reported monthly, within 30 calendar days from the last calendar day of the month. The IFF is remitted quarterly, within 30 calendar days after the last calendar day of the quarter. Remitting the IFF monthly alongside the sales report is permitted, but the quarterly date is the one the clause enforces.

Every report must reconcile to the contractor’s accounting records. GSA auditors compare reported sales against the contractor’s general ledger, accounts receivable aging, and bank deposits. Discrepancies trigger post-award audits.

A recurring discrepancy is worth naming: sales made through GSA Advantage or eBuy go unreported because the contractor’s system never flagged the order as a GSA transaction.

Nil reports are required, and they are now monthly. If there was no contract activity during the month, the contractor must still submit a confirmation of no reportable transactional data within 30 calendar days of the last calendar day of that month. Missing a nil confirmation carries the same consequence as missing a report with sales. The duty runs through physical completion of the last outstanding task or delivery order, so it does not stop when the selling stops.

Chart of Accounts Modifications for GSA Sales Tracking

Standard GovCon chart of accounts need four additions for GSA Schedule holders. Create a revenue account (or sub-account) exclusively for GSA Schedule sales, separate from other government contract revenue. Create an IFF expense account to capture the IFF fee as a cost of doing GSA business. Create an IFF payable account (current liability) for the accrued fee between recognition and payment. Create a TDR pricing documentation folder for transaction-level records by SIN category.

In QuickBooks, classes work for firms with a single GSA schedule. Firms holding multiple SINs (Special Item Numbers) across different product or service categories benefit from sub-accounts by SIN, since IFF reporting breaks down by SIN category. Match the account structure to your reporting granularity. The GovCon chart of accounts guide covers the base structure. Layer these GSA-specific accounts on top.

How Does Transactional Data Reporting Replace the Price Reduction Clause?

Effective with MAS Refresh 31, GSA made TDR mandatory for all Multiple Award Schedule SINs. TDR does not currently apply to VA Schedule contracts, which still run the older regime. For TDR contracts GSA states plainly that three things are not required: tracking price reduction violations under the legacy Price Reductions clause (GSAR 552.238-81), most favored customer and basis of award information, and the Commercial Sales Practices disclosure. In exchange, contractors report transaction-level data on every GSA sale, and GSA uses that data to identify pricing anomalies.

The accounting shift is significant. Under the old Price Reduction Clause, contractors tracked one customer’s pricing against GSA ceilings. Under TDR, every transaction generates reportable data: the buyer, the price paid, the SIN category, and the date. This requires granular sales records tied to individual invoices, not quarterly aggregates.

The transition has an order of operations. An existing non-TDR contractor receives a Participate in TDR mass modification, separate from the standard Refresh mass modification, and must accept the Refresh 31 modification first. Non-TDR requirements continue to apply until the effective date of the Participate in TDR modification, so a contractor mid-transition still carries the old basis-of-award tracking. Confirm which clause set your contract holds today rather than assuming the refresh already moved you.

Commercial Sales Practices Documentation

This is the obligation most GSA Schedule guidance still gets wrong, including guidance written after Refresh 31.

The Commercial Sales Practices disclosure describes a contractor’s pricing methodology, discount structure, customer categories, and most-favored-customer policy. It used to become a standing contractual commitment that had to be updated whenever commercial pricing practices changed. Under TDR it is not required at all. The GSAM prescription is explicit that the CSP format applies “when the solicitation contains the basic clause 552.238-80” [GSAM 515.408], and a TDR contract carries the alternate rather than the basic clause. The modification clause splits the same way: Alternate II of GSAR 552.238-82, used for TDR contracts, drops the Commercial Sales Practice Format submission that the basic clause requires when adding items or SINs.

Two consequences follow. If your firm still runs a discount-tracking system built to mirror CSP categories, that system now serves a requirement your contract no longer imposes, and the effort belongs on transactional data accuracy instead. And the exception still matters: a contractor mid-transition, or a VA Schedule holder, carries the full CSP and basis-of-award regime. Confirm which clause set governs before retiring any record.

Trade Agreements Act Compliance and Country-of-Origin Tracking

GSA Schedule products must comply with the Trade Agreements Act (TAA), meaning products are manufactured or substantially transformed in the United States or a TAA-designated country [FAR 52.225-5]. Selling non-compliant products through a GSA Schedule is a False Claims Act violation. Penalties start at $14,308 per claim and reach treble damages.

The accounting obligation is inventory and procurement documentation. For every product sold under the GSA Schedule, maintain a country-of-origin record tied to the purchase order or supplier documentation. Service contractors face a lighter burden, though software licensing and hardware components embedded in service deliveries still require TAA verification.

Build TAA compliance into the procurement workflow, not the sales workflow. Verify country of origin when purchasing or sourcing, not when invoicing. By the time a non-compliant product appears on a GSA invoice, the FCA exposure already exists. A single field in the purchase order record (country of origin, TAA-compliant yes/no) prevents the problem at the source.

What Triggers a GSA Post-Award Audit?

GSA OIG conducts post-award audits examining pricing accuracy, sales reporting completeness, IFF payment compliance, and, on TDR contracts, the accuracy and completeness of reported transactional data. Five behaviors recur in GSA Office of Inspector General post-award audit work, and each maps to a record the auditor asks for by name.

1. Late or missing IFF payments. The clause makes a single unpaid or late IFF remittance a contract debt and sufficient cause for termination, so late payment is the fastest way to draw attention.
2. Sales reporting discrepancies. Reported sales diverge from what ordering agencies report on their end. GSA cross-references data from both sides.
3. TDR pricing anomalies flagged by GSA analytics. GSA’s TDR system collects transaction-level pricing data. Statistical outliers in pricing patterns, including prices significantly above or below established baselines, generate automated review flags.
4. High modification volume. Frequent pricing modifications suggest instability in the underlying pricing structure and invite a closer look at how those prices were justified.
5. Pricing inconsistencies across ordering agencies. GSA cross-references TDR data across agencies. Offering different prices to different agencies for the same SIN without contractual basis generates audit referrals.

The direction of travel is documented rather than inferred. GSA reports that the initial mandatory TDR implementation in 2025, covering a limited set of items, produced $20.2 million in annual cost avoidance, and projects $50 million once TDR is fully implemented across MAS [GSA, 10 April 2026]. Those savings come from analyzing contractor-reported transaction data. For a Schedule holder the implication is that pricing is now examined against a dataset, not against a self-reported tracking narrative.

Frequently Asked Questions

Key Takeaways

• GSA Schedule accounting adds four parallel obligations to standard GovCon bookkeeping: monthly transactional data reporting, quarterly IFF payments (currently 0.75%, changeable no more than once a year), TAA compliance, and records granular enough to reconcile all three. Each needs dedicated accounts built into the chart of accounts from contract award.
• TDR became mandatory for all MAS SINs with Refresh 31 in April 2026, and it removed three requirements rather than one: price reduction tracking, most favored customer and basis of award data, and the Commercial Sales Practices disclosure. If you still maintain a CSP-mirroring discount tracker, it is serving a requirement your contract no longer imposes.
• Watch the two different clocks. Transactional data is due monthly, 30 days after month end. The IFF is due quarterly, 30 days after quarter end. Nil reports follow the monthly clock, and missing one carries the same consequence as missing a month with $5 million in sales.
• Build TAA compliance into procurement, not sales. Verifying country of origin at the purchase order stage prevents FCA exposure before it reaches a GSA invoice. Penalties start at $14,308 per claim.
• GSA credits its 2025 partial TDR rollout with $20.2 million in annual cost avoidance and projects $50 million at full implementation. That analysis runs on contractor-reported transaction data, which makes reporting accuracy the control that matters most.

GSA Schedule contracts create revenue opportunities and compliance obligations in equal measure. Treat the accounting setup as a one-time event at contract award and the demand letter arrives at post-award audit. Run the Compliance Readiness Check to evaluate whether your current system handles GSA-specific tracking. Holding or pursuing a GSA Schedule? Book a discovery call with our CPA-managed team to build the right accounting structure from the start.