If you're reading this, you've probably got a SAM screen open in another tab with an error on it. You've already cleared your cache, tried a different browser, and maybe opened a ticket that hasn't gone anywhere. You're not doing anything wrong. Most SAM errors are matching problems or data problems, and the message on the screen almost never tells you which.
This is a lookup article. Find your symptom below, read the likely causes in order of how often they turn out to be the culprit, and work the fix. The last section covers something nobody writes down: how to get a Federal Service Desk ticket moving when it's been sitting for two weeks.
This is the most reported SAM error and one of the least explained. You're in the Assertions section, you've got your NAICS codes entered, you hit Save and Continue, and the page throws a generic failure. Nothing on screen tells you which field is the problem.
Start with the official step. If your work in progress is throwing errors, the documented advice is to delete that draft update and start the update over. That clears a corrupted draft, and for a fair number of people it's the whole fix. Do this before you go hunting.
If the error comes back, start looking at your NAICS list. This next part is practitioner troubleshooting rather than documented guidance, so treat it as a method that works in practice rather than an official diagnosis. In our experience the frequent culprit is one bad code in the list. Codes get revised, retired, and remapped on a cycle, and a code carried forward from an older registration can sit there looking perfectly normal. If your registration has been renewed a few times, you've got codes in there you haven't looked at in years.
Isolate rather than guess. Strip your list down to your primary code alone and save. If that works, add codes back in small batches, saving each time, until the save fails again. The batch that broke it contains your bad code. Split it and repeat until you've found the single code.
Starting the whole registration over from scratch is a different thing, and it usually doesn't help. Deleting a bad draft update is fine. Abandoning the registration itself and rebuilding it is not, because if you re-select the same codes from memory you'll re-select the bad one and hit the identical wall, having lost everything else you'd entered.
Worth knowing while you work, though this is practitioner observation rather than documented behavior: newer codes you add tend to appear at the bottom of the list rather than in numeric order, so check the bottom of the panel to confirm what actually landed after each batch.
If you strip down to your primary code alone and it still won't save, stop isolating. We've seen people do exactly that and hit the identical error with a single code selected, which tells you the problem isn't in your NAICS list at all. At that point the failure is somewhere else on the page or in the record behind it, and continuing to remove codes just costs you time.
Three things to check next. First, whether the PSC entries on the same page are the actual problem, since Goods and Services covers both and a Federal Supply Code entry with a missing place-of-manufacture answer can block the save just as effectively. Second, whether anything earlier in the registration is incomplete, because this page depends on data entered before it and a gap upstream can surface as a failure here. Third, whether the draft itself is corrupted, which is the case where deleting the work in progress and restarting the update genuinely is the fix.
If none of that clears it, this is a ticket, and it's a strong one. You've isolated further than most people ever do. Say in the ticket that the error reproduces with a single NAICS code selected and name the browsers you tested. That's a specific, reproducible report, and it's a different conversation than "the page won't save."
Overwhelmingly a name mismatch. The legal business name in your registration has to match IRS records character for character. That means punctuation, abbreviations, and spacing. "Smith & Sons, LLC" and "Smith and Sons LLC" are different names as far as the matching system is concerned. It has to be your legal name, not your DBA, and not whatever's printed on your bank account.
Pull out your IRS EIN letter and compare line by line. That's the CP 575 if you still have the original, or a 147C if you've requested a replacement. Either one shows the name the IRS has on file.
Second cause: a recently issued EIN. A brand new EIN takes time to propagate into the systems SAM checks against, and guidance on how long is genuinely inconsistent. Government quick start guides for SAM commonly tell you to allow about two weeks before a new EIN is ready to use, while some older guidance puts activation at two to five weeks. There's no single authoritative number.
What that means practically: if your EIN is less than two weeks old, wait before you keep trying, because you may be failing against a record that doesn't exist yet. If you're past two weeks and everything else matches character for character, propagation is still a plausible cause out to around five weeks, but at that point it's worth working the other possibilities rather than just waiting.
Third cause: an address problem wearing an EIN costume. Validation checks name and address together, and an address mismatch can surface as what looks like an EIN failure. Suite numbers getting stripped is a common one. P.O. boxes aren't accepted as a physical address.
This is where people lose the most time, because the rejection usually doesn't say what was wrong with the document.
The structural thing nobody explains: SAM's validation documentation requirements are split into two lists. One list proves your legal name and physical address. The other proves your entity start year and state. Most people submit one document, it only satisfies one list, and the submission fails. At least one of your documents has to show your legal name and physical address together, and you need something covering the start year and state too.
In our experience, bank letters get rejected and bank statements generally don't. This one is practitioner knowledge rather than a documented rule, but the reasoning holds up: banks write letters for banking purposes, not for federal validation, and they rarely contain the exact combination of information the reviewer needs. A bank statement in the legal business name showing the physical address is on the accepted list. A letter from your banker vouching for you usually isn't the document that clears this.
On the state side, what tends to clear validation is something stamped as filed with an authority or issued by the state: a Secretary of State certificate of filing, a certificate of good standing showing the date of incorporation or organization, or a stamped certificate of formation. Articles of Incorporation that aren't stamped as filed are a frequent rejection.
On the IRS side, the document that works is the CP 575 EIN confirmation notice, not the SS-4 application you filled out. The SS-4 is what you sent in. The CP 575 is what the IRS sent back. If your CP 575 is lost, the IRS won't reissue it, but you can request a 147C letter by phone through the IRS Business and Specialty Tax Line at 800-829-4933, and the 147C serves the same purpose.
Age rules cut both ways, and people get this backwards. Documents issued on a monthly or annual cycle, like bank statements and utility bills, have to be from the last five years. A state business registry screenshot is different: it has to be a current record pulled from the state's site, with the search result and the URL visible in the image. Foundational documents work in the opposite direction. Stamped articles of incorporation have no age limit at all as long as nothing has changed, so a filing from 1998 is fine if your name and address still match it.
One more: your documents have to show your entity information exactly as you typed it into the entity information screen. Not close enough. Exactly.
The SS-4 is what you sent the IRS. The CP 575 is what the IRS sent back. Only one of them clears SAM validation.
𝕏 ShareYou answered the ownership questions, or you think you did, and now the registration insists there's an immediate owner or highest level owner above you. You can't move forward and you can't find where to turn it off.
Check the ownership answers first. There are two separate questions: immediate owner and highest level owner. Both refer to legal entities, not individuals. If your company is owned by people rather than by another company, the answer to both is no. A yes answer carried forward from a prior registration is a common cause, because updates reuse your previous responses.
If the answers are right and the hierarchy is still there, ask where the data is actually coming from. When you report an owner, SAM verifies that owner's CAGE code against the Defense Logistics Agency's CAGE database, and CAGE records are assigned and maintained by DLA rather than by GSA.
One important caveat before you go calling DLA. If you have an active SAM registration, DLA generally won't change your CAGE record on a direct request. Updates to the CAGE master file for registered entities flow through your SAM update, which means the fix still runs through SAM even though the data lives in a DLA system. Going directly to DLA at cage.dla.mil is mainly the path when there's no corresponding SAM registration behind the CAGE code.
So the useful move is to ask the question, not to assume you're in the wrong queue. "Is this hierarchy data coming from SAM or from the CAGE record, and which system do I need to correct it in?" That's a question a first-level agent either answers or escalates, and either outcome moves your ticket.
The setting that controls this is called SAM Search Authorization, and it's the checkbox labeled "include in public search" during registration. Whether you provided it decides who can find you.
First, rule out the thing that looks like a problem and isn't. Entity searches on SAM require being signed in. If you or a customer searched while signed out and got nothing back, that tells you nothing about your settings, because signed-out searches return nothing for everyone. Even the largest federal contractors don't come up that way. So if support told you the answer was that people need to sign in, that was a real answer rather than a brush-off.
If you provided Search Authorization, any signed-in SAM user can find your registration, whether or not they have any connection to your company.
If you didn't provide it, your record doesn't appear in the public search display. The only people who can pull it up are users with a role on your entity and users signed in from a federal government email address. Everyone else gets nothing even when signed in.
Here's the test that actually tells you something. Sign in to SAM with a personal account that has no role on your entity, then search your legal business name or UEI. If you come up, Search Authorization is on and the problem is elsewhere, most often how the person searching is spelling your name. If you don't come up from an account with no role, the setting is off.
How to actually turn it back on: you can't just tick the box and walk away. You start an entity update, choose to update or renew the entire registration rather than a single section, step through to the page with the public search checkbox, check it, then continue all the way through and submit. The change doesn't take effect until that submitted registration finishes processing.
Two reasons not to leave it off. The HUBZone and 8(a) programs require your entity to be included in public search, so opting out can block you somewhere you weren't expecting.
And opting out isn't privacy. Your data is still released through FOIA requests, bulk data extracts, and the public API. All the setting does is keep you out of the search display on the site. If you turned it off expecting to be invisible, you aren't.
You formed in Delaware, you operate in Texas, and validation can't reconcile the two addresses. There's no special Delaware rule here and your structure is perfectly ordinary. It's the standard address-matching rules landing hard on a common setup: the registered agent address on your state record isn't where you actually work, and the matching system is trying to line up records that legitimately disagree.
Set your expectations accordingly, though. Ordinary doesn't mean quick. Address mismatches tend to be among the slower validation problems to clear, because the fix often runs through another organization's records rather than through SAM. Budget time and don't plan a deadline around a fast resolution.
Start with what's on your IRS documentation. The address on your CP 575 or 147C has to agree with what you put in the registration, because that's one of the records being matched against. If your IRS record still shows the formation address and you've entered the operating address, that's your mismatch.
Then make sure your documents cover both lists. Your state filing proves start year and state. Something else has to prove your legal name and current physical address together. A registered agent's address won't do that for you.
If the IRS has the wrong address, fixing it there first is usually faster than fighting validation around it. Just build in a wait afterward. An IRS record change needs time to propagate before SAM can match against it, so give it at least a couple of weeks rather than retrying the next morning against stale data.
SBA has been consolidating its federal contracting certification systems into MySBA Certifications, and the legacy portals people bookmarked years ago no longer go where they used to. HUBZone's old portal, for example, is no longer reachable through SBA Connect and now lives inside MySBA Certifications.
If you're locked out, don't assume your certification lapsed. Register with MySBA Certifications and claim your business there before you panic.
This migration has been running in stages and the details keep moving, so go to sba.gov and follow its current links to MySBA Certifications rather than trusting a bookmarked URL or any third-party walkthrough, including this one. Starting from SBA's own site means you land wherever the system actually lives today instead of wherever it lived when someone wrote an article about it.
Almost every person who ends up searching their error text at eleven at night has already opened a ticket. Many of them have waited weeks. Here's what actually changes the outcome.
Isolate the failure before you file. A ticket that says "the Goods and Services page won't save" gets a script. A ticket that says "this specific code blocks the save, reproducible in Chrome, Edge, and Safari on two devices" gets a human. Do the isolation work first, then file.
Include the exact error text, verbatim. Copy it character for character, including punctuation. Generic descriptions get generic answers.
State what you've already ruled out. Browsers tested, devices tested, cache cleared, codes removed. This single paragraph is what keeps you from getting the first-level troubleshooting script you already ran.
Ask explicitly for escalation beyond first level. You're allowed to do this. If the response you got doesn't address what you reported, say so directly and request escalation rather than restating the problem and hoping.
If there's a deadline, say so and give the date. A blocked grant award or a proposal due date is legitimate context and it affects how a ticket gets handled. Don't bury it.
Ask which system the bad data lives in. If your problem might be in the CAGE record rather than in SAM, ask which one holds it and which one you correct it in. It's a specific question that a generic answer can't satisfy, so it tends to either get you a real answer or get your ticket escalated.
Know the channels. The Federal Service Desk is at fsd.gov, with a web form, live chat, and phone support at 866-606-8220, Monday through Friday, 8 a.m. to 8 p.m. Eastern, excluding federal holidays. International callers use +1 334-206-7828. The web form is available around the clock. There's never a fee for FSD support, and there's never a fee to register in SAM.
A ticket that says "the page won't save" gets a script. A ticket naming the exact code that blocks the save, reproducible across three browsers, gets a human.
𝕏 ShareMost of these failures come down to the same thing: a system trying to match what you typed against a record held somewhere else, and finding a difference you can't see on your screen. Before you assume something is broken, pull your IRS letter and your state filing, put them next to your registration, and read them against each other line by line. A surprising number of multi-week tickets turn out to be a comma.
When you're stuck and there's a deadline attached: if you've been blocked for two weeks with an award or a proposal date hanging on it, you don't have time to keep guessing. Speak to a USFCR Registration and Contracting Specialist at (866) 216-5343. We work inside these systems every day and we know which failures are fixable in an afternoon and which ones need a ticket routed to a different office entirely.
Why does my Goods and Services page say something went wrong when I save? First delete the work in progress and start the update again, which is the documented step for a draft throwing errors. If it recurs, the frequent cause in practice is a NAICS code in your list that no longer maps cleanly, often one carried over from an older registration. Strip your list to the primary code, save, and add codes back in batches until the save fails to identify the bad one.
Should I delete my registration and start over if it won't save? Deleting a draft update that's erroring is the documented first step and often works. Abandoning the registration itself and rebuilding it from scratch is different, and it usually doesn't help, because re-selecting the same codes recreates the same failure after you've lost everything else you'd entered.
Why isn't my EIN recognized during SAM validation? Usually your legal business name doesn't match IRS records exactly, including punctuation and abbreviations. Compare your registration against your CP 575 or 147C letter character by character. The second most common cause is a newly issued EIN that hasn't propagated into IRS validation records yet. Guidance varies, but allowing about two weeks from the date on your IRS letter before attempting your registration is the common recommendation.
What's the difference between a CP 575 and a 147C? The CP 575 is the original EIN confirmation notice the IRS sends when your EIN is assigned, and it's never reissued. The 147C is the replacement verification letter you request if the CP 575 is lost. Both confirm the same information.
Why can't anyone find my entity in SAM search? First check how they searched. SAM entity searches require signing in, so a signed-out search returns nothing for every entity and tells you nothing. If they were signed in and still couldn't find you, you likely didn't provide SAM Search Authorization, the "include in public search" option. Test it by signing in with an account that has no role on your entity and searching your UEI. Turning the setting on requires a full entity update and resubmission, not just checking a box.
FAQ View full FAQ page: https://usfcr.com/resources/faq/
Top Articles
Writing a Winning Capabilities Statement in 2026