IRS and Tax Filing Issues

I was actually going to mention this earlier, but I couldn't quite find the right moment—have you considered whether anything changed in your system settings just before this started happening? 🙂 You might have accidentally installed a new version of Java or some similar update

Henry Edwards33 said:Look, if you're still filing using the "old" forms in June, what's the big deal? 🤷

In just fourteen days, we will have reached the eight-month mark, at which point the seven-month filings become due; should we not reasonably expect the experts at the IRS to have updated the digital forms to align with USA regulations by then?

The IRS is going to be the death of me.
I can't sign anything—not a single sales tax form will go through. Every time I hit sign, it just tells me the form isn't signed. To make matters worse, getting a hold of anyone at IRS customer service is mission impossible. Anyone got a clue what to do??

that’s probably just because of that new Java update... honestly, just ditch that version and grab something like Java 7 update 20 instead
or you could try pulling the card out and popping it back in to get it signed—but then you'd have to do that whole dance every single time you need a signature

It’s going to ask you to sign it a second time. When that pop-up appears, just hit NO, and it should process the signature correctly. I’m running Java 7.25 and that’s how it works for me.

Sent from my iPhone using Twitter

I couldn't get it to work on Edge at all, but switching over to Google did the trick instantly. On Edge, those pop-ups I usually see just wouldn't show up, so I kept hitting NO. As long as it went through, I don't care. 🙂 thanks

Man, I don't even know where to start. I’ve been wrestling with these sales tax forms all morning, and I honestly feel like I just wasted a massive chunk of my day. I finally figured out how to sign everything, but by the time I got my head around it, I realized I hadn't even finished submitting the full batch. And then—just when I thought I was making progress—they go and roll out a brand-new version of the form! Now the system won't even let me submit anything for the June period. I feel like I'm about to lose my mind here. 🙂 Does anyone have any advice on how to handle this?

Sam Wells5 said:Man, I don't even know where to start. I’ve been wrestling with these sales tax forms all morning, and I honestly feel like I just wasted a massive chunk of my day. I finally figured out how to sign everything, but by the time I got my head around it, I realized I hadn't even finished submitting the full batch. And then—just when I thought I was making progress—they go and roll out a brand-new version of the form! Now the system won't even let me submit anything for the June period. I feel like I'm about to lose my mind here. 🙂 Does anyone have any advice on how to handle this?

There is 😉

Once you navigate to the forms section, simply click the arrow within the sales tax form menu, and you should see the option for the period ending July 31, 2013.

Brian Campbell36 said:There is 😉

Once you navigate to the forms section, simply click the arrow within the sales tax form menu, and you should see the option for the period ending July 31, 2013.

Thank you so much, I mean it. I’m going to go try that right now. Honestly, I woke up with such a stomach cramp earlier, I really need this sorted out.

Ever since they rolled out that new app yesterday, it keeps telling me my digital signature isn't valid on the forms. So, naturally, I try calling their customer service line, and of course—nothing. Not a single soul picks up the phone.

I figured it out. If you're running into the same headache I was, just try sending it through Chrome—it actually works.

Does anyone here have experience trying to send an R-form through the e-filing portal, and if so, have you run into any glitches lately? Everything seems to be functioning perfectly fine on my end—I can navigate the menus without a hitch—but the moment I select my file and hit "sign and submit," absolutely nothing happens. It’s like the button is dead. I could sit here clicking it until tomorrow and I wouldn't get so much as an error message; there's just total silence from the system. To try and troubleshoot, I actually uninstalled Java 7.25 and rolled back to an older version, but even that didn't change a thing. That signature button is completely unresponsive. Any advice or help would be greatly appreciated!

Brenda Chase3 said:Does anyone here have experience trying to send an R-form through the e-filing portal, and if so, have you run into any glitches lately? Everything seems to be functioning perfectly fine on my end—I can navigate the menus without a hitch—but the moment I select my file and hit "sign and submit," absolutely nothing happens. It’s like the button is dead. I could sit here clicking it until tomorrow and I wouldn't get so much as an error message; there's just total silence from the system. To try and troubleshoot, I actually uninstalled Java 7.25 and rolled back to an older version, but even that didn't change a thing. That signature button is completely unresponsive. Any advice or help would be greatly appreciated!

I'm hitting the exact same wall. I called Goldman Sachs about it, but they couldn't give me a straight answer...

The real issue stems from the Okta application.
Even after reaching out to the IRS, I didn't get much traction there, but at least they actually called me back, which was a nice change of pace compared to the usual helpdesk experience. I'm going to copy and paste the email my buddy sent me explaining the fix. Once I went through a fresh installation, everything started working perfectly again.

