Versnq AMS
LiveAttendance, leave and shifts — accounted for to the day
A multi-tenant attendance platform for Indian companies. Your own address, your own rules, your own roster — and a month-end export your existing payroll runs from without being re-typed.
01
LiveAttendance
One button to clock in, and a day that is either accounted for or visibly not.
- Clock in and out with a live session timer
- Office, work-from-home and on-field modes
- Late judged against that employee's own shift and its grace window
- Night shifts that cross midnight land on the right day
- “Not marked” is kept distinct from “absent” — they are different problems
- A daily work note, written by the employee, editable the same day
02
LiveCorrections & audit
Someone forgets to punch every single week. The fix is a request, not an argument.
- Employee raises a regularization; HR approves or refuses with a comment shown back verbatim
- Admin can mark on behalf when biometrics fail — a reason is required, always
- Nobody can mark their own attendance through the on-behalf route
- The server refuses attendance for a day that has not happened yet
- Every change logged: who, what from, what to, why — readable per record
03
LiveAttendance policy
Your rules, enforced by the server rather than by reminders on WhatsApp.
- Detect unmarked attendance after N working days
- Then do nothing, warn the employee and their manager, or block their next clock-in
- Auto-mark absent after N unmarked working days
- Corrections: master switch, monthly cap per employee, how far back, which statuses
- Require a reason; require a document after N days
04
LiveShifts & rosters
Ten people, ten different days off — without inventing ten shifts to say so.
- As many shifts as you actually run: morning, evening, night, general
- Per-shift working days, so a six-day week and a Wednesday-off week coexist
- Per-employee weekly offs
- Overnight shifts understood as crossing midnight, not as an error
- Assignments by date range, with rotation handled and overlaps refused by name
05
LiveLeave
Leave types you define, balances that move exactly once, and working days counted correctly.
- Custom types: days per year, half-day, carry-forward with a cap, negative balance, document required
- Apply, approve, reject, cancel — balance moved on approval, returned on cancellation
- Working days computed from that employee's own shift, minus holidays
- HR can file and approve on behalf, with the employee's balance shown inline
- Balance rows locked on apply and approve, so a double-click cannot double-spend
06
LiveReports & export
The month, as a grid your existing payroll can run from without being re-typed.
- Muster roll: the whole month as a grid, per-employee week-offs shaded correctly
- Monthly summary: present, late, absent, WFH, on field, leave, not marked, hours, overtime
- Attendance rate = days at work ÷ days due at work — a Sunday worked does not cover a Tuesday missed
- Joiners and leavers appear for the part of the month they worked
- Excel export with real dates and times, not strings
07
LivePeople & access
Staff without an email address are first-class here, because on a real shop floor most of them are.
- Sign in by employee ID or email — email is optional
- Auto-numbered employee IDs with your own prefix
- Bulk import by pasted CSV, with a per-row error report
- Soft delete: deactivated, never deleted, reactivation possible
- Three roles and four scopes, re-checked on every endpoint — hiding a button is never the control
Honest roadmap
What is not built yet — and why
Most software companies hide this page. We would rather you find the gap now than three weeks after signing.
Leave accrual, probation & comp-off
Monthly accrual instead of one annual grant, per-employee probation, and compensatory off spent oldest-first — on a ledger you can show someone, line by line.
Supervisor & labour workforce
A supervisor scoped to their own crew, marking twenty people at once for workers who have no device of their own.
Biometric device integration
Punches pushed from the machine straight into attendance. The most-asked-for gap for Indian companies.
Mobile app / PWA
Punch, apply for leave and approve from a phone.
GPS clock-in & geofence
Block or flag a punch made outside the office. The database columns are already in place, so this is a switch-on rather than a build.
Payroll
Deliberately not shipped. Until it can be built to the standard the rest is held to, clients run payroll from the Excel export — which exists for exactly that.
On payroll, specifically
Payroll is the one module where a bug is somebody's salary, found on payday. We are not shipping a version we are not certain of. Until then AMS produces the Excel export your current payroll runs from — which is exactly why that export was built first.
Under it
Built to be someone's system of record
Attendance data decides pay. It has to be correct, attributable and impossible for one company to read out of another.
Tenant isolation
Every request carries its company on the token, and every query is filtered by it server-side. Keys are UUIDs, so your size cannot be read off a URL.
Permissions, re-checked
Ninety-nine endpoints, each gated on an atomic permission code and a scope — own, team, department or company. A hidden button is never the control.
Auditable by design
Manual entries, approvals and automated changes all land in one log: who, what it was, what it became, and why.
One working calendar
Attendance, muster, leave day-counting and the absence counter all read the same source. They cannot drift apart.
Sessions that behave
Short-lived tokens in httpOnly cookies with silent refresh, so nobody is logged out mid-shift and nothing is readable from JavaScript.
Self-hosted in India
Your data sits on infrastructure we run, with nightly backups and per-tenant HTTPS. No third-party data processor in the middle.
Next step
See it on your own roster
A working demo takes about twenty minutes, and we will use your shifts and your week-offs rather than a sample company.