Back to Arizona Unemployment

Dylan Cooper

DES inactive claim backpay owed after returning to work - what happens now?

So my situation is kind of a mess and I'm hoping someone here has dealt with something similar. I was laid off back in January, filed my Arizona DES unemployment claim, and got approved without any issues. I was filing my weekly certifications every Sunday like clockwork, reporting zero wages, doing my job search activities. Everything was going fine until I got a job offer in mid-March and started working again. Here's where it gets complicated. I accepted the job and just... stopped filing. Nobody told me I was supposed to do anything special, I just figured the claim closed itself out when I stopped certifying. My new employer pays every two weeks so there was about a 10-day overlap period right when I started where I technically wasn't earning anything yet from the new job but I'd already stopped claiming. Fast forward to now - I went back into my UIBNEFITS.AZ.GOV account to check something and noticed my claim shows as 'inactive' but there's also a note about a potential balance remaining. I did some math and I think Arizona DES might actually owe me backpay for that gap period between when I stopped certifying and when my first paycheck from the new job actually hit. We're talking maybe $680-$720 in benefits I never claimed. Can I even go back and file those weeks now? The weeks in question are from March. My claim isn't closed, just inactive. I'm fully employed now but if DES actually owes me money for those certified weeks I missed, I want to know if I can still get it. Has anyone navigated this before?

Dealing with an inactive claim that might still have backpay sitting on it - yeah this is actually more common than people think and it's genuinely frustrating to figure out on your own. I went through almost the exact same thing last year when I went back to work and left money on the table because I didn't know what to do. Here's the thing though - before you do ANYTHING with those missed weeks, you need to actually talk to a DES agent directly. Not the automated system, not the portal messages that take three weeks to get a response. An actual human who can look at your claim and confirm whether those weeks are still certifiable and what the proper process is for submitting late certifications. I know calling DES feels impossible but I found something called Claimyr that actually got me through to a live agent without spending my entire day redialing. The site is claimyr.com and there's a video showing exactly how it works at https://youtu.be/vwA1GGuV83Y - it basically handles the hold queue nightmare for you. When I finally got through, the agent was able to tell me exactly which weeks were still open for late certification and walked me through submitting them. Saved me from just guessing and potentially messing up my claim.

0 coins

The part about talking to an actual agent first - are you saying the portal itself won't let you file those weeks, or that it technically might let you but could cause problems if you do it without guidance first?

0 coins

Filing late without checking first is what I'd warn against. The portal might show those weeks as available but if you submit wages or zero wages incorrectly for a week that overlaps with your return-to-work date, DES can flag it for adjudication and then you're waiting weeks for review instead of just getting the payment. An agent can mark the weeks appropriately before you certify so the system doesn't kick it back.

0 coins

Claimyr worked for my sister when she had an overpayment dispute - she said the hold time was way shorter than calling directly. Definitely worth trying if you need to actually reach someone at DES.

0 coins

The claim showing inactive with a remaining balance - that actually tells you something important. DES doesn't close out a claim and wipe the balance just because you stopped certifying. The benefit year is still active, usually 52 weeks from your initial claim date, and any weeks you didn't certify during that period are potentially still accessible depending on how late you're filing. What state your claim is in matters a lot here. 'Inactive' just means no recent activity, not that it's terminated. You'd want to check if your original benefit year end date has passed - if it hasn't, those weeks from March are probably still certifiable through the UIBENEFITS portal.

0 coins

Checked my benefit year end date and it shows July 2025, so I'm still within the window. Does that mean I can just go certify those weeks directly in the portal, or is there an extra step because they're so far back?

0 coins

Being within your benefit year is the first box checked. The portal typically allows backdated certification for weeks that are past due, but there's usually a limitation - DES allows late certifications going back a certain number of weeks before they require manual processing by an agent. Weeks from March filed now in May might be right at the edge of that window. Try accessing the certification section and see if those weeks appear in your available queue. If they do, proceed carefully with accurate wage reporting.

0 coins

I thought once you stopped claiming for more than like 30 days the whole thing just expired automatically. Sounds like that's not actually how it works?

0 coins

The 30 day thing is a pretty widespread misunderstanding - I believed the same thing honestly. What actually happens is the claim goes into inactive status, not terminated status. Those are genuinely different things in the DES system. Terminated means your benefits ended for a specific reason, inactive just means you stopped submitting certifications. The underlying benefit year and any remaining balance are still there until the year actually expires.

