Back to Arizona Unemployment

Adriana Cohn

DES weekly certification excessive earnings earnings allowance not subtracted - what's happening?

Something is seriously off with my benefit calculations and I can't figure out if I'm reading the portal wrong or if DES actually made an error. I work part-time right now - picked up some shifts at a distribution warehouse about 3 weeks ago while still collecting UI. I reported every dollar I earned on my weekly certifications, no problem there. But when I look at my payment history, it looks like DES just... deducted my FULL gross wages from my benefit amount instead of only taking the portion above the earnings allowance. Like they didn't apply the allowance at all before doing the math. So instead of getting a reduced benefit check I'm getting zero, or sometimes like $12. I should be getting somewhere around $190-$210 per week even with the hours I'm working because I'm not earning anywhere near enough to disqualify myself. My weekly benefit amount was set at $385 when I was approved. Has anyone run into this where the earnings allowance just wasn't factored in? Is this a system glitch or am I misunderstanding how the calculation is supposed to work?

Claimyr is genuinely the move here if you need to get someone at DES on the phone fast - claimyr.com is the site and there's a video showing how it works at https://youtu.be/vwA1GGuV83Y. I had almost the exact same calculation mess on my account last year where my partial wages were being applied wrong, and the only way I actually got it fixed was talking to a live agent who could see the backend of my claim. The hold times through the regular DES line were brutal - I tried for two weeks before finding Claimyr. Once I got through to an agent they corrected the payment calculation same day.

0 coins

Checking that video out right now, this is exactly the kind of thing where you need a human to look at the actual numbers.

0 coins

Going to look into this - been trying the DES line since Tuesday and it just disconnects me every time.

0 coins

Used it last spring for a different issue. Worked for me too.

0 coins

Your weekly benefit amount of $385 means your earnings allowance should be around $96 before DES starts reducing your payment dollar for dollar. So if you earned say $200 gross in a week, they should subtract $200 minus $96 which equals $104, and then your benefit would be $385 minus $104 which is $281. If instead they're just doing $385 minus $200 and paying you $185, or worse doing $385 minus $385 and zeroing you out, that's definitely a system error or a data entry issue on how your earnings were coded. Pull up each week's payment detail screen in the UIBENEFITS portal and screenshot everything before you call.

0 coins

Pulling those screens up right now - yeah it looks like they skipped the allowance step entirely and just took the whole wage amount off the top.

0 coins

The math you laid out is exactly right, the allowance is 25% of WBA for Arizona. OP's should be $96.25 to be precise.

0 coins

Wait so the allowance is based on the WBA not some flat number? I had no idea it was calculated that way, I thought it was always just a set amount.

0 coins

First thing I'd do in your spot is grab those payment detail pages for each week in question and write down exactly what numbers appear next to 'gross wages reported' vs 'wages applied.' Sometimes the portal shows the full wage in one field but the actual deduction field shows the correct reduced amount - the display can be confusing. The underlying rule is that only whatever you earned above 25% of your weekly benefit amount should count against your payment. If the deduction field is showing your full gross wages with no subtraction for the allowance, that's a genuine miscalculation and you'll need to get it corrected through DES directly.

0 coins

Checked every week - the 'wages applied to benefit' field is showing the entire gross amount, not the reduced figure. So the system definitely isn't applying the allowance before that step.

0 coins

Same exact issue hit me in December. The agent I eventually reached said it can happen when part-time wages get entered under the wrong earnings code and the system treats them differently.

0 coins

Had a similar display thing happen to me and it turned out the portal was just showing me one number but paying another - worth confirming by checking your actual bank deposits against what the payment summary says.

0 coins

Another angle worth trying - Claimyr helped me get through to DES when I had a payment discrepancy that had been sitting unresolved for almost a month. I'd given up on the phone queue entirely. The agent I spoke with could actually pull up my individual weekly certifications and see where the system had flagged my wages incorrectly. For something like a DES weekly certification excessive earnings earnings allowance not subtracted situation, you pretty much need a rep to manually review the certification records because the online tools don't let you contest a calculation error directly. Site is claimyr.com.

0 coins

Appreciate this - going to try it today. I need this sorted before my next certification is due Thursday.

0 coins

A month sitting unresolved, that's rough. DES really doesn't make it easy to flag calculation errors through the portal alone.

0 coins

Agreed, there's no 'dispute this calculation' button anywhere I've ever found on the UIBENEFITS site.

0 coins

Something that tripped me up early on - the earnings you report are supposed to be gross wages for the week you WORKED them, not when you got paid. If your pay periods straddle certification weeks you might be doubling up wages in a single certification period by accident, which could make it look like you earned way more than you actually did that week and push you over the threshold. Worth double-checking which week each shift actually falls in.

