Back to New York Unemployment

Mei Chen

NYSDOL gov login unemployment direct deposit not updating - anyone else?

My direct deposit information has been stuck showing my old bank account for going on two weeks now and I genuinely don't know what to do at this point. I updated my banking details through the NY.gov login portal after switching banks last month - closed the old checking account because of fees, opened a new one at a credit union, went into Unemployment Services and updated the direct deposit routing and account numbers right away. Got the confirmation screen and everything. But my last two weekly payments both tried to go to the closed account. The first one bounced back and is now showing as 'payment returned' in my claim history. The second one I certified for on Sunday and I'm terrified it's going to do the same thing. I've been trying to reach NYSDOL by phone for three days straight. Every time I get through the automated system it either tells me call volume is too high and hangs up or I sit on hold for over an hour and then get cut off. I've logged into Unemployment Services probably six times and I can see my new bank info is in there now - it shows the correct account - but the payments keep routing to the old closed account somehow. Anyone dealt with this specific issue? Is there some lag time between updating your direct deposit and it actually taking effect? Could the returned payment be holding up my whole claim? I need this money and I'm losing my mind trying to get answers.

My third week waiting on a payment issue actually got resolved after I found a tool called Claimyr - it waits on hold with NYSDOL for you so you end up talking to a live agent without spending your whole day on the phone. You can check it out at claimyr.com and there's a video showing how it works at https://youtu.be/Rdqa1gKtxuE. I had almost the exact same situation, updated my direct deposit through the gov login portal and my payment still went to the wrong account. The agent I reached through Claimyr was able to manually flag my account and get the returned payment reissued within a few days. Worth trying if you can't get through the regular way.

0 coins

Mei Chen

Author

Trying this right now honestly because I've been on hold for so long today that my phone battery died twice. Did the agent actually fix the routing issue on their end or did you have to do something additional in your Unemployment Services account?

0 coins

Week two of my own direct deposit mess and I'm bookmarking anything that might help. How long before the agent actually picked up when you used that?

0 coins

My agent was able to fix it on the NYSDOL side directly - I didn't need to touch my Unemployment Services account again after the call. The routing issue was apparently a known system lag they can manually override.

0 coins

Sounds too good to be true honestly but I've tried everything else so at this point what do I have to lose

0 coins

Two returned payments in a row is a serious flag on your account - that happened to me back in the spring and my entire claim went into a mini-adjudication because of it. NYSDOL's system apparently treats repeated payment failures as a potential identity or fraud issue, which makes no sense when you can literally see the updated banking info sitting right there in Unemployment Services. The fix I eventually found was to send a secure message through the portal specifically referencing the returned payment dates and your new account's routing number in the message body. That creates a paper trail and sometimes gets someone to look at the account manually.

0 coins

Mei Chen

Author

Mine went into some kind of hold status after the first returned payment and I didn't even get a notification about it, I just noticed when I logged in. The secure message route is a good idea - did you use the general inquiry category or is there a specific one for payment issues?

0 coins

Payment returns absolutely can trigger an account review. My cousin - wait no the instructions said not to start like that - anyway my situation last year had the same thing happen. Use the 'Payment Inquiry' category in the secure message system if it's available, otherwise 'General Claim Inquiry' works but takes longer to get a response.

0 coins

Payment Inquiry is the right one to use. Also attach a screenshot of your Unemployment Services account showing the new banking info is already there - that pre-empts the standard response they send asking you to update your direct deposit.

0 coins

Forty-eight hours is roughly how long NYSDOL's system is supposed to take to reflect a direct deposit change before it applies to pending payments - but that's the stated timeframe, real world it can be longer. If you updated the account and certified within that window, there's a decent chance your new payment is already locked to the old routing number on the backend even though the portal shows the new info. It's a system sync issue they've had for a while now.

0 coins

Mei Chen

Author

Mine was definitely updated before the certification window opened so theoretically 48 hours had passed. But I'm starting to wonder if there's a separate backend update that doesn't sync with what's visible in Unemployment Services.

0 coins

The portal showing one thing and the actual payment system doing another is so NYSDOL it hurts. I've had my claim status show 'paid' for three days before money ever showed up in my account. Their backend is just not in sync with the customer-facing site half the time.

0 coins

Exactly - the UI system that processes payments is older than the web portal layered on top of it. Changes made in the portal take time to actually write through to the payment processing side. It's a legitimate technical gap in their infrastructure, not a user error.

