Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Locked Batches Payment Entry Locked Batch Payments Journal Locked Batches Selecting all batches for posting '(*POST_IN_PROGRESS*)' |
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This article was created as a Master Article for all things Locked Payment Batches within Munis. Batches can get locked for a few different reasons including multiple users attempting to make changes in the same batch or with two different programs, server connectivity issues and even users clicking the browser (X) to close out of Munis programs instead of Munis' built in Back button which allows processing to finish before closing out properly. There are also times where users might be selecting all of the batches for posting in a program like Payments Journal and this can erroneously lock the batch for posting by that user. There are also times where sites may see a 'POST_IN_PROGRESS' message related to one or more batches after a failed posting which these are due to server to Munis connectivity or users hard closing out of Payments Journal before the posting finishes either from Munis, Chrome or other supported browser. Munis will lock the batch and populate the clerks name as '(*POST_IN_PROGRESS*)'. See resolutions below to assist in unlocking batches in the respective version and scenario. |
...
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
11.3 and Below (v11) Payments Journal Locked Batches1. Navigate to General Revenues>Payment Processing>Payments Journal or Property Revenues>Payment Processing>Payments Journal. If a different message then step 9 appears, please submit a case with Munis Support. 2017.1+ (v12) Payment Entry Locked BatchesA Payment Batch can be locked in Payment Entry by a user and another user attempting to pull it into another program such as Payments Proof or Payments Journal for an Output or Posting Process when a user may have released the batch but left it open in Payment Entry. When this happens, most times user's can unlock these batches themselves. The user or clerk who has the Payment batch locked in Payment Entry is the only user who can attempt to unlock or free this batch up. Usually, that user will still have the batch held in Payment Entry or may have more than one instance of Payment Entry open without knowing. That specific user should confirm this and then perform the following process. 1. Re-Open Munis Payment Entry. If the above steps do not work or the user that has locked the batch is not available, please submit a case with Munis Support. 2017.1+ (v12) Payments Journal Locked BatchesPayment Batches can also be locked within the Munis Payments Journals program. This can happen if a user selects a few batches or does a wide open search in the Payments Journal program. This action locks the selected or all of those batches for posting. The batches will remain held for posting if the user leaves the program open on their machine or if they close Payments Journal using the browser (X) and does not use the Back button to close the program. When this happens, as above those batches are held for posting in that program by that specific user. This specific user should always un-select these before leaving the program using the following steps. 1. If the user has left the Payments Journal program, it will need to be re-opened by that user. If the above steps do not work or the user that has locked the batch is not available, please submit a case with Munis Support. 2017.1+ (v12) Payments Journal Locked Batches with (*POST_IN_PROGRESS*)In this scenario, Munis has hard locked batches. Please submit a case with Munis Support. |
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
What is Batch Locking? Accounts Receivable Settings Use Batch Locking |
...