0 coins

Something I'd double-check before certifying those missed weeks - when you started the new job in mid-March and there was that 10-day gap before your first paycheck, were you technically still available for work during that gap? Because you said you HAD accepted the job offer already. I'm asking because DES's able and available requirement is about whether you're genuinely available to accept full-time work, not just whether you're currently earning wages. If you'd already accepted and committed to the new position during that gap period, there's an argument that you weren't fully 'available' in the DES sense even though you hadn't been paid yet.

0 coins

That's a point I hadn't thought about. I had accepted the offer but hadn't signed anything formal - it was a verbal acceptance. My actual first day of work was March 17th. The gap I'm talking about is roughly March 10th to March 17th, the week before I started. Would that week be the problem or would weeks before the offer even factor in?

0 coins

The week before your actual start date where you'd verbally committed - that one is genuinely gray area and an agent would need to assess it. Weeks before you received or accepted the offer should be clean since you were actively job searching and available. It's really just that final pre-start week that might get scrutinized if you certify it. Report everything accurately and let DES make the determination rather than leaving the money unclaimed because you're unsure.

0 coins

The available for work definition always trips people up. I used to think it meant physically able to show up somewhere, not all the conditions around it. The DES definition includes not just physical availability but also whether you have anything that would prevent you from accepting work if offered - which a pending start date technically could be depending on how strict the reviewer is.

0 coins

Went through almost this identical situation - inactive claim, realized I had uncertified weeks, tried to figure out if I could still get that money. The DES portal is genuinely confusing about this because it doesn't just show you a clear list of certifiable past weeks the way you'd expect. After spending two days trying to navigate the portal and getting nowhere with the phone queue, someone in another thread pointed me to Claimyr at claimyr.com - there's a walkthrough video at https://youtu.be/vwA1GGuV83Y that explains the service. It connected me to a DES agent who pulled up my claim, confirmed which weeks were available for late certification, and noted on my account that I was processing backdated weeks so it wouldn't trigger a fraud flag. That last part is apparently really important - agents can add notes to your claim that essentially pre-clear the late submission.

0 coins

Wait - there's actually a fraud flag concern with filing these late? That's something I definitely need to know more about. What triggers that exactly?

0 coins

Submitting certifications for a string of weeks all at once, especially after a gap, can get flagged by DES's automated system as potentially suspicious activity even when it's completely legitimate. The system sees multiple certifications submitted in rapid succession for past weeks and sometimes kicks them into adjudication review. Having an agent document the reason for the delay on your account essentially tells the system it's expected activity. It doesn't always happen but it's a real risk if you just go certify 4-5 weeks all at once without any prior contact.

0 coins

This thread is making me realize I might have the same issue from earlier this year. Filed about 6 weeks of claims and then landed a contract position and just stopped without doing anything official. Never thought there might be money sitting there.

0 coins

Sounds like your situation mirrors the OP's pretty closely. Worth logging into your UIBENEFITS account and checking the claim status and benefit year end date before that window closes on you.

0 coins

One thing worth mentioning that I haven't seen brought up yet - when you do certify those missed weeks, the wage reporting for the week you actually started working is different from the gap weeks before it. For the weeks you were fully unemployed and job searching before mid-March, you'd certify zero earnings. For the week that contains your actual first day of work, you need to report the actual gross wages you earned that week even if your first paycheck hadn't been issued yet. DES goes by when wages were earned, not when they were paid. So if you worked three days in a pay period, you report those days' wages for that week even though you hadn't received a check.

0 coins

So the week I started, March 17th, I'd report just the wages for March 17th through whatever the end of the DES week is, right? Not the full first paycheck amount?

0 coins

Exactly that. DES benefit weeks run Sunday through Saturday. So whatever you earned from your first day through that Saturday is what gets reported for that week - multiply your hourly rate by hours worked or if salaried divide your weekly rate proportionally. Your UI benefit for that week would then be reduced based on those partial earnings, not eliminated entirely unless you earned over your weekly benefit amount.

0 coins

The earned vs paid distinction is what messes people up constantly. Someone gets their first paycheck two weeks after starting and assumes they had zero income for those first two weeks because they hadn't been paid yet. Then they certify zero wages and get the full benefit amount and suddenly DES comes back with an overpayment notice months later. Report what you earned when you earned it.

