Back to Virginia Unemployment

Giovanni Gallo

Virginia VEC says my unemployment claim couldn't be processed because of outstanding claim

Okay so I'm completely lost and stressed out right now. Filed a new unemployment claim two weeks ago after getting laid off from my warehouse supervisor job and instead of getting approved or even getting put into adjudication like I expected, I got this bizarre message saying my unemployment claim couldn't be processed because of outstanding claim — but I haven't filed for unemployment in over two years. The last time I collected was briefly in 2022 when I got furloughed, and that ended fine. No overpayment notices, no flags, nothing. I even went back and checked my old CSS portal account and everything shows as resolved. So why is Virginia VEC acting like there's some unfinished business from a previous benefit year? I have no idea what an 'outstanding claim' even means in this context. Does it mean there's money I owe them? Does it mean there's an old claim that wasn't formally closed? I'm a single parent with two kids and I just need to understand what's actually blocking my new claim from moving forward. Any help would be huge right now.

Wait, did the message appear on the CSS portal itself or was it in a separate letter they mailed you? Because that actually changes what your next step should be. The portal sometimes throws that error when there's an old benefit year that technically didn't get a formal closure determination — doesn't necessarily mean you owe anything. If it's a portal message, logging out and back in after 24 hours sometimes clears it if it was a system glitch. But if it came in an official letter with a determination date and decision number on it, that's a different animal entirely and you'd need to respond within a specific timeframe.

0 coins

How recent does the letter have to be for the timeframe to still be open? Mine showed up only as a portal notification, not a physical letter — at least nothing has arrived in the mail yet.

0 coins

Portal notifications and mailed letters run on different clocks sometimes. I'd check both your CSS inbox AND your physical mail for the next few days before assuming it's just a system thing.

0 coins

Same thing happened to me in early 2024 — portal said outstanding claim, no letter, and it turned out there was a stale claim from 2021 that never got a final week certified. VEC had to manually close it on their end before my new claim could process.

0 coins

Honestly the fastest way through this kind of thing is actually getting a live VEC agent on the phone — the portal messages almost never give you enough detail to know exactly what's blocking it. I know calling VEC is basically a nightmare normally, but I used Claimyr a few weeks ago when my own claim hit a wall and got connected to an agent same day. The site is claimyr.com and there's a quick video showing how it works at https://youtu.be/GK1CFuX4p2k — seriously saved me hours of redialing. An agent can pull up your old benefit year and tell you in like two minutes whether there's a balance, an open week, or just a system flag that needs clearing.

0 coins

Is the process pretty straightforward even if you've never used anything like that before?

0 coins

Did it end up resolving the actual claim issue or just help you get the info about what was wrong?

0 coins

sounds too easy lol but I've been trying to call VEC for nine days straight so at this point I'd try anything

0 coins

Okay so here's what that message usually actually means in plain terms. You left that 2022 claim — your last benefit year ran until a certain end date, right? If you stopped certifying before that date without a formal separation, VEC's system sometimes keeps the claim in a kind of open-limbo status. It doesn't mean you owe money. It means the system thinks you might still be on that old claim. When you filed the new one, the backend saw two 'active' or unresolved records associated with your SSN and threw up the block. The fix is usually an agent manually closing the old benefit year on their side, which is a pretty routine thing for them to do — but you do have to reach them to get it done.

0 coins

Mine ended in spring of 2022 and I definitely stopped certifying way before the benefit year would've ended — does that make it more or less likely to be this open-limbo thing?

0 coins

Actually stopping early is exactly what causes it. If you'd kept certifying until they cut you off, the system closes it properly. Stopping on your own leaves it in that weird in-between state.

0 coins

they really need to fix this, the system should auto-close after a claimant stops certifying for more than like 30 days. this is such a common issue

0 coins

Can I ask something that might be dumb — did you happen to work any gig or contract work between 2022 and now? Even something short-term? Because sometimes a 1099 situation during an old benefit year can pop up as 'outstanding' if the wage records didn't match what you reported, and that's a slightly different situation than just an open claim. Not trying to alarm you, just want to make sure we're pointing you in the right direction.

0 coins

Briefly did some contract work in fall 2023 but that was well after my 2022 claim ended — would that even be connected?

0 coins

