Independent, not SAM.gov

The CAGE code is now a view, not a value: what Oct 2026 changes

Updated 6 October 2026

ZeroGov covers US federal contracting from the contractor side, and we are independent of SAM.gov and of the General Services Administration. With the SAM.gov move into the IAE architecture in October 2026, the CAGE code is no longer a box you fill in. That small change has outsized consequences for offers, payment files, and past performance citations, so the rest of this page walks through what changed, what stayed, and what to verify before you sign anything this week.

What the CAGE code actually is, in one paragraph

Commercially and Government Entity, written CAGE, is a five character identifier that the Department of Defense assigns to any entity that does business with the federal government, and that other agencies reuse through interagency agreements. The first character locates the country, the next four are a sequential assignment that the Defense Logistics Agency manages in its capacity as the NATO codification bureau for the United States. The code rides inside your SAM registration, in your invoices through the System for Award Management payment profile, and in every offer you submit through SAM.gov, PIEE, or the procurement system an agency uses.

Until October 2026 the CAGE appeared in the SAM registration form as an editable field once a registration was active. You could read it on your record, copy it, and paste it into a SF 33, a SF 1449, or a vendor cover letter. The form, however, never let you type the value. The platform always asked the Defense Logistics Agency for it behind the scenes, stored it on your entity record, and presented it back to you. The change in the IAE architecture is that the form no longer shows a CAGE field at all. The code lives in a service the IAE platform calls, and the SAM.gov screen renders the five character string as a read only line near the legal business address.

What is moving where, and what the contractor sees

The Integrated Award Environment is the General Services Administration program that consolidates the federal procurement backend, and the SAM.gov registration interface is one of its component services. In the first week of October 2026 the SAM.gov registration was migrated to the IAE architecture, with a read only weekend, a Tuesday cutover, and a week of observed quirks documented in earlier ZeroGov posts. The migration is partly cosmetic and partly structural. On the cosmetic side, the page that used to say CAGE Code at the top of the entity summary now reads Commercial and Government Entity code, with a tooltip that explains the acronym and an information icon that opens a glossary entry. On the structural side, the field is no longer part of the editable entity record. It is a computed view.

In practical terms, a contractor who signs in to SAM.gov on or after October 6, 2026 sees the five character code rendered next to the legal business address, with a small refresh icon and a creation date. Hovering or tapping the icon re issues a request to the CAGE service. The request is fast on weekdays and slow on Sundays because the Defense Logistics Agency batch assigns new codes in business hour windows, but existing codes are returned immediately. A contractor who needs the value in another system copies it from the SAM.gov summary or pulls it from the entity API endpoint that the IAE now publishes under the SAM data services contract.

The old path through a CAGE Code Request tool, where a contractor filled out a web form to ask for an assignment before a SAM registration existed, has been retired and folded into the same service. A new entrant who tries to register a brand new entity without a CAGE now sees a placeholder that reads Pending CAGE assignment, and the assignment lands on the record within one business day. Awarding activities that used to wait two business days for a code to populate a vendor record can now treat the placeholder as a signal to look again tomorrow, since the integration between the assignment service and the SAM data store is event driven rather than nightly.

Why the change matters for offers, payment, and past performance

Three workflows touch the CAGE code on a recurring basis, and each one is affected in a small but specific way.

First, offers. A solicitation that flows through SAM.gov, the Procurement Integrated Enterprise Environment, or a service like the DoD Enterprise Procure to Pay system expects the offeror to include the CAGE code on the SF 33 or SF 1449, and on cover sheets that the agency format requires. The agency compares the value you type to the value the IAE returns when the procurement system calls the entity API. Under the old regime a typo in the SAM field could survive for years because the form accepted any five character string. Under the new regime the IAE returns a canonical value, the procurement system rejects mismatches at offer receipt, and the contractor is forced to fix the record before the solicitation closes. ZeroGov has seen three different award offices post notices in the last week reminding offerors that offer receipt errors are not curable after the closing time, so a wrong CAGE in the offer is now a fatal flaw rather than a curable deficiency.

Second, payment. Invoices submitted through the Invoice Processing Platform, the Wide Area Workflow, and the Department of Defense third party payment systems index payees by CAGE and by taxpayer identification. The IAE migration changed the way the payment office reads the SAM registration. The payment system still pulls a canonical CAGE from the entity record, but the system no longer falls back to a value the offeror typed into a proposal. If the SAM registration is in a Submitted state, the payment system reads the prior active CAGE and accepts the invoice. If the SAM registration is in a draft state because the contractor abandoned the renewal, the payment system rejects the invoice at the header level and routes the rejection back to the contractor with a code that reads Vendor record not active in SAM. We will dig into that error code in a separate post, because the language is new and the help desk traffic in the week after the cutover has been heavy.

