Back to Washington Unemployment

Mason Davis

ESD missing employer information have you worked what does it mean on my weekly claim?

Okay so I've been filing my weekly claims for about six weeks now and everything was going fine until this week when I hit a totally different screen. It's asking about employer information and there's this question that just says something like 'have you worked' but then it seems like it's pulling up an employer that I don't even recognize. Like the name showing up isn't any place I've ever worked at, at least not that I can remember. I've been in retail for about 12 years hopping between a few different companies so I guess it's possible something old is in there but this feels wrong. I don't know if this is some kind of identity thing or if ESD just has bad data on me. I've tried submitting the weekly claim but it won't let me get past this screen without answering whether I worked for this mystery employer. I don't want to say yes and accidentally trigger some adjudication nightmare. I don't want to say no and have it look like I'm hiding something either. Has anyone run into this 'have you worked' prompt with an employer that doesn't match your actual work history? What does it mean and what am I supposed to do?

Wait, is the employer name completely foreign to you or could it maybe be a parent company? That trips people up all the time. Like I thought I never worked for some company called 'Retail Holdings Group' but that was actually the corporate owner of the store chain I was at. Worth checking before anything else.

0 coins

Looked it up just now and yeah it doesn't match any parent company I can find for my last employer. It's like a completely different industry even. This is so weird.

0 coins

Same thing happened with mine, turned out to be a staffing agency. I'd done a one-week temp thing years back and totally forgot about it. ESD had it though lol.

0 coins

Honestly the fastest thing I'd do in your position is call ESD directly to have them look at what's actually on file for your account before you answer anything on that screen. The 'have you worked' question with an unrecognized employer is usually either a data pull from wage records submitted by an employer you forgot about, or occasionally a mismatch from someone else's account. Either way you need an agent to see the actual wage record tied to that employer name before you accidentally confirm or deny something that could flag your claim. Getting through to ESD by phone though is its own battle. I found Claimyr at claimyr.com and it basically gets you connected to an ESD rep without you having to sit on hold forever or keep redialing. There's a demo video at https://youtu.be/7DieNd3C7zQ that shows how it works. I used it when my own claim had a weird employer flag and had an agent on the line within the same day who could actually pull up my wage history and explain what was showing.

0 coins

Trying Claimyr right now actually, I really can't afford to mess this up by guessing.

0 coins

Does that actually work for ESD specifically? I've been burned by services that claim to help with government agencies before.

0 coins

Used it for ESD myself, that's how I know. The video demo at the link shows the actual process.

0 coins

Pull up your wage and salary history first thing - you can actually see this in your eServices account under the earnings tab. ESD uses wage records submitted by all your employers going back several years to prepopulate that 'have you worked' question. Sometimes employers report wages under a business name that's different from the storefront you worked at. I'd cross-reference what's showing in your wage history with the employer name on that claim screen before calling anyone.

0 coins

Finding that tab now, hadn't even thought to look there. Good call.

0 coins

This is the right move. The wage records section saved me so much confusion when I had a similar thing come up. The name in my records didn't match what I thought I worked for but it was totally legit.

0 coins

Just want to add - if you do see a wage record from an employer you genuinely never worked for, that could be a wage theft or identity situation and ESD has a specific process for disputing those. But try Claimyr to get an actual agent first because they can flag it internally while you're on the call. The site is claimyr.com and it cuts through the hold time problem.

0 coins

ugh ESD data is SO unreliable. I had an employer show up in my claim that had been out of business for literally four years. The system just keeps old records alive forever apparently. I spent two weeks in adjudication because I answered that question wrong without knowing what the employer was first. Don't do what I did, do NOT answer until you know exactly what you're confirming.

0 coins

Two weeks in adjudication just from that one answer? That's exactly what I'm afraid of.

0 coins

Yeah it was awful. They wanted pay stubs, separation documents, everything from a job I hadn't thought about in years. Eventually resolved but it delayed payments significantly.

0 coins

This tracks. Adjudication gets triggered when your answers don't align with what wage records show, or when there's any hint of unreported earnings. The system flags it automatically. Getting ahead of it by understanding the employer record first is so much smarter than answering blind.

0 coins

wait does this mean ESD can see every job you ever had going back forever?? asking because i have some old jobs i kind of forgot to put on the initial application and now im nervous

0 coins

Not forever, wage records typically go back around five to six years but it depends on what employers reported. The initial application asks about recent employment to establish your base year, which is roughly the first four of the last five completed calendar quarters. If you had something outside that window it's probably not relevant to your current claim, but if something is inside that window and matches what ESD has on file, discrepancies can cause problems.

