Indiana Unemployment and several other state and federal agencies are now requiring SOC (Standard Occupational Code) to be reported for each employee record when reporting to the agency. https://www.bls.gov/soc/2018/home.htm Viewpoint KB article recommends using the current field labeled Occupational Category for this purpose. However, that field currently controls all EEOC reporting which uses entirely different codes https://eeocguide.com/eeo-form-codes.htm . The same field cannot be used for 2 entirely different and distinct codes. Viewpoint has suggested that field be changed back and forth as needed for reporting to the various reports. That is absurd when you have more than 1,000 employees! Rather 2 distinct fields are REQUIRED:
* EEOC Code (the current the field labeled Occupational Category) - used for all EEOC reporting.
* SOC Code - (new field needed) used for SOC reporting.
Both these fields need to be on PR Forms (Add'l Info), because some PR customers do not have HR module.
Furthermore this new SOC needs to be programmed to integrate with Aatrix interface correctly.
I would classify this as a software defect - NOT a suggestion for enhancement. However, Viewpoint Support suggested that I place it here as a new suggestion. It is now required by many state and federal tax and regulatory agencies. Payroll software not providing this requirement and corresponding correct reporting is a known defect that needs to be corrected.
Guest
| Company | Milestone Contractors & Heritage Group |
| Job Title / Role | Viewpoint Business Analyst |
| 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.
© 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 strongly agree that we need 2 separate fields to enter these codes as they are different. And the SOC code should appear on the PR Unemployment Report. Washington state is now requiring SOC code reporting with the state unemployment report. After spending hours talking with Viewpoint and Aatrix, I will either be forced to pay $9.49 plus $0.49 per employee I'm reporting to file online with Aatrix, or I will have to create a spreadsheet to track this outside of Viewpoint. Washington state has been announcing this for months and still nothing from Viewpoint other than to use the Occupational Categories field and use Aatrix (which means I have to pay Aatrix to do what I used to do for free and was very very easy to report, but now is being turned into a complicated process).