chime works good for everything else but government stuff is always complicated

UPDATE: Got it fixed! Ended up using that Claimyr service someone mentioned to get through to an agent. Turns out there was a mismatch between how my name was entered in the NYSDOL system and my Chime account (I had my middle initial on one but not the other). The agent manually approved my direct deposit and said it should be working for my next payment. Thanks everyone for your help!

wait so was it actually unemployment money or IRS?? im confused now

UPDATE: You guys were right!! I finally got through to NYSDOL using Claimyr (took about 25 minutes to get an agent) and they confirmed exactly what happened. There was a processing error between the Treasury Department and NYSDOL where some stimulus payments were incorrectly sent through the unemployment system to people who weren't eligible. When the error was caught, they reversed the payments but didn't notify anyone. The agent was super helpful and is sending me a formal letter explaining the error that I can take to my bank. She also gave me a special reference number to provide to the IRS if I need to follow up with them. She said they're working on a mass communication to everyone affected, but that could take weeks. Thank you all for your help! I'm relieved to finally understand what happened, though still annoyed about the overdraft fees. Going to my bank tomorrow with the case info.

btw just so u know this happens when they findmissing wages but it CAN also happen if ur claim type changed. like if u were on a disaster claim and got moved to regular UI or something. but sounds like urs is the wage thing since u didn't apply for anything new

Just wanted to update - I got my regular payment this week and the amount was the same as always, but when I log in it shows I have more weeks available now. So you guys were right! Thanks again for clearing this up!

Update: I finally got through to someone at the IRS! You all were right - it was an adjustment to my 2024 taxes related to the unemployment benefits I received last year. Apparently there was some change in how they calculate the taxes on those benefits, and I overpaid. Thanks everyone for your help! For anyone else seeing these mysterious deposits, definitely check your tax transcript online or try calling the IRS to confirm what it's for.

I used that Claimyr service someone mentioned above and got through in about 30 minutes! Otherwise I think I would still be trying. The agent was really helpful and confirmed it was exactly what you all suggested - a tax adjustment for my unemployment benefits from 2024.

Just called the tax department (took FOREVER to get through) and they confirmed these refunds are legit but the rep said NOT EVERYONE will get one! You only qualify if you had unemployment income AND your adjusted gross income was under $150,000. Also they said some people might get notices AFTER the refund is deposited so don't panic if you haven't gotten an email yet!

I just checked my NY tax account online and there's a new section that shows "Unemployment Benefit Adjustment" with a status. Mine says "Processing - Expected issue date: May 13, 2025" with the amount! Everyone should check their online accounts if they have one set up.

Thanks everyone for the helpful advice! I'm going to report that I didn't work but was available, and I'll start keeping better documentation of my availability and shift offerings. Really relieved to hear from other per diem workers who've navigated this successfully.

I had this same issue when I was doing substitute teaching. My advice is actually to call your employer's HR department too and ask them how they respond to unemployment verification requests for per diem workers with no shifts. That way you know both sides are giving consistent information. My school district had a specific way they verified my availability vs. when work wasn't available.

my friend got double paid when she changed banks... dol sent payment to both old and new account. she had to pay one back obviously

Thanks everyone for all the helpful advice! I'm going to wait until after this week's payment posts to my current account before making any changes. It's not worth risking a delay. I'll update here if I run into any issues with the process in case it helps someone else.

UPDATE: I finally got through to a representative! They explained that there was indeed a system error. Apparently, when I certified for those two weeks while working full-time, the system incorrectly processed them as if I had received benefits (even though I reported working 5 days and received $0). This caused my benefit balance to incorrectly show as exhausted. The rep fixed it on their end and my correct remaining balance is now showing. They advised that in the future, if I'm working more than 4 days consistently, I should stop certifying until I need benefits again.

I'm in a completely different situation but reading this thread made me realize I've been making a similar mistake! I've been working 3 days a week and certifying but I think I've been answering one of the questions wrong... now I'm worried I've messed up my claim. Has anyone had to do a backdated certification correction before?

so wait do u have to pay anything back if u made too much at the new job?

Thanks everyone for the help! I'm going to certify this Sunday, report that I've returned to work, and include my days worked and wages earned. Based on all your advice, that seems like the proper way to handle it. Appreciate all the responses!

Does anyone know if this will delay our payments??? I NEED my money to hit my account by Thursday to pay my rent! I cannot afford any delays this week. Will they still process everything on time even with these website issues?

I had this problem a couple weeks ago. What worked for me was using a different web browser (I switched from Chrome to Firefox) and making sure I wasn't using any VPN or ad blockers. Sometimes those security features can mess with government websites. Also I found that the mobile version of the site worked when the desktop version was having problems.