Fall 2023 would be a totally separate benefit year window so it shouldn't reach back and affect a 2022 claim. You'd be looking at two completely different claim periods, they shouldn't interact.

0 coins

Yeah that timeline should be clean. The 2022 claim and 2023 wages would be in separate benefit year buckets. Sounds more like it really is just the open-limbo closure issue the other person described.

0 coins

SAME EXACT THING happened to me and I want to warn you it can drag on if you don't get proactive. My 'outstanding claim' block sat there for THREE WEEKS because I kept waiting for VEC to fix it on their own. They don't. They are not going to spontaneously close your old claim and release the new one. You have to initiate the contact, you have to get an agent to look at your specific record, and then it takes them maybe 48-72 hours to actually process the manual closure. The sooner you get that ball rolling the sooner you get paid.

0 coins

Three weeks — did you lose those weeks of benefits entirely or could you backdate them once it got resolved?

0 coins

I got to backfile for the weeks I missed once the block lifted, so the money wasn't lost forever but man it was stressful waiting. Make sure you document every day you try to contact them in case you need to explain the gap.

0 coins

Seconding that you should document everything. Screenshots of the portal error, dates you called, everything. VEC can be really reasonable about backdating when there's a system-side issue causing the delay.

0 coins

Quick question about your old CSS account — is it the same login you're using now, or did you create a new account when you filed this time? Because sometimes people create a second CSS profile without realizing it and then there are two separate account records for the same SSN and THAT also throws an outstanding claim error. It's worth double-checking you're not accidentally looking at a ghost account.

0 coins

Pretty sure it's the same login, same email address — but honestly how would I even verify that for certain?

0 coins

You'd need to call VEC to have them check how many CSS profiles are linked to your SSN — it's not something visible from your end on the portal. Another reason a live agent call is really the most direct path here.

0 coins

I've seen this double-account thing trip people up more than you'd think. Especially if you registered a long time ago and forgot the email, then registered again with a different one when you came back to file.

0 coins

Oh man I really feel for you dealing with this as a single parent. The outstanding claim thing is super stressful because the error message gives you absolutely nothing to work with. Can I ask — when you check your claim status right now, does it show 'pending,' 'in adjudication,' or something else entirely? The status label on the portal can sometimes hint at what kind of outstanding issue it is.

0 coins

It's showing as pending but there's literally no indication of what kind of pending — no adjudication notice, no request for additional information, nothing.

0 coins

Pending without any associated issue on the portal is usually either the open-limbo thing or a wage record discrepancy. Both fixable, both need an agent. Adjudication would look different and have its own notice.

0 coins

If there's no adjudication flag showing that's actually a decent sign — means they haven't formally found a problem with your eligibility, just a technical processing block.

0 coins

Does anyone know if Virginia VEC has like a specific department or unit that handles these old claim closures? I'm dealing with something similar and every agent I reach seems to just transfer me somewhere else and then the call drops. It's genuinely infuriating. I've been at this for two weeks.

0 coins

There isn't a separate unit per se — any regular claims agent can initiate the manual closure on their end. The issue is that some agents aren't sure how to do it and just transfer you, which is a training gap on their side. If you get transferred, ask specifically to speak with a claims examiner rather than a general agent.

0 coins

Ugh I know exactly what you mean about the transfer loop. I got transferred three times in one call before getting disconnected. So demoralizing.

0 coins

Try calling right at opening time, like the first five minutes they're open. I've had way better luck actually reaching a knowledgeable agent at that hour versus calling midday when everyone's clogging the lines.

0 coins

Just want to drop back in here — I tried Claimyr after seeing it mentioned above when my claim had a processing block and yeah it worked. Got through to a VEC agent in a couple of hours instead of my usual routine of calling 40 times and getting disconnected. The agent was able to look at my old benefit year right then and confirm what was blocking the new claim. Website's claimyr.com, there's a demo video at https://youtu.be/GK1CFuX4p2k if you want to see what it's like before committing. Definitely worth it when VEC phone access is basically the only way to fix these manual-closure situations.

0 coins

Did the agent you reached actually have the authority to close the old claim on the spot, or did they just log a request?

0 coins

She said she was putting in the closure request and that it would process within 48-72 hours. And it did — my new claim started moving after about two days. So she couldn't flip a switch instantly but she did initiate it in real time.