0 coins

My situation last fall was nearly identical - old bank account got closed, updated everything in Unemployment Services right away, watched two payments disappear into the void before anything got fixed. The returned payments will eventually be reissued but here's the part nobody warned me about: they may mail you a paper check for the returned amount instead of retrying the direct deposit, and the check takes another 7-10 business days on top of everything. So if you need the money soon I'd push hard to get an agent to manually reissue it rather than waiting for the automatic process.

0 coins

Mei Chen

Author

The paper check thing is exactly what I was afraid of - I do not have 7-10 more days right now. Did you end up having to call in to prevent the paper check or did it just happen automatically?

0 coins

Mine happened automatically - they just mailed the check without any notice. By the time I found out through my account message center the check was already in transit. If I had reached an agent sooner I think they could have redirected it back to direct deposit.

0 coins

My paper check from a returned payment sat in a mail facility for 11 days before I got it. The agent I eventually spoke to said there's no way to cancel a check once it's been generated, you just have to wait. So getting ahead of it before they issue the check is crucial.

0 coins

This whole paper check fallback feels like it was designed in 1987 and nobody updated it lol

0 coins

My fourth attempt at reaching NYSDOL this week finally worked when I used Claimyr - I had the same payment routing issue and spent two weeks hitting dead ends on hold. Ended up on the phone with an agent who pulled up my account while I was on the line and saw immediately that the system had a pending payment still queued to my old routing number even though my profile showed the new account. She manually redirected it on her end. The whole conversation took about 15 minutes once I actually had an agent.

0 coins

Mei Chen

Author

Getting more convinced this is the route I need to take. The manual redirect is exactly what I need someone to do because I can clearly see from my account that the info is updated - it's something on the backend.

0 coins

My experience with NYSDOL agents has been hit or miss - some really know what they're doing and others just tell you to wait 2-3 weeks and hang up. Sounds like you got a good one.

0 coins

She was genuinely helpful - gave me a reference number for the manual redirect so I could track it. I think being specific about what you need when the agent picks up helps - I said 'I have a returned payment due to a system lag on a direct deposit update' and she knew exactly what I was talking about.

0 coins

The reference number thing is so important. Any time an agent tells you something or does something on your account always ask for a reference number or case number right then.

0 coins

My bank actually flagged me about the attempted deposit to the closed account before NYSDOL even updated my claim status. Apparently when a direct deposit is rejected the funds get held in some kind of return limbo for up to five business days before NYSDOL's system registers it as returned. So your 'payment returned' status showing up in your claim history means the money is already back on NYSDOL's side - it just hasn't been reissued yet.

0 coins

Mei Chen

Author

The 'payment returned' status appeared in my history about four days after I expected the deposit. So the timeline you're describing tracks. What I don't know is whether the reissuance happens automatically or if someone has to trigger it manually.

0 coins

Automatic reissuance does happen but only after a certain holding period that varies and I've seen people say anywhere from 10 to 21 days. Manual trigger from an agent is faster. Much faster.

0 coins

My reissuance took 18 days on the automatic side. Got a paper check I wasn't expecting. Manual trigger from an agent is the right answer here.

0 coins

30 days is apparently when NYSDOL's system will automatically void a returned payment if it hasn't been reissued - then you'd have to file a lost payment request to get it back at all. I found this out the hard way. If your first returned payment is approaching that mark get on the phone with NYSDOL as soon as humanly possible.

0 coins

Mei Chen

Author

My first returned payment is now at 15 days. So I'm at the halfway point of that window which is making me extremely anxious. I haven't been able to get through to anyone still.

0 coins

Push as hard as you can to get through. That 30-day window is not something they extend easily from what I understand. Document everything - screenshot your account showing the payment returned status with the date.

0 coins

My agent told me the same 30-day thing. She also said if the void does happen you have to file a specific form for a manual reissuance request and it can take another 3-4 weeks on top of that. Getting ahead of it is so much better.

0 coins

The whole system is designed to make you give up. Fight for your money because nobody is going to come looking for you.

0 coins

My claim had a similar payment routing issue and after two weeks of failed calls I tried Claimyr - ended up speaking with an NYSDOL agent who said the direct deposit update through the gov login portal had completed but the payment batch for my certification had already been queued before the update fully propagated. Basically a timing issue they deal with regularly. The agent manually queued a reissuance to the correct account.

