- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Employees and payroll
Thank you so much! This was exactly what the problem was!
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Employees and payroll
@DivinaMercy_N @dso0216 and many others. Dare we hope that the bug that was causing QBDT to crash when accessing e-pay history has FINALLY BEEN FIXED? I have been testing it periodically for the last year-and-a-half with no success. But TODAY! In two files, I was able to check e-pay history for payroll liabilities and the program did not abort! It would be lovely if true, and lovelier if those of us who have waiting on this INV-52183 fix would be notified that it is solved - as we were promised we would be. Are we now able to e-pay MD UI again? Or is that still a manual process?
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Employees and payroll
Well, I'll be! Thanks for the good news valprice1. Confirming I can also see my payroll liability epay history for the first time since October 2020. As for your other question, I am not aware of any changes to Beacon that would allow automated payment via Quickbooks. If you find out that's the case, please let us know. Until then, we'll continue to pay via the Beacon website.
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report Inappropriate Content
Employees and payroll
@Bmore I fully intend to test it this month. The issue was that Beacon required a type of payment that QB didn't support. I can never remember which is which ACH-Credit vs. ACH-Debit. In one, you tell the bank to send the money, in the other, you tell the entity to request the money from your bank. So it may still not work, but worth a try!