Seven governed ERP profiles
QuickBooks Online/Desktop, NetSuite, Deltek Costpoint, Unanet, Sage Intacct and Dynamics 365 exports are adapted into one controlled schema.
Monthly Transactional Data Reporting
Close every GSA TDR month with a controlled, reviewable packet
Saxum converts customer-controlled source data into a reviewed upload draft, exception register, reconciliation and signed control packet. The contractor’s authorized POC remains responsible for portal access and certification.
No portal credentials. No guaranteed external result. Scope confirmed before sensitive material is transferred.
Flagship product depth
GSA source-to-approval depth
Deeper deterministic controls reduce setup and recurring review work while preserving customer-controlled submission and qualification boundaries.
Multi-contract and amendment control
Contract/SIN profiles, prior-period deltas and contract-level summaries surface changes before the monthly packet is approved.
Authorized approval packet
Saxum prepares the review evidence and SRP-shaped draft; the contractor’s authorized POC retains upload and certification.
Review how Saxum separates internal execution from external proof →
Available for controlled onboarding. Provider-specific connections and external outcomes are qualified with each customer; internal completion is never represented as provider acceptance.
Fail-closed reviewUnsupported facts remain unresolved.
Transparent changesCorrections receive a visible audit trail.
Least-data intakeOnly necessary information is requested.
Independent serviceNo agency or platform affiliation implied.
Reviewed 12 August 2026
Current requirement snapshot
Transactional Data Reporting is mandatory across MAS SINs. Reports are submitted monthly, including applicable zero-sales reporting, and are due within 30 calendar days after the end of each reporting month. From 1 July through 31 December 2026, GSA also has a trial period for good-faith errors in six newly required data fields: ship date, order date, ZIP code shipped to, federal customer, Unique Catalog ID and cloud service type. Reporting, applicable fields and correct IFF obligations still remain in force. The contractor’s authorized POC retains upload and certification responsibility.
The operational problem
Why the standard portal or checklist is not enough
TDR is a recurring month-end process: extract sales, map fields, resolve credits and zero-sales periods, reconcile totals, prepare the upload and retain evidence. The submission portal is only the final step; the operational risk sits upstream.
Truth boundary: Saxum controls preparation, evidence and technical review. It does not replace the customer’s legal, tax, accounting, scientific or regulatory professionals, and it does not control external acceptance.
Best-fit customer
MAS contractors, GovCon accountants and consultants managing multiple contractor accounts
Problems this product helps control
Monthly GSA Transactional Data Reporting cycles where ERP exports, the current SRP upload fields, reporting basis, IFF evidence and provider outcomes need controlled reconciliation.
What Saxum needs
A bounded intake, not an open-ended data dump
The case starts with enough context to reproduce the problem and define responsibility. Credentials, unrelated personal data and unsupported assumptions are excluded.
- Contract and SIN context
- Monthly transaction export
- Prior SRP result or accepted-file sample, when available
- Named authorized POC and reporting calendar
The deliverable
What arrives at the end of the engagement
The output is designed to be reviewed, handed off and defended—not merely marked “passed.”
- Field-mapped upload draft
- Blocking-error and warning register
- Monthly sales reconciliation
- Zero-sales or exception documentation
- Submission checklist for the authorized POC
- Signed control packet and evidence bundle
Controlled workflow
From messy source material to a reviewable release packet
Each stage has a clear stop condition. When evidence is insufficient, the case pauses rather than manufacturing certainty.
Map
Confirm contract scope and map the customer’s source columns to the reporting fields.
Validate
Run structural, type, date, amount and reconciliation controls.
Review
Resolve exceptions with the contractor or adviser without guessing.
Package
Deliver the upload draft and signed evidence packet for authorized submission.
Recurring control platform
A monthly close system—not another spreadsheet handoff
The control room preserves each contractor separately, reuses approved mappings, reconciles the newest cycle, routes exceptions to named owners and prevents release until the configured review gate is complete.
Close and reconcile
Validate the upload population, compare the general ledger, estimate and reconcile IFF, measure period variance and preserve a signed source-to-output trail.
Adviser portfolio mode
Manage segregated contractor accounts, team roles, due dates, recurring schedules, white-labelled summaries and a cross-client portfolio report.
Rule and value evidence
Watch the official GSA source for change, pause affected cycles for review, and show errors prevented, records processed and estimated time avoided.
First-cycle outcome proof
Show the buyer exactly what Saxum proved
The first controlled cycle produces customer-visible proof before the workflow is expanded. Saxum keeps internal completion separate from external/provider acceptance and never turns estimates into verified outcomes.
Source coverage
See which files, mappings and authority sources were used, what was missing and which assumptions remained unresolved.
Exception register
Every blocker has a reason, owner and current state. Unsupported facts remain open instead of disappearing into a generic pass.
Evidence-graded scorecard
Separate Saxum-completed work from provider-final evidence, verified value, source-backed exposure, observed time savings and estimates.
Commercial fit
Use this when the cost of an unresolved exception exceeds the cost of review
Saxum is strongest when the workflow repeats, the evidence is fragmented and one preventable mistake can delay revenue, create rework or weaken the customer’s audit trail.
Indicative pricing
$999 onboarding · $499/month per contract · adviser plans from $1,500/month
Every engagement starts with scope confirmation. Pilot and research offers are intentionally limited until the workflow is proven on paid cases.
Start a TDR first-cycle assessment →Questions buyers ask
GSA TDR Control FAQ
Direct answers on access, responsibility, deliverables and limits.
No. The contractor’s recognized and authorized POC logs in, uploads and certifies. Saxum never asks for MFA credentials.
Yes. The control packet documents the reporting period and the customer’s declared zero-sales basis.
No. GSA systems and contract facts remain authoritative. Saxum reduces preventable preparation errors and preserves evidence.
Yes. The adviser plan standardizes intake, mappings and review evidence while keeping each contractor segregated.
The accepted mapping becomes a controlled baseline, so later cycles focus on exceptions and changed facts.
Primary references
Verify the underlying requirement
Saxum product pages link to primary agency or platform material so buyers can confirm the official requirement themselves.
Primary-source review date: 12 August 2026. Re-check before each engagement.
Related Saxum desks
Continue the control layer
Bring the real case, not a hypothetical
Describe the workflow, deadline and evidence you already have. Do not send passwords, API keys or regulated data through the public form.
Saxum Control Platform
Run this workflow in the encrypted control room
Schedule or run the engine, apply saved mappings and connectors, assign exceptions, collect evidence, complete Human ReviewPass and publish signed outputs with measurable value reporting.
Open the control roomEvaluate before onboarding
See the workflow before you bring customer data
Every executable Saxum product now has a synthetic first-cycle walkthrough. Where a free checker or guide exists, it is linked here too.