


Ask the community...
Pro tip: once you find your account number, write it down somewhere safe. You'll need it for weekly claims, job search activities, and any correspondence with Washington ESD. Don't rely on having to look it up every time.
UPDATE: I found it! It was in my SAW account under the claim details section like someone mentioned earlier. Thanks everyone for the help. For anyone else looking, it's not labeled very clearly but it's there near the top of the claim summary page.
Wait, are you the original poster? I thought Sophia Miller was looking for her account number, not Natalie Wang. Either way, glad someone found theirs! @Sophia Miller did you try the SAW account method yet?
Update: Just filed my claim for this week and found the question about having a definite date to return to work. I answered YES and provided my start date. The system accepted it and shows I should receive payment as normal! Thanks everyone for the help and advice. Will update again if there are any issues with payment.
Just wanted to add my experience - I had a similar situation about 6 months ago with a 10-day gap between accepting a job offer and my start date. The key is being completely transparent on your weekly claims. I answered YES to the "definite date to return to work" question and provided all the details they requested. ESD continued paying me until my actual first day of work with no issues at all. The only thing that caught me off guard was that they did ask for documentation later (just my offer letter showing the start date), so keep that handy just in case. Sounds like you're handling everything correctly though!
This thread has been super helpful! I'm saving it for reference during my unemployment period. The 26-week timeline gives me a clear goal to work towards.
One final note - if you do exhaust your regular 26 weeks of benefits, make sure to keep your Washington ESD account active and continue job searching. If the state's unemployment rate rises significantly, Extended Benefits could potentially become available, and you'd want to be ready to claim them.
Washington ESD typically announces Extended Benefits through their website and local media when they become available. It's triggered by specific unemployment rate thresholds.
Thank you everyone for all the helpful information! I feel much more prepared now. I'm going to start gathering my documents and continue job searching while I wait for my last day. Hopefully I'll find something before then, but at least I know I have options.
I'm sorry to hear about your situation Andre. As someone who works in HR, I can confirm that business closures definitely qualify for unemployment benefits in Washington. Since you've been there for 3 years, you'll easily meet the wage requirements. One thing I'd add that others haven't mentioned - ask your employer if they're providing any severance pay, as this might affect the timing of when your unemployment benefits start. Also, if your company has 50+ employees, they're required to give 60 days notice under the WARN Act, so you might have more time than you think. Keep your chin up - this kind of transition is never easy but you're taking all the right steps!
Geoff Richards
Update: Good news! The secure message worked. I sent exactly what was suggested, with the UCX reference and attached my DD-214. Got a response this morning saying they've reviewed my military service and removed the disqualification. Claim is now showing as pending payment instead of disqualified! Thanks everyone for the help. For any other military folks reading this in the future - definitely reference UCX specifically and have your DD-214 ready.
0 coins
Jacinda Yu
•That's great to hear! This is exactly why it's so important to be specific with UCX references. The system is designed to eventually work correctly for military claims, but you sometimes need to guide it to the right department. Glad you got it resolved!
0 coins
Aliyah Debovski
Congratulations on getting this resolved! This is such a valuable thread for other military members who might face the same issue. I'm bookmarking this for future reference. It's frustrating that the system doesn't handle UCX claims properly from the start, but at least there's a clear path to resolution. Thank you for updating us with the outcome - that really helps the community!
0 coins