0 coins

Went back through my timesheets - I've been reporting by work week correctly, not by pay date. So that's not the issue here.

0 coins

This mix-up trips so many people up though. Good call flagging it.

0 coins

Yep worked for me wrong in that exact way my first month on UI. Overstated earnings by like $300 because I was going by my paycheck date.

0 coins

Real question - does the earnings allowance reset every week or is it like a cumulative thing for the benefit year? I've been doing partial UI for two months and I genuinely don't know if I've been calculating this right.

0 coins

Each week stands on its own - there's no carryover from one certification period to the next. Every week DES looks at what you reported for that specific week and applies the 25% allowance fresh.

0 coins

Rechecking all my past certifications right now then, I may have been misreporting.

0 coins

Totally separate calculation every week, nothing rolls over. You'll want to verify each one individually on the portal payment history page.

0 coins

ZERO payment on weeks where you clearly have earnings below the disqualifying threshold is a red flag. That shouldn't be happening. DES sometimes miscodes self-employment wages differently than W2 wages, could something like that have happened with how your warehouse job is classified? Like did you get a 1099 from them or W2?

0 coins

Definitely W2, it's a regular employer, nothing freelance about it. So that classification issue shouldn't apply.

0 coins

Then yeah it really sounds like either a data entry error on DES's end or a glitch in how your wages were processed when you first reported them.

0 coins

The 1099 vs W2 coding thing is real, it happened to my cousin and took forever to fix because the agent had to reclassify the income type manually.

0 coins

Before calling, it helps to have your employer's name, your hire date with them, and the exact gross dollar amounts for each week ready to read off. When I had a payment calculation issue last fall the agent asked me for all of that upfront and it made the call go a lot faster. Having the portal open on a second screen while you're on the phone helps too so you can read the specific field names they're asking about.

0 coins

Writing all that down now - WBA, weekly gross amounts, specific weeks affected, employer info. Good call.

0 coins

Claimyr is what finally got me through to someone worth talking to after I'd been ghosted by the standard queue for weeks - claimyr.com - and when I did get through I had everything prepped like you're describing and the agent fixed my calculation error while I was still on the line. The prep really does matter.

0 coins

Having your claim ID number handy too speeds things up a lot. It's on every portal screen in the top right.

0 coins

My agent last year told me that when partial wages are entered manually by a DES employee rather than auto-imported through the wage reporting system, the allowance calculation sometimes doesn't trigger automatically. It's supposed to but there's apparently a step someone has to check off. Could be what happened here.

0 coins

That would explain a lot actually - especially if my employer hasn't been submitting wage data electronically and someone at DES had to key it in.

0 coins

Claimyr got me to an agent who explained almost this exact same thing to me - there's apparently a backend flag that has to be set for the partial wage formula to run, and if it's missing the system defaults to full deduction. The fix on their end takes maybe five minutes once they find it. claimyr.com if you need to get through without spending your entire morning on hold.

0 coins

Manual entry issues are way more common than DES lets on. The automated wage match system is supposed to catch most of this but it doesn't catch everything.

0 coins

Have you filed any kind of inquiry through the portal message center about this? Sometimes sending a written message creates a paper trail even if nobody calls you back right away. At least then you have a timestamp showing you flagged it before the next certification.

0 coins

Sent a message through the portal on Wednesday - no response yet. At this point I'm not waiting on that and trying to get a live person instead.

0 coins

Yeah the message center is basically a black hole for anything time-sensitive. Worth having as a backup record though.

0 coins

Never gotten a reply through the portal message system in under 10 business days personally. Phone is the only way for anything urgent.

0 coins

Can I ask what your average part-time hours look like per week? Because I'm wondering if maybe you're right at the edge of where the allowance kicks in and your situation is actually correct, just counterintuitive. Like if your gross wages are very close to your WBA the payment really can drop close to zero legitimately.

0 coins

Earning about $155-$175 gross per week. With a $385 WBA and $96 allowance I should still be getting around $200+ after the reduction. I'm definitely not near the cutoff.

0 coins

Yeah at those numbers you're right, that's clearly not a legitimate zero-payment situation. Something is off on their end.

0 coins

The disqualifying threshold is when gross wages equal or exceed your WBA, so with a $385 WBA you'd need to earn $385 or more in a single week to get zeroed out legitimately. At $155-175 you should absolutely be receiving a partial benefit.

0 coins

Something nobody has mentioned - when you certified, did the system give you a confirmation screen showing a pending payment amount or did it just say 'submitted' with no dollar figure? Sometimes a weird certification screen interaction is a clue that something got flagged on the backend during that specific week.

0 coins

