The 2016 FAR rule took the DUNS name out of its definition, and that wording outlasted the 2022 switch

A FAR rule published September 30, 2016, replaced the proprietary DUNS number with a “unique entity identifier” defined by pointing to SAM.gov. It removed the legal tie to one supplier and left the systems change for later; the identifier switched on April 4, 2022.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

A FAR rule published September 30, 2016, replaced the proprietary DUNS number with a “unique entity identifier” defined by pointing to SAM.gov. It removed the legal tie to one supplier and left the systems change for later; the identifier switched on April 4, 2022.

  1. The week The other items that day ranged widely.
  2. The words: what the rule changed in the FAR text That last sentence is the design.
  3. The lock-in: why a proprietary identifier was a cost problem The rule’s regulatory flexibility analysis stated the problem plainly.
  4. The plumbing: where the identifier did its work The rule revised the definition of being registered in SAM.
  5. The deferred decision: what the rule left for later The councils were explicit.
  6. How the change landed on different parties For a contracting office, the 2016 change was a vocabulary change.
  7. Objections, in order The rule did not move any system. [1] It did remove the need to amend the FAR before a switch.
  8. With hindsight The switch came on April 4, 2022.

The week

On September 30, 2016, the Federal Register published Federal Acquisition Circular 2005-91. [2] The circular carried ten Federal Acquisition Regulation cases and a set of technical amendments, agreed by the civilian and defense acquisition councils. [2] Item V was FAR Case 2015-022, “Unique Identification of Entities Receiving Federal Awards.” [2]

The other items that day ranged widely. They included a prohibition on contracting with corporations that had delinquent federal taxes or felony convictions, and updated reporting of veterans’ employment. [2] They also included rules on consolidation and bundling, contractors performing private security functions, and a limit on allowable contractor employee compensation costs. [2]

The identifier rule was short. The Department of Defense, the General Services Administration and NASA issued it as a final rule, effective October 31, 2016. [1] Its summary said the change to the FAR removes the proprietary standard or number. [1]

That number was the Data Universal Numbering System number, known as DUNS, from Dun and Bradstreet. [1] The FAR had used it to identify entities that receive federal awards. [1] The rule removed references to the DUNS number and pointed instead to the website where the identifier used for federal contractors would be located. [1]

The rule had been proposed on November 18, 2015. [3] The proposal said unique identification of entities is critical to ensure federal dollars go to responsible parties, awardees are paid on time, and awards are recorded and reported. [3] It said that identification was then done through the FAR using the proprietary DUNS number. [3]

The proposal tied the change to transparency laws. It cited the Federal Funding Accountability and Transparency Act and the Digital Accountability and Transparency Act. [3] It said those laws require expanded identification of entities working with the government, and standards to trace federal dollars from appropriation to results. [3]

The final rule reported the comments. Ten respondents submitted comments, and all ten agreed with the rule. [1] The councils made no changes as a result. [1] Six respondents proposed alternatives to the current identifier, such as the Legal Entity Identifier or the Commercial and Government Entity code. [1]

The councils said those alternatives were outside the rule’s scope. [1] They said OMB and the Treasury, with GSA and the Award Committee for E-Government, were establishing a process for considering alternatives. [1] They said the analysis of alternatives was anticipated to be completed in fiscal year 2017. [1]

The rule was candid about timing. Its regulatory flexibility analysis said the government did not intend to move away from the DUNS number in the short term. [1] It said removing regulatory references to a proprietary identifier would create opportunities for future competition that could reduce costs to taxpayers. [1]

The analysis also gave a scale. As of June 2015, it said, there were 380,092 unique and active DUNS numbers in the System for Award Management attributed to government contracting. [1] It said the rule was internal to the government and imposed no direct requirements on vendors. [1] It added that entities whose own systems used the DUNS number could be affected if the identifier changed later. [1] It also replaced the FAR’s “generic DUNS number” with a “generic entity identifier,” for the limited cases where a contract is reported without the contractor’s own identifier. [1]

The September 30 rule changed words in a regulation. By its own account, the government did not intend to move away from the DUNS number in the short term. [1] That gap between legal text and working systems is the subject of this article.

