I just want to chime in on this.

I have payroll clients in ILL, OK & MD.

I have no issues with pulling up Pay Liabilities - E-Payments tab for my ILL & OK clients.

When I try to pull up for my MD clients, I get the Unrecoverable Error.

Our engineers are working on a permanent fix to the issue, shuaib95.

I do appreciate your time for posting your question here. I checked our system and our engineers are currently investigating the root cause of this issue. I'd suggest reaching out to our Payroll Support Team so we can add your account to the notification list. This way, you'll be able to receive updates through email. 

Let me know if you have other questions. I'd be more glad to help. Take care!

Any updates? 

I just found out that my last payment was rejected and had to spend over an hour-and-a-half on the phone with support to figure out why because the history tab still crashes QB.  The support person told me that he doesn't see an open issue regarding this problem.  PLEASE tell me he is wrong!!!!

Hello @valprice1,

Currently, we have an on-going investigation where users, like you, get kick out of the program after it crashes. Rest assure that our engineering team is in all hands working to fix this as soon as possible.

In the meantime, they have suggested opening QuickBooks Via Administrator as the workaround. You can do so by following the steps below:

1. Close QuickBooks.
2. On the QuickBooks icon, right-click it.
3. Select Properties.
4. Under Compatibility, select Run as Admin.
5. Click Save and close.

However, I'd still recommend contacting our Customer Care Support. Even if you have reached them, only one of our specialist from the Payroll Team can associate your account to the said open investigation. To do so:

1. Go to Help.
2. Select QuickBooks Desktop Help.
3. Click Contact Us.
4. Enter QuickBooks Crashes in the Tell us more about your question: field.
5. Select Search.
6. Click Start a Message.

Additionally, I've also included this helpful reference for a compilation of articles you can use while working with your payroll: Help Articles for QuickBooks Desktop Payroll.

We appreciate your patience as we're working on this. Please let me know in the comments if you have any other questions. Stay safe and well!

@JonpriL 

Running as admin has no effect on this.  And when you call in to talk to someone, they say they can't find an open investigation, so they can't add you to the list of people who need to be notified, then they force you to go through all the stupid, useless troubleshooting steps all over again, and then they hang up on you before starting an investigation, so you wind up in the same irritating, infuriating, loop.  Just sayin'.

In case anyone else needs it, the investigation number is INV52183.

I sent QBW file to them.  After couple of days, I got call from QB - Support and they discussed all my issues and went over  the whole thing.   In summary - they cannot fix it.

Shen said, she checked the files and there was no error with my data file.  and it is due Maryland State issue, they will provide an update (software) when they fix it. They can not do anything at this point and have to live with this issue.

I then asked them about possible issues at year end W2, efile, other state efile.  According to her, it will not be an issue and if there is one - We will have to live with this until they (QB) find a resolutions.

Here is quickbooks,  will not allocate resources to fix the problem and every other quarter they jack up their fees.  Totally unacceptable.  their Epayment fees over the past year and half went up to $0.75 cents per item to $3.00.

They got us and they do not care very much at this point.  

Thank you 

RR

We have been experiencing the same problem since Maryland's Beacon transition with both of our QuickBooks Desktop files that use Enhanced Payroll services.  These files are being accessed from two different computers running two different versions of QuickBooks (Pro and Accountant).  The result is always the same - clicking on the E-Payments history tab under Payroll Liabilities causes a software crash.  

Based on the recommendation above, I contacted QB support this morning and asked that I be "added to the list" for Investigation INV52183.  I was assured that investigation number is correct and "ongoing" and then given a new case number which is supposed to be linked to that investigation. 

We also had the EFTPS password issue described above .  I'm thinking that the EFTPS error was unrelated, but since it caused many of us to click on the E-Payments tab for the first time since the Beacon transition, it felt like it might have been connected.  Changing our EFTPS password resolved that issue for us.

Intuit - hope you're listening.  This crash is a serious issue that needs to be resolved quickly.

@RR2448 

