Back to Nevada Unemployment

Victoria Charity

Unemployment double dip issue after filing new claim benefit year ended - Nevada DETR help

So my benefit year wrapped up about six weeks ago and I went ahead and filed a brand new claim right after. Got approved, got a new claim balance showing, everything looked fine on CSS. But then I noticed something weird - my payment history is showing what looks like an overlap between the last week of my old claim and the first week of the new one. Both weeks show as paid. I work in construction and had a brief return to work between the two claims (maybe 3 weeks), so I don't know if that's what triggered this or if the system just did something funky during the transition. Now I'm getting nervous because I've heard horror stories about Nevada DETR flagging these situations as a 'double dip' and sending overpayment notices months later. I didn't intentionally claim twice for the same week - I just filed the new claim when my benefit year ended like I was supposed to. The CSS portal doesn't show any flags or pending issues on my account, but I'm not sure if that means I'm in the clear or if the adjudication is just slow to catch up. Has anyone run into this kind of overlap between benefit years? Did Nevada DETR send you a notice or did they just quietly correct it? I really don't want to get hit with an overpayment demand for something I didn't do on purpose. Should I be calling them proactively or just wait and see what happens?

Benefit year transitions are genuinely one of the messiest parts of Nevada DETR's system. The overlap you're describing usually happens when the final week of your old benefit year falls into the same payment cycle as the opening week of your new claim. DETR's backend is supposed to catch this automatically, but I've seen it take 4-8 weeks before the system reconciles and sometimes it throws an adjudication flag even when you did nothing wrong. The 3-week work period you mentioned actually helps your case a lot - it creates a clear break in the record.

0 coins

Three weeks of construction work between claims, that's actually a solid paper trail. My gap was only a few days and DETR made me submit pay stubs before they'd move forward.

0 coins

Good to know the work gap helps. I do have my pay stubs from those three weeks saved. Should I upload them preemptively to CSS or just hold onto them in case I get a letter?

0 coins

Hold them. If you upload stuff they didn't ask for it can actually trigger a manual review and slow everything down. Wait until they contact you first.

0 coins

Waited exactly 47 days after my benefit year ended before DETR said anything about an overlap issue on my claim. The notice came in the mail, not through CSS messages, which surprised me. When I finally got someone on the phone they said the overlap was a known system quirk during benefit year rollovers and they resolved it in about 10 minutes once I could actually talk to a person. The CSS portal never showed any flags the entire time.

0 coins

Mail notice, not CSS - that's the part that gets people. I almost missed mine because I assumed everything important would show up in my online account.

0 coins

Okay so the mail thing is kind of alarming to me. I've been monitoring CSS obsessively but not necessarily checking my physical mail every day. Good reminder to do that.

0 coins

DETR sends the official legal stuff by mail because it starts the appeal clock. The CSS messages are more like informational. Big difference between the two.

0 coins

Claimyr is what finally got me through to an actual Nevada DETR agent when I had a benefit year transition mess. I'd been calling for two weeks straight and either hitting the busy signal wall or getting cut off after 45 minutes on hold. Someone in another thread mentioned claimyr.com and I checked out the video demo at https://youtu.be/Mc9FNfOF_yY - it basically handles the hold queue for you and calls you back when an agent is on the line. Got connected within a few hours. The agent I spoke with looked at my account in real time and confirmed the overlap was a system error, not a fraud flag. Worth knowing about if you can't get through on your own.

0 coins

Two weeks of trying sounds brutal. I'm going to watch that video and probably use this if I can't get through by end of this week. Did they ask you to have anything specific ready when the agent picked up?

0 coins

I was skeptical about services like this but the Nevada DETR phone situation is genuinely impossible some weeks. If it actually gets you to a live agent that's valuable.

0 coins

claimyr.com - saving this. I have a different issue (standby status not showing correctly) but same problem of not being able to get anyone on the phone.

0 coins

