to identify the person and interpret the time correctly. Device connectivity, user mapping, and attendance rules work together to make that possible.
Akadvia ERP supports two synchronisation methods that feed device logs into the same attendance processing workflow.
- Agent Mode: Uses a Windows Sync Agent to transfer records from compatible TCP/IP devices.
- Push Mode: Accepts logs through the HTTP API from compatible devices or integrations.
Choose the method supported by your specific device and firmware. Wi-Fi connectivity alone does not confirm compatibility with the Push API.
Register the Device in Your School Panel
Open School Panel → Biometric → Biometric Devices → Add New Device and enter the relevant configuration details.
- Device Name: Use a recognisable label, such as Main Gate Entrance.
- IP Address: Enter the device’s local network address, such as 192.168.1.201.
- Communication Port: Match the port configured on the device.
- Sync Mode: Select Agent or Push according to the integration being used.
- Direction: Choose Auto, In Only, or Out Only to reflect the device’s purpose.
Clear naming and direction settings help administrators distinguish entry devices from exit devices when reviewing records.
Connect the Selected Sync Method
For Agent Mode, use the Windows Sync Agent to communicate with the supported device over the local network. Check that the configured address and port match the device before reviewing transferred logs.
For Push Mode, the integration submits attendance batches to /api/v1/biometric/push-log using a POST request. Authentication uses the device’s API token as a Bearer token, and the request body uses JSON.
Each log includes the biometric user ID and timestamp, with a status value where applicable. Duplicate detection checks the combination of school, device, user ID, and timestamp, allowing identical records to be recognised during retries.
Link Biometric IDs to Students and Staff
Device user numbers must be associated with the correct school profiles before their logs can become attendance records.
- Open the Device Control Panel: Select the relevant device and enter User Mapping.
- Choose a Biometric User: Click the Map option beside the device user.
- Select the School Profile: Find the corresponding student or staff member.
- Review the Association: Confirm that the device ID belongs to the selected person.
Logs for unmapped users remain stored but are skipped during attendance processing. If logs are arriving without attendance updates, check these associations first.
Define How Punch Times Are Interpreted
Open School Settings → Biometric Attendance Settings to configure the rules used for attendance processing.
- With Time Windows: Punches outside both configured entry and exit windows are ignored. The earliest qualifying entry and latest qualifying exit are used.
- Without Time Windows: The fallback uses the first punch as entry and the last punch as exit.
- Late Arrival Rules: School Start Time and the configured Grace Period determine whether a qualifying arrival is marked Present or Late.
Review these settings against the school’s operating schedule before relying on the resulting attendance reports.
Resolve Common Sync Problems
A device can successfully send records while attendance processing still needs attention. Check the relevant stage before changing the entire setup.
- 401 Unauthorized: Verify the Device API Token against the value shown on the Edit Device page.
- 403 Forbidden: Check that the device is Active and configured for Push Mode.
- Logs Received but Attendance Missing: Review biometric user mappings and applicable punch windows.
- Late Arrivals Recorded as Present: Check School Start Time and the Grace Period.
💡 Validate one complete journey first: a device punch, a received log, the correct user mapping, and the expected attendance result.
With Akadvia ERP, schools can connect compatible attendance devices to student and staff records and apply consistent rules to daily entry and exit activity.