How HRZyra actually works
Seven sequences, each one following a real task from the person who starts it to the thing that comes out the other end. Who does what, and what the product does in between without being asked.
Screenshots are being captured
We would rather show you nothing than show you a mockup. These sequences are accurate now; the screens that illustrate them are being captured from the real product and will appear here. If you want to see it working before then, a demo is the fastest route.
What happens between someone clocking in and the register being right?
A day of attendance, from punch to register
Starts when:An employee starts their shift.
Who does what
Clock in
Employee
Through a biometric device, a geo-fenced punch on their own phone, the web, or a shared kiosk — whichever suits where they work. All four land in the same register.
Miss a punch
Employee
The realistic case. A device is down, someone forgets, a field engineer goes straight to site. The register now has a gap that has to be resolved before payroll.
Raise a regularisation
Employee
Against the specific day, with a reason. It goes to their approval chain rather than into an email to HR.
Approve it
Manager
From the queue or from their phone, with the day and the reason in front of them. The register updates and the change is attributed.
Happens on its own
- Overtime, late-mark and short-hours rules applied as the data arrives, not at month end
- Missing punches and unapproved absences raised as live exceptions on the day they occur
- Multi-site and multi-shift rosters kept in a single view rather than one sheet per location
What changes
Month-end reconciliation stops being a two-day exercise in chasing four sources, because the exceptions were handled on the days they happened.
More on this moduleOr ask us to walk through attendance against your own setup.
Walkthroughs being recorded
Three short screen recordings, each answering something a static page cannot. They are not up yet — this is what they will cover.
about 2 min
A payroll run, start to finish
The clearest single answer to "how much work is a payroll cycle". Watch the inputs arrive from attendance and leave, the statutory computation happen inside the run, and the bank file and Form 24Q come out of the same operation.
about 3 min
From a punch to a payslip
The one thing a screenshot cannot show: that these are not four systems. Follow a single day’s attendance through regularisation, approval, the payroll run and onto the employee’s payslip.
about 2 min
What an employee actually sees
Adoption decides whether any of this works. Ninety seconds of the employee’s own app — payslip, leave balance, applying, declaring investments — is the fastest way to judge whether your workforce will use it.
Ready to fix payroll for good?
See HRZyra run against your own salary structures, attendance rules and statutory obligations.
Free migration · No credit card