Paper timesheets and manual Excel entry carry errors straight into payroll. The Time & Attendance module brings the whole month together in a single flow: QR + GPS geofenced mobile clock-in/out, shift and rotation planning, an automatic anomaly queue, manager-approved manual entries, and overtime requests. When the month closes, the timesheet is locked and exported cleanly to your ERP as a payroll feed, so no one has to key the same data in twice.
Logo, Mikro, SAP, Netsis and Uyumsoft calculate payroll, but they do not natively provide field workers scanning a QR code from their phone, proof that they started work inside a GPS geofence, detection of spoofed locations (mock GPS) and device changes, shift rotation templates, or the manual-entry and overtime approval flows that field staff need. Building this on top of SAP or Logo means an expensive custom project that runs for months, coded shift rule by shift rule and geofence point by geofence point. Time & Attendance ships this layer ready to go; the ERP simply receives the locked, approved timesheet.
The employee scans the on-site QR code from the native mobile app (Sanctum token); the system records the GPS coordinate, the distance to the geofence boundary and the location accuracy. Punches outside the geofence, with low GPS accuracy or from unauthorized locations are flagged automatically. Clock-in via web/kiosk is also supported.
Mock GPS detection, device binding for managing approved or blocked phones, checks for shared devices and clock skew, policy-based mandatory selfies, and offline sync detection. Every suspicious punch is still recorded, but it is flagged and routed to the exception queue.
Shift definitions that distinguish day, night and shifts that cross midnight; multi-day rotation templates (e.g. 2 day - 2 night - 2 off) and the roster generated from them. You plan teams with templates and free yourself from assigning people one by one.
Sixteen exception types are raised automatically, including late arrival, early departure, missing punch, absence, out-of-geofence, mock location, daily/night/annual overtime cap breaches and unapproved overtime; the manager reviews and resolves them from a single queue. Problem days are not overlooked and get cleared before they spill over to month-end.
An employee logs a forgotten punch via a 'missing entry correction' request, and planned overtime via an 'overtime request'. Policy can make overtime pre-approval mandatory; overtime without pre-approval is flagged as an anomaly. Every request is recorded with an audit trail.
The manager approves or rejects their team's manual-punch and overtime requests. HR or an authorized manager can add a punch directly without waiting for a request, void an incorrect punch, or override a day; every intervention is logged.
Rule sets by department or location: overtime and additional-hours multipliers, selfie/QR/device-binding requirements, and permitted clock-in sources. The public, religious and company holiday calendar feeds day-close, leave and holiday premium calculations.
The monthly timesheet is generated automatically from the period's punches; it goes to the manager with day-by-day rows (timesheet entries), is approved and then locked. A locked timesheet cannot be changed; data integrity is guaranteed and the payroll period closes cleanly.
The daily operations dashboard, period summary and department-level overtime reports export to CSV. The locked timesheet is produced as a payroll CSV and transferred to the ERP/payroll system; who worked how much on which day is available in a single click.
The employee scans the on-site QR code from their phone; the system records the GPS position, distance to the geofence, accuracy and the device. Out-of-rule punches are flagged and sent for review, but never lost.
The punch is matched to the employee's shift from their rotation plan and to the department attendance policy; late arrival, early departure and overtime cap conditions are calculated automatically.
The manager clears the anomaly queue and approves the team's missing-punch and overtime requests; HR steps in directly when needed. In-month inconsistencies are closed here.
At period end the timesheet is generated day by day automatically, sent to the manager and approved. Overtime, holiday and absence rows arrive ready to go.
The approved timesheet is locked (no longer editable) and exported to the ERP as a payroll CSV. The same data is never re-keyed by hand; payroll errors are stopped at the source.
Time & Attendance reads employee master data (personnel, department, location) from the ERP and, once its single concrete output - the monthly timesheet - is approved and locked, writes it back to payroll. The ERP remains the single source of truth for payroll and personnel; the portal takes on the attendance-control layer in between.
Employee, department and location data is pulled read-only from the ERP (SAP/Logo/Uyumsoft); Time & Attendance links punches, shifts and timesheets to these people. For companies without an ERP, personnel can be managed via Excel import.
The locked monthly timesheet is produced as a payroll CSV with day-by-day work, overtime and holiday line items and transferred to the ERP/payroll system. Only approved, locked data goes to the ERP; no draft or flagged punch flows through.
The native mobile app for the field uses the /api/pdks/* endpoints with a Sanctum token, and the web (Inertia) routes serve the office/kiosk; both feed the same shift, policy and timesheet core. There is no per-user licence - every field worker can be added.
Tell us your ERP and your process. We’ll show how this module works and scope it into your subscription — no man-day, licence or setup fee.
Book a Demo →