0 coins

ok that makes me feel slightly better. mine was way older than that so hopefully fine.

0 coins

Something I'd look at immediately - does the employer name on the claim screen have any similarity to a business name that might have changed? Companies get acquired and rebrand all the time. I had 'GreenLeaf Distribution LLC' show up and I was totally confused until I realized it was a produce company I did seasonal work for that had been bought out and renamed. The EIN stayed the same so ESD still connected it to me even though the name meant nothing.

0 coins

Going back through my work history with this in mind. I did have one job where the company merged with something bigger partway through my time there.

0 coins

That's probably it then. When a company merges or gets acquired mid-employment the wage reporting can get messy in ESD's system. The agent should be able to reconcile it pretty quickly once you're actually talking to one.

0 coins

Acquisition and rebrand situations are genuinely the most common reason for mystery employer names from what I've seen in this forum. Usually pretty easy to clear up once you have the context.

0 coins

okay I looked into Claimyr after the mention above and I actually used it this morning for a different ESD issue. Got through in about two hours vs the week I spent trying to call normally. For this specific situation it makes sense because you really do need an agent to look at the wage record on the back end, that's not something you can fully see yourself through eServices.

0 coins

Glad to hear it works, I'm already in the queue.

0 coins

two hours is wild compared to what i normally experience calling ESD. usually i give up after getting disconnected twice.

0 coins

Yeah the disconnect thing is brutal. The Claimyr system holds your place so you don't have to stay on the phone the whole time.

0 coins

The 'have you worked' question with an employer pulldown is part of ESD's crosscheck process against quarterly wage reports that every Washington employer has to file. Here's the thing though - the question isn't necessarily asking if you recognize the employer name. It's asking if you performed work and received wages from an entity that reported wages under your Social Security number. So the cleaner way to think about it: did you work somewhere and receive a paycheck during that period, even if the name showing doesn't match what you'd call that employer? If yes, you generally answer yes. If you have literally no recollection of any work connected to that entity at all, that's when you need to look deeper before answering.

0 coins

That reframing actually helps. So it's less about the company name and more about whether I earned wages in that period.

0 coins

Exactly. The name in ESD's system comes from how the employer registered with the state, not necessarily what they call themselves publicly. Your answer should reflect the reality of your work history, not whether the name rings a bell immediately.

0 coins

This is a really good way to explain it. I wish someone had told me this when I had a similar question pop up. I panicked and answered wrong and had to file an amended explanation.

0 coins

Has anyone considered this could be a straight up error on ESD's end? Like they misassigned someone else's wage record to your account? It happens more than you'd think, especially with common names. My cousin had someone else's employer showing up and it took months to untangle.

0 coins

Real possibility. That's actually the most urgent version of this problem because if someone else's wages are attached to your SSN, that affects your base year calculation and your benefit amount, not just your weekly claim.

0 coins

Exactly, and ESD is not quick to fix it on their own. You have to push on it.

0 coins

Had something similar once. My advice would be to get through to ESD by phone as soon as possible if you think it's a data error rather than a forgotten employer. I used Claimyr to skip the hold nightmare - claimyr.com - and it got me in touch with someone who could actually see the wage records tied to my account and start a correction request on the spot. Much better than trying to handle identity or data errors through the message system.

0 coins

following this thread because i have a question thats kind of related - what happens if you skip the 'have you worked' question entirely and just submit? Does it let you?

0 coins

Try submitting a claim without completing required fields and you'll hit a validation error. ESD's system won't process an incomplete weekly claim. You'd just be stuck at the same screen.

0 coins

ugh okay so there's literally no way around answering it. thanks for saving me from trying that.

0 coins

Yeah no shortcuts unfortunately. That question is a required field for a reason.

0 coins

My situation last year was almost identical to this - found out that the mysterious employer ESD had on file was actually a company I'd done a trial shift for. Like a one-day thing, they paid me a small amount, and apparently they reported that to the state. I had completely forgotten about it and it still showed up years later causing confusion on my claim. Even tiny amounts of wages get reported if the employer follows proper procedure.

0 coins

Oh wow, a trial shift would never have crossed my mind. Thinking back now there was something like that at a coffee place I tried before my retail career took off.

0 coins

That's probably exactly it then. ESD sees everything that gets reported to the state tax agency. Even one-day placements, training periods, some internships if they were paid.

0 coins

This is why the wage history tab in eServices is so valuable, it shows you everything on record so you can figure out where these employer names are coming from.

0 coins

