Connecting Attendance Data to brioHR: TimeTec, Hybrid, SFTP, and API Options Explained
Easily sync clocking data into brioHR using the method that best matches your operational setup. Explore our four primary integration options below to find the right fit for your organization.
Audience & Scope
Audience: HR Admin
Module: Time Attendance
Country: Global
Pre-requisites: HR Module Permission for Time Attendance Module
Introduction
brioHR offers four primary integration options to sync clock-in and clock-out data into the Time & Attendance module:
1. TimeTec Biometric Device Integration (TC10 Model)
2. Hybrid Attendance Option (Device + App)
3. SFTP Integration (Batch File Import)
4. API Integration (Real-Time Connect)
1. TimeTec Biometric Device Integration (TC10 Model)
Ideal for offices or physical job sites where staff clock in using physical biometric hardware via fingerprint or facial recognition scanning.
- Full Action Log (Default Mode): Employees must explicitly select "Clock In" or "Clock Out" on the device screen before scanning. Every single scan is logged as-is to provide an unedited audit trail, though duplicate scans are treated as valid entries.
- First & Last Log (First_Last Mode): Employees simply scan their fingerprint or face without selecting an action type. The system automatically treats the first scan of the day as "Clock In" and the last scan as "Clock Out," filtering out accidental double-taps. (Note: Break times are not tracked in this mode).
- First & Last Log with Break Tracking: An add-on for shift employees that automatically captures break-out and break-in scans within a configured break window without requiring manual button selections on the device.
- HR Admin Notes:
- Enabling TimeTec device integration automatically turns off mobile facial recognition and geolocation enforcement for that policy.
- Break tracking in First & Last mode requires Hybrid Attendance to be switched OFF for the company.
LEARN MORE:
2. Hybrid Attendance Option
Designed for hybrid organizations where some employees work on-site using physical hardware, while others work remotely or on the field.
- How It Works: Allows HR Admins to enable attendance tracking across multiple channels so employees can clock in via TimeTec hardware devices, the brioHR Mobile App, or a Web Browser based on their working arrangements.
- HR Admin Note: Hybrid Attendance cannot be enabled simultaneously with TimeTec Break Tracking.
LEARN MORE: Enabling Hybrid Attendance as a HR Admin
3. SFTP Integration (Batch File Import)
Best for organizations using legacy on-premises access systems, turnstiles, or third-party hardware that can export clocking logs to a server.
- Full Action Log: Imports every recorded timestamp in the batch file as-is. It handles high data volumes efficiently without requiring device configuration in brioHR.
- First & Last Log: Automatically filters the batch file to capture only the first and last timestamps of the day, ignoring intermediate taps.
- First & Last Log with Break: Not available yet for SFTP integration.
- HR Admin Note: Updates happen in scheduled batch file transfers rather than real-time.
LEARN MORE:
4. API Integration (Real-Time Connect)
Designed for companies with custom software, custom mobile apps, or third-party tools that need to send attendance data directly into brioHR.
- Full Action Log: Pushes or pulls every clocking event into brioHR in near real-time as it occurs.
- First & Last Log: Accepts real-time data but only records the first clock-in and last clock-out event for attendance calculations, discarding extra taps.
- First & Last Log with Break: Not available yet for API integration.
- HR Admin Note: Requires technical setup and maintenance by your internal IT or engineering team.
LEARN MORE:
Comparison Summary for HR Admins
| Integration Method | Calculation Modes | Sync Frequency | Best For | Technical Effort Required |
| TimeTec Device (TC10) | Full Log, First & Last, First & Last + Break | Real-Time | On-site teams using fingerprint or facial recognition scanners | Low (Plug & Play configuration in brioHR) |
| Hybrid Attendance | Flexible across App & Hardware | Real-Time / Sync | Distributed teams (mixing office, field, and remote staff) | Low (Toggle setting in Admin panel) |
| SFTP Integration | Full Log, First & Last | Scheduled Batches | Existing on-premise access control or turnstile systems | Low to Moderate (Requires file transfer configuration) |
| brioHR API | Full Log, First & Last | Near Real-Time | In-house software or third-party application integration | High (Requires IT / Developer engineering effort) |
Common Issues/FAQ
Q1: Which integration option should we choose if we already have an existing access control or turnstile system?
A1: SFTP Integration is usually the best fit. It allows your existing hardware to export clocking logs directly to a server, which brioHR then processes automatically without needing new physical devices.
Q2: Can employees clock in using both biometric physical devices and their mobile app?
A2: Yes, by enabling Hybrid Attendance, your team can use TimeTec hardware on-site and the brioHR mobile app or web browser when working remotely or in the field. (Note: Hybrid Attendance cannot be enabled if you are using TimeTec Break Tracking).
Q3: What is the difference between "Full Action Log" and "First & Last Log"?
- Full Action Log: Records every single clock record made throughout the day as-is, providing a complete audit trail.
- First & Last Log: Only counts the very first clock record of the day as "Clock In" and the last scan as "Clock Out," automatically discarding accidental double-taps or extra scans in between.
Q4: Can we track employee break times using SFTP or API integrations?
A4: Not at this time. Break tracking within "First & Last Log" mode is currently only available for TimeTec Hardware Devices.
Q5: Do we need IT or software developers to set up these integrations?
A5: It depends on the method-
- TimeTec Device & Hybrid Attendance: Require zero coding and can be managed directly by HR Admins in the brioHR dashboard.
- SFTP Integration: Requires minor setup from your IT team to schedule standard file transfers.
- API Integration: Requires engineering effort from your IT or software team to write custom integration code.
Related Articles
Ownership
By: Aqilah