Third, past performance. The Contractor Performance Assessment Reporting System, the Architect Engineer contractor performance system, and the various agency scorecards identify the performer by CAGE. A past performance citation that names a CAGE that has been superseded because the contractor changed the legal business address and triggered a re assignment will fail a source selection evaluation check if the offeror does not explain the change. Under the new architecture, the CAGE that the IAE returns is the one that the SAM registration currently has, not the one that was active when the past performance was recorded. ZeroGov recommends that offerors run a quick CAGE history report through the entity API before submitting any source selection response in November and December 2026, so the evaluator does not have to ask for clarification.

What this page is not

This page is not a SAM.gov help article. We are not affiliated with the Integrated Award Environment, the General Services Administration, the Defense Logistics Agency, or the Office of Management and Budget. We do not speak for the contractor support desk, and we do not have the ability to look at your specific entity record. Treat the SAM.gov help articles, the IAE release notes, and the Federal Service Desk ticket tracker as the authoritative sources for your own registration.

This page is also not legal advice. If the CAGE re assignment has implications for a size protest, a service disabled veteran owned small business status, a HUBZone status, an 8(a) admission, or a small business set aside challenge, talk to counsel. The size standards and the affiliation rules are independent of the identifier, and the IAE migration did not change those rules.

How to verify your CAGE before the next deadline

The fastest way to confirm the CAGE that the IAE has on file is to sign in to SAM.gov, open the entity summary, and read the line under Commercial and Government Entity code. The value updates in place when the legal business address changes, and the platform shows a short audit note that names the address that triggered the update. If you want a machine readable view, the IAE entity API returns a CAGE object that includes the current value, the assignment date, and the country code that the Defense Logistics Agency uses to issue the prefix.

For contractors who are mid registration, the workflow is to finish the entity record, submit the registration, wait for the Entity Validation Service to return a result, and then refresh the entity summary to see the CAGE. The validation step is the gating event, and it is unchanged by the IAE migration. Contractors who are mid renewal should pay particular attention to the renewal deadline, because the 60 day window that the SAM renewal rule describes is independent of the CAGE display, and a lapsed registration will still show a CAGE on the read only view while the registration status reads Expired.

For contractors who need to change the CAGE because the entity underwent a merger, a sale, or a legal name change, the right tool is the entity registration edit, not a CAGE Code Request. The CAGE service listens to the entity registration edit, the address change, and the legal business name change, and it issues a new code when the change is material. The old code is retired 30 days after the change is published. During the 30 day window both codes resolve to the entity, and the procurement systems accept either one. After 30 days only the new code is valid.

Common questions contractors ask this week

Contractors ask whether the CAGE is now optional. It is not. The federal acquisition regulation still names the CAGE as the data element that the contracting officer verifies at award, and the System for Award Management still requires the entity record to be active. The change is in the surface, not in the rule.

Contractors ask whether they need to download a CAGE certificate. The DoD no longer issues a paper or PDF certificate for the CAGE. The IAE summary page is the source of record, and contractors who need to attach a CAGE reference to an offer attach the SAM.gov summary print or paste the value into the offer cover sheet. A copy of the SAM.gov summary is not a substitute for a representation or certification, and the offer is still governed by the representations and certifications that the offeror signs.

Contractors ask whether the change breaks the entity API. The IAE entity API still returns the CAGE under the same field name, and the response shape is backward compatible. The new behaviour is the inclusion of a derivation object that lists the inputs the platform used to compute the code, which is useful for debugging but not required for normal use.

Where to watch in the next thirty days

The next batch of IAE release notes is expected in the second half of October 2026, and the release notes are likely to describe the path to a fully event driven assignment service that returns a CAGE within seconds rather than within a business day. The Office of Management and Budget is also expected to publish a memorandum that aligns the federal procurement data standards with the new entity record, and the memorandum will name the CAGE as a derived data element rather than a stored one.

For contractors, the practical watch list is short. Confirm the legal business address. Confirm the entity registration status. Read the CAGE line. Make sure the value is in every offer, every invoice header, and every past performance citation. Treat the CAGE as a calculated view, and treat the inputs to the calculation as the record you maintain. ZeroGov will continue to track the IAE migration, the FAR remap, and the contractor experience in the coming weeks.

Independent information, not legal advice. Confirm status and rules on sam.gov and the current FAR text.