Currently, when there is a PO that has coding changes, the only way the unapproved invoice is updated for the new coding is if the PO is removed (or the PO line is removed) and readded to the unapproved invoice line. It should just be updated when the PO is updated. An invoice can get all the way to posting before it kicks out an error that the PO line doesn't match the PO. This causes a lot of work to fix. Also, if an unapproved item has an error that will not let it post, it shouldn't be able to be pulled into a posting batch and the error should show prominently in the unapprove invoice form.
| Company | Texas State Utilities, LLC |
| I need it... | Yesterday...Come on already |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.