Currently we can close a fiscal period in the past; however, there is not a way to prevent users from posting to a future date. For instance, recently an employee posted to 12/28/18 instead of 2/28/18. Since it was greater than 60 days in the future, PC warned the user, but the user chose to post the entry anyway. There should be a way to restrict posting to a specific time frame.
Company | John E. Jenkins, Inc. |
Job Title / Role | Accounting Manager |
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.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
This feature has been included in the 3.12.1 release available 1/11/2019
CJ Forgus, we do as well. Quite a few of them. And lots of temporary offsetting entries that will need to be reversed. So ridiculous.
Yeah, it's a problem when users ignore warnings, postings should then be removable and not written in stone, I don't know who did thought such a fixed system would work well.
We've got entries that someone posted in 2014 that were dated 2020. Can't wait until I don't have to look at them anymore.
From my experience, I think "likely but not yet planned" means the solution is years away, if it's really coming at all.
As you can see, a warning was given; however, the user chose to bypass the warning. Without a true fail safe in place, a user can post to any future date. As a business we need a way to ensure that each user can only post into a specific time frame. If we can close past periods, why not restrict to posting to future periods?
This is already in the system under Administration System Settings, it's a warning about posting an x number of days in the future or in the past. You must have it set to the default 99,999...
A warning should help with this.