Our argument is that the 2016 rule removed the legal lock-in to one supplier’s identifier and left the operational lock-in in place. It rewrote the FAR so the identifier was defined by function and by pointer to SAM.gov. [1] It deferred the choice of a replacement, and every system keyed to the old number, to later work. [1] In our reading, that sequence was sound, and its cost was time.

We take the rule in four parts:

  1. The words: what the rule changed in the FAR text.
  2. The lock-in: why a proprietary identifier in a regulation was a procurement and cost problem.
  3. The plumbing: where the identifier did its work in awards, payments and reporting.
  4. The deferred decision: what the rule left for later, and who was to decide it.

The first part is the legal change, the second the economic reason for it, the third the systems it touched, and the fourth the work it postponed. Together they cover what the rule did and did not do. After them we look at how the change landed on different parties, take the strongest objections in order, and end with checks a procurement or grants leader could run.

The words: what the rule changed in the FAR text

The new definition

The rule removed the FAR definitions of the DUNS number and the DUNS+4 number. [1] It added a definition of “unique entity identifier”: a number or other identifier used to identify a specific commercial, nonprofit or government entity. [1] The definition ended by directing readers to www.sam.gov for the designated entity for establishing unique entity identifiers. [1]

That last sentence is the design. The regulation did not name who issues the identifier. It named where to find out. In our reading, that turned a supplier choice into an administrative fact that could change without rulemaking.

A number or other identifier

The definition did not require a number. It said “a number or other identifier.” [1] That small phrase widened the field of possible replacements. An alphanumeric code, or a standard identifier issued under an international scheme, would fit the words.

In our reading, the drafters were avoiding a second lock-in, this time to a format. Systems built for a nine-digit numeric field would need changes for anything else. The definition put the format question with the designated entity, not in the FAR.

What the words left alone

The rule did not change the duty to register in SAM. [1] It did not change the CAGE code. [1] It did not change the transparency act data that registration had to include. [1] It said there was no change to recordkeeping. [1]

It also did not reach outside the FAR. Grants and other assistance, which run under title 2 of the Code of Federal Regulations, were outside its scope. [1][7] A reader in 2016 could see that the same identifier served both worlds, and that only one of them had changed its wording. [3]

The payment suffix

The rule also defined an electronic funds transfer indicator. It was a four-character suffix to the unique entity identifier, assigned at the entity’s discretion. [1] Its purpose was to establish additional SAM records for alternative EFT accounts for the same entity. [1]

This replaced the role the DUNS+4 had played. [1] In our reading, separating the payment suffix from the base identifier kept a feature agencies relied on, multiple bank accounts for one entity, while removing the proprietary name.

The generic identifier

The rule replaced the “generic DUNS number” with a “generic entity identifier.” [1] It defined that as an identifier assigned to a category of vendors, not specific to any individual or entity. [1] Its use was to be limited to listed situations. [1]

Authorized generic identifiers were maintained by the Integrated Award Environment program office. [1] They could be used to report contracts in place of a contractor’s actual identifier only in those situations. [1] Even then, the rule said, the generic identifier did not override solicitation provisions requiring the contractor to have its own. [1]

The contracting officer’s duties

The rule revised the contracting officer’s reporting duty. The contracting officer had to identify and report a unique entity identifier for the successful offeror on a contract action. [1] The identifier had to correspond to the offeror’s name and address in the offer, the contract and the SAM registration. [1]

The contracting officer also had to give the payment office the unique entity identifier and, if applicable, the EFT indicator. [1] Those two duties cover the two ends of an award: what is reported about it and who gets paid.

Provisions and clauses

The rule renamed the solicitation provision at 52.204-6 as “Unique Entity Identifier.” [1] It tied a clause at 52.204-12, “Unique Entity Identifier Maintenance,” to solicitations and contracts containing that provision. [1] Contractors would see the change in the documents they sign.

The rule also changed four government forms. [1] It made the form changes “Previous Edition Usable,” to avoid agencies and contractors having to make unnecessary system changes for nonsubstantive edits. [1] That choice shows the councils were thinking about systems cost even in small details.

What the CAGE code is

The rule distinguished the Commercial and Government Entity code from the unique entity identifier. [1] It pointed readers to FAR subpart 4.18 for the CAGE code, describing it as a different identifier. [1] The CAGE code stayed in the SAM registration definition alongside the unique entity identifier. [1]