0 coins

Mei Chen

Author

The 'queued before propagation' explanation matches exactly what I think happened to me. I updated everything but certified before the new info was locked in on the payment side.

0 coins

That's the most common version of this issue apparently. The agent said to always wait a full 72 hours after updating direct deposit before certifying if possible - though that's not always practical given the certification window.

0 coins

72 hours is a smart rule of thumb that I wish someone had told me before I ran into this exact issue last year.

0 coins

My weekly certification went through fine right after updating my direct deposit once and another time it routed to my old account. There's genuinely no way to know from the user end whether the update has propagated to the payment backend or not. NYSDOL should have a confirmation beyond just the portal showing updated info - like an email saying 'your new banking information is now active for future payments' but of course that doesn't exist.

0 coins

Sending a secure message to ask for explicit confirmation that the update is active would at least create a record of when they acknowledged it. Not a perfect solution but better than nothing.

0 coins

My secure message on this exact question got a response in about 4 days saying my account information had been updated. By that point I had already certified twice and was crossing my fingers. The lack of real-time confirmation is a genuine system flaw.

0 coins

They need a simple status indicator in Unemployment Services that shows 'direct deposit update active as of [date]' instead of just showing your current bank info. Such an easy fix that would prevent so many support calls.

0 coins

My situation last month was different from yours but I want to mention that when I had an issue affecting my payment timing I found out there's a Payment Status line within the main NYSDOL phone system that sometimes has shorter holds than the main claimant line. Not a guarantee but worth cycling through the phone menu options to find it rather than always defaulting to the main claimant queue.

0 coins

Mei Chen

Author

Trying that menu path next time I call - I've been going straight to the claimant services option every time.

0 coins

Press through to option 2 for payment status issues specifically instead of holding for a general agent. I've had slightly better luck that way though it's still not great honestly.

0 coins

My experience with the payment status line is that it just reads you the same information visible in your Unemployment Services account. For anything that actually needs a human to fix, you need a live agent. But it can at least confirm whether NYSDOL's system shows your payment as returned or pending.

0 coins

My updated direct deposit info showed correctly in Unemployment Services for three weeks before I discovered payments were still going to my old account. The portal and the payment backend are genuinely separate systems that don't sync reliably. I'd been blaming myself for weeks thinking I had entered the information wrong before an agent explained the disconnect to me.

0 coins

Mei Chen

Author

The self-blame spiral is real. I went back and re-entered my routing and account numbers three different times thinking I had made a typo somewhere.

0 coins

I did the same thing. Triple-checked every digit. The issue isn't user error - it's that there's no indicator in the portal that tells you when the backend has actually picked up the change.

0 coins

My bank sent me a paper showing exactly when each deposit attempt was made including the rejected ones - that documentation was useful when I finally talked to an agent because it showed timestamps that matched the routing lag.

0 coins

My HR rep when I got laid off actually warned me that NYSDOL direct deposit updates can take longer to reflect in payments than the portal suggests. She had seen multiple coworkers run into this same thing over the years. I went into it knowing to wait a few extra days before my first certification after updating banking info. Wish I had known about that buffer period earlier.

0 coins

Mei Chen

Author

Your HR rep is more helpful than anything I found on the actual NYSDOL website about this.

0 coins

She dealt with a lot of layoffs unfortunately and had seen enough people go through it to know the common pitfalls. The NYSDOL website is genuinely not useful for edge case situations like this.

0 coins

The NYSDOL website FAQ reads like it was written by someone who has never actually filed for unemployment. It covers only the simplest use cases.

0 coins

My first certification after a bank switch taught me to always call ahead to confirm before anything is submitted. I know it sounds excessive but after going through the returned payment process I'd rather spend 20 minutes on the phone in advance than deal with 3 weeks of payment delays. The agents can verify whether your direct deposit update has fully propagated through their backend before you certify.

0 coins

Mei Chen

Author

Verifying before certifying is advice I wish I had read two weeks ago. I'm going to implement this rule for any future changes to my account.

0 coins

It's one of those things you only learn after getting burned. Also worth noting that agents can see a flag in your account that shows 'pending banking update' which is different from the update being fully active - that flag is not visible to us in Unemployment Services.

0 coins

The 'pending banking update' flag is news to me. So there is essentially a hidden intermediate state between 'updated in portal' and 'active in payment system' that we can't see? That explains so much.