Just noticed your EFTPS password expired link - this one is not actually related to the thread about the crashing of QB and inability to file or pay MD UI through QB. 

EFTPS announced a new protocol last year - if you file through a 3rd party (i.e., QB payroll), your EFTPS password will expire every 13 months and must be reset.  When you log into EFTPS directly, it doesn't tell you this!

So you will need to go onto the EFTPS website, under My Profile and change the password every year.  Then you will need to update that password in QB when you are sending the next payment.  I'm setting reminders for all my clients who use QB Desktop payroll.

Thank you.  good update and I did change PW etc at EFTPS.

The other issue (MD) - is not resolved.  I have to login to EFTPS to confirm, if my payment has been accepted. I used to get email payment status - "Accepted/Rejected" when a payment was made to IRS - for some reason, I am not getting for this client - for other Clients - No issues.

Thank you

@RR2448That's interesting - I did run two payrolls today and received the email confirmation in desktop, both the submitted and accepted versions.  When you next go to e-pay the liability, check your email address to ensure that it is correct?  One of my clients had an unmonitored email address listed on the e-pay confirmation/pin/password screen - once we changed it, the emails showed up regularly.  (That was the reason that they didn't know the payments were being rejected due to a need to change the password.)

I feel like the widespread attempts to increase security and improve functionality are just snowballing us all into nightmares of inefficiency.  Between Maryland Department of Labor, EFTPS, the various bank websites, and Intuit, I might as well go back to pencil and ledger paper and pen and paper checks.  :)

And, yes, you are correct.  The Maryland Beacon UI issue and the ability to review the e-payment status tab are not resolved.  At this point, I think all Maryland employers need to know that they will have to pay their Q4 contributions by check or epay on the Beacon site.  And they will need to file the form manually (on paper) or directly on the Beacon website as well.

Thanks for the information about the EFTPS password expiration! My December EFTPS payment made through Quickbooks was rejected because of this. I got an email notification saying my password had expired, but I then logged onto the EFTPS site and it worked without any mention of my password being expired. To your point, it looks like the password is valid and works when logging in, but is considered expired as far as third party apps go. For December, I made my payment via the EFTPS web site. I was going to leave my password alone and try again next month via Quickbooks to see if it was an anomaly, but now I know that I actually need to change it and will do that before making my January payment.

Same situation occurred to me.  Need assistance!

Hi there, huggins1. I'd be more than happy to go over what you'll need to do when encountering a "One or more scheduled liability payments is missing information that will prevent it from displaying on the Payroll Center." message.
 

This type of error indicates that one or more scheduled liability payments weren't processed due to missing information. It can be fixed by correcting what your books are flagging on the payment(s).
 

Here's how:

1. In your top menu bar, go to Employees, Payroll Center, then access the Pay Liabilities tab.
2. On your Other Activities section, click Manage Payment Methods.
3. Choose Schedule Payments. A list of existing scheduled payments will be displayed. Look for any that show a warning sign (⚠️).
4. If any of them are flagged for missing details, you'll need to use your Edit... button to enter the required info.

In the event you've entered all of your information, but still see the same error message displaying, you'll want to get in touch with our Customer Care Team. They'll be able to pull up your account in a secure environment, conduct further research, and create an investigation ticket if necessary.
 

They can be reached while you're signed in:

1. In your top menu bar, go to Help, then QuickBooks Desktop Help.
2. Hit Contact Us.
   
