Back to Arizona Unemployment

Kevin Bell

Unemployment back pay went from paid back to progress - what happened?

So I logged into the CACTUS portal this morning fully expecting to see my back pay sitting in my account and instead I'm staring at a status that makes zero sense to me. A few days ago everything showed as paid out - like, the full amount I was owed for the weeks I was waiting through adjudication. I figured the money was on its way to my debit card. But now when I check the portal the status has completely flipped and it's showing something like 'in progress' again. How does money go backwards? I never got a letter, no message in my portal inbox, nothing explaining why a payment that was already marked as paid would suddenly revert. I've been waiting on this back pay for almost six weeks now and I genuinely cannot afford another delay. Has anyone seen their unemployment back pay go from paid back to in progress before? Is this a system glitch or did something actually change with my claim?

Before anyone else jumps in - your situation with the back pay flipping statuses is exactly what happened to my cousin last month and the only thing that actually moved it forward was getting a live DES agent on the phone. I know that sounds impossible because the hold times are brutal, but we used a service called Claimyr to get through. You go to claimyr.com and there's a video walkthrough at https://youtu.be/vwA1GGuV83Y that explains how it works. Basically it handles the hold queue for you and calls you back when an agent picks up. My cousin's payment had been stuck in that same weird reversal loop and the agent was able to see a flag on the account that wasn't showing up anywhere in the portal. Got it resolved same day.

0 coins

I'd push back a little on the same-day resolution part - in my experience even when you DO reach an agent they sometimes have to escalate to a payment specialist and that takes another 24 to 48 hours. Still worth calling though, an agent can at least tell you WHY the status flipped.

0 coins

Appreciate you sharing this, I had no idea a service like that existed. The few times I've tried calling I either get the busy signal immediately or I sit on hold for an hour and then it disconnects. I'll check out that video tonight.

0 coins

the portal statuses are honestly meaningless half the time, calling is definitely the move

0 coins

Your back pay showing paid and then reverting to in progress usually points to one of a few things happening behind the scenes. Working at a job during one of those weeks you claimed - even a single shift - can trigger a manual review that temporarily pulls the payment back. The other common cause is that your bank account or debit card info changed around the same time the payment processed, which flags it for verification. Neither of these means you've been denied, it just means someone at DES has to manually clear a flag before the payment releases again.

0 coins

Nothing changed on my end with banking info and I definitely reported all my work correctly. Could it flip for a reason on DES's side, like a system update or audit?

0 coins

I'd question whether the bank info thing is always the trigger - mine reverted and my bank info hadn't changed in over a year. I think sometimes it's just a backend processing error that corrects itself, though obviously you don't want to just wait and hope.

0 coins

my claim did the exact same thing and it was because they re-ran an eligibility check after the initial payment was queued, nothing i did wrong

0 coins

The week you last filed your weekly certification before the status changed matters a lot here. If that certification was right around the time DES was processing the back pay batch, the system can essentially collide with itself - the certification triggers a fresh eligibility review while the payment is mid-release. The rule is that any open review, even a routine one, holds the funds until the review closes. It's not a denial, but it also won't self-resolve without someone manually releasing it.

0 coins

That timing actually lines up - I filed my weekly cert the same day the status switched. So what do I actually do to get someone to release it?

0 coins

Not sure the certification timing is always the cause, I've heard of this happening to people who hadn't filed a cert in weeks, but calling DES to ask them to manually clear it is definitely the right step regardless of the reason.

0 coins

yes the certification collision thing is real, happened to me too, agent released it in literally five minutes once i got through to one

0 coins

Just to add some frustration to this thread because I've lived this nightmare - my back pay went through the exact same reversal cycle TWICE before it finally paid out. First time it went from paid to in progress, I called, agent said it was cleared. Then a week later it reverted again. Turned out there was a discrepancy in my employer's wage report versus what I'd reported, which kept triggering re-reviews. The second agent I spoke to actually walked through the wage records with me line by line and found that my former employer had reported one extra week of wages that didn't match my end date. Getting that corrected took about two weeks but after that the payment finally processed for real.

0 coins

