HR teams on Dahua devices
Understand a punch-direction refusal and fix it in the export instead of in the data.
Dahua Attendance Excel Export: Headers and Pitfalls
A Dahua SmartPSS-style attendance export is a punch log: one row per event with an ID, a name, a time and a type. The header shape our tests cover is UserID, Name, Time, Type. WatheeqaHR reads UserID as the employee ID, Time as the full date and time of the punch and Type as its direction. A Type value that is not a known in or out code refuses the file instead of being guessed.
Dahua: header shape, what WatheeqaHR reads and pitfalls
The header shape our tests cover
The automated tests resolve this header row: UserID, Name, Time, Type, with UserID as the employee ID. Export the attendance or transaction records from your Dahua software as Excel or CSV and keep the columns as they come.
What WatheeqaHR reads from it
UserID is the employee ID, matched through the looser userid pattern that comes last in the ID list, so a more specific ID column elsewhere in the file would win. Name is the employee name. Time is treated as the combined date and time of the punch, so no separate Date column is needed. Type is the direction.
Pitfall: direction codes
Each distinct Type value is checked against the recognised in and out codes: in, check in, clock in, on duty, c/in, 0 and entry on one side; out, check out, clock out, off duty, c/out, 1 and exit on the other, plus the Arabic words حضور, دخول, انصراف and خروج. One unrecognised value refuses the whole file with 'Unknown punch-direction codes'. Re-export with plain In and Out values.
Pitfall: Type holding a verification method
If every Type value is only a verification method, such as FP, Face, Card or Password, or empty, the column is ignored as a direction. The first punch of each day then counts as check-in and the last as check-out, so a stray extra punch changes the result.
Before you upload
Short labels such as Type are matched only as a whole header, so keep the column named Type rather than a longer phrase. Upload one month at a time, under 5 MB, and check the preview for the employee column.
Features
| Feature | Description |
|---|---|
| UserID | Employee ID, via the looser userid pattern. |
| Name | Employee name. |
| Time | Combined date and time of each punch, so no Date column is needed. |
| Type | Direction. Known in and out codes only; unknown values refuse the file. |
Who uses this
Site administrators
Pick an export where each event row carries an explicit In or Out value.
Frequently asked questions
How do I convert Dahua attendance data to Excel?
Export the attendance records from your Dahua software as Excel or CSV and upload them to the free analyzer to get an Excel report. WatheeqaHR reads the exported file and does not connect to the device.
Does a Dahua export need a separate Date column?
Not for this shape. Time is read as the full date and time of the punch.
Why was my Dahua file refused for unknown direction codes?
The Type column holds a value that is not a recognised in or out code. Re-export with explicit In and Out values rather than internal numbers.
What if Type only lists Face or Password?
Those are verification methods, not directions, so the column is ignored and the first and last punch of the day decide check-in and check-out.
Is this a Dahua compatibility guarantee?
No. This page describes the header shape our tests use. Exports vary by device and software version, so test your own 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