Orgnest
HR & payroll · by Oadbox
Your people drive your success
HR, payroll and professional services automation for Indian businesses — from ten people to ten thousand.
At a glance
- PF · ESI · PT · TDS
- Same-day setup
- Multi-state, multi-entity
Built for
HR, finance and operations leaders at businesses from 10 to 10,000+ employees.
Live at
orgnest.coThe problem
Used by the payroll executive, the line supervisor and the finance lead.
Payroll rarely fails at the calculation. It fails because attendance, overtime approvals, joiners, exits and variable pay arrive late, from four different places, and keep changing after the run.
Orgnest puts the employee lifecycle, statutory payroll and project delivery on one platform. Attendance feeds payroll, timesheets feed invoices, and compliance is calculated rather than remembered.
It is built for the reality of Indian businesses: multiple states, multiple entities, and statutory rules that change without asking.
A payroll month on Orgnest
One salary cycle, day by day
Payroll software gets bought in a boardroom, but it is judged at the site gate, the HR desk and the finance cabin on the 28th. This is where Orgnest sits across one ordinary salary cycle.
What we counted first
Orgnest began the way every Oadbox product does — sitting in HR rooms and finance cabins through the last week of the month. Four numbers kept coming back:
5 days
From muster close to payslips
The last week of every month went on reconciling attendance before a single rupee could be released. Nothing else in HR moved during it.
4
Spreadsheets behind one payroll run
An attendance sheet, a salary master, an LOP-and-arrears working and a statutory working — each owned by a different person, each reconciled against the others by hand.
1 in 9
Payslips corrected after release
Usually loss of pay marked against the wrong month, or a leave approved over WhatsApp that never reached the register.
21 days
Billable hour to client invoice
Hours worked early in the month sat in a consultant's own sheet until someone chased for them at month-end, and the invoice followed a week after that.
Counted across our own early site visits — HR desks, finance cabins and one factory gate — before Orgnest existed. Every business differs; your numbers are the first thing we ask about.
- Day 1
The site gate
The first shift files past the biometric reader at the site gate while a technician two districts away punches in from his phone, inside the geo-fence around the client's premises. Both land in the same monthly view, against the same roster. Nobody carries a muster roll back to the HR desk at the end of the week.
- Day 4
The HR desk
A new joiner sits at the HR desk with her file. The documents go onto her profile once — PAN, Aadhaar, bank details, the signed offer — and the reporting line she has just been given shows up on the org chart the same afternoon. Her manager's team count moves without anyone redrawing a slide.
- Day 11
Between site visits
A supervisor approves two days of casual leave from his phone between site visits; the balance was checked against policy before the request ever left the employee's screen. A reimbursement claim behind it needs a second sign-off, so it moves up a level on its own. No slip is printed, signed, or lost in a tray.
- Day 18
The finance cabin
The delivery team's hours for the fortnight are already logged against projects, so the client invoice is assembled from them rather than reconstructed from memory at month-end. GST sits on the document as it is raised. The same hours tell the practice head who is over-committed and who is carrying a light month.
- Day 25
The muster closes
Attendance for the month is settled in one view — biometric punches, mobile punches, approved leave and the night roster, all against the same calendar. Loss of pay falls out of that instead of being argued over at a desk. The HR executive spends the afternoon on the exceptions, not on rebuilding a sheet from four sources.
- Day 28
The payroll run
Payroll runs in a single pass. PF, ESI, PT and TDS are computed rather than copied forward from last month's working, and the payslips and statutory registers come out of the same run. The finance cabin's afternoon goes on checking exceptions, not on the spreadsheet everyone had learnt to open carefully.
- Payday
Payday morning
Salaries go out. The payslips came out of the same run, so nobody queues at the HR desk for a printed copy, and the registers behind them are already split the way each state wants them — PF and ESI everywhere, professional tax where it applies. The filings become a review rather than a rebuild.
What quietly disappears
None of this is dramatic. It is the same salary cycle — minus the artefacts everyone assumed were permanent.
The muster roll kept at the site gate
The leave slip signed and left in a tray
The payroll spreadsheet only one person could open
The envelope of stapled reimbursement bills
The statutory working re-typed for every state
Key workflows
What it actually runs.
One-click payroll runs
PF, ESI, PT and TDS computed automatically, with statutory registers and payslips generated in the same pass.
Attendance that fits the field
Geo-fenced mobile punches, biometric devices and shift rosters, reconciled into a single monthly view.
Employee directory with AI insights
Profiles, documents and history in one place, with surfaced patterns on attrition risk and utilisation.
Timesheet to invoice
Billable hours convert into GST-compliant client invoices without a spreadsheet in the middle.
Living org charts
Reporting lines that update themselves as people join, move and are promoted.
Leave, claims and approvals
Policy-driven leave balances, expense claims and multi-level approvals on web and mobile.
Live in a day
Bulk employee import and guided setup mean a first payroll run on the same day you start.
Enterprise security
AES-256 encryption, SOC-2 aligned controls and granular role-based access.
Why Oadbox
We know the industry
Orgnest was designed inside hr & payroll operations, not adapted from a horizontal tool.
How hr & payroll worksIt runs on our core
Tenancy, permissions, statutory compliance, offline mobile and audit trails are inherited, not rebuilt for each product.
Inside the platformWe still operate it
The team that built Orgnest runs it — monitoring, support, releases and the next version.
How we workMore from Oadbox
11 other products, same foundation.
Want to see Orgnest on your own data? That is the only demo worth having.
Thirty minutes with someone from the product team — how you work today, and an honest answer on whether this fits.