Create an option to UN-POST tickets if they haven't been invoiced.
Editing tickets in history is much more difficult than in edit, for good reason. If tickets are posted before proper edits are complete, it is very time consuming to resolve.
users are not able to put tickets on hold once they have been posted, they have to exclude the customer from invoicing when only a few tickets need to corrected.
tax service exceptions that kick out during invoicing or posting. It would be very helpful to be able to put the tickets back in edit and correct destinations and orders and tickle the tickets with the correct zip combinations. We sometimes have to do a back door data update script to correct invalid addresses
APEX companies that have a lot of other charges that must be added to the tickets before invoicing and ticket changes from the plants are not turned into the billing department until tickets have been posted in many cases. This could help with having to do multiple credit rebills to our customers.
We have no audit record of tickets changes when the changes are made on tickets in history. This is an audit issue.
Can you articulate the impact on your billing process when you must edit the posted tickets? For example, to bill a day’s worth of tickets takes X number of hours on a good day. If you must edit tickets in history before you can invoice them, how much time to the billing process is added to fix those tickets? And how frequently does this occur?
Still gathering statistics
Chris,
Can you articulate the impact on your billing process when you must edit the posted tickets? For example, to bill a day’s worth of tickets takes X number of hours on a good day. If you must edit tickets in history before you can invoice them, how much time to the billing process is added to fix those tickets? And how frequently does this occur?