The thesis: one vendor record is becoming two, and the design work starts now.
For years, a supplier doing business with the US federal government has kept one certification profile in the System for Award Management: entity details like its Unique Entity ID and banking information, alongside procurement-specific and by-submission-of-offer representations, all refreshed together under FAR 52.204-8’s annual certification. On June 23, 2026, the FAR Council published FAR Case 2026-001, proposing to split that record in two. Entity-level data would stay in SAM. Everything tied to a specific procurement would move into the solicitation and the resulting contract instead.
The comment period closed July 23, 2026, and no final rule has been adopted. That gap between a proposed rule and a final one is exactly the window where a procurement or ERP team can redesign the vendor master record calmly, instead of scrambling once a contracting officer asks for a certification the vendor master was never built to hold at the solicitation level.
What actually changed, and what did not.
SAM.gov currently collects three categories of representations and certifications: Type 1, entity-level, true of the company regardless of which contract it is bidding on; Type 2, procurement-specific, tied to the particular solicitation; and Type 3, by submission of offer, made fresh with each proposal. GSA’s Integrated Award Environment program previewed a plan in 2025 to keep only Type 1 in SAM, moving Type 2 and Type 3 into individual solicitations and resultant contracts. FAR Case 2026-001 turns that plan into a formal proposed rule.
The rule is one of four proposed rules issued together, covering 20 FAR parts, and implements Executive Order 14275, Restoring Common Sense to Federal Procurement. FAR Case 2026-001 itself covers Parts 1, 2, 4, 33, 39, 40, and 53. Inside Part 4, the Council proposes relocating security and supply-chain restriction requirements to an expanded Part 40, which also consolidates Controlled Unclassified Information handling, Section 889 parts A and B, and Federal Acquisition Supply Chain Security Act orders that previously sat as separate, open FAR cases. The remaining Part 4 provisions reduce the certifications a contractor makes centrally in SAM, and the Council proposes eliminating FAR 52.204-8, the Annual Representations and Certifications clause, since it no longer has a central home for what it used to require.
None of this is adopted text yet. It is a proposed rule with a closed comment window, not a rule already in force, and this overhaul has moved in phases before: earlier FAR Overhaul changes already took effect for other parts, including a February 1, 2026 effective date for the first wave of threshold changes and clause renumbering, such as FAR 52.204-21 becoming FAR 52.240-93. A vendor master record that already treats FAR citations as fixed strings, rather than values that can change, will need to catch up either way.
Before and after FAR Case 2026-001.
| Dimension | Current state | Proposed under FAR Case 2026-001 |
|---|---|---|
| SAM registration scope | Entity-level, procurement-specific, and by-submission-of-offer representations and certifications all sit together in SAM under one annual certification | Only entity-level representations and certifications remain in SAM. Procurement-specific and by-submission-of-offer items move into each solicitation and resultant contract |
| Annual certification clause | FAR 52.204-8, Annual Representations and Certifications, requires offerors to complete the full set inside SAM | The Council proposes eliminating FAR 52.204-8, since most of what it covered no longer lives centrally |
| Security and supply-chain provisions | Sit inside FAR Part 4 alongside general administrative and registration matters | Relocate to an expanded FAR Part 40, alongside Controlled Unclassified Information handling, Section 889 parts A and B, and Federal Acquisition Supply Chain Security Act orders |
| Rulemaking status | GSA previewed the plan in 2025 through the Integrated Award Environment program, with no proposed rule yet | Formal proposed rule published June 23, 2026 as part of a four-rule package spanning 20 FAR parts, comments closed July 23, 2026 |
Building the supplier compliance record.
A vendor master record that stores every certification as one vendor-wide field will not survive this split intact. What it needs instead is a record with an entity layer and a solicitation layer, each refreshed on its own cycle. Seven fields carry most of the value.
Entity golden record
Unique Entity ID, taxpayer identification number, banking details, and the entity-level representations and certifications that stay in SAM, refreshed on SAM's own cycle rather than assumed current.
Solicitation-linked certifications
Every procurement-specific and by-submission-of-offer certification, stored against the solicitation or contract number that required it, not overwritten by the next award.
Security and supply-chain classification
Controlled Unclassified Information handling status, Section 889 compliance, and Federal Acquisition Supply Chain Security Act screening results, tracked under the consolidated Part 40 framework.
Socio-economic and size status
Small business and set-aside status as certified for a specific solicitation, since that status can now be a per-award fact rather than a standing entity attribute.
SAM reconciliation cadence
The date the entity record was last synced against SAM, and an owner responsible for catching a lapsed registration before it blocks an award.
Award-level audit trail
A link from each certification back to the solicitation, the contracting officer, and the date it was made, so a protest or an audit can trace the record to its source.
Clause and rule tracking
A watch list for FAR clause renumbering and the eventual final rule, following the precedent already set when FAR 52.204-21 became FAR 52.240-93 under an earlier phase of the overhaul.
The record one governed supplier needs.
The split does not require a new platform to start. A structured record like the one below, held in whatever system already tracks vendor master and contract data, carries the entity and solicitation layers separately from the first entry.
Example supplier compliance record
{
"supplier_id": "example-federal-supplier",
"entity_record": {
"uei": "EXAMPLE1UEI9",
"sam_registration_status": "active",
"sam_last_synced": "2026-08-01",
"entity_level_reps_certs": ["type_1"]
},
"solicitation_records": [
{
"solicitation_number": "EXAMPLE-2026-0142",
"contracting_officer": "example-co",
"certifications": ["type_2", "type_3"],
"small_business_status": "certified_small_business",
"certified_date": "2026-06-10"
}
],
"supply_chain_screening": {
"cui_handling": "required",
"section_889_status": "compliant",
"fascsa_screening": "cleared",
"far_part": "40"
},
"clause_watchlist": [
{ "old_clause": "FAR 52.204-21", "new_clause": "FAR 52.240-93" }
],
"rulemaking_tracking": {
"far_case": "2026-001",
"comment_period_closed": "2026-07-23",
"final_rule_status": "not_adopted"
}
}The same structure scales from a single federal award to a supplier holding dozens of active contracts, since each solicitation record stands on its own rather than overwriting whatever the last award happened to certify.
Implementation checklist.
Separate the vendor master record into an entity-level layer synced from SAM and a solicitation-level layer that never gets treated as durable across contracts.
Stop storing procurement-specific certifications as a single vendor-wide field, since the proposed rule moves that data out of SAM entirely.
Build a reconciliation job that checks SAM entity registration status on a schedule, rather than trusting whatever was true at first onboarding.
Tag every certification, security screening, and size-status entry with the solicitation or contract number that produced it.
Scan active proposal templates and contract boilerplate for references to FAR 52.204-8, since the Council has proposed eliminating it.
Track FAR clause renumbering the way the overhaul's first phase already did with FAR 52.204-21 becoming FAR 52.240-93.
Route Controlled Unclassified Information handling and Section 889 or supply-chain screening results into whatever record now maps to the expanded Part 40.
Treat the closed comment period as a signal to start the redesign now, not as a reason to wait for a final rule that may only confirm what has already been proposed.
Start with the vendor master schema, not the SAM lookup. Teams that separate the entity and solicitation layers now will find the eventual final rule is a data-source change, not a data-model rebuild.
Constructive failure modes to design around.
Keeping one vendor-wide certification field and letting it silently go stale once procurement-specific certifications are supposed to live at the solicitation level instead.
Assuming an active SAM registration proves a supplier is compliant for a specific award, once Type 2 and Type 3 representations no longer sit in SAM at all.
Leaving FAR 52.204-8 referenced in proposal boilerplate and internal checklists after the clause is eliminated, so a reviewer chases a requirement that no longer exists.
No process for FAR clause renumbering, so contracts written against old citations quietly drift out of sync with the current text.
No audit trail linking a certification back to the solicitation that required it, so a protest or an audit starts from a blank page instead of a record already in place.
Every one of these is fixable with the same record discipline procurement teams already apply to purchase order approvals and contract close-out files.
What to ask ERP or contract-management vendors now.
Can it separate entity-level vendor data synced from SAM from procurement-specific certifications tied to one solicitation?
Does it store certification text against the solicitation or contract number, rather than overwriting a single vendor-wide field on every award?
Can it flag FAR clause renumbering across active contracts automatically, the way it would need to for FAR 52.204-21 becoming FAR 52.240-93?
Does it track Controlled Unclassified Information handling and Section 889 or supply-chain screening status under the consolidated Part 40 structure?
Will it alert a procurement owner when a supplier's SAM entity registration lapses or comes due for refresh?
Can it produce an audit trail linking each certification to the specific solicitation, contracting officer, and date that required it?
A vendor that can answer all six with a live screen, rather than a roadmap slide, has already built the record this article describes.
Practical takeaway.
FAR Case 2026-001 is still a proposed rule, and its comment period is closed with no final text adopted. What it already establishes, with reasonable confidence, is the direction: the vendor master record built around one certification field per supplier is heading toward a split between what stays true entity-wide and what belongs to one solicitation. A procurement or ERP team that builds that split now will meet the final rule with a record already shaped for it, instead of rebuilding the vendor master under deadline once the rule takes effect.
Sources.
- GovInfo: Federal Register text of FAR Case 2026-001, Revolutionary FAR Overhaul, Parts 1, 2, 4, 33, 39, 40, and 53
- SAM.gov: official alert on Revolutionary FAR Overhaul impacts to SAM
- GSA Integrated Award Environment: Revolutionary FAR Overhaul impacts on the System for Award Management
- Crowell & Moring: Not just the FAR, SAM.gov gets overhauled too
- Wiley: FAR Council begins rulemaking to implement the FAR overhaul, proposing revisions to 20 FAR parts
- USFCR: the FAR overhaul, what small business contractors need to know
A targeted search for public X and Twitter commentary on FAR Case 2026-001 and the SAM vendor record split returned one relevant post, a law firm’s announcement of an updated FAR Overhaul reference guide, short of the two to four high-signal posts this format calls for. Ordinary citations are used instead, and nothing is fabricated.