Put in a warning message if an invoice gets logged in with an accounting date that is more than 6 months ahead of the current month in GL. With the current system, not having any warning is a bad problem, particularly in January, because December invoices are still rolling in. When bookkeepers log in December invoices, they are often forgetting to change the new year back to the old year, and the invoice accidentally gets entered with an accounting date that is effectively a year in advance, e.g. '12/17/2017' when it should have been '12/17/2016' (and thus all of the entries reject). VERY frustrating. A simple warning message would take care of this significant problem.
by: Dan S. | over a year ago | 1 Financial Management
Comments
Put a warning but allow it to post up to year end so it doesn't sit in new for months on end when it is correct. An example is our state estimated tax payments we receive the list and setup for payment through December and process them through our state website in March when we receive them, however the payments for December sit in GL new from March until Sept when it will allow them to post through. It is inconvenient if we do have to move items out of GL new/rename it due to an actual date error because we would have actual accurate items to post as well as error items in the GL new.
To take this a step further, it would also be great to have a setting which allows a "hard stop" to be set; i.e., you get the warning as usual (entering into a future period), but also can set future entries to whatever you desire so that they cannot be entered beyond that date. Would work great for prior entries as well.
Of course, if Sage got rid of a set number of financial periods in the GL Master file and ran everything off of transaction data, this would not be an issue.