3. Enter a brief description of the issue in our Ask a question (or tell us what's wrong) field.
   
4. Click Continue.
   
5. Select We’ll contact you for a callback or Message Us to start an instant messaging session.

Be sure to review their support hours so you'll know when agents are available.
 

Please feel more than welcome in sending a reply if there's any questions. I'll be here to help. Have a lovely day!

Hi ZackE -

Can you please update us Maryland payroll users on the status of Investigation INV52183. This is the software issue that has arisen since the replacement of Maryland's former workers compensation system on October 1st.  The symptom is that Maryland payroll users experience a full software crash in QuickBooks (program ends) upon selecting the "E-Payments" tab under "Payment History" on the "Pay Liabilities" tab of the "Employee Center".  This issue is well documented by multiple users and is already the subject of an investigation by your engineering team (#INV52183).  It is most urgent that this issue be resolved so that Maryland users and view their E-Payment History. 

Please update us on your progress in fixing this software issue.

Thank you,

Michael Saxon

Hi there, @bmore.

I'm here to help you get to the right support.

The Community is unable to track the details about the updates of this investigation number. This needs special tools for privacy and security purposes. Since you've mentioned in your previous post that you've already contacted the QuickBooks Care Team about this investigation. They will send you an email once it's already fixed.

I'd still recommend contacting our QuickBooks Care Team to know more about how this investigation goes.

You may consider checking the support hours before contacting them to know the right time to call at your convenience.

You can always tag my name in the comment section if you have other questions. I'd be happy to answer them. Take care.

Thanks for the quick reply, MarsStephanieL.  To be clear, this is a blanket issue affecting many Maryland customers of QB payroll.  In fact, the investigation was actually started at the request of a different user.  There is nothing confidential or private about a hard program crash that many Maryland payroll users have experienced upon pressing the E-Payments tab in QB Desktop as described above.  I think we would all appreciate it very much if you, as an Intuit employee, could save us the time of making further phone calls to support (each requiring a lengthy explanation) by finding out for us when we can expect this critical program error to be fixed.

Thanks again,

Mike

Thanks a whole bunch; this worked for me, you just saved me a lot of heartache.  It was my last try to fix before I let QB support delete my file and then use an earlier, pre error message file and then "just re-enter the data to bring it up to date".  I am rapidly loosing patience with QB - I have used it for 25 years, it used to be so problem free, and now!.

Hello @scouse, welcome to the Community.

I'm so happy that the support you found here has helped you reach your goal!

If you have any additional questions, please let me know so that I may assist you.

I hope you have a wonderful rest of your week :) 

Thank you Big Red Consulting. I use QuickBooks Non-Profit Edition, but I could never find the "Related Activities Button." Your instructions are clear and exact.  Mine was the Maryland Unemployment, which I have been e-filing for several years. It was weird because just out of the blue one day, I get this error message.  Anyway, thanks to you, I was able to go in an fix it; unfortunately, however, the option to e-file is no longer available.

Thanks again for your help.

Is there an update on when Intuit will fix the bug where Quickbooks Desktop crashes when the E-Payments tab is selected within Payroll Center, Pay Liabilities, Payment History? Or is there a work around that allows us to use the E-Payments tab without having Quickboioks crash?

Hi there, apach.

Currently, our software engineers are currently investigating this issue. Rest assured, we're doing our best to get this rectified as soon as possible.

If you haven't contacted us yet, your Customer Care Team to add your contact information to our notification list. This way, you'll be updated once we get this resolved. Once you're in, you can provide this investigation number for a faster transaction: INV-52183.

In the meantime, you'll want to consider making all MD (Maryland) forms inactive to prevent QuickBooks from crashing. Here's how:

1. Select Employees from the top menu bar.
2. Choose Payroll Center.
3. Go to the File Forms tab, then select Make Form Inactive from the Forms drop-down menu.
4. Inactivate all the forms for the state of Maryland.

Additionally, I've included some articles that will help you manage your taxes payments and tax forms in QuickBooks Desktop:
 

• Pay and file your payroll taxes online 
• View and print payroll tax forms

I'll be right here to assist you again if you need more help in completing your other tasks. You're always welcome to tag me in your comments and posts.

Thanks for the suggestion. I made all the MD forms inactive, but unfortunately, Quickbooks still crashes when I hit the E-Payments tab. Let me know if there is any other work around you can think of to get that tab working without Quickbooks crashing.

Thank you!

Thank you, I had this same QB error just show up today and it even had the same cause: a missing state Unemployment Agency account number.