Two reversals sounds absolutely exhausting. Did you have to do anything on your end to dispute the employer's wage report or did DES handle that internally?

0 coins

the employer wage discrepancy thing is more common than people realize, employers sometimes report termination dates wrong which throws everything off

0 coins

I'd gently push back on waiting two full weeks for a wage correction - if you call and explicitly ask for the wage audit team you can sometimes get it expedited to a few days rather than the standard processing timeline.

0 coins

My sister went through this exact status flip situation about two months ago and after three weeks of getting nowhere through the portal, a friend told her about Claimyr. She was really skeptical at first but she tried it through claimyr.com and watched the demo video at https://youtu.be/vwA1GGuV83Y before using it. She reached an agent within a couple hours and found out there was a hold on her account from an identity verification step that had somehow been skipped when her claim was originally approved. The agent resubmitted the verification, the hold cleared, and the back pay hit her account two days later. She said the agent seemed surprised the portal hadn't flagged it visibly.

0 coins

Identity verification being the hidden cause is concerning me now because I never got any notification about that either. If that's the issue the portal really should show it somewhere.

0 coins

I had an ID verification hold too and had no idea until I called, the portal just said in progress with zero explanation, so frustrating

0 coins

The identity verification step being invisible in the portal is a known issue - DES's system doesn't always push those flags to the claimant-facing side, which is why calling is often the only way to actually see what's blocking a payment.

0 coins

Something most people don't know about the in progress status is that it covers about six or seven completely different underlying situations in DES's system. The portal just slaps the same label on all of them, so from your end paid reverting to in progress could mean anything from a routine system batch issue to an active adjudication being reopened. The most useful thing you can do before calling is to gather your claim ID number, the specific week dates the back pay covers, and the exact dates the status changed. When you get an agent that info speeds up the lookup significantly.

0 coins

Gathering that info is a good call - I have screenshots of when it showed paid too, would those be useful to mention to the agent?

0 coins

Screenshots probably won't change anything on the agent's end since they're looking at internal records, but keeping them for yourself as documentation is never a bad idea in case you end up needing to appeal anything.

0 coins

seven different things under one status label is insane design honestly

0 coins

yeah the portal was clearly not built with claimants in mind, it withholds more than it shows

0 coins

Not sure if this helps but I want to mention that the fourth time I tried reaching DES about a similar payment issue I used Claimyr and it was genuinely the first time I felt like I actually had a path to resolution instead of just burning hours on hold. You can find it at claimyr.com and there's a video at https://youtu.be/vwA1GGuV83Y if you want to see what it looks like before committing. The agent I eventually reached was able to see that my payment had been flagged for a supervisor review because the amount exceeded a certain threshold - apparently larger back pay amounts get additional scrutiny, which nobody tells you about anywhere.

0 coins

The larger amounts getting extra scrutiny is new information for me and honestly explains a lot - my back pay covered eight weeks so it's a pretty significant sum.

0 coins

The threshold review for larger amounts is real and the cutoff is lower than you'd think, I believe anything over a few hundred dollars in a single payment can trigger it, though the exact number probably varies.

0 coins

wish i had known about the amount threshold before waiting three weeks thinking mine was just processing normally

0 coins

Since you've had it show paid before reverting, make sure you also check whether any of those back pay weeks appear in your payment history with a paid date stamp even if the current status says in progress. Sometimes the portal displays a stale current status while the payment history section reflects the actual most recent action. If the payment history shows those weeks as paid with a date, the money may have actually been sent and is sitting in a processing queue at your bank rather than being held by DES.

0 coins

Just checked and no - the payment history also shows in progress for those weeks, nothing stamped as paid with a date. So it's genuinely stuck on DES's end.

0 coins

The payment history versus current status mismatch is worth checking in every situation like this - good practical troubleshooting step before escalating to a call.

0 coins

Mine showed in progress everywhere too when it got stuck, the payment history not updating is usually a sign the payment is legitimately held rather than just a display glitch

0 coins