0 coins

Overpayment notices months after the fact based on wage records from employers - yes, this is how a lot of overpayments happen. DES cross-references earnings through the state's wage reporting system and if what an employer reported doesn't match what you certified, you get an overpayment determination. The penalty interest and collection process is way worse than just getting a slightly smaller benefit check upfront.

0 coins

okay so reading this I'm confused about something - if you're already back to work full time, like fully employed now, why would DES even pay those back weeks? don't you have to be unemployed to get the money? I thought it only paid out for weeks when you actually needed it

0 coins

The benefits are for weeks that already happened when you were unemployed and eligible - not for your current situation. Those March weeks existed, OP was unemployed and certifiable then, they just didn't file. The payment would be retroactive for those past weeks of unemployment, not for right now. Being employed today doesn't erase the fact that you were eligible during those specific past weeks.

0 coins

oh ok that makes sense, so its like claiming money you were already owed just didn't collect it yet

0 coins

Basically yes. It's the same as if someone forgot to cash a paycheck from three months ago - the work was already done and the money was already earned, they just hadn't collected it.

0 coins

The fact that your account shows a note about a potential remaining balance is actually a good sign - it means DES's system itself is flagging that there's unresolved money, not that everything closed out cleanly. I've seen accounts where the balance just shows zero after inactivity so the fact yours explicitly notes something owed suggests those weeks are still accessible. One thing I'd recommend - before you certify anything, take screenshots of your current account status showing that balance note. If anything goes sideways during the late certification process you'll have documentation of the account state before you touched it.

0 coins

Screenshots - honestly would not have thought of that but it's a smart move. Taking those right now actually.

0 coins

Covering yourself with documentation is never overkill with DES. Date and timestamp the screenshots if possible. Also if you end up talking to an agent, write down the date and time of the call and the agent's ID number if they provide one. Having a paper trail of your good-faith effort to properly handle the late certifications protects you if DES later questions why you filed those weeks months after the fact.

0 coins

Agent ID number thing is SO important. I had an agent give me wrong information once about my job search requirements and had no way to prove what I was told. Now I log every single call.

0 coins

I want to bring up something that might be relevant depending on how much time has actually passed. DES has provisions for late certification but there's a point at which the late filing requires a specific waiver request rather than just normal portal submission - I believe it's something like 28 days past the week in question but I might be slightly off on the exact number. If March weeks are now beyond that window, you might need to submit a written request explaining why you're certifying late rather than just going in and certifying normally. I'd actually tried to do this after coming back from medical leave once and ran into this exact wall - ended up having to go through a whole separate process. On that note - I'd used Claimyr a couple times by then to reach DES agents and by that point I'd figured out you can actually explain the specific situation before the agent picks up so they're somewhat prepared for the conversation when they answer. Made those calls a lot more efficient than just reaching an agent cold.

0 coins

The 28-day window you're mentioning - that would potentially put some of my March weeks in the waiver territory depending on the exact dates. If it's a waiver request, is that filed through the portal or is it a separate paper form?

0 coins

The waiver request process for late certifications, in my experience, was initiated through a phone conversation with an agent who then documented it on the claim and sent follow-up instructions. I don't think there's a self-service portal option for it - it goes through agent-assisted processing. Which is another reason talking to someone before you do anything else makes sense.

0 coins

The window for normal late certifications versus the waiver process - does anyone know if that window is a hard cutoff or if it has exceptions? Like would a situation where someone didn't know they could claim those weeks count as an exception?

0 coins

From what I understand it has exceptions but DES doesn't advertise them widely and they're handled on a case-by-case basis. Not being informed that late certification was possible is probably a reasonable basis for an exception request but you'd have to make that case to an agent or potentially in writing.

0 coins

There's something that tripped me up for a long time that this whole situation is bumping up against - I used to assume that DES automatically notifies you when there's money sitting on your claim that you haven't collected. Like I figured if there was backpay owed, they'd send me a letter or an email or something. Turns out that's not really how it works. DES doesn't proactively chase you down to tell you to come claim your benefits. The balance sits there, the benefit year counts down, and if you never certify those weeks before the benefit year expires the money just goes away. I found this out the hard way when a benefit year ended and I had three unclaimed weeks that just evaporated.

0 coins

Three weeks of benefits just gone because nobody told you? That's genuinely awful. DES really should have some kind of notification system for uncertified weeks.