0 coins

Exactly. The agent I spoke to described it as an internal processing queue. The portal just shows a snapshot of what you entered, not the actual payment system status.

0 coins

My NYSDOL experience has taught me that any time you make a change to your banking or personal information you should screenshot the confirmation screen the portal shows, note the exact date and time, and save it somewhere. If a payment goes wrong you'll want that documentation to show when the update was submitted versus when the problem payment was processed.

0 coins

Mei Chen

Author

I did screenshot the confirmation screen fortunately. Combined with my claim history showing the returned payment date it should give a clear timeline.

0 coins

That timeline documentation is exactly what an agent needs to manually investigate. With those screenshots you have everything - when you updated, what the portal confirmed, and when the payment failed. That's a strong case for manual reissuance.

0 coins

Screenshotting every step of your Unemployment Services interactions is just a general best practice at this point. The portal doesn't save a detailed history of changes you've made to your account settings.

0 coins

My weekly payments were on a Thursday schedule and I noticed that direct deposit updates made on a Tuesday were sometimes not hitting until the following week's payment cycle regardless of what the portal showed. If NYSDOL batches payments by day of week the update timing might interact with that batch schedule in ways that aren't obvious from the user side.

0 coins

Mei Chen

Author

Mine payments were on a Tuesday schedule and I updated my banking info on a Thursday so there might be something to the batch timing theory here.

0 coins

The batch processing angle would explain why the portal shows updated info but payments still go to the old account - the payment batch for your cycle might have already been generated with the old routing number before your update was processed.

0 coins

Payment batches are processed overnight in cycles and your update has to clear before your payment batch runs. If you update after the batch for your payment cycle is already staged, you'll need to wait for the next cycle or get an agent to manually intervene on the queued payment.

0 coins

My overall takeaway from every NYSDOL direct deposit issue thread I've read is that the gov login portal is basically a data entry interface that feeds into a backend payment system on a delayed schedule that isn't communicated to users anywhere. The fix is almost always either waiting out the batch cycle or getting a live agent to manually intervene on a queued payment. There's no middle ground the user can access themselves.

0 coins

Mei Chen

Author

After this experience I'm leaning toward 'live agent intervention' as the only real fix for anything time-sensitive. The waiting approach is not viable when rent is due.

0 coins

For anything time-sensitive an agent is the only path. For informational issues the secure message system works eventually but takes days. The phone is the only real-time option in NYSDOL's support structure.

0 coins

My policy now is phone first for anything that could affect a payment date. Secure messages for record-keeping and documentation. Never rely on the portal alone showing updated info as confirmation that a change is live.

0 coins

Claimyr worked for my situation which was also a direct deposit mess after updating through the gov login portal - I'd been trying for over a week to get through and finally ended up on the phone with an NYSDOL agent who could see both the old and new routing numbers in my account history and explained exactly what had happened. She reissued the returned payment to the correct account while I was on the phone with her. It was the first real answer I'd gotten after days of being cut off or told to wait.

0 coins

Mei Chen

Author

Getting an agent who can actually see the full account history including both routing numbers is exactly what I need. I'll give it a try today.

0 coins

My agent also confirmed the second payment I had certified for was already locked to the new routing number, so I didn't have to worry about a second returned payment. Having that confirmed by someone who could actually see the backend was a massive relief.

0 coins

Real-time backend visibility from an agent is so much more useful than anything we can see in the portal. The portal is basically a filtered view that doesn't show half of what's actually happening on our accounts.

0 coins

My resolution only came after speaking to a live agent too. The portal, the secure messages, the automated payment status line - none of those fixed anything. Only an agent with backend access could actually resolve it.

0 coins

My general frustration with NYSDOL is that every problem that requires human intervention requires getting past a phone system designed to prevent human contact. The irony of a system built to help people in financial stress being impossible to reach is not lost on me.

0 coins

Mei Chen

Author

Every day I don't get through is another day my bills get further behind. The system should not be this hard to navigate when you're already dealing with job loss.

0 coins

The design of the system puts maximum burden on the person who can least afford to spend time and energy on bureaucratic obstacles. It's genuinely demoralizing.

0 coins

My hope for anyone reading this thread is that you fight through it because giving up doesn't get your money back. Keep calling, keep sending messages, document everything. The money is yours and they owe it to you.

0 coins

Related posts

New York Unemployment AI

Expert Assistant
Secure