One thing to watch for when you do get through to an agent - ask them to tell you which department currently has ownership of your claim file. When back pay gets stuck in a reversal like this sometimes it's sitting in a queue between departments and nobody is actively looking at it because each department thinks the other one is handling it. My second reversal was partly caused by this. The agent who finally fixed it called it a handoff gap and said it's more common with multi-week back pay because those get routed through more departments than a single week payment.

0 coins

Asking which department owns the file is a great specific question - much better than just asking why it's stuck. I'll write that down for when I call.

0 coins

the interdepartmental handoff thing sounds exactly like what happened with my claim, the payment was technically not lost just sitting in a queue that wasn't being worked

0 coins

you should also ask the agent to put a note on your file that you called and are waiting, that sometimes bumps it to the top of the manual review list

0 coins

Something else to think about - your old job at the place you left before filing might matter here. If your former employer filed any kind of late protest or wage correction in the past few weeks, DES has to pause payment processing on your claim until they review it. Employers have a window to dispute claims even after they've been approved and even after back pay has been queued. It's a really frustrating part of how the system works but the employer basically gets a second bite at contesting things. The agent can tell you if an employer action is what triggered the reversal.

0 coins

My former employer and I did not part on great terms so this is actually a real concern. Is there anything I can do if they did file a late protest?

0 coins

If your former employer filed something late you absolutely have the right to respond to it, DES has to notify you and give you a chance to rebut. Make sure your contact info in CACTUS is current so the notice doesn't go somewhere you don't check.

0 coins

The employer protest window being open even post-approval is something a lot of people don't realize and it catches people off guard when their claim gets pulled back after they thought everything was settled

0 coins

Coming back to the practical side of things - when your back pay finally does process and hit your account, double-check that the full amount matches what you expected. After a reversal and manual release there have been cases where the system processes the payment minus some weeks due to a recalculation during the manual review. It's not super common but it happens. If the amount is short you have a 30-day window from the payment date to request a correction, so keep track of exactly what you're owed.

0 coins

Keeping track of exactly what I'm owed by week is something I should probably do before I even call - good thinking, I'll pull up my weekly claim history and total it up.

0 coins

my payment came through short by almost two weeks worth and i didn't catch it right away, took forever to get corrected after the fact

0 coins

the 30 day window for corrections is good to know, I never knew there was a time limit on that

0 coins

The in progress status after a paid status can also sometimes mean that your weekly certification for the current week is somehow linked in the system to the back pay release. DES sometimes bundles current and past payments into a single release batch and if anything about your current week is unresolved it can hold up the whole batch. Worth checking that all your most recent certifications are fully submitted with no incomplete sections.

0 coins

All my recent certifications look complete on my end but I'll go back and check each one more carefully - maybe there's a question I answered that triggered a flag I didn't realize.

0 coins

the job search activity entries being incomplete is a surprisingly common reason certifications get flagged, make sure you have the right number of contacts entered for each week

0 coins

I had a cert flag once because i listed the same employer contact twice across two weeks and it got flagged as a duplicate, tiny things like that can apparently hold everything up

0 coins

Just want to say that reading this thread is giving me flashbacks to my own claim situation last year. Everything you're describing is so familiar - the portal telling you nothing useful, the payment appearing and disappearing, calling and getting disconnected. I eventually got through and it turned out to be a completely internal DES processing error that had nothing to do with my eligibility at all. They apologized and released the payment but I had to push really hard to get anyone to look at it.

0 coins

Hearing that it turned out to be an internal error is both reassuring and infuriating - reassuring because it means I might not have done anything wrong, infuriating because I shouldn't have to push to get it fixed.

0 coins

the internal processing error explanation seems to be the catch-all for anything DES doesn't want to explain in detail, but at least when they give you that answer it usually means the payment is coming

0 coins

Something I want to add here - if the agent tells you it was an internal error make sure you ask them to put the resolution reason in writing or at minimum get their employee ID number. If you ever get audited later you want a record that DES acknowledged it was their system issue and not something on your claim that was incorrect.

0 coins

The timeline of when you last worked before filing matters in a situation like yours too. If you had any income within the base period that DES hasn't fully reconciled, back pay can get held even after initial approval because the wage computation is still being finalized on their end. The base period goes back quite a bit - it's not just the last few weeks before you filed. So if you had any overlapping contract work, side income, or a gap in employment that might have wages attached to it, those could all be getting reviewed.