That distinction mattered later. Some commenters offered the CAGE code as a replacement for DUNS. [1] The rule kept both concepts separate, leaving any merger to the analysis of alternatives.

The lock-in: why a proprietary identifier was a cost problem

What the councils said

The rule’s regulatory flexibility analysis stated the problem plainly. It said the requirement limits competition by using a proprietary number and organization to meet the government’s identification needs. [1] It said removing the references would provide opportunities for future competition that could reduce costs to taxpayers. [1]

The councils said the government was interested in reducing cost, and that was why it pursued the case. [1] In our reading, that is an economic argument, not a technical one. The DUNS number worked. The issue was who controlled it and on what terms.

The bundling question

One commenter challenged a line in the proposal. The proposal had said the requirement limited competition by using a proprietary number to meet the identification need and the need for other business information associated with it. [1] The commenter said that suggested the business information was only reachable through DUNS. [1]

The councils answered that nothing in the FAR linked business information services to the DUNS number. [1] They said agencies were free to procure business information services as they saw fit. [1] In our reading, that answer separated two purchases that had traveled together: an identifier and data about the entity behind it.

Why identifiers create lock-in

An identifier becomes valuable through use. Each system that stores it, each report that cites it and each match that relies on it raises the cost of changing it. The rule’s analysis acknowledged that entities’ own systems might be affected if the identifier changed. [1]

A regulation that names one supplier’s identifier adds a legal layer to that lock-in. Any switch would need a rule change first. The 2016 rule removed that layer. [1] In our reading, it did not touch the operational layer, where the switching work lies.

Switching costs fall on both sides

The rule’s analysis named two groups that could bear costs. Government systems were one. [1] Entities that had arranged their own business systems to use DUNS were the other. [1] A switch would land on both.

That split shapes how a switch is planned. The government controls its own systems and can schedule their changes. It does not control vendor systems. A switch plan needs a notice period long enough for outside parties to change their own records, and a clear statement of which date governs.

The scale of use

The rule’s analysis gave one measure of scale: 380,092 unique and active DUNS numbers in SAM attributed to government contracting as of June 2015. [1] That figure covered contracting. It did not count grant recipients, subrecipients or other users of the number.

Each of those numbers was a record that would need a replacement. Each replacement had to be matched to the same legal entity without error. The matching work was the real cost of any switch, and it scaled with use.

Data standards as a lock-in point

The proposal pointed to a data standard for identifying entities receiving federal awards, developed under the Digital Accountability and Transparency Act. [3] It said creating and maintaining data standards would make it easier to collect and display essential information. [3]

A data standard can lock in a supplier as firmly as a regulation. If the standard names a proprietary field, every system that implements it inherits the dependency. In our reading, the 2016 FAR rule and the transparency standards had to move together. A FAR free of DUNS would not help much if the reporting standards still required it.

Contract terms that keep choice open

The rule did not discuss the government’s contract with the identifier’s supplier. [1] A procurement leader can still draw a design point. When an organization buys an identifier or a reference data service, the exit terms matter as much as the price.

Useful terms would cover the right to keep using identifiers already issued, the right to export the validation data behind them, and a transition period if the service ends. In our view, an organization that cannot leave a reference data supplier without breaking its own records has bought a dependency, not a service.

What competition could mean

The rule did not say what competition would look like. It allowed for a future in which a different supplier, a government-run system or a nonproprietary standard could provide the identifier. [1] Commenters had suggested the Legal Entity Identifier, a global standard, and the CAGE code, which the government already ran. [1]

Each option had different economics. A government-generated identifier puts the cost of validation inside government. A purchased service puts it in a contract. A global standard spreads the cost of validation across its issuers and the entities that pay them. In our reading, the 2016 rule’s value was that it let the government choose among them without first amending the FAR.

The identifier in public data

The transparency laws the proposal cited call for standards to trace federal dollars from appropriation to results, and the proposal said data standards would help collect and display essential information. [3] An identifier in that data is how a reader follows money to an entity. When the identifier belongs to a private supplier, its use in public data rests on terms the public does not see.

The 2016 rule did not discuss this. [1] In our reading, it is part of the same economics. A government-controlled or nonproprietary identifier lets the public reuse spending data without depending on one company’s terms.

Who paid for the old arrangement

