@dso0216   The crashing was caused by the update to the Maryland UI site (when they switched to Beacon), which meant that e-payments could no longer be sent through the QB system.  It caused all kinds of problems, some of which have subsequently been fixed, but the crashing is still an issue.  The case number is INV-52183 - please do keep reporting it.  No amount of updating QB, rebuilding your file, clean reinstalls, or upgrades will fix it.  The engineers need to deal with it and all the Maryland clients should be SCREAMING.  I believe it may be happening to Virginia folks too, since VA UI just started forcing epayments differently, but I haven't been able to confirm that.