I'm in a similar boat - my company just announced they're closing in 6 weeks and I'm trying to wrap my head around all this too. From what I'm reading here, it sounds like the main takeaway is to file immediately after your last day regardless of severance, but be prepared to report every severance payment which will likely zero out your benefits temporarily. One thing I'm still confused about - if we're getting severance paid out over multiple weeks, do we need to keep certifying every two weeks even though we know we won't get any UI benefits during that time? It seems like the answer is yes based on what everyone's saying, but I want to make sure I don't accidentally mess up my claim by not certifying during the severance period. Also, has anyone dealt with a situation where the company hasn't finalized the severance details yet? They keep saying "we'll let you know" but time is running out and I need to plan my finances. Should I be pushing HR harder for specifics?

I just went through this exact scenario when my retail job ended due to store closure in December. Here's what worked for me: File your UI claim the day after your last work day - don't wait! Your benefit year starts when you file, not when you receive payments. During the weeks you receive severance, you'll report it as "other income" and select "severance pay" from the dropdown during certification. This will likely result in $0 UI benefits for those weeks, but your claim stays active. The tricky part is the certification questions - they don't explicitly say "severance" so look for "Did you receive any other type of income?" and be sure to report only the amount you received during that specific 2-week certification period, not your total severance. Keep certifying every two weeks even when getting $0 benefits! I cannot stress this enough - skipping certifications can permanently mess up your claim. Once your severance payments end, your full UI benefits should automatically resume. Start documenting everything NOW: get your severance agreement in writing, keep records of payment amounts/dates, and clarify with HR whether it's true severance or "pay in lieu of notice" as this affects EDD processing. One last tip: continue your job search activities even during severance weeks. EDD still requires this and I've seen people get disqualified for not maintaining job search records during their severance period. The whole process was smoother than I expected once I understood the system. Good luck!

congrats!! good to know about that claimyr thing might try it next time i get stuck in edd hell lol

So glad you got this resolved! I'm dealing with a similar situation right now - my certification has been stuck in outstanding status for 4 days after I reported some freelance income. Reading through this thread gives me hope that calling is the way to go. I've been hesitant to try that Claimyr service since I'd never heard of it before, but seeing that it actually worked for you makes me feel more confident about giving it a shot. It's ridiculous that we have to pay a third party service just to talk to our own state agency, but if it gets results then it's worth it. Thanks for updating us with your outcome - these success stories really help when you're stuck in EDD limbo!

So glad you got through and got it resolved! This is exactly why I keep telling people about hidden flags in the system - there are so many technical glitches that create invisible barriers. I've seen the ID.me sync issue multiple times where people think they're verified but EDD's system shows something different. For anyone else reading this who might have similar pending issues, it's also worth asking the rep to check for any "stop payment indicators" or "eligibility review flags" that might not show up on your UI Online account. Sometimes there are multiple layers of holds that need to be cleared. Thanks for updating us with the resolution - it gives hope to others dealing with the same nightmare!

This thread is a goldmine of information! I'm dealing with a similar pending certification issue right now (going on 3 weeks) and reading through everyone's experiences gives me hope that there's actually a solution. I've been doing the endless calling routine like you were, Sean, but I'm definitely going to try the Claimyr service and also submit that specific "Pending certification with no issues identified" message through UI Online that Nia mentioned. It's so frustrating that we have to become detective-investigators just to get our rightful benefits, but at least this community shares the real strategies that actually work. Thank you all for being so detailed with your advice - it's clear everyone here understands the desperation and stress of dealing with EDD's broken system.

This thread should honestly be pinned to the top of this community! As someone who works in customer service for a different government agency, I can tell you that these special character database sync issues are unfortunately common across many older government systems. What Derek and others have experienced is a classic case of legacy databases that weren't designed to handle Unicode characters properly. The fact that ID.me uses modern character encoding but EDD's systems strip out or convert special characters during data transfer is a textbook example of poor system integration. For anyone still struggling with this, here are a few additional tips: 1) When you get through to an EDD rep, ask them to check not just how your name appears, but also ask them to verify the CHARACTER COUNT matches what's on your documents - sometimes invisible characters get added during transfers. 2) If possible, ask them to update your name in ALL their systems during the same call rather than just fixing one database. 3) Screenshot your successful login once you get it working - you'll want that exact format if you ever need to re-register. It's absolutely shameful that people have to become database troubleshooting experts just to access unemployment benefits, but this community knowledge-sharing is invaluable for navigating these broken systems!

This thread is an absolute goldmine for anyone dealing with EDD and special character issues! I'm new to this community but unfortunately not new to EDD problems. My wife has a hyphenated maiden name (Chen-Williams) and we've been stuck in the exact same loop Derek described for almost 2 months now. The ID.me verification was "successful" according to their system, but we keep hitting that dreaded "information doesn't match our records" error when trying to register for UI Online. We've been using telecert for now, but it's so limited compared to what you can do online. Reading all these success stories with Claimyr is giving me hope that there's actually a light at the end of this tunnel. It's honestly criminal that in 2025 we still have government systems that can't handle basic name formatting, but I'm so grateful for communities like this where people share real solutions. The technical insights from Sara and Ryder about database sync issues really help explain why this keeps happening to so many people. Going to try Claimyr first thing Monday morning and will definitely ask them to check ALL their systems like everyone has recommended. Thanks Derek for sharing your detailed experience and thanks to everyone else for adding their solutions - you're all heroes for helping people navigate this broken system!

As someone who's been working in senior advocacy for over a decade, I'm absolutely thrilled to see this thread and all the accurate information being shared! This misinformation about Social Security recipients not being eligible for unemployment benefits is one of the most persistent and harmful myths I encounter in my work. What makes me especially angry is that this false information often comes from employers and supervisors who should know better. Whether it's intentional (to discourage claims and keep their UI tax rates down) or just ignorance, the result is the same - seniors who have worked and paid into the system for decades are being denied benefits they've rightfully earned. Elijah, you did exactly the right thing by questioning what your supervisor told you and seeking out accurate information. Too many seniors just accept what they're told and miss out on thousands of dollars in benefits. Your question and this entire discussion thread is going to help countless other seniors who find themselves in similar situations. For anyone reading this who might face layoffs in the future: ALWAYS verify benefit eligibility directly with the appropriate agency (EDD for unemployment, SSA for Social Security issues) rather than taking an employer's word for it. And don't let anyone make you feel guilty for claiming benefits you've paid into through decades of hard work!

I'm new to this community but had to jump in after reading through this incredible thread! I'm 64 and have been terrified about what would happen if I lost my job since I started collecting Social Security last year. My HR department actually told us in a meeting that "people on Social Security can't collect unemployment" - and I just accepted it as fact! Reading everyone's experiences here has been both a huge relief and really frustrating. It's clear this misinformation is absolutely everywhere, and who knows how many seniors have missed out on benefits they deserved because of these lies. Elijah, thank you for having the courage to question what your supervisor told you instead of just accepting it. This thread is going to be a lifesaver for so many people! I'm bookmarking it and sharing it with my senior center - I bet there are others there who have been given the same wrong information. To all the people who shared their stories and expertise here - THANK YOU. You've literally changed how I think about my financial security in retirement. If I ever face a layoff, I'll know exactly what to do and won't let anyone discourage me from filing for benefits I've paid into for 40+ years of working!