This would be extremely useful for payroll to set an effective date for new company wide rate/limit changes and also be able to track rate changes and their effective dates.
Example, annual SUTA rate and limit increases could be added to this database with an effective date (toggle for calendar date or first payroll after) on the date they are received instead of a mass update at YE between last payroll and first payroll. If set up right it might also let past payrolls be reprocessed at actual rates for the period.
HSA/401K negative earnings annual limits could be updated this way also.
Company | Barnard Construction |
Job Title / Role | Payroll Manager |
I need it... | 12 months |
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.
I just submitted duplicate suggestion as VSTA-I-2872. We need this because our 4th QTR reporting in Aatrix is using the wrong rate. It's using the rate we configured for the new year payroll calculations.