The rule did not report what the government paid for DUNS-related services. We do not estimate it, and the figure is not needed for the argument. The point for a procurement leader is structural. When an identifier is free to the entity but bought by the government, the price is set in a contract the entities never see.

The plumbing: where the identifier did its work

Registration

The rule revised the definition of being registered in SAM. A contractor was registered when it had entered the mandatory information, including the unique entity identifier and the EFT indicator if applicable, the CAGE code and the transparency act data. [1] Registration was the gate the SAM provision set for offerors. [1]

That makes the identifier a key, not a label. Other registration fields hang off it. A change of identifier means re-keying the registration, its history and everything that refers to it.

Award reporting

The contracting officer’s duty to report the identifier for each contract action fed federal procurement data. [1] The rule also changed references in FAR sections 4.1402 and 4.1705 from “DUNS number” to “entity identifier.” [1]

Those references show how far the identifier reached. GSA later listed the systems that used it: SAM.gov, the procurement data system, the subaward and subcontract reporting systems, and the performance and integrity systems. [5] A broken link in any of them breaks the trail the transparency laws were meant to create. [3]

Payment

The contracting officer had to put the identifier, and the EFT indicator if any, on documents sent to the payment office. [1] The payment office uses those to match an invoice to a registered bank account. In our reading, a mismatch here is a visible failure of a switch, because a vendor does not get paid.

Generic identifiers and their limits

Generic entity identifiers let a contract be reported without the contractor’s actual identifier in listed situations. [1] They were maintained by the Integrated Award Environment program office. [1] The rule said their use should be limited. [1]

A generic identifier hides the entity in the data. That is sometimes necessary, for example where disclosure would cause harm. Every use is also a gap in the transparency trail, so an agency would want to track how often it relies on them and why.

Matching name and address

The identifier had to correspond to the offeror’s name and address as stated in the offer and contract and as registered in SAM. [1] That ties identity verification to the identifier. Whoever issues the identifier decides how a legal entity’s name and address are validated.

In our reading, that is where the switch would be hardest. Validating that an entity exists and is who it claims to be is a service with its own data sources. Moving the identifier means moving or rebuilding that validation.

Subaward reporting

Prime awardees report on their subawards, and GSA later told them to use each subawardee’s own identifier when they do. [5] That reporting needs an identifier for the subawardee as well as the prime. Any switch therefore reaches entities that never registered fully with the government.

GSA’s later guidance showed how that played out. It told subcontractors and subrecipients that used DUNS for reporting to get the new identifier themselves. [4] It said a prime could not request one for its subawardee. [4] In our reading, that put a duty on smaller entities that the 2016 rule had described as unaffected unless the identifier changed. [1]

History and analytics

Federal spending data accumulates over years. In our reading, contract actions, subawards and performance records reported before a switch would keep the DUNS numbers they were reported under. Anyone analyzing spending by entity across a switch needs a crosswalk from old identifiers to new ones.

The 2016 rule did not address historical data. [1] That is a predictable gap in identifier changes. The forward path gets planned; the back catalog becomes a matching problem for every analyst who uses it.

Mergers, renames and moves

Entities change. They merge, rename themselves and move. The rule required the identifier to correspond to the offeror’s name and address in the offer, the contract and SAM. [1] Each change tests that correspondence.

Under DUNS, those updates ran through the supplier. After the switch, GSA said entities would make legal name and address updates through SAM.gov instead of going to Dun and Bradstreet. [5] In our reading, that moved a recurring maintenance task into the government’s own help desk and validation process.

Validation and integrity

The proposal said unique identification helps ensure federal dollars go to responsible parties. [3] That is an integrity function. The identifier is where checks on exclusions, past performance and ownership attach.

The later FAR overhaul proposal made the validation step explicit. Its proposed solicitation text said the government would independently validate the existence and uniqueness of an offeror before assigning an identifier. [8] In our reading, that sentence describes the service DUNS had bundled with the number in 2016. Whoever validates entities carries part of the government’s fraud control.

Systems outside the FAR

The FAR governs procurement. Grants and other assistance follow OMB guidance in title 2 of the Code of Federal Regulations. [7] The 2016 FAR rule did not change title 2. [1] A full switch had to reach both.

