I would like to hear from anyone who is using Great Plains as the Financial Software. I have a specific interest in how you handle posting date. Do you have a system in place for making sure all the batches get posted every day? Or do you allow for a delay in Posting.
I would also be interested in knowing if any of you have issues with handling the default GL? Our users have a habit of putting things in the default GL when there is a delay ion getting a proper GL. Does this cause errors in Great Plains?
I
I'm not sure about Great Plains, but this sounds like you're trying to "outsource" some of tessitura's functionality and I'm not sure how wise that would be. If you post to the default GL and then make corrections in Great Plains, then Tessitura's posting history is no longer accurate.
I would NEVER post to the default GL, since the only way to correct that in Tessitura is by running an UP_UNPOST stored procedure. Using it in place of the real GL when there is a delay makes sense, and I do it too, but we have the liberty to do so since we don't post batches every day.
Also, I'm the only person in the organization who does our batch posting. This means I'm responsible for the accuracy of these postings, so I make a point of examining every "pre-posting summary" to make sure a few specific GLs (including the default one) either never show up or fit within a predetermined restriction. This process allows me to use the default GL as a safeguard -- if I am setting up an event and I don't know what the GL is supposed to be, OR I'm setting up a free event where there's never supposed to be ticket revenue, I assign the Default GL -- so if it ever shows up in the pre-post, I know something was configured incorrectly or I forgot to update the paid event to the correct GL.