0 coins

There's technically a notification in the portal but it's not exactly prominent and if you've stopped checking your account regularly because you're employed you'd never see it. I checked my account every week religiously when I was unemployed and barely at all once I had a job - which is exactly when the notification about uncertified weeks would have been visible.

0 coins

This is why I always suggest people stay logged into their UIBENEFITS account even after going back to work, at least until the benefit year closes out officially. And if you need to actually resolve anything or confirm the account status with a real person, that's what I ended up using Claimyr for - claimyr.com - because the online portal questions only go so far and sometimes you need an actual agent to tell you the balance is real and the weeks are still open.

0 coins

Something nobody has mentioned - when you went back to work did your employer or HR say anything about DES or unemployment when you were onboarding? Some employers, especially larger ones, have HR staff who actively report new hire start dates directly to DES. I'm not saying this to scare you but it's worth knowing that DES may already have a record of your employment start date in their system from the employer side. This is actually fine and doesn't create a problem for you as long as what you certify matches that date. It becomes a problem if there's a mismatch.

0 coins

HR didn't specifically mention DES during onboarding but I know larger employers do that reporting. My employer is medium-sized, maybe 200 employees. How would I know if they've already reported my start date to DES?

0 coins

You can't see what your employer has reported to DES from the claimant side of the portal - it's not visible in your account. The employer-side reporting goes into the wage and new hire database on the DES agency side. What this means practically is that you should assume DES already knows your start date and certify accordingly rather than hoping they don't have that information.

0 coins

This is why honesty on the certifications is just the only viable approach. DES has cross-matching with employer wage records, the new hire registry, the state tax agency. The idea that you can shade the truth on certifications and not get caught eventually is basically a myth at this point.

0 coins

ok so i have a dumb question - when the OP says the claim shows 'inactive' on the portal, is that the same as the claim being in adjudication? i always thought inactive and in adjudication were the same status

0 coins

Those are actually completely different statuses that mean very different things. Inactive just means no recent certification activity - the claim itself is fine, there's nothing to review, it's just sitting there not being used. Adjudication means there's a specific issue on the claim that DES is actively investigating before they'll release payment - like a question about whether you were actually eligible, whether your separation was for good cause, that kind of thing. Adjudication is a flag, inactive is just... quiet.

0 coins

oh okay that makes way more sense, i was way overthinking it. so inactive is basically just dormant not problematic

0 coins

Dormant is actually a good way to put it. The claim is there, it has a balance, it's just not being interacted with. Adjudication would mean there's a stop on payments for a reason. Inactive has no stop.

0 coins

reading through this whole thread and one thing jumps out - OP, you mentioned you calculated roughly $680-$720 in unclaimed benefits. is that based on your weekly benefit amount multiplied by the number of weeks, or did you account for the fact that the week you started working would have a partial benefit based on those few days of wages? because if week 1 of employment falls in your uncertified period, that week's benefit is going to be less than your full WBA depending on what you earned those first few days

0 coins

Honestly I just multiplied my weekly benefit amount by the weeks I didn't certify without factoring in partial wages for the start week. So my actual backpay amount is probably a bit lower than $680-$720 once that partial week gets factored in. Good catch.

0 coins

Worth recalculating with the partial wages so you're not surprised. If your WBA is around $240 per week and you earned say $300 in those first partial days at work, your benefit for that week might be zero or close to it depending on how the earnings offset works. The other pre-employment weeks should be your full WBA though.

0 coins

The earnings offset formula DES uses is that for every dollar over a certain threshold you earn, benefits reduce by a corresponding amount. It's not a straight dollar-for-dollar offset - there's a small earnings disregard before benefits start reducing. So you'd still potentially get a partial benefit even for a week with some wages, as long as total earnings didn't exceed your WBA.

0 coins

I want to go back to something from earlier in the thread because I think it got glossed over. The poster mentioned they never received any instruction about what to do when returning to work. This is actually something DES should be covering during the initial claim orientation. When you file, there's supposed to be information provided about claimant responsibilities including what to do when you return to work - specifically that you should report your return-to-work date through the portal, not just stop certifying. The fact that so many people don't know this suggests either the information isn't being communicated clearly or people aren't reading everything during setup.

0 coins

I definitely didn't read everything thoroughly when I first filed. There was a lot of information and I think I got to the parts about weekly certifications and job search and kind of skimmed the rest. In hindsight that was a mistake.

0 coins

The return-to-work reporting process is buried in the initial orientation materials and most people don't encounter it until they actually need it. DES expects claimants to know this but their communication of it is pretty inadequate. You're not alone in missing it - I'd guess a significant percentage of claimants who go back to work without properly notifying DES did exactly what you did.

0 coins

DES really could do a better job surfacing the most critical actions claimants need to take at key transitions - starting work, refusing an offer, change in household circumstances. Instead it's all buried in a document most people click through during the application.

0 coins

The portal could easily send an automated notification if certifications stop for more than two weeks asking if you've returned to work and explaining next steps. The technology to do this clearly exists. It just isn't being used.

0 coins

JUST WANT TO ADD - if you do end up getting those back weeks paid out, keep the documentation of that payment in case your new employer ever runs an unemployment insurance rate audit or something that flags your former employer's account. It's unlikely to affect you directly as the employee but I've heard of weird situations where employers got confused about UI payments showing up after someone had already been rehired somewhere else and it created questions.

0 coins

Is that actually a thing that happens? Employers getting notified about UI payments after someone's already left? I had no idea employers could see that level of detail about former employees' claims.

0 coins

Employers get notified about claims filed by former employees because it can affect their UI tax rate. Whether they can see payment details after the fact for late certifications I'm honestly not 100% certain - but the notification piece during the initial claim definitely happens. Former employers can protest a claim during the initial eligibility determination.

0 coins

The employer notification thing is for active claims, usually within a specific window after separation. By the time someone is certifying backdated weeks months later I'd be surprised if there's a fresh notification to the former employer about those specific payments. But documenting everything is always wise regardless.

0 coins

Came to this thread because I've been in a similar weird limbo situation - my claim has been inactive since February when I picked up freelance work and I didn't know if I should close it out officially or just leave it. Reading through here I realize I should probably check my benefit year end date and figure out if there's anything I should be doing before that date passes. Does anyone know if there's an official 'close my claim' option in the portal, or does it just naturally expire?

0 coins

There's a return-to-work notification option in the UIBENEFITS portal that you're supposed to use when you go back to work - it's different from the claim just expiring naturally. For freelance or self-employment, the reporting situation is more complex because you might still technically be partially eligible depending on how much you're earning. Worth clarifying with DES whether your freelance income is treated as self-employment or regular wages for UI purposes.

0 coins

The freelance vs self-employment thing is actually something I've been uncertain about. I'm doing gig-style work through a platform, not traditional employment. I genuinely don't know how to report that or if it disqualifies me from claiming partial benefits.

0 coins

Gig platform income and UI eligibility is genuinely one of the murkier areas of unemployment rules right now. Generally speaking, if you're classified as an independent contractor rather than an employee the income might not be reported the same way, but DES still expects you to report earnings even from self-employment. That's a conversation worth having with an actual DES agent since the rules around gig work are applied inconsistently.

0 coins

This is making me think I should not have been as hands-off about my claim as I've been. Going to look into the actual status before my benefit year ends.

0 coins

Coming in toward the end of this thread to flag something for OP. When you certify those missed weeks, the job search activity entries matter too. For each week you certify, you're supposed to have documented job search activities from that specific week - not from today, but from back in March when those weeks actually occurred. If you kept any records of your job search activities from that period - emails to employers, application confirmations, LinkedIn activity, that kind of thing - save all of it before you certify. DES can audit weekly certifications and ask for documentation proving your job searches were conducted during the week you're claiming for.

0 coins

I do still have my email applications from that period and I kept a spreadsheet of my job search contacts like DES requires. So that documentation should be intact. Is there a minimum number of job search activities DES requires per week in Arizona?

0 coins

DES currently requires a minimum of one job search activity per week in Arizona, though they encourage more. Each activity needs to be logged with the employer name, contact information, position applied for, and date. Your spreadsheet sounds like exactly what they'd want to see if audited. Keep it somewhere accessible.

0 coins

The one-per-week minimum is correct but during active job searching most advisors suggest doing more - both because it genuinely helps and because having robust documentation if audited is better than the minimum. For OP's purposes since those weeks are past, whatever activities they actually did are what they had - you can't retroactively create more.

0 coins

Arizona Unemployment AI

Expert Assistant
Secure