0 coins

ok this is making me reconsider, two days turnaround is way better than the two weeks I've been spinning my wheels

0 coins

For what it's worth — I work in HR and we see the VEC side of things sometimes when our laid-off employees call us confused about their claims. The outstanding claim message almost always traces back to one of two things: either an open certification period from a prior claim that was never formally ended, or a wage record that VEC received from an employer that didn't match what a claimant reported. For a warehouse supervisor job that ended and started clean, the wage mismatch scenario is less likely unless there was a severance payout involved. Did you get any kind of severance when you were laid off this time or in 2022?

0 coins

No severance either time — both layoffs were pretty sudden and there was no payout involved.

0 coins

Clean break with no severance points pretty strongly toward the open-limbo closure issue rather than a wage dispute. That's the simpler of the two to fix — an agent just needs to flag the old claim as closed and your new one should process.

0 coins

Good to know about severance — I didn't realize that could create a wage discrepancy flag on a previous claim.

0 coins

Honestly Virginia VEC's system is so outdated it's wild. The fact that a claim from 2022 that you stopped using can still sit in some phantom-open state and block a 2025 claim with no explanation is just terrible design. No other state's unemployment system works like this and it falls entirely on claimants to figure out what's wrong. I've had three interactions with VEC this year alone and every time the agent I finally reached was like 'oh yeah that's just a system thing we see sometimes' like okay great thanks for designing a system that creates problems for people who are already in a rough spot.

0 coins

Real talk though, is there anywhere to submit feedback or complaints about VEC's system design? Like an actual channel that someone monitors?

0 coins

You can contact your state delegate's office and they sometimes have constituent services staff that can escalate to VEC on your behalf. It's not a feedback channel exactly but it can get things moving faster when the normal process stalls.

0 coins

The delegate's office thing genuinely works — I had a friend who got completely stonewalled by VEC and her delegate's office got her case resolved in like a week. Worth keeping in mind as a last resort.

0 coins

Have you tried submitting a written inquiry through the CSS portal's message center about the outstanding claim error? I know calling is the fastest fix but while you're waiting to get through, a written record of your inquiry can help establish a contact date if you need to request backdating later. Some agents have told me written portal messages actually do get reviewed, just on a slower schedule.

0 coins

Should I reference anything specific in the message, like the old claim year or the error message text?

0 coins

Include whatever specific details you have — your old claim's approximate start and end dates, the fact that you believe it was never formally closed, and the exact wording of the error you're seeing. The more specific, the better chance a reviewer can route it to someone who can actually action it.

0 coins

I'd do both — submit the portal message AND keep trying to call or use a service to get through. The written message alone can sit in a queue for a long time.

0 coins

Something I learned the hard way — after your old claim gets manually closed by an agent, you have to re-initiate your new claim. Like the act of closing the old one doesn't automatically push the pending new one through. An agent should tell you this but mine didn't and I sat there for another week thinking the fix was processing when actually I had to go back in and refile or reactivate.

0 coins

Wait — does refiling reset the effective date of the new claim, or does it hold the original filing date?

0 coins

Great question and yes it matters a lot. The effective date should stay as your original filing date as long as you can show you filed before the block was resolved — that's why documentation of when you first tried to file is important. I'd double-check with the agent explicitly when you get them on the phone.

0 coins

This varies slightly based on the reason for the block so definitely confirm with an agent. In my experience the original effective date was preserved because the delay was VEC's system issue, not a claimant error.

0 coins

Jumping in with my own similar situation — I got the same outstanding claim message and I've been convinced for two weeks it means I owe VEC money back from 2023. Reading this thread I'm now thinking maybe I was catastrophizing. Is there any way to know for sure whether it's an open-limbo issue vs. an actual overpayment flag without calling?

0 coins

If there's an actual overpayment on your account, VEC is required to have sent you a formal Notice of Overpayment by mail — it's a specific document with a dollar amount, the weeks in question, and your appeal rights. If you haven't received that letter, it's probably not an overpayment flag. Outstanding claim from an open-limbo is different and doesn't trigger that formal notice.

0 coins

No letter like that ever showed up — that's actually a huge relief to know. I've been dreading every day my mailbox.

0 coins