The 'double dip' label gets thrown around a lot but what DETR actually investigates is whether someone collected benefits for the same calendar week twice. If your old claim paid out for week ending, say, March 2nd, and your new claim also paid for the week ending March 2nd, that's the actual problem. If your new claim started the week of March 9th or later, you're almost certainly fine. Pull up both payment histories and check the actual week-ending dates side by side - that'll tell you definitively whether there's a real overlap or just a visual coincidence in how the portal displays things.

0 coins

Week-ending dates specifically - okay I just pulled both up. The last payment from my old claim shows week ending 4/13 and my first new claim payment shows week ending 4/27. So there is a two-week gap. Does that mean I'm actually in the clear?

0 coins

Yes, a two-week gap between week-ending dates is clean. No overlap. What you're probably seeing in your payment history is the display of both claim records in the same view, which can look alarming but isn't actually a double payment for the same week.

0 coins

This is the right way to check it. I panicked for days over what turned out to be exactly this - both records showing in one list but different weeks. DETR rep confirmed it was fine when I finally got through.

0 coins

Used to think that if you filed a new claim right when your benefit year ended, there would automatically be an investigation period. That's not actually true - DETR only initiates adjudication on the new claim if something in your work history or the reason for separation triggers it. A benefit year ending naturally and you filing a new claim is a routine event for them, not a red flag on its own. The system is designed to handle exactly this scenario.

0 coins

Counterpoint: my new claim after benefit year end DID go into adjudication even though my separation was the same as the original claim. So I don't think it's always routine.

0 coins

Fair point - there are situations where they re-verify eligibility at the start of a new benefit year even with the same employer separation. Usually resolves faster than an initial claim though.

0 coins

My second benefit year claim took 11 days to process, first one took 3 weeks. Seems like they do have your history to reference the second time around.

0 coins

Something nobody's mentioned: when you filed the new claim, what did you list as your base period employers? If the construction job you worked between claims was listed in the new claim's base period, that's what determines your new benefit amount and shouldn't cause a double-dip issue. But if you forgot to list that employer and they cross-reference later, that can trigger a separate audit.

0 coins

I listed the construction company and both of my previous employers in the new application. The brief return to work was for my same construction employer so it was easy to include.

0 coins

That's good. Consistency between what you reported on the claim and what shows up in wage records is what prevents the audit flags. You're in better shape than you might think.

0 coins

Wage record cross-referencing is real and it happens automatically. DETR pulls quarterly wage data from employers, so inconsistencies get caught whether you report them or not. Best practice is always to over-report rather than under-report.

0 coins

I have to be honest - when I read 'double dip issue' I immediately assumed fraud scenario. But reading your situation, it really sounds like normal benefit year transition. The system just isn't great at making it visually clear which payments belong to which claim year in the CSS portal.

0 coins

Yeah the portal makes it look like one continuous stream of payments when really they're two separate claims. I wish it at least drew a line between them or labeled them differently.

0 coins

The CSS portal shows claim balance and payments but doesn't clearly demarcate benefit year boundaries. It's a known usability issue. Plenty of people freak out over the display when their actual account is completely clean.

0 coins

Calling Nevada DETR to get proactive confirmation is genuinely the right move here, and Claimyr made that possible for me when I had a similar transition question. The regular phone line was running 2+ hour waits every day I tried. Used claimyr.com and got a callback same afternoon. The agent pulled up both claim records side by side and walked me through exactly what I owed versus what was legitimately paid. Took maybe 15 minutes of actual call time to get complete peace of mind.

0 coins

Peace of mind is exactly what I need right now. I keep second-guessing the week-ending date comparison I did because I want to be 100% sure, not just 90% sure.

0 coins

Agent walking through both records at once is valuable because they can see the internal flags that don't show on your CSS view. Sometimes there are pending reviews you have no idea are happening.

0 coins

Same situation before my second benefit year started. Getting that direct confirmation from an agent was the only thing that made me stop obsessing over it.

