Integrating OneOfficeERP With Biometric Attendance Devices

The Attendance punch logs from the biometric device are check-in and check-out logs of an employee. OneOfficeERP has a provision to store these logs in a document called Employee Checkin.

Attendance can then be marked based on the Employee Checkin records and the Shift Type of the employee by using Auto Attendance

Integrating your Biometric Device (or any access control system that collects IN/OUT logs), can be done using the following steps

1. Setting up Auto Attendance to mark attendance from the Employee Checkin

Before you import employee's Check-in and Check-out logs into your OneOfficeERP system, you would have to set up the employees and their shifts to be able to generate attendance using the Auto Attendance feature in OneOfficeERP.

Please refer to setting up Auto Attendance

2. Populating the Biometric Punch Logs into OneOfficeERP's Employee Checkin

Depending on your biometric system and its features, there can be a lot of ways you can import the Punch logs into OneOfficeERP:

2.1. Use Data Import Tool

The simplest possible solution (in terms of implementation complexity) would be to generate an Excel/CSV of the Check-in/Check-out and use the built-in data import tool in OneOfficeERP to periodically import to your Employee Checkin Document
Please refer to the Data Import Tool for more on how to do this.

2.2 API Integration

You can automate the process of importing the Biometric Punch Logs by integrating it with the available API in OneOfficeERP.
This method requires our technical team to implement alongside the Biometric system vendor.

2.3. Integrate ZKTeco or similar devices

This method works only for ZKTeco or similar devices that use the ZKProtocol to communicate over TCP/IP.
We would need to customize your ERP install to communicate with the device.
This Script pulls biometric logs from a supported device and uses the API mentioned in the above step to push the data into OneOfficeERP.

2.4 Supported Devices

The following list of devices is known to work with OneOfficeERP. This list is by no means exhaustive, as many others would surely work (maybe a little bit of tweaking).

Firmware Version : Ver 6.21 Nov 19 2008
Platform : ZEM500
DeviceName : U580
Firmware Version : Ver 6.60 Apr 9 2010
Platform : ZEM510_TFT
DeviceName : T4-C
Firmware Version : Ver 6.60 Dec 1 2010
Platform : ZEM510_TFT
DeviceName : T4-C
Firmware Version : Ver 6.60 Mar 18 2011
Platform : ZEM600_TFT
DeviceName : iClock260
Firmware Version : Ver 6.60 Feb 4 2012
Platform : ZEM560_TFT
DeviceName :
Firmware Version : Ver 6.60 Oct 29 2012
Platform : ZEM800_TFT
DeviceName : iFace402/ID
Firmware Version : Ver 6.60 Mar 18 2013
Platform : ZEM560
DeviceName : MA300
Firmware Version : Ver 6.60 Dec 27 2014
Platform : ZEM600_TFT
DeviceName : iFace800/ID
Firmware Version : Ver 6.60 Nov 6 2017
Platform : ZMM220_TFT
DeviceName : (unknown device) (broken info but at least the important data was read)
Firmware Version : Ver 6.60 Jun 9 2017
Platform : JZ4725_TFT
DeviceName : K20
Firmware Version : Ver 6.60 Aug 23 2014
Platform : ZEM600_TFT
DeviceName : VF680 (face device only, but we read the user and attendance list!)
Firmware Version : Ver 6.70 Feb 16 2017
Platform : ZLM30_TFT
DeviceName : RSP10k1
Firmware Version : Ver 6.60 Jun 16 2015
Platform : JZ4725_TFT
DeviceName : K14
Firmware Version : Ver 6.60 Jan 13 2016
Platform : ZMM220_TFT
DeviceName : iFace702 (without voice function, test with encoding='gbk')
Firmware Version : Ver 6.60 Apr 26 2016
Platform : ZMM210_TFT
DeviceName : F18/ID
Firmware Version : Ver 6.60 May 25 2018
Platform : JZ4725_TFT
DeviceName : K40/ID
Firmware Version : Ver 6.60 Jun 16 2015
Platform : JZ4725_TFT
DeviceName : iClock260
Firmware Version : Ver 6.60 Jun 5 2015
Platform : ZMM200_TFT
DeviceName : iClock3000/ID
Firmware Version : Ver 6.70 Jul 12 2013
Platform : ZEM600_TFT
DeviceName : iClock880-H/ID