Connecting biometric devices to payroll: a practical guide

What are the steps to connect biometric devices to payroll?

Before buying any device or system, gather details of the devices you already have: brand and model, whether each one connects over the network or only via USB, where it is installed, and how many employees clock in on it each day. These details shape the import method and integration effort more than anything else.

The most important next step is unifying employee IDs. If an employee is enrolled on the device under one number and in payroll under another, their records will land on the wrong person or be lost entirely. Check both lists line by line before the first pull, and make every new hire start in the system and then get pushed to the device, not the other way round.

• Confirm the device model and network capability
• Match each employee’s ID between device and system
• Define shifts, grace periods and lateness rules
• Schedule automatic pulls (hourly or daily)
• Decide who may edit records, with a reason logged for every edit
• Review the first month in parallel with the old method

Fingerprint, face or mobile check-in: which suits you?

Many companies in Iraq combine methods: a fingerprint or face device at headquarters, and mobile check-in for sales reps and site crews. What matters is that every record flows into one system with the same rules, so no group of employees ends up with a different calculation.

How do you define shifts, grace periods and lateness?

A shift is the yardstick every record is measured against: start and end times, the grace period before lateness counts, the minimum working hours, and the break. An employee on a fixed morning shift differs from a nurse on a rotating rota, or a guard on a night shift that starts in the evening and ends the next morning.

Define each shift type once, link employees or departments to it, and use a weekly rota for departments whose hours change. The system then knows which record belongs to which day, so a night shift doesn’t turn into an absence one day and a double attendance the next.

• Morning, evening, night and rotating shifts
• A grace period before lateness counts
• Minimum hours for a full day and a half day
• Breaks counted as working time or not
• A weekly rota for departments with changing hours

Which cases need written rules?

Write a policy for each case before go-live; the system applies it precisely but doesn’t invent it.

For example: if an employee forgets to clock out, does the day count as a half day, or do they submit a correction request that their line manager approves? The second option is fairer and clearer, because it leaves a written trail for every exception and stops silent edits to records.

For Fridays and public holidays, decide in advance whether work on those days is part of a normal rota or an exception requested by management, and how it is calculated, according to the applicable law and the company’s policy. Ideally a legal specialist or accountant reviews these rules before they are adopted.

• Forgotten check-outs
• Night shifts spanning two days
• Public holidays and leave
• Working on a Friday or a day off
• Leaving early with or without permission
• Field work outside the office
• Multiple devices across branches

How do overtime and deductions flow from the device to payroll?

Once the rules are applied, the system produces a period summary per employee: days present, absences with and without excuse, minutes late, overtime hours and leave taken. That summary is what moves to payroll, not the raw logs that no accountant can realistically review.

How overtime converts to money, and how much is deducted for lateness and absence, is set by the company’s policy according to the applicable law. The system’s job is to apply those rules equally to everyone and pass the result to the HR and payroll system without manual re-entry.

And make overtime require approval: not every stay after hours is overtime. When a manager approves overtime in advance or after the fact, disputes drop and this payroll line stays under control.

• Close the attendance period before preparing payroll
• Review exceptions and correction requests before closing
• Overtime approved by the line manager
• Summary passed to payroll automatically
• A payslip showing the source of every deduction

What happens when the internet drops or there are several branches?

Internet and power cuts are part of daily reality in many Iraqi cities, and the integration has to be designed around that. Many common fingerprint devices keep logs in their internal memory, so if the connection drops employees keep clocking in and the logs are pulled once the network returns, with nothing lost. Confirm this for your device model before relying on it.

In multi-branch companies each device is tagged with its branch and its logs are pulled into one central database, so reports appear consolidated for management or per branch. Watch each device’s clock too: a device running a few minutes slow creates phantom lateness for every employee on it, so it is better to sync the time automatically from the server.

• A UPS for devices at sites with power cuts
• An alert when a device stops syncing for longer than a set time
• Device clocks synced automatically from the server
• Reports per branch and a consolidated one for management

What does an employee see in a self-service app?

When employees see their record as it happens, mistakes get fixed the same day instead of surfacing on the payslip at month end. An employee app or portal takes pressure off HR, because employees answer most everyday questions themselves without visiting the department.

• Day-by-day attendance and lateness
• Submit leave or permission requests and track approval
• Request a correction for a missed punch, with a reason
• Remaining leave balance
• Monthly payslip
• Field check-in within a geofence for staff working off-site

How do you protect biometric data and employee privacy?

Fingerprint and face data is sensitive and must be handled with care: limit who can see it, tell employees why it is collected, and never use it for anything other than attendance. At system level you need role-based permissions, an audit trail for every attendance edit, regular backups, and a protected connection between devices and server where the device supports it.

Government departments usually have extra requirements, such as hosting data on internal servers and tightly defined viewing permissions. See how we handle these requirements on our digital transformation for government page.

• Viewing permissions by job role
• An audit trail for every manual edit
• Data used for attendance only
• Regular backups
• Removing an employee’s data from devices when they leave, per the organisation’s policy

Where should you start?

Start by listing your devices and writing your attendance policy, then run the integration in one branch for a full month in parallel with the old method, and compare results employee by employee before rolling out to other branches.

If you want to see how a biometric time and attendance system brings devices, shifts and field attendance together and feeds the result to payroll, or you want a cost estimate based on your number of devices and branches, check our pricing page or contact us so we can review your current devices before any purchase decision.