0 coins

Another angle worth considering: did you certify any weeks after your benefit year ended but before your new claim was approved? That gap period is where I see people accidentally create overlap problems. If you kept filing weekly claims on the old claim number after the benefit year ended and then those weeks also got covered by the new claim, that's where real double payments happen.

0 coins

No - I stopped filing on the old claim as soon as the CSS showed the balance at zero. Then waited about 5 days before the system let me file the new application.

0 coins

Zero balance stopping you is exactly the right stopping point. As long as you weren't manually submitting weekly certs on the old claim hoping for a miracle payment, you're fine.

0 coins

Had a client who kept certifying on an exhausted claim for 3 weeks because nobody told him to stop. That created the exact double-dip flag situation. Used Claimyr to get through to an agent to fix it and they actually waived the overpayment because it was the CSS portal's fault for not clearly indicating the claim was done.

0 coins

Took me a long time to understand this but Nevada DETR distinguishes between three different things that all look similar: an accidental overlap from benefit year transitions, an actual fraudulent double claim, and a system-generated payment error. The first one usually gets handled administratively with no penalty. The second one is serious. The third one, where DETR made the error, actually entitles you to a waiver process if they try to collect it back. Based on what you're describing, you're in category one at worst.

0 coins

The waiver process for category three is real but requires you to prove the error was on DETR's side, which means documenting every communication. Screenshot everything, date-stamp everything.

0 coins

Exactly. Even if you think you're in category one, treat your documentation like you're in category three. Having it doesn't hurt you; not having it might.

0 coins

This three-way distinction is something I wish I'd understood earlier. I was so scared of the word 'overpayment' that I didn't realize there were different procedures and different outcomes depending on how it happened.

0 coins

Weekly certification accuracy during the transition is what DETR actually scrutinizes most. Each week you certified, did you accurately report any earnings from that construction return-to-work, your availability to work, and your job search activities? If your certifications were clean and accurate during both the old claim's last weeks and the new claim's opening weeks, the payment accuracy question almost answers itself.

0 coins

Every week I worked construction I reported the earnings. Even the partial weeks where I worked like two or three days I calculated the gross and reported it. Never tried to hide any of it.

0 coins

Reported earnings on partial weeks - that's exactly right. Partial week earnings don't disqualify you, they just adjust that week's payment. Claimants who try to hide those weeks are the ones who get flagged.

0 coins

Job search activities during the work weeks matter too. When you were working those three construction weeks you're technically not required to do your full 3 job search activities, but some people don't know that and think they messed something up.

0 coins

Went through almost this exact situation 8 months ago - benefit year ended, filed new claim, got nervous about the payment display in CSS. Spent probably 6 hours over three days trying to call DETR. The hold music is the same loop and I still hear it in my dreams. Eventually everything resolved on its own after about 3 weeks but I wish I'd just gotten through to someone faster to confirm.

0 coins

6 hours of hold time over three days is exactly what I'm trying to avoid. I'm already at about 3 hours total this week.

0 coins

If I were doing it again I'd have used a service to get through rather than grinding the redial button. The uncertainty is the worst part and it's not worth extending it out.

0 coins

The 'resolves on its own' outcome is common for clean benefit year transitions, but waiting weeks to find out when you could have confirmed in one phone call is unnecessary stress.

0 coins

Overlooked detail in these situations: make sure your mailing address on file with Nevada DETR is current. If they send that official letter to an old address and you miss the 11-day appeal window (11 calendar days in Nevada for most UI decisions), you lose the right to contest even if the decision is completely wrong.

0 coins

Address is current, I double-checked it on CSS last week actually. But the 11-day appeal window is terrifying. That's really short.

0 coins

11 calendar days including weekends and holidays. It's one of the most important things to know about Nevada DETR and most people don't find out until they've already missed the deadline.

0 coins