The proposal said the analysis of alternatives had to keep integrity protections for the needs of the loans, financial assistance and procurement communities, and of transparency communities. [3] In our reading, that breadth explains why a FAR change alone could not move the government off DUNS. Every community had its own rules and systems.

The deferred decision: what the rule left for later

What the rule said it did not decide

The councils were explicit. The scope of the rule was limited to removing the proprietary standard or number. [1] The analysis of alternatives and of considerations for evaluating them was beyond the scope of the case. [1] The councils said they would share commenters’ recommendations with the agencies doing that analysis. [1]

The proposal had described the process. OMB and the Treasury, with GSA and the Award Committee for E-Government, would establish a process for considering options. [3] It would include soliciting information about viable alternatives from all sectors, including private companies, nonprofits and federal providers. [3]

What the analysis had to weigh

The proposal said the analysis would maintain statutory and regulatory integrity protections for the needs of the awarding communities. [3] The final rule said the identifier provides multiple pieces of business information and serves multiple functions. [1] It said analysis would ensure any replacement satisfied the full range of information needed. [1]

That is a requirements list in outline. Any replacement had to identify, validate, link to payments and support reporting, across contracts, grants and loans.

Who was in charge

The rule named the players: OMB, the Treasury, GSA and the Award Committee for E-Government. [1] It did not name a deadline beyond the expected completion of the analysis in fiscal year 2017. [1] In our reading, splitting the decision from the rule was correct. It also meant the switch depended on a cross-agency process without a statutory date.

Why not decide in 2016

The councils had reasons to wait. The government was in the process of determining requirements, the rule said. [1] A replacement chosen before requirements were settled could repeat the lock-in. Commenters had offered at least two candidates. [1] In our reading, that pointed to no settled choice.

The rule also protected the status quo. By saying the government did not intend to move away from DUNS in the short term, it told vendors and agencies not to rebuild systems yet. [1] That avoided a scramble. It also meant no one had a date to plan for.

There was a sequencing logic too. The wording change could be done once, through a FAR case, with notice and comment already complete. [1][3] The systems change needed an identifier, a validation process and a migration plan, none of which existed in 2016. Doing the cheap, certain step first and the costly, uncertain step later is a defensible order.

Signals a planner could read in 2016

The rule gave planners three signals. The government did not intend to move away from DUNS in the short term. [1] The analysis of alternatives was expected to finish in fiscal year 2017. [1] And the regulation no longer stood in the way of a switch. [1]

A careful planner could act on those signals without guessing a date. It could stop hard-coding DUNS as a permanent key, tag where it was used, and watch for the outcome of the analysis. Those steps did not require knowing which identifier would win.

What a deferred decision costs

Deferral is not free. Every year of delay adds records keyed to the old identifier and systems built around it. The rule’s own figure of active DUNS numbers in SAM was a snapshot from June 2015. [1] In our reading, the count was likely to grow while the decision waited.

Deferral also leaves suppliers in a strong position during the wait. In our reading, the government’s bargaining position with the incumbent was best once a credible alternative existed and a switch date was set. The 2016 rule created the legal room for that, and the later process had to supply the rest.

What success would look like

The rule did not define success for a switch. [1] A program leader could set criteria in advance. Payments continue without interruption. Every active registration maps to one new identifier and one legal entity. Subaward reports keep flowing. Historical records stay traceable.

In our reading, those criteria belong in the plan before any date is set. They turn a technical migration into something an oversight body can check.

How the change landed on different parties

A federal contracting office

For a contracting office, the 2016 change was a vocabulary change. The forms were usable in their previous editions. [1] The work was in the systems that store and report identifiers, which the office did not own. The office’s main exposure was matching names, addresses and identifiers on each award. [1]

An agency finance office

A finance office pays against the identifier and the EFT indicator. [1] It owned the risk that a later switch would break payment matching. The 2016 rule gave finance offices a reason to inventory where DUNS was stored long before any switch date.

A state or local government receiving federal funds

States, counties and cities receive grants under title 2, not the FAR. [7] The 2016 FAR rule did not change their obligations. [1] Their exposure came later, when grant rules moved to the new identifier. Those governments also make subawards, and the current grant rules require first-tier subrecipients to have an identifier. [7]

A health system or university with federal grants and contracts

