If you enter a Miscellaneous Receipt and don't a enter distribution line, you get a Warning, but you are still allowed to charge a credit card using PAYA. If the PAYA batch settles, you are left with an entry in the receipt batch that will become an ERROR batch. Once that ERROR batch has been created, you are stuck. You can't edit the Distribution in the ERROR batch and you can't Delete the ERROR batch. Because the PAYA charge has been settled, you cannot VOID the transaction. The only way to get this situation cleared is via direct editing in SQL. (There are about 7 fields that need to be edited.)

My suggestion is to tighten the error handling (the Warning referred to above) to disallow using the Charge button (PAYA) if there is an undistributed balance. I contend there is never a good reason to have a Misc Receipt that is not yet distributed when charging a credit card via PAYA.

An operator error that results in having to directly manipulate data via SQL Management Studio is a really bad idea. Therefore, make the Warning a Hard Error.

by: Robert G. | over a year ago | General Enhancements