Each week it showed a pending payment amount that looked reasonable, then later when I checked back the payment history showed the wrong lower amount. So the initial estimate was right but the actual payment was wrong.

0 coins

That's really useful info - means the initial calculation was correct and something downstream changed it. Definitely a backend issue, not a reporting error on your part.

0 coins

This narrows it down. The certification itself processed fine - whatever went wrong happened at the payment calculation stage after. That should be easier for an agent to trace and reverse.

0 coins

these things drag on FOREVER if you don't stay on top of them. I had a similar partial payment miscalculation for 6 weeks before I finally got through to someone and they had to process a bunch of corrected payments all at once. start pushing hard now before it compounds.

0 coins

Already four weeks behind on this. Really need to get it resolved before the next one hits.

0 coins

four weeks is fixable, I've heard of people getting 10+ weeks corrected at once. don't stop calling.

0 coins

DES can and does issue corrected payments going back multiple weeks when it's their calculation error. Make sure you document exactly which weeks are affected.

0 coins

For anyone reading this later - the standard partial UI formula in Arizona works like this: take whatever you earned, subtract 25% of your weekly benefit amount, then subtract that result from your WBA. If the number comes out positive you get paid, if it comes out negative or zero you don't. The system is supposed to do this automatically but clearly that doesn't always happen. The key document that explains all of this is the UI claimant handbook, section on partial benefits, though honestly calling DES is faster than trying to decode that doc.

0 coins

Saving this explanation - way clearer than anything I found on the DES website.

0 coins

Does this formula apply the same way for every week regardless of whether you worked full weeks or partial weeks?

0 coins

Same formula applies regardless of hours - what matters is the gross dollar amount you earned that week, not the number of hours. DES doesn't care if you worked 2 hours or 20 hours, only the dollar total goes into the formula.

0 coins

Went through almost this identical situation and want to share what actually resolved it for me. After finally reaching an agent they found that my wages were being pulled in through an employer wage match that was categorized as 'full week earnings' instead of 'partial week earnings' in their system. The wrong category bypasses the allowance calculation entirely and treats your wages like you were fully employed. Once they fixed the category code the corrected payments went out within a week.

0 coins

This sounds exactly like what might be happening to me. Going to specifically ask an agent to check that earnings category code when I get through.

0 coins

This is valuable info. The category code thing is not documented anywhere on the claimant-facing side of the portal.

0 coins

Writing 'check earnings category code' on a sticky note for my next call. Good to know this is a specific thing they can look at.

0 coins

Random but make sure you're not accidentally hitting the 'full-time employment' radio button on your weekly certification instead of 'part-time' - sounds dumb but I did it once and it zeroed out my payment for that week because the system treated me as fully employed. Had to call in and get it manually corrected.

0 coins

Went back and checked - all certifications show 'part-time' correctly. But good thought, that would do it.

0 coins

Yeah just figured I'd throw it out there, the simplest things sometimes cause the biggest headaches.

0 coins

Quick update request - will you post back here when you get it resolved? I'm having a weirdly similar issue starting this week and want to know what actually worked for you.

0 coins

Will update once I get through to DES. Going to try the Claimyr route today since the regular line keeps dropping me.

0 coins

Following this thread. Good luck.

0 coins

Same, would love to know the resolution especially what the actual cause was.

0 coins

One more thing - if DES corrects the calculation and issues back payments, those corrected amounts count toward your maximum benefit amount for the year just like normal payments. So your total benefit entitlement for the year stays the same, you're just getting the weeks you were underpaid corrected. Doesn't extend your benefit year or anything like that.

0 coins

Good to know - I was going to ask about whether back payments affect the benefit year total.

0 coins

Correct on all counts. The corrected payments fill in the originally underpaid weeks, they don't add new weeks to your entitlement.

0 coins

UPDATE: Got through to a DES agent this morning. The agent confirmed the earnings category issue - my employer wage data was imported under a code that bypassed the partial wage formula entirely. She corrected it on the backend and manually recalculated all four affected weeks. Corrected payments for the difference are showing as pending in the portal already. Total they owe me is about $812 in underpayments across the four weeks. Really glad I pushed on this because I genuinely would have let it go thinking I was misunderstanding the formula. If you're seeing this same problem - zero or near-zero payments when you're only working part-time - it's worth fighting.

0 coins

Came back to say thank you for updating. Calling first thing tomorrow.

0 coins

Exactly the category code issue I described. Glad you got it sorted and $812 is not nothing - worth every minute of that hold time.

0 coins

Great outcome. Those backend coding errors are surprisingly common and they'd just sit there forever if claimants didn't push to get them fixed.

0 coins

This whole thread is going to help people. The earnings allowance not being applied is a real thing that happens and now there's an actual documented fix.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure