Biometric devices
Register devices per branch, match device users to employees, and send sync-time, reboot and clear-logs commands.
Employee records, attendance, leave, payroll, employee self-service and a manager dashboard, all on one shared record and all running on the configuration you set once.
Each one shares the same employee record and is built around how the work actually happens, not a generic form, and runs on the configuration you set once.
One profile holds everything about a person: personal details, addresses, education, bank and identity documents, and a timestamped history of every change.
New hires fill in their own details from an onboarding link
Probation, confirmation, notice and exit are tracked as real stages
Bulk import brings existing employees in from a spreadsheet
No chasing documents or re-entering data. Once your employee settings are configured, codes, statuses and history update themselves.
Employees
482
31
438
9
Priya Menon
Arjun Rao
Devika Iyer
Karthik N
Asha Rao
Biometric punches land automatically, and each day is processed against the shift and late-login rules that apply to that person.
Late arrivals, missing punches and half days are flagged for you
Employees raise correction requests from their own portal
Lock a month once it is final so payroll uses settled numbers
No need to babysit the data. Devices sync on their own and daily processing follows the policy set for each branch, department or employee.
Daily attendance
451
7
24
18
Priya Menon
Arjun Rao
Devika Iyer
Karthik N
Asha Rao
Set leave types, accrual, carry-forward and encashment once per policy, then apply them to the right teams or branches.
Employees apply and see a live balance, including days on hold
Approvals follow the route each policy sets: manager, HR or both
Approved leave updates the balance and attendance together
No request gets stuck with nowhere to go. If there is no manager to approve, the flow moves to HR exactly as you configured it.
Leave requests
Meera Iyer
Asha Rao
Ravi Kumar
Devika Iyer
Karthik N
Define pay components, salary structures and statutory policies once, then run payroll from the attendance and leave you already trust.
PF, ESI and professional tax applied per branch policy
Late-login deductions and loss of pay come straight from attendance
Payslips are released, then delivered to employees by email
A finalized period stays finalized. Run history locks, so later changes create a new run instead of quietly rewriting the old one.
Pay run · September 2026
₹2.41 Cr
₹38.6 L
₹2.02 Cr
Asha Rao
Arjun Rao
Devika Iyer
Karthik N
Employees sign in to your organization's own account from a phone or a laptop and find what they need without asking HR.
Profile, addresses, documents and a log of when details changed
Daily attendance, monthly timesheet and correction requests
Leave balances with days on hold, plus apply and withdraw
Holiday calendar and upcoming colleague birthdays on the home page
Released payslips with PDF download; PAN, Aadhaar and bank numbers masked
No need to worry about requests getting lost or data going stale. Every flow runs the way you configure it: requests reach the right approver, balances update, and payslips appear on their own. You choose which portal features each organization switches on.
The team is everyone who reports to a manager, directly or through other managers. Switch between direct reports and the whole team, and open any person for detail.
Present, on leave, absent, late and missing-punch counts for today
A 7-day, 30-day or month-to-date attendance trend
Who is on leave now and whose leave starts soon
Birthdays, work anniversaries, new joiners and people on notice
Probation confirmations coming due, including overdue ones
The dashboard builds itself from attendance, leave and the employee record, so managers don't wait on HR for a report and HR doesn't have to prepare one.
My team · 12 people
8
2
1
2
Employees raise requests, the right people decide, and the result lands in the balance and the attendance record together.
Approval route set per policy: manager, HR, manager then HR, or auto-approve
Pending leave is held against the balance, so it can't be double-booked
No one approves their own request; HR can step in on any request
Approved corrections reprocess the day, so payroll sees the right attendance
Locked periods and closed leave cycles block late changes
If an employee has no manager, or the manager is the requester, the request moves to HR on its own. Nobody forwards emails or re-keys a decision, and no request is left without an approver.
Approvals
Step 1
Employee requests
Step 2
Manager decides
Step 3
HR confirms
Step 4
Applied
Meera Iyer
Asha Rao
Ravi Kumar
Pre-boarding, onboarding, probation, confirmation, resignation and exit are real stages in the system, not notes in a sheet. Each stage change updates the employee's status and history on its own, so there is nothing to reconcile later.
HR sends an onboarding link, or bulk-imports employees from a spreadsheet template.
The new hire completes personal, bank, identity, education and family details; HR reviews them.
Probation end dates are tracked and surfaced to managers before they fall due.
Confirm the employee once probation is complete; the change is logged in their history.
Record the resignation and last working day; the employee shows as on notice until exit.
Settle leave balances, finalize the exit, and archive the record with its full history.
Payroll is where small errors get expensive. Each run is calculated from policies you can read, and every employee's figures can be opened and traced.
Pay components, salary structures, pay groups and PF, ESI and professional tax policies.
Paid days, loss of pay and late-login deductions come from the attendance and leave modules.
Calculate every employee in one job, with a job history you can reopen.
Open any employee's breakdown, edit a line or loss-of-pay days, and reprocess one person without redoing the run.
Hold or release pay per employee. Released payslips show in the portal and are delivered to employees by email as PDFs.
You don't need to worry about a figure going missing between modules. Attendance, leave and policies feed each run automatically, and every number can be traced back to where it came from.
Late-login rules can deduct days, a flat amount or a percentage of gross
TDS and one-off payments are entered per employee in the run
Payslip · September 2026
Earnings
Deductions
Net pay
₹49,367
The supporting pieces are built into the same platform, not bolted on as separate tools.
Register devices per branch, match device users to employees, and send sync-time, reboot and clear-logs commands.
Shift, late-arrival and missing-punch policies assigned to the whole company, a location, department, designation or one employee.
Lock a month once attendance is final so later edits can't quietly change what payroll already used.
Monthly, annual or earned accrual, carry-forward and encashment rules, opening balances, and a ledger for every movement.
Separate calendars per location, with optional holidays, assigned to the branches that observe them.
Locations, departments and designations are real records that reporting, assignment and payroll all read from.
Bring existing employees in from a spreadsheet template, with a result report showing what was and wasn't accepted.
Configure how employee codes are generated, so new joiners get consistent IDs without manual numbering.
Payslip PDFs are delivered to employees by email automatically when pay is released.
Grant access by role, down to individual actions. Separate permissions for viewing, editing and running payroll.
A record of sensitive actions, including payslip downloads, so you can answer who did what and when.
Issue revocable keys so other systems can read biometric logs securely, without sharing a user login.
Nothing is one-size-fits-all. Policies are set once and applied consistently, but every policy can differ by branch, pay group, or employee.
Leave types, accrual cycles, and approval routes set per policy, not hardcoded per company
Pay components and salary structures configurable per employee or per pay group
PF, ESI, and professional tax policies applied per branch, not one rule for the whole company
Attendance, shift and late-login rules configurable per location, department, designation or employee
Employee portal features switched on or off per organization, including payslip view and download
Every organization gets its own subdomain, its own logo and brand colors on every screen employees see, and role-based access so people only see what belongs to them.
Access, history, and finalized numbers are treated as things that need to hold up later — not just fields in a form.
Once a pay period is finalized, its numbers are locked — later changes create a new run instead of silently rewriting history.
Every screen and action checks against a defined set of permissions, so a manager and an HR admin see different things by design.
Employee history timelines and an audit log record what changed and when, including payslip downloads. Identity and bank numbers are masked in the employee portal.
Each organization gets its own subdomain and its own data — there's no shared workspace where one tenant's records are visible to another.
We'll walk through employees, attendance, leave and a live payroll run, set up for your branches and policies.