To make it simple, you just head over to the Chase website, navigate to the Support section, select the web installation option, and then install the drivers for your card reader along with the new Okta. When you go to sign your first document, the system will prompt you for the file path to acpsk11#, so you'll need to type that in. Just make sure you do a quick search on your computer beforehand so you know exactly where that specific file is located.

And just like that, everything is back up and running smoothly.

silverbadger said:The real issue stems from the Okta application.
Even after reaching out to the IRS, I didn't get much traction there, but at least they actually called me back, which was a nice change of pace compared to the usual helpdesk experience. I'm going to copy and paste the email my buddy sent me explaining the fix. Once I went through a fresh installation, everything started working perfectly again.

To make it simple, you just head over to the Chase website, navigate to the Support section, select the web installation option, and then install the drivers for your card reader along with the new Okta. When you go to sign your first document, the system will prompt you for the file path to acpsk11#, so you'll need to type that in. Just make sure you do a quick search on your computer beforehand so you know exactly where that specific file is located.

And just like that, everything is back up and running smoothly.

🤔

I think there's some logic to what was written here, but I'd probably need a much longer explanation to actually grasp what needs to be done. 😁

Could you maybe break it down step-by-step for the complete amateurs, or at least give me a slightly more detailed version? 😁

Alright, so,

we’ve been dealing with this massive headache where digital signatures just won't play nice with any of the major banks out there because of some Java update glitch.
Someone already suggested—basically, just wipe Java off your system entirely, grab the absolute latest version from the web, and THEN—hit up your Control Panel, open the Java settings, and uncheck that "enable next generation Java plugin" box under the Advanced tab.

Honestly, if you actually see that specific option, that second step might be all you need to do (though, fair warning, it doesn't always show up unless you've manually installed the newest version first).

Just make sure you kill off every single browser window you have open before restarting the app, and then everything should click right into place. (And seriously, YOU HAVE TO BE PATIENT while it processes those signatures!)

Really hoping this saves at least a few people from a meltdown, because man, I know how incredibly annoying this whole mess can be.🙂

copperscout17 said:Alright, so,

we’ve been dealing with this massive headache where digital signatures just won't play nice with any of the major banks out there because of some Java update glitch.
Someone already suggested—basically, just wipe Java off your system entirely, grab the absolute latest version from the web, and THEN—hit up your Control Panel, open the Java settings, and uncheck that "enable next generation Java plugin" box under the Advanced tab.

Honestly, if you actually see that specific option, that second step might be all you need to do (though, fair warning, it doesn't always show up unless you've manually installed the newest version first).

Just make sure you kill off every single browser window you have open before restarting the app, and then everything should click right into place. (And seriously, YOU HAVE TO BE PATIENT while it processes those signatures!)

Really hoping this saves at least a few people from a meltdown, because man, I know how incredibly annoying this whole mess can be.🙂

As for the freezing issue, that didn't work for me. We followed those steps and the signing button still won't respond. It doesn't throw an error or anything; it’s just completely dead. We spoke with support at Chase, and they told us they'd reach out once they figured out a fix, but nobody has called today and the function is still broken.

When I was dealing with those signature issues, I found that this directive from the IRS actually cleared everything up for me.

Michael Perez83 said:When I was dealing with those signature issues, I found that this directive from the IRS actually cleared everything up for me.

Thanks, triax, but I think we’re dealing with a different beast entirely here. Our settings are perfectly configured; we’ve actually walked through the entire setup process with IT administrators over the phone three separate times now, yet that signature button remains completely unresponsive. It isn't even throwing an error message—that would at least be progress. Instead, you click the button, it highlights as if it's registering the mouse click, and then... nothing. It’s just dead. I called support again today because we haven't heard a peep from anyone in five days, and the representative basically admitted they're getting calls about this exact issue from everyone. They couldn't tell me what's causing it or why it's happening, and more importantly, they had no idea how to fix it. They've logged the bug and they're aware of it, but honestly, they seem totally clueless on how to resolve it.

silverbadger said:The real issue stems from the Okta application.
Even after reaching out to the IRS, I didn't get much traction there, but at least they actually called me back, which was a nice change of pace compared to the usual helpdesk experience. I'm going to copy and paste the email my buddy sent me explaining the fix. Once I went through a fresh installation, everything started working perfectly again.

To make it simple, you just head over to the Chase website, navigate to the Support section, select the web installation option, and then install the drivers for your card reader along with the new Okta. When you go to sign your first document, the system will prompt you for the file path to acpsk11#, so you'll need to type that in. Just make sure you do a quick search on your computer beforehand so you know exactly where that specific file is located.

And just like that, everything is back up and running smoothly.

If this is intended as a solution to the issue I described earlier, could you please walk me through the steps in a bit more detail? I'm finding the instructions a little hard to follow. Also, I have an e-card (not a USB stick), if that makes any difference.