Anviz CrossChex sites
Avoid the No. versus User ID mistake that turns every record into a different employee.
Anviz Attendance Excel Export: Headers and Pitfalls
Anviz CrossChex exports come in at least two shapes in our tests. One is EnNo, Name, DateTime, Mode. The other is No., User ID, Name, Dept, Device No., Record Type, Verify Mode, Time. WatheeqaHR reads EnNo or User ID as the employee ID and DateTime or Time as the punch timestamp. The leading No. column is a record sequence, not a person, and Mode and Record Type are not read as direction.
Anviz: header shape, what WatheeqaHR reads and pitfalls
The two header shapes our tests cover
The automated tests resolve two Anviz shapes. Shape one is EnNo, Name, DateTime, Mode, with EnNo as the employee ID. Shape two is No., User ID, Name, Dept, Device No., Record Type, Verify Mode, Time, with User ID as the employee ID. Use the CrossChex attendance record export as Excel or CSV.
What WatheeqaHR reads from them
EnNo or User ID is the employee ID, Name the employee name, and DateTime or Time the punch timestamp. Dept, Device No., Record Type and Verify Mode are not used by the analyzer. Neither shape has a direction column the analyzer looks for.
Pitfall: No. is not the employee
The leading No. column is a sequence number for the record. In the tests, User ID wins over No. when both exist. No. is a last resort: it is chosen only when no earlier ID pattern has data. If the User ID column is blank on every row, the analyzer can fall back to No., which may make every record look like a different person, so check the preview before relying on counts.
Pitfall: Mode and Record Type do not set direction
Mode in the first shape and Record Type in the second are not among the columns read as direction, so the first punch of each day counts as check-in and the last as check-out. A single punch in a day shows as a missing punch for review, not as a confirmed absence.
Before you upload
Keep the original DateTime or Time column as exported, upload one month at a time under 5 MB, and look at the employee count in the first report. An employee count close to the number of records suggests No. was used as the ID.
Features
| Feature | Description |
|---|---|
| EnNo | Employee ID in the first shape. |
| User ID | Employee ID in the second shape; preferred over No. when populated. |
| No. | Record sequence number. Used as the ID only as a last resort. |
| DateTime / Time | Combined punch timestamp. |
| Mode / Record Type / Verify Mode | Not read as direction. |
| Dept / Device No. | Not used by the analyzer. |
Who uses this
HR and payroll reviewers
Understand why check-in and check-out come from first and last punch for these files.
Frequently asked questions
How do I convert an Anviz CrossChex report to Excel?
Export the attendance records from CrossChex as Excel or CSV and upload them to the free analyzer. WatheeqaHR reads the exported file and does not connect to the device.
Is the No. column the employee ID?
No. It is a record sequence number. WatheeqaHR prefers User ID or EnNo and uses No. only when nothing else has data.
Why does my Anviz report show a different employee for every row?
If User ID is empty on every row, No. can be used as the ID. Re-export with the User ID column populated.
Does the Mode or Record Type column set check-in and check-out?
Not in the analyzer. The first punch of the day is check-in and the last is check-out.
Is this an Anviz compatibility guarantee?
No. This page describes the two shapes our tests use. Test your real file.
Related pages
Start with your real attendance file
Upload an Excel or CSV export and review the result free — no signup required.
Analyze attendance free Create free account