The appeal window running over weekends is brutal. I've heard of people getting letters on Fridays who effectively had 7 business days. Document the envelope postmark date if possible, it can matter.

0 coins

Something that helped me understand my own transition situation: the CSS portal has a section under 'Claim Summary' that shows your claim effective date and benefit year end date explicitly. If your new claim's effective date is after your old claim's benefit year end date, you have a clean start. Can you see those dates on your end?

0 coins

Just looked - new claim effective date is April 14th, old benefit year ended April 13th. So one day apart but no actual overlap of the year dates themselves.

0 coins

April 14th start the day after April 13th end is a textbook clean transition. The system processed it correctly even if the display is confusing.

0 coins

Effective date information is the definitive answer right there. Week ending dates plus claim effective dates both pointing to no overlap - OP you're good.

0 coins

Used to believe that proactively calling DETR to report a 'possible issue' would protect you from penalties later. Actually learned the hard way that calling to flag something that isn't actually a problem can create a record that makes auditors look twice when they'd otherwise just move on. If your dates are clean and your certifications were accurate, silence isn't hiding anything - it's just not creating unnecessary noise.

0 coins

This is real and underappreciated advice. Voluntary disclosure of a non-issue is different from disclosing something that's actually wrong. Know the difference before you call.

0 coins

Okay this is making me rethink my instinct to call proactively. If the week-ending dates show a clean gap and the effective dates are consecutive, maybe I should just watch and wait rather than potentially flagging my own account for something that wasn't a problem.

0 coins

Watching and waiting is reasonable given your specific numbers. But keep your documentation organized so if something does arrive in the mail you can respond within that appeal window without scrambling.

0 coins

One thing worth knowing from someone who works in the construction industry and has dealt with seasonal UI claims: when you have multiple return-to-work stretches within a benefit year, your base period wage records can look complicated to an automated system even when everything is totally legitimate. DETR's automated flags are tuned to catch fraud patterns, and construction workers who cycle in and out of work legitimately sometimes trigger those patterns. Doesn't mean you've done anything wrong, just means you should be ready to explain it if asked.

0 coins

Seasonal construction pattern is exactly my situation. Good framing to have ready.

0 coins

The key phrase when talking to a DETR agent is 'seasonal employment in the construction industry with the same base period employer.' That language usually signals to them immediately that this is a standard pattern they've seen.

0 coins

Same employer returning to work is actually simpler for them to verify than a new employer every time. They can see the wage records match up without needing additional documentation.

0 coins

Just want to add for anyone reading this later: the CSS portal not showing flags does NOT mean there are no flags. Some adjudication flags are internal and don't surface to the claimant-facing view until a determination is actually made. The portal is a simplified view of your account, not the complete picture.

0 coins

This is probably the most useful paranoia-inducing thing I've read in this thread. So even a clean CSS view is not a guarantee.

0 coins

Not a guarantee, no. But combined with clean week-ending dates, clean effective dates, and accurate certifications, it's a very strong set of indicators. You can't have perfect certainty without talking to an agent.

0 coins

The internal flag thing is exactly why getting an agent to look at your full account record is valuable. They see a different layer than what CSS shows claimants.

0 coins

Circling back to what finally gave me resolution in my situation: I wrote down both claim numbers, all payment dates, all week-ending dates, and the name of every employer involved before I called. The agent was able to pull everything up faster because I could give her exact references instead of just saying 'I think there might be an overlap.' Being specific saved probably 20 minutes of call time.

0 coins

Both claim numbers specifically - I should write that down. I know my current claim number but I'd have to dig for the old one.

0 coins

Old claim number is in your CSS portal under claim history. Worth finding it before you call so you're not fumbling during the conversation.

0 coins

Preparation before the call makes a huge difference. When I used Claimyr to get connected, I had everything laid out in front of me and the whole conversation was quick and clean because I wasn't trying to find things mid-call.

0 coins

Nevada Unemployment AI

Expert Assistant
Secure