Pulls data straight from the time clocks on your factory floor and in every branch, processes it against the correct shift — including night shifts, shifts crossing midnight and overtime before or after a shift — then runs your own payroll formulas.
Deploy on your own server (on-premise) or on a VPS. Your payroll data stays where you decide.
Most manufacturers already own time clocks. What is missing is the middle: turning raw punches into a number you can pay against.
Nobody needs all of it. Each group only gets the part that belongs to their job.
Close attendance, run payroll, manage records, contracts, insurance and tax. Full control within their granted scope.
Check hours and payslips on their phone, submit leave, overtime and missing-punch requests.
Approve their team's requests, review the line's attendance, track overtime and absence for the day.
Consolidated figures by company and site, payroll cost, headcount movement, exports to Excel.
Shaped by the real problems of factories and multi-site operations, not by a generic feature list.
Device logs are processed against each person's actual shift, with mid-shift breaks and overtime pairs separated automatically.
Your pay policy becomes a formula set stored in the system, running in sequence with effective dates.
An agent runs inside each site's internal network and only calls outward. Time clocks never face the internet.
Runs in the phone browser with dedicated Android and iOS apps. Switch it on module by module when you are ready.
Counted directly from the source code, not a marketing estimate.
years building management systems that run on real production floors
Engineers from large companies and corporate groups.
We are a group of engineers from large companies and corporate groups, used to systems that run for real on a production floor — where one wrong number does not stop at the screen, it becomes wrong pay for hundreds of people.
The on-site agent pulls logs from each device on a schedule. Raw logs are kept untouched for later reconciliation, while a normalised copy is matched to the right employee by card or device number.
The system picks each person's shift for the day, pairs in and out punches chronologically within the shift window, separates mid-shift breaks and overtime pairs, then computes hours, lateness, early leave, night hours and overtime tiers.
Approved leave and overtime are reconciled into the timesheet. HR reviews the monthly grid, edits individual cells where needed, then locks the period so nothing changes quietly afterwards.
Your formula set runs in sequence against the closed timesheet. The result is a payroll register, an Excel export, one-page A5 PDF payslips, and email delivery with a per-employee send log.
Every module shares one employee directory, one permission model and one multi-level approval mechanism.
Employee profiles, dependants, digital records with attachments, health checks, maternity, rewards, discipline, transfers and leavers.
Contracts, annexes, renewals, print templates per contract type, expiry alerts and electronic contracts with a signing flow.
Daily and monthly timesheets, raw punches, card management, device logs, period locking, anomaly alerts and approval of missing-punch requests.
Shift catalogue, shift assignment, legal shift groups, work calendar and public holidays, attendance symbols.
Leave requests in a matrix view, annual leave balances, overtime requests, overtime caps per normal/rest/holiday day and per month and year.
Base pay, salary scales, allowances, deductions, parameters, formulas, payroll runs, payslips, salary advances, period locking and payment batches.
Annual tax finalisation, progressive brackets, authorisation to finalise, input from external sources, risk analysis, report templates and XML export.
Participation records, contribution levels, increases and decreases, contribution periods, calculation from payroll and reconciliation sheets.
Hiring demand, candidates, pipeline, interview scheduling and scoring, offers with approval, talent pool, employee referrals and analytics.
Plans, courses, classes and attendance, learning paths, self-study content with tests, certificates and compliance tracking.
Review cycles, criteria sets, form templates, scoring scales, monthly reviews, goals and OKRs, 360 reviews, nine-box calibration and competency frameworks.
A dedicated reporting store for HR, attendance and payroll; report designer, data source declaration and Excel export.
Agent management, time clocks, command queue, sync history, error queue, backup and restore of users, fingerprints and faces, agent version control.
Users, roles, companies, approval-level configuration, approval queue, automatic numbering, per-company grid column settings, error log and change log.
Public REST API with API keys and rate limits, signed webhooks, n8n integration, outbound email and push notifications.
Sales orders, purchase orders, products and stock. An extension for smaller businesses that want everything in one system.
No modules in this group.
Rotating shifts, many lines, frequent overtime, hourly workers. This is the problem the product was built around.
Several locations, a few devices each, and a need to know who clocked in where before consolidating one payroll.
Several legal entities sharing an HR team, but needing separated data, separated payroll rules and separated access.
Running HR and payroll as an outsourced service for many clients, most often FDI companies. Each client gets its own data, its own formulas, its own access scope.
Most attendance projects fail because expectations were set wrong at the demo. We do the opposite.
ZKTeco and Ronald Jack are fully supported. Hikvision, Dahua and Suprema currently only get a connection test. That is written on the features page rather than hidden until contract signing.
The demo uses one month of your own punch data and your actual pay policy. You see immediately whether the numbers come out right, instead of watching a sample dataset.
Installed on a server in your company or a VPS you own. You get direct database access, and you can extract everything at any time.
Written from real rollout work, not repackaged brochures.
Four classic failures when a shift ends after midnight, and how to check whether your current system has them.
USB sticks, vendor software, exposing devices to the internet, or an on-site agent — compared honestly.
28 questions to ask a vendor before signing, grouped by the six risks that sink these projects.
Question not here? Send it over — we answer plainly rather than talking around it.
ZKTeco and Ronald Jack devices are fully supported: log download, connection test, device clock read, plus backup and restore of users and biometric templates. For some other brands the system currently only verifies network reachability — log reading needs additional integration. Send us your device model and we will tell you plainly whether it works today or needs work.
Formulas are not hard-coded. They live in the system, per company, each with its own effective date range. Allowances, deductions, insurance and tax are declarable steps that run in sequence, with each step able to read the results of the previous one. During rollout we build your formula set from your actual payroll policy and reconcile it against your previous payroll run.
Yes. Overnight shifts are a standard case, not a manual workaround. Each shift declares start and end time, mid-shift break, overtime thresholds before and after the shift, and the punch-collection window so it never picks up scans belonging to the adjacent shift. See why night shifts get miscalculated.
No. The system runs on a server inside your own company if you prefer. If you choose a VPS, you still own the server and the database. Both SQL Server and PostgreSQL are supported.
Excel import covers most master data and transactional records. Where the data sits in the previous system's database, we read it directly and match on employee code, running in preview mode before anything is written.
It depends on how complex your pay policy is and what state your data is in, so we do not quote a generic number. After a discovery session you get a plan with dates specific to your operation.
Send us one month of punch data and your current pay policy. The demo runs on your real numbers, not a sample dataset.
