Attendance that checks itself against real shift times
An attendance management system Bangladesh companies can trust needs to do more than log a clock in and a clock out. Every record Utso creates is compared to the shift it actually belongs to, so “late” and “on time” are calculated against reality, not against a single flat cutoff that ignores rotating shifts, split shifts, or branch-specific hours.
Three sources become one record
Most employee attendance software Bangladesh teams have used before locks them into a single data source. Utso merges three:
- ZKTeco biometric devices: fingerprint, face, or card readers, including ones sitting behind an office firewall, connected so entry and exit records come in automatically, on a schedule you set. No manual export, no USB drive carried between the terminal and a laptop.
- A manual online timer: a one-click start/stop timer for employees without a biometric device nearby, correct even when the employee is working across time zones, so it holds up for remote attendance management Bangladesh use cases as well as a fixed office.
- spreadsheet upload: upload your old records in one go, or for a location that has no connected hardware yet.
All three can be active for the same company at the same time, and every punch, whichever source it came from, gets merged into one canonical daily attendance record per employee.
Checked against actual shift times
Late-arrival and early-exit time is calculated against the shift snapshot the employee was actually scheduled for, not a single company-wide clock in time. An employee on a night shift is not marked late by a rule written for the day shift.
Accurate down to the second
Late-arrival and early-exit time is computed down to the second against the shift snapshot, not rounded to the nearest hour. That precision is what keeps small rounding errors from turning into a real discrepancy once a whole team’s attendance is totalled at month end.
Grace period you control
Set how many minutes late still counts as on time, and change it whenever your company policy changes. There is no fixed system default forcing every company into the same tolerance.
Choose your own sources, per company
Biometric, timer, and spreadsheet upload can each be turned on or off independently for your company, so you run only the sources that actually fit your offices, rather than paying for or configuring hardware integrations you will never use.
Manual corrections need a reason
If HR fixes an attendance record by hand, the system asks for a reason before saving the change and keeps a full record of who made it and when.
Built on the same shift engine
Attendance data feeds directly into shift scheduling, so coverage gaps and overtime show up in the same place the schedule was built, instead of a separate report someone has to match up by hand at month end.
Works with what you already have. No need to buy new hardware if you already run ZKTeco biometric devices, including devices sitting behind an office firewall.
Every correction is logged. HR overrides need a reason and are recorded, so nothing changes silently.
Grace period, your rules. Set your own late-arrival window instead of a fixed system default.
Included in the core HRM suite. Attendance is part of the base platform from the Starter tier, not a separate paid add-on.
BDT pricing. No USD conversion friction on your subscription.
Built for how attendance actually happens on the ground
A biometric attendance software Bangladesh deployment rarely looks like a single clean office with one machine at the door. Utso is built around the messier reality.
Multiple branches, one dashboard
Biometric devices at different locations each connect independently through their own secure connection, but every punch still lands in the same unified attendance record set for the company, not a separate system per branch that someone has to match up by hand every month. For a business running several offices or retail locations, that means one place to see who was present, anywhere.
Devices behind an office firewall
Fingerprint and face-recognition terminals are common across Bangladeshi offices and factories, but IT connectivity to them is often inconsistent: a device sitting behind a router with no public IP and no one available to open firewall ports. Utso is built for exactly that situation: once a device is connected, punch logs are pulled on a schedule automatically, with no ongoing IT effort required after initial setup.
Remote and field employees
Not every employee clocks in at a biometric terminal. Field staff, remote employees, and anyone working from a client site can use the manual online timer instead, and their attendance still lands in the same daily record as everyone else’s, calculated against their own shift.
Migrating historical data
Switching from a paper register or another system does not mean losing attendance history. spreadsheet upload brings historical records in bulk, so past attendance data does not just start from zero on the day you switch over.
Mixed sources without double-counting
A company can run biometric devices at its main office, a manual timer for field sales staff, and spreadsheet upload for a newly acquired branch, all at the same time. The system merges all three into one record per employee per day rather than creating duplicate or conflicting entries.
Biometric hardware at industrial scale
For a factory or industrial employer already running ZKTeco fingerprint or face terminals across hundreds or thousands of workers, the existing terminals are usually the starting point, not something to replace. The hardware keeps working exactly as installed, and Utso pulls the punch data automatically on a schedule instead of someone exporting a file from each terminal by hand at the end of every month.
Attendance you can defend, not just record
An attendance tracking system for SME Bangladesh businesses actually rely on has to hold up if it is ever questioned, whether by an employee disputing a late mark or by an auditor reviewing labour law compliance.
Every override is an audit record, not a silent edit
When HR corrects a record by hand (fixing a device misread, backfilling a day the network was down, or adjusting for an approved exception), the system asks for a reason before saving and writes down the old time, the new time, who changed it, and when. Keeping records like this is part of what labour law asks for, not an extra.
Shift-aware, not just clock-aware
Because every check-in and check-out is compared to the actual shift snapshot rather than a single flat rule, disputes over what counted as “late” have an actual record to point to (the scheduled shift, the grace period in effect at the time, and the recorded punch) rather than a manager’s memory of what happened that day.
Start your 2-month free trial and see how attendance tracking fits your team before you pay anything. Attendance is part of the core HRM suite, not a separate paid add-on.
