Tips for front line users leaving batches held

Hi all, I know Tessitura does not recommend auto-closing or auto-posting of batches. We have multiple venues that the front line users close the batches at the end of the day, but do not post them. Finance does that the next business day. A couple of times we have had users leave their batch in held at the end of the day, then accidentally re-open that batch the next day and start using it again before Finance can get ahold of it. I'm wondering if any other front line/visitor services managers can shed some light on what they do to ensure all batches are closed at the end of the day. Thanks! Grant Offermann
Parents
  • Grant, At our organization, I'll periodically check our batches in Batch Administrator and if anything is in Open or Held status, I'll communicate either to a supervisor or to the user directly that they need to get that batch to at least closed status by end of day. We also have two locations, though our batches are primarily initiated and worked in at our primary location. We also have users who are empowered by our Director of Finance to post batches once they've been closed, which keeps things pretty tidy since a closed batch is automatically worked all the way through the workflow. Thank you, Brian
Reply
  • Grant, At our organization, I'll periodically check our batches in Batch Administrator and if anything is in Open or Held status, I'll communicate either to a supervisor or to the user directly that they need to get that batch to at least closed status by end of day. We also have two locations, though our batches are primarily initiated and worked in at our primary location. We also have users who are empowered by our Director of Finance to post batches once they've been closed, which keeps things pretty tidy since a closed batch is automatically worked all the way through the workflow. Thank you, Brian
Children
No Data