Just want to give an update from my own experience since this thread is still going - I had the same 'have you worked' mystery employer situation about three months ago. Used Claimyr to get an ESD agent and they walked me through my entire wage record history on file. Turned out to be a staffing agency that placed me for a week a couple of years back. The agent noted in my file that I'd called to verify before answering, I answered honestly, and the weekly claim went through with no adjudication at all. That prior call and verification apparently mattered. The agent said noting your attempt to verify before answering actually helps if anything does get flagged later.

0 coins

That is incredibly reassuring to hear. The idea that proactively calling to verify before answering could actually protect you from adjudication issues is exactly the kind of thing I would never have known.

0 coins

Definitely worth the effort to call first. And yeah Claimyr at claimyr.com made it actually possible to reach someone the same day instead of hoping to get through after a week of trying.

0 coins

The 'noted the call in your file' thing is really interesting. ESD agents can annotate your claim and that annotation becomes part of your record if anything is ever reviewed later.

0 coins

Can I ask a dumb question - once you answer the 'have you worked' question correctly and get past it, does it keep asking you about that same employer every week? Or is it a one-time thing?

0 coins

Generally it's tied to your base year wage history so it would only come up if ESD needs to verify those wages once during your claim period. For most people it's a one-time verification, not a recurring question each week.

0 coins

Okay that's a relief. The thought of navigating that every single week sounded exhausting.

0 coins

Mine only came up once. After that the weekly claims went back to normal. The system just needed that verification to close out the wage crosscheck.

0 coins

something that helped me understand all this better was the ESD website actually has a section explaining how they verify wages through employer quarterly reports. its dry reading but if you search within the ESD site for 'wage verification' you can find it. explains why employers you don't immediately recognize still appear - its based on tax reporting not on what you remember the place being called

0 coins

Bookmarking that, appreciate it.

0 coins

Yeah took me a while to figure out that ESD's view of your work history comes from the state tax side, not from what you put on your initial application.

0 coins

What I'd do if I were you - before even calling, write down every single job you've had in the last five or six years, including short term stuff, temp placements, one-off gigs where you got a check, anything. Then compare that list against what's in your wage history on eServices. The employer name on the claim screen should match one entry in your wage records. If nothing on your list could possibly explain it, then yes it's potentially a data issue. But most people, when they really think hard, find something that explains it.

0 coins

Did this exercise and found two jobs I'd kind of glossed over mentally as 'tiny' because they were so short. One of them might be the match.

0 coins

Yeah the tiny ones are always the culprit. People remember their career jobs but forget the two-week thing they did between bigger roles.

0 coins

Great advice. The mental accounting of your own work history is always less complete than what the state has on file. They see every payroll tax submission.

0 coins

Not sure if this helps but when I was in a similar situation my ESD agent told me that answering 'no' to 'have you worked' for an employer that actually paid you wages, even if you forgot about it, can get flagged as an inconsistency because their wage records will show the wages were paid. It's not necessarily treated as fraud if you just forgot, but it does put your claim into a review state. Whereas if you answer 'yes' and it turns out to be an error in ESD's data, that's also a problem but easier to correct with documentation. Neither wrong answer is great but the data error one is at least fixable with proof.

0 coins

This is really helpful context for understanding why getting it right the first time matters so much.

0 coins

Exactly why getting an agent to look at the actual wage record before you answer is the smarter path if there's any uncertainty at all.

0 coins

wait so they can tell if you answer no but actually worked there? like they can see the discrepancy?

0 coins

Yes, the wage records submitted by employers are in ESD's system regardless of what you answer. Your answer is checked against what they already have.

0 coins

Circling back to give this thread a bit of closure since OP seems to have figured out next steps - the core takeaway here is that the 'have you worked' question with an unrecognized employer name means ESD's wage records tied to your SSN contain an entry from that employer. It could be a name mismatch, an acquisition, a temp placement you forgot, a trial shift, or in rarer cases an actual data error. The correct response order is: check your wage history in eServices, try to match it to your actual work history, call ESD if you can't reconcile it before answering, and answer based on actual wage receipt not on name recognition.

0 coins

This is basically the perfect summary of everything I've learned in this thread. Thank you to everyone who replied, genuinely.

0 coins

Well said. The name showing in ESD's system comes from employer registration and tax reporting, it was never designed to match what you'd call the place. Thinking about it in terms of 'did I receive wages in this period' rather than 'do I recognize this name' is the right frame.

0 coins

Good thread overall. These kinds of questions don't have obvious answers from just reading the ESD instructions and it helps to hear from people who've been through it.

0 coins

Washington Unemployment AI

Expert Assistant
Secure