An academic health system may hold research grants, service contracts and subawards at once. Each runs through a different rule set. The identifier links them. The 2016 change was the first sign that the link would change, with no date attached.

Such an institution also makes subawards to partner sites and community organizations. Under current grant rules, it may not make a subaward to a first-tier subrecipient that lacks an identifier. [7] Its sponsored programs office therefore carries part of the identifier’s upkeep for others, which a switch would expose.

A contractor or vendor

The rule said it imposed no direct requirements on vendors. [1] It acknowledged vendors whose systems used DUNS could be affected if the identifier changed. [1] For a vendor, the prudent step was to stop treating DUNS as a permanent key in its own government contracts systems. A contracts team could add a separate field for the federal identifier, populated from SAM, and use its own internal key for everything else. That would turn a later switch into a data update rather than a rebuild.

A federal grants program office

A grants office works under title 2, not the FAR. [7] The 2016 FAR rule did not change its rules. [1] Its awards, though, sit in the same SAM registrations and reporting systems as contracts. [5] A switch in those shared systems would reach the grants office whatever its own rules said.

A grants office reading the 2016 rule would have asked when title 2 would follow. The answer would come through OMB guidance, which current 2 CFR part 25 now reflects. [7]

A prime contractor with many subcontractors

A prime contractor reports on its subcontracts; GSA’s fact sheet addressed primes that report subaward activity. [4] Its systems hold an identifier for each subcontractor. When the identifier changes, the prime needs its subcontractors’ new identifiers to keep reporting.

GSA’s later guidance put the duty on the subcontractors. It said a prime could not request a new identifier for a subawardee, and recommended that subcontractors share theirs with the primes that report on them. [4] A prime with a long supplier list would face a collection exercise as large as its own registration change.

A small business

Small businesses register in SAM to compete for federal contracts. The rule’s flexibility analysis said it imposed no direct requirements on vendors. [1] For a small firm, the practical effect in 2016 was none. Its exposure came at the switch, when it had to find and use a new identifier in its offers and invoices. [4]

The analysis also noted that some entities had arranged their own systems to use the DUNS number. [1] A small firm that keyed its accounting or proposal records to DUNS would carry that change itself.

A bank or lender in federal programs

Lenders that take part in federal loan guarantee programs deal with federal identifiers too. The current grant rules require recipients of a federal guarantee, such as lenders of guaranteed loans, to complete entity validation and acquire an identifier. [7] That rule is later than 2016. It shows the identifier reaching financial institutions through program participation.

Objections, in order

1. Changing words without changing systems achieved nothing

The rule did not move any system. [1] It did remove the need to amend the FAR before a switch. In our reading, that is a real gain. Regulatory change on the critical path of a technology switch adds risk and delay.

2. The government should have chosen a replacement in 2016

The councils said requirements were still being determined. [1] Choosing then could have locked in a second supplier or standard before the needs were clear. The cost of waiting was uncertainty for agencies and vendors. In our reading, waiting was the better of two imperfect options.

3. A pointer to a website is weak regulatory drafting

A definition that sends readers to sam.gov depends on what the website says. [1] That makes the rule’s practical content changeable without notice and comment. The trade-off was flexibility. In our reading, the risk is acceptable for an identifier, which is administrative, and would be harder to accept for a substantive duty.

4. Nonproprietary standards were already available

Commenters named the Legal Entity Identifier and the CAGE code. [1] The rule did not report an evaluation of either against the government’s full requirements, which included validation, payments and reporting across communities. [1][3] Availability is not the same as fit.

Each candidate also had its own reach. The CAGE code was already a government identifier, but the FAR treated it as a different identifier with its own subpart. [1] An international standard would bring its own governance and fees. In our reading, the government needed to weigh those features before choosing, which is what the deferred analysis was for. [1]

5. The cost argument was not quantified

The rule did not quantify savings. [1] It argued that removing a proprietary reference created opportunities for competition that could reduce costs. [1] That is a reasonable argument without a number. A procurement leader would want the number before the switch, not before the wording change.

6. A switch this large needed a statutory mandate

The transparency laws the proposal cited set duties to identify entities and trace spending. [3] They did not, as the proposal described them, name a supplier. The 2016 rule worked within that framework by removing the supplier’s name from the FAR. [1][3] A statute might have set a date. In our reading, the lack of one made the timeline depend on administrative will.

