Collaborate with Viewpoint and your peers by providing us with your input
Currently we cannot use symbols in the Vendor Invoice field. In American Contractor, we are not limited that way. This field should allow text, numbers, and symbols. Why not?!
Jim Saad
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.
Just to bring this up again. All other software packages allow ALL symbols to be used on invoice numbers. It really does not make any sense why PC cannot do that as well!!! It boils down to poor programming IMO. PC should be up to the same scale/quality as its competitors. Please reconsider this request!
I am sorry. Currently, PC's AR invoice number field does not allow the % character. It does allow manual entry of alpha numeric characters instead of auto-numbering is we want it that way. I do.
So in my responses, please note that PC does not allow the % sign to be used in AR or AP. I think it should because American Contractor allowed for it and it is a good option to have for those of us that need it.
Thanks.
Here are some examples of why this is an important technical issue to resolve:
1. General Contractors often track their subcontract invoices by % of completion. So, an invoice could be coded like 1501Dr1 60% May 2016. This invoice format shows job number 1501, the sub's draw 1 at 60% complete billed in May 2016.
2. PC does not allow spaces in the format.
American Contractor allowed this format w/o issue.
2. AR invoice numbers allow the % characters now and it works great. Please don't take that away!
3. If the % character is not allowed, we have to use more characters like "perc", "pct", etc., which really mades a mess of the AP invoice number. So based on the example above, in PC it would look like:
1501Dr160pctMay2016 compared to 1501Dr1 60% May 2016. You can see a big difference between the two examples.
4. If you are a subcontractor, you might use a special numbering scheme for invoices progress billings or not. The point is that when a general reviews the Cost & BIlling Detail reports that show the invoice number, there is much to be gained by using invoice numbers that give the entire picture of what/when a sub billed simple by allow the % and space format!!!
Thanks for the clarification Cindy! Using the % is very handy for noting % complete on sub invoices. We can do do in the AR invoice field but not in AP. The % sign can really help. Without it, we have to type "pct", "prc" that kind of thing. I hope you will consider this request and allow us to use the vendor invoice field with all characters like we can the AR invoice field.
Thanks much.
Of the example symbols provided in the request, ProContractor will allow all in the Vendor Invoice number field with the exception of the percent sign (%). The list of symbols not valid in the Vendor Invoice Number field include comma (,), period (.), tilde (~), single quote (‘) and percent sign (%).
This does not already exist as of 3.6!
Please see this screenshot:
http://screencast.com/t/jXOsMVqd8re