This page lists what is actually running in the product. Where something is only at a basic level we say so, so the demo holds no unpleasant surprises.
The heart of the system. Everything downstream stands on the hours closed here.
A detailed grid per employee per day, showing the full basis for every calculated hour.
A period summary in the D01–D31 grid layout HR teams already know.
The source layer you fall back on when a number is disputed.
Closed means closed.
Most attendance software breaks here, on night shifts and shifts crossing midnight. This is the most carefully built part.
Missing punch correction. A worker who forgot to scan can raise a correction request on their phone, approved by their manager on web or mobile. Approval writes a valid punch flagged as manual — the raw device log is never edited.
The engine runs a declared formula set, not hard-coded logic.
Salary masking. A user flagged for salary masking sees zero in every money column and cannot export, print, calculate, approve or send. This is enforced at the server, not merely hidden in the interface.
Runs in the phone browser, with dedicated Android and iOS apps.
Also included: org chart, HR decision templates, labour ledger and statutory report layouts, plus a strategic group covering headcount planning, job descriptions, asset assignment and engagement surveys.
This is what lets the system work in a plant with an isolated internal network.
We state support per brand instead of claiming compatibility with every time clock on the market. If your device falls in the group needing integration, ask before signing so the timeline is explicit.
Tell us the module that matters most and the demo goes straight there instead of touring every screen.