The absence of a formal overpayment notice is a good sign but keep in mind mailed letters from VEC can sometimes be delayed. Worth calling to confirm definitively so you're not in the dark.

0 coins

Can I ask what the resolution looked like on the portal once it was fixed? Like did the outstanding claim message just disappear and the status updated, or did you get a new determination notice? Trying to understand what 'fixed' actually looks like so I know when to stop watching anxiously.

0 coins

Mine just updated — the error message cleared and the claim status changed to 'in progress' or similar within about 72 hours of the agent submitting the closure. No separate notice, just the status changed.

0 coins

Same experience here. No fanfare, no email notification, the portal just looked different one morning and I could start certifying. I'd recommend checking every morning rather than waiting for an alert.

0 coins

That's weirdly anticlimactic but good to know — I won't hold my breath for a congratulations email from VEC haha

0 coins

One thing I want to flag that nobody's mentioned yet — your situation as a single parent may affect how quickly you need this resolved from a benefits standpoint, so if you end up in a prolonged back-and-forth with VEC, check whether your county has emergency assistance programs that can bridge the gap while your UI claim is blocked. It's not the same as unemployment but depending on your county social services there may be something that can cover short-term essentials. Just want to make sure you have options while navigating this.

0 coins

That's genuinely good to know — I hadn't even thought about county-level options. Do you know if applying for that affects the UI claim at all?

0 coins

Emergency assistance from county social services is typically separate from unemployment and shouldn't impact your VEC claim — they're different programs through different agencies. Worth calling your county DSS to confirm, but in my understanding the two don't interfere.

0 coins

This is a really solid point. SNAP and local emergency assistance are also worth looking at in the meantime — they're designed for exactly this kind of gap situation.

0 coins

Okay update from me — I had the same outstanding claim problem a couple months ago (old 2021 claim never formally closed) and I ended up using Claimyr to get through to VEC after failing to reach anyone for over a week. The agent I got pulled up my file, confirmed the open benefit year, and put in the manual closure. Exactly what everyone here is describing. claimyr.com and there's a video at https://youtu.be/GK1CFuX4p2k — for a situation like this where you literally need a live agent to do a manual action on the backend, there's really no substitute for actually talking to someone. Took about two and a half days after that call for my claim to start processing normally.

0 coins

Two and a half days is so much better than the limbo I've been in. Did they ask you to do anything on the portal after the call, or was it all on their end?

0 coins

The agent told me to just watch the portal and wait — she said not to file anything new or take any action on the portal while the closure processed, so as not to confuse the system. I followed her instructions and it resolved cleanly.

0 coins

That's a really important tip about not touching the portal while the closure processes. I could see someone anxiously clicking around and accidentally creating another complication.

0 coins

Coming back to something OP said at the start — your CSS portal showing everything as resolved from 2022 is actually consistent with the open-limbo issue because that view doesn't necessarily reflect the backend claim status. The portal shows claimant-facing information but the claim record on VEC's side can be in a different state. It's a transparency gap in their system basically.

0 coins

So I could see 'resolved' on my end and there's still something open on their end that I can't see — that is incredibly frustrating system design.

0 coins

Yeah it's one of those situations where the UI you interact with doesn't match the actual data state. Unfortunately the only way to see what's happening on the backend is to have an agent read it to you directly.

0 coins

This is exactly the problem I was ranting about earlier. Claimants are flying blind and have no idea what their own record looks like to VEC. It shouldn't require a phone call to find out if you owe anything or have an open claim.

0 coins

Can anyone confirm whether you have to file a new initial claim after the old one gets closed, or if the pending new claim just processes automatically? I've seen conflicting info in this thread and I'm about to have an agent close my old claim tomorrow and I want to know what to do after.

0 coins

Based on what I've seen, the safest move is to ask the agent explicitly at the end of the call — they should be able to tell you what happens to the pending claim once the block clears. Some systems auto-push it, some require you to reactivate. Don't assume either way.

0 coins

I had to reactivate mine manually but I've heard others say it processed automatically. Ask the agent before you hang up and get a name or reference number for your call if possible.

0 coins

Regardless of which way it goes for you — keep your original filing date documentation. That date matters for calculating your benefit effective date and backdating any weeks you couldn't certify during the block.

0 coins

Virginia Unemployment AI

Expert Assistant
Secure