RECOMMENDED FIELDS FAQ
This article will provide additional details to commonly asked questions regarding recommended fields.
Recommended Fields - Payroll Input File Only
Where do recommended fields appear in my reports?
Mapped recommended fields appear in the census report for each employee where data is available.
Why are recommended fields that I mapped blank?
If a mapped field is blank, no data was available for that employee in the payroll input file.
Why does an employee have a tickmark “(A)” next to their name in the census?
This indicates that an employee has multiple values for the same mapped recommended field. For example, if an employee has two dates of hire, they will have an “(A)” tickmark in front of their name.
When multiple values appear in the recommend fields, the value associated with the latest record is populated.
- Date fields: The most recent date is used.
- Non-date fields (e.g., employee type): The record is selected based on the most recent data available.
Recommended Fields - Payroll and Demographics Input Files
My demographic file is failing validation. Why is this?
- Ensure there is only one header row.
- See the uploader page for instructions as well as the “Download Instructions” tab for the instructions.
Do payroll and demographics files need the same identifier?
Yes. The same identifier (SSN, Employee ID) must be mapped and be identical between employees for AuditMiner to match the data between the two files.
What if the same recommended field is mapped in both payroll and demographics files?
- AuditMiner prioritizes the data provided by the payroll input file. However, if no data in the payroll input file is available for an employee, the demographics file is used.
- If neither file contains data for the related employee, the field remains blank.