7. A government-run identifier only moves the cost inside government

It does. Validation, help desk work and entity updates become government tasks, as GSA’s 2022 bulletin later showed. [5] The cost is then visible in the government’s budget instead of in a supplier contract. In our reading, visible cost under the government’s control is easier to manage than a dependency priced by one supplier.

Checks a procurement or grants leader could run

The words

  • Find every rule, policy, form and contract template that names a supplier’s product where a function is meant.
  • Rewrite definitions by function and by pointer to an authority, as the 2016 rule did.

The lock-in

  • Set success criteria for any identifier switch before choosing a date.
  • List external identifiers and data standards your organization depends on, who controls each, and on what terms.
  • Separate the identifier from any data service bought with it.

The plumbing

  • Map where each identifier is stored, matched and reported: registration, award, payment, subaward reporting and analytics.
  • Name an owner for name and address matching, and test it on a sample of records.

The history

  • Keep a crosswalk from retired identifiers to current ones for every record that analysts or auditors use.
  • Check that reports spanning a switch date match entities correctly on both sides.

The deferred decision

  • For any planned switch, write down who decides, by when and against which requirements.
  • Keep vendors and partners informed of status, even when the answer is that nothing changes yet.

With hindsight

The switch came on April 4, 2022. A GSA fact sheet described the change as moving from the DUNS number to the Unique Entity ID (SAM), generated by SAM.gov. [4] It said that on April 4, 2022, the DUNS number would be removed and the new identifier would be authoritative. [4] It called the transition a governmentwide initiative. [4]

The fact sheet set out what entities had to do. Entities with an active or expired SAM registration already had a Unique Entity ID (SAM) and did not need to act. [4] Subcontractors and subrecipients that used DUNS for reporting had to get the new identifier before April 4, 2022. [4] It said a prime could not request one for its subawardee. [4] The CAGE code would not be affected. [4]

GSA confirmed the change in a bulletin dated April 5, 2022. The bulletin said that as of April 4 the Unique Entity ID from SAM.gov was the authoritative identifier for those doing business with the federal government. [5] It said the DUNS number was no longer valid for federal award identification. [5]

The bulletin named the systems. It said SAM.gov, eSRS, FSRS, FPDS, FAPIIS and CPARS, as well as all other GSA systems, were using only the Unique Entity ID. [5] It said entities would now update their legal business name and address through SAM.gov, not through Dun and Bradstreet. [5] In our reading, that moved the validation work the 2016 rule had left open into the government’s own system. [5][1]

The FAR definition did not change for that switch. As checked on November 16, 2026, 48 CFR 2.101 still defined a unique entity identifier with the 2016 wording. [6] It still directed readers to www.sam.gov for the designated entity for establishing unique entity identifiers. [6]

Grant rules followed their own path. As checked on November 16, 2026, 2 CFR part 25 defined the unique entity identifier as the universal identifier assigned by SAM.gov. [7] It required recipients to ensure first-tier subrecipients have one before making a subaward, without requiring full SAM registration. [7] Its source note cited a rule of April 22, 2024. [7]

The same part reached lenders. It said recipients of a federal guarantee, such as lenders of guaranteed loans, must complete entity validations and acquire an identifier. [7] That extended the identifier into financial institutions that take part in federal programs.

The FAR itself is now under review. On June 23, 2026, the FAR Council published a proposed rule overhauling FAR parts 1, 2, 4 and others, to implement Executive Order 14275. [8] Its proposed definition kept the 2016 approach: an identifier used to identify a specific entity, with a pointer to www.sam.gov. [8] Its proposed solicitation text said the government would independently validate the existence and uniqueness of an offeror before assigning an identifier. [8]

Comments on that proposal were due July 23, 2026. [8] As checked on November 16, 2026, we found no final rule from it in the Federal Register. Until one appears, the 2016 definition remains the text in force. [6]

What held up from 2016 is the drafting choice. A definition written by function and by pointer survived a change of issuer and a proposed overhaul of the FAR. [6][8] What the rule could not do was set the pace of the systems change, which arrived on April 4, 2022. [4][5]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • FAR
  • unique entity identifier
  • SAM.gov
  • vendor lock-in
  • grants
  • data standards