Master Article - Munis Accounts Receivable Locked Batches

Description of Issue
  • Locked Batches
  • Payment Entry Locked Batch
  • Payments Journal Locked Batches
  • Selecting all batches for posting
  • (*POST_IN_PROGRESS*)
Context
  • Accounts Receivable
  • Payment Entry
  • Payments Proof
  • Payments Journal
  • Locked Batches
  • (*POST_IN_PROGRESS*)
Cause

This article was created as a Master Article for all things Locked Payment Batches.

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 programs instead of using the 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 connectivity or users hard closing out of Payments Journal before the posting finishes either from the program, Chrome, or another supported browser. In these cases, the batch will lock and populate the clerks name as:  (*POST_IN_PROGRESS*)

See resolutions below to assist in unlocking batches in the respective version and scenario. 

Resolution

11.3 and Below (v11) Payments Journal Locked Batches

1. Navigate to General Revenues>Payment Processing>Payments Journal or Property Revenues>Payment Processing>Payments Journal.
2. Click Search.
3. Enter the locked batch number in the Batch field, click Accept.
4. Munis should give a Batch Selection Error Prompt stating: Unable to select batch number. This batch will not be included in your selection. To review your selection of batches, please view the maintain page.
5. Click OK.
6. Click Maintain.
7. The batch will show selected where the column header should display a Locked By and Locked Since field, although there are times where this might not be the case and not look locked.
8. Click Update.
9. A prompt should appear stating the Batch number is currently selected by a User. Would you like to override this lock and take control of this batch?
10. Click Yes.

If a different message then step 9 appears, please submit a case with Munis Support.

2017.1+ (v12) Payment Entry Locked Batches

A 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.
2. Use Search or click Browse to identify the locked batch. 
3. Click Resume. This will bring the user into the Bill Find module in Payment Entry. Click Back.
4. Use the Munis Back button in the upper left hand corner of Munis and not the browser (X) to close out of the program. 

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

Payment 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.
2. Click Search.
3. Click Accept.
4. A prompt might show about Batch Selection Errors, this is reporting the locked batches. Check to enable In the future, do not show this message. Click OK.
5. Click the Batches tab.
6. Click Update.
7. Click Select None.
8. Click OK.
9. Click Back.

If the above steps do not work or the user that has locked the batch is not available, please use the next resolution. 

2019.1+ Payments Journal Locked Batches 

  • New functionality was added to let users unlock batches without Support's intervention. 
  • To use this functionality, users must be granted the appropriate permissions by following the steps outlined here: Permission to override Payment Locked Batches
  • When permissions have been added, users can unlock batches without Support's assistance using the steps found here: Unlock a Payments Journal batch

2019.1+ Payments Journal Locked Batches with (*POST_IN_PROGRESS*)

  • New functionality was added to let users unlock batches without Support's intervention. 
  • To use this functionality, users must be granted the appropriate permissions by following the steps outlined here: Permission to override Payment Locked Batches
  • When permissions have been added, users can unlock batches without Support's assistance using the steps found here: Unlock a Payments Journal batch
Additional Information