When creating a new expense item, the system defaults automatically to the current date. Most users will not bother changing the date to the actual date of the transaction. By having a portal setting option enabling us to have Date be blank by default, We can force users to pick a date and hopefully they will select the date of the Transaction as they were trained to do.
having the option to relabel the Date as "Transaction Date" would be beneficial as well
Jason Warmby
| Company | Hathaway Dinwiddie Construction |
| Job Title / Role | Director of IT |
| I need it... | 1 month |
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.
© 2024 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.
As a follow-up it seems our accounting team is manually adjusting this date to be the transaction date for all submitted expenses so that they can better audit against fraud. The combination of expense amount and transaction date are the only way we can truly check for duplicate submissions. Using a autogenerated date is creating more work for our accounting team to correct on every submission. Accountants don't care about the date someone submitted the expense, but they do care about the transaction date matching the receipt, the field should be labeled Transaction Date
The default date, if kept, is also malfunctioning. It defaults to today's date right up until 5:00 PM Pacific time / 8:00 PM EST, and then the date rolls over to the next day. At first I assumed it was on London time, but it's actually 1:00 AM London time. Our users were trained to submit receipts same-day and not worry about changing the date because it would be correct. This doesn't work for dinner receipts I guess. A local timezone portal setting seems to be the answer.
System Level is fine for us, but I can see a lot of value in having this functionality at the Company Level as well.
Company Level
Do you see this being decided at a company level, pr group level, or at a system level?