< Back to California Unemployment

Amara Okonkwo

EDD certification page won't accept fractional hours - need urgent help

I'm completely stuck on my bi-weekly certification! When reporting my work hours, I need to enter 32.5 hours for a part-time job I picked up last week, but the EDD system keeps rejecting decimals or fractions. When I try to enter '32.5' it gives me an error saying 'please enter a valid number.' If I round up to 33, my reported wages won't match my actual earnings, but if I round down to 32, I'm under-reporting. Has anyone else dealt with this technical glitch? What's the proper way to report partial hours on UI Online? I don't want to get flagged for incorrect reporting, but the system literally won't accept my actual hours worked!

don't stress too much, just round up to 33 hours. the system doesn't accept decimals, never has. the small difference in wages isn't going to trigger any red flags.

0 coins

Amara Okonkwo

•

Thanks for responding! Are you sure rounding up is the right approach? I'm worried because my employer will report the exact hours/wages, and I don't want any discrepancies.

0 coins

The EDD system is designed to only accept whole numbers for hours worked. The official guidance is to round to the nearest whole hour. In your case, since 32.5 is exactly halfway, you could technically round either way, but I always recommend rounding up to be safe. The small difference in reported wages (half hour's worth) won't trigger any issues, especially if you explain the rounding in the additional information section at the end of the certification. Just add a brief note stating your actual hours were 32.5 but you had to round due to system limitations.

0 coins

Dylan Hughes

•

Actually, this is incorrect advice. EDD specifically states you should round DOWN, not up. Their internal systems reconcile this. I worked for EDD for 7 years and this was always our guidance to claimants.

0 coins

NightOwl42

•

OMG I HAD THE EXACT SAME PROBLEM LAST MONTH!!! I worked 18.75 hours and couldn't enter it! I called EDD like 47 TIMES trying to get through to ask about this. FINALLY got someone after 3 days who said to just round to nearest whole number and make a note in the comments section. The whole system is SO STUPID and outdated, they seriously need to fix this!!! Why build a system that can't handle basic decimals in 2025?!?!

0 coins

Amara Okonkwo

•

Did you have any issues after you submitted with the rounded number? No flags or problems with your payment?

0 coins

I remember having this exact problem! I just rounded down and moved on with my life. Never had any issues.

0 coins

Dylan Hughes

•

This is a common question. The EDD system only accepts whole numbers for hours worked. The correct procedure is to round DOWN to the nearest whole hour. So in your case, enter 32 hours. This is the official EDD policy - they know their system has this limitation and their internal processes account for minor discrepancies during employer verification. Make sure your reported wages are exact to the penny though, as those must match employer records precisely. The hours field is primarily used for calculating your hourly rate to ensure it meets minimum wage requirements.

0 coins

Amara Okonkwo

•

Thank you for the clear explanation! I'll enter 32 hours and make sure my wages are exactly correct.

0 coins

Dmitry Ivanov

•

Here's what I learned during my unemployment journey - fractional hours are indeed a problem with the EDD system. After struggling to get through on the phone lines for days (constant busy signals and disconnections), I found Claimyr.com which connected me to an EDD representative in about 20 minutes. The agent confirmed I should round to the nearest whole hour and ensure my wages are exact. You can see how their service works in this video: https://youtu.be/JmuwXR7HA10?si=TSwYbu_GOwYzt9km. Saved me so much frustration when I had questions like this that weren't clearly explained on the website.

0 coins

Ava Thompson

•

is that service legit? sounds too good to be true with how impossible it is to reach edd

0 coins

Dmitry Ivanov

•

Yes, it's legitimate. I was skeptical too but it worked for me when I was desperate to get an answer about my certification. Saved me days of constant redialing.

0 coins

guys are overthinking this waaay too much lol. i've been on unemployment 3 times and always just rounded however was easiest. nobody at edd is gonna come after you for a half hour difference... they got bigger fish to fry

0 coins

Amara Okonkwo

•

UPDATE: I ended up entering 32 hours as suggested and made sure my wages were exactly correct to the penny. I also added a note in the comments section explaining that I worked 32.5 hours but rounded down due to system limitations. My certification went through without any issues! Thanks everyone for your help with this frustrating technical limitation.

0 coins

Great to hear! Adding the comment was a smart move. That creates a record of your intention to be accurate in case there's ever a question later.

0 coins

NightOwl42

•

When I had this problem last year I just decided to always work whole hours LOL! I literally told my boss I can only work in full hour increments because the EDD system is so bad. Surprisingly he was cool with it since he knew how important my UI benefits were during my partial employment. Maybe ask your employer if you can work rounded hours to avoid this whole mess?

0 coins

That's actually pretty clever! Wish I'd thought of that.

0 coins

Anthony Young

•

This is such a common frustration with the EDD system! I've been dealing with UI certifications for a while now and can confirm that the system absolutely does not accept decimal hours - it's been like this for years unfortunately. The safest approach is to round DOWN to the nearest whole hour (so 32 in your case) and make sure your wage amount is exactly correct to the penny. The EDD's internal systems are designed to handle these minor discrepancies during employer verification, and they prioritize wage accuracy over precise hour reporting. Always add a note in the comments section explaining the actual hours worked vs. what you entered due to system limitations - this creates a paper trail showing your good faith effort to be accurate. It's frustrating that a government system in 2025 can't handle basic decimals, but at least now you know the workaround!

0 coins

Amara Okafor

•

Thank you for the detailed explanation! This is really helpful for anyone dealing with this issue. I'm glad to see there's a consistent approach that works - rounding down and adding that explanatory note seems to be the consensus from everyone who's actually dealt with this. It's ridiculous that we have to work around such basic system limitations, but at least there's a clear path forward that won't get us in trouble.

0 coins

I had this exact same issue a few months ago! The EDD system is definitely outdated when it comes to handling fractional hours. What worked for me was rounding DOWN to 32 hours (as others have mentioned, this seems to be the official guidance) and making sure my wage amount was precise to the penny. I also wrote a brief note in the additional comments section saying something like "Actual hours worked: 32.5, rounded down due to system limitations." Never had any follow-up issues or flags on my account. The key thing to remember is that EDD's backend systems are built to handle these small discrepancies - they know their own system's limitations. Your employer will report the exact hours/wages to EDD separately, and their reconciliation process accounts for rounding differences in the hours field. Just make sure those wage dollars and cents are exactly right!

0 coins

Chris King

•

This is really reassuring to hear from someone who's actually been through this! I was so worried about getting flagged for inaccurate reporting, but it sounds like EDD's backend systems are designed to handle these rounding discrepancies. The tip about making sure the wage amount is exact to the penny while allowing flexibility on hours makes total sense. I'll definitely follow this approach - round down and add that explanatory note. Thanks for sharing your experience!

0 coins

Julian Paolo

•

I just went through this same nightmare last week! The EDD system really is stuck in the stone age when it comes to basic functionality. After reading through all the responses here, it's clear that rounding DOWN to the nearest whole hour is the way to go - so many people have confirmed this approach works without issues. What really helped me was calling it out explicitly in the comments section with something like "Actual hours: 32.5, entered 32 due to system limitation." The wage amount being exact to the penny seems to be what really matters for their verification process. It's honestly embarrassing that a state system can't handle decimals in 2025, but at least there's a proven workaround that won't get you flagged. Hope this helps future people dealing with the same frustrating limitation!

0 coins

Thanks for adding another data point! It's really helpful to see so many people confirming the same approach. I was initially worried about the discrepancy between what I report and what my employer reports, but seeing all these success stories with rounding down + explanatory notes makes me feel much more confident. It's wild that we all have to deal with this workaround for such a basic feature, but I'm grateful this community exists to help navigate these system quirks. Definitely going with the round down approach and detailed comment - seems like the safest path that won't trigger any red flags.

0 coins

Carmen Reyes

•

I've been certifying for UI benefits for over a year now and this fractional hours issue comes up constantly in this community! Based on all the responses here and my own experience, the consensus is definitely clear: round DOWN to the nearest whole hour (32 in your case) and make absolutely sure your wage amount is precise to the penny. I always add a note in the comments section like "Actual hours worked: 32.5, rounded to 32 due to system limitations" - this shows good faith reporting and creates documentation if there's ever a question. The EDD's verification systems are built to handle these small hour discrepancies since they know their own system can't accept decimals. What matters most for matching employer records is that wage amount being exact. It's frustrating that we have to work around such a basic limitation, but this approach has worked consistently for everyone I've seen try it. Don't stress too much about the half-hour difference - focus on getting those wages reported accurately!

0 coins

Mei Wong

•

This is exactly the kind of comprehensive advice I was looking for! It's really reassuring to hear from someone with over a year of experience dealing with these certifications. The "round down + explanatory note + exact wages" approach seems to be the gold standard based on everyone's responses here. I was initially panicking about this technical glitch, but seeing so many people successfully navigate it with the same method gives me confidence. It's honestly ridiculous that EDD's system can't handle basic decimal entry in 2025, but I'm grateful this community exists to help newcomers like me figure out these workarounds. I'll definitely go with rounding down to 32 hours and adding that detailed comment - thanks for taking the time to share your experience!

0 coins

Aisha Ali

•

I'm dealing with this exact same issue right now! It's so frustrating that the EDD system can't handle something as basic as decimal hours in 2025. Reading through all these responses has been incredibly helpful - it sounds like the consensus is definitely to round DOWN to the nearest whole hour (so 32 in cases like this) and make sure the wage amount is exactly correct to the penny. The advice about adding an explanatory note in the comments section seems really smart too - something like "Actual hours worked: 32.5, rounded to 32 due to system limitations." It's reassuring to see so many people confirm this approach works without triggering any flags or issues. Thanks everyone for sharing your experiences - this community is a lifesaver for navigating these ridiculous system limitations!

0 coins

California Unemployment AI

Expert Assistant
Secure

Powered by Claimyr AI

T
I
+
20,087 users helped today