0 coins

The base period going back further than I thought is worth me checking - I did do a few weeks of contract work about nine months ago that I may not have thought to include because it felt too far back.

0 coins

Nine months back is very likely within your base period - the standard base period in Arizona covers roughly the first four of the last five completed calendar quarters before you filed. Contract income within that window should have been reported.

0 coins

If that contract income wasn't reflected in your original claim wage records it could absolutely be what triggered the review when DES cross-referenced with tax records, that kind of discrepancy often surfaces after initial approval rather than before

0 coins

Has anyone else noticed that these payment reversals seem to happen most often right before or right after a weekend? I've seen people in this forum mention the status flipping on Fridays and then getting stuck over the weekend because there's no one at DES to manually release anything. If yours changed on a Friday afternoon that might be adding days to your wait for no reason other than the timing.

0 coins

Mine actually did flip on a Friday which feels like terrible luck - so the two weekend days might just be dead time before anyone can even look at it.

0 coins

The Friday timing theory makes intuitive sense but I'd be a little cautious about assuming it's the main cause - plenty of reversals happen mid-week too and take just as long to resolve.

0 coins

DES really should have weekend processing capabilities in 2025 but here we are

0 coins

Something worth knowing about the CACTUS portal specifically - the status you see in the portal can lag behind the actual internal system by anywhere from a few hours to a full business day. So while you're seeing in progress right now, the agent looking at the backend might see something completely different and more specific. This is part of why calling is so much more effective than refreshing the portal - you're essentially looking at a delayed snapshot while the agent sees the live system. I used Claimyr to reach an agent about a payment issue a while back - claimyr.com - and the first thing the agent said was that my portal was showing outdated info compared to what they were actually seeing on their end.

0 coins

That portal lag explains so much - I've been refreshing it multiple times a day hoping to catch an update and it sounds like I might just be looking at stale data each time.

0 coins

The portal lag is real but I'd push back slightly on it being just a few hours in every case - during high-volume periods I've heard of the portal being a full 48 hours behind the internal system.

0 coins

knowing the portal is basically a delayed snapshot makes me feel better about not being able to read anything useful from it, was driving myself crazy trying to interpret every little change

0 coins

I'll also mention that if this drags on more than another week without movement, you can request a formal status review by submitting a written inquiry through the CACTUS portal messaging system. It doesn't always speed things up but it creates a paper trail and once you have a submitted written inquiry on file you have more grounds to escalate to a supervisor level review if the regular agent can't resolve it.

0 coins

The written inquiry creating a paper trail is something I hadn't thought of - even if it doesn't speed things up it sounds like a smart parallel step to take alongside calling.

0 coins

The written inquiry route is worth doing but be aware the standard response time on portal messages is listed as five to seven business days, so it shouldn't be your only approach if you need this resolved faster than that.

0 coins

I submitted a portal message once and got a response three weeks later that just said my claim was being reviewed, completely useless but at least it was something in writing

0 coins

To bring this back around and try to give you something concrete to do tomorrow morning - the most effective sequence I've seen work for people with this exact status flip situation is: call early, ideally before 8:30am because the queue fills up fast after that; have your claim ID and the specific week dates ready; ask the agent explicitly to check whether a payment flag exists on your account and which team owns it; and ask them to note in your file that you called. That combination tends to move things faster than a general inquiry about why your payment is delayed.

0 coins

This is exactly the kind of step-by-step I needed. Calling before 8:30, having my info ready, asking about the flag and the owning team - writing all of this down right now.

0 coins

Calling early is real, the DES lines do fill up extremely fast and after about 9am on weekdays the hold times become much longer, the early callers genuinely get better service

0 coins

the note-in-file request is underrated advice, I never thought to ask for that explicitly but it makes sense that having a record of contact puts some accountability on the DES side to follow up

0 coins

One addition to this solid advice - if the agent tells you they can't help and you need to call back, ask them to transfer you to a payment specialist rather than re-entering the general queue

0 coins

Arizona Unemployment AI

Expert Assistant
Secure