The back office for facility management.
Contracts, sites, postings, attendance, payroll and statutory filings, in one system built for manpower companies in India. Staff punch in by face at the gate; payroll is ready when the month closes.
Everything between the contract and the payslip.
AdminHub runs the office. NPunch runs the gate. Together they take a site from signed contract to paid staff without a spreadsheet in between.
The back office, in one place.
For the people who run sites, staff and payroll at a facility-management or manpower company.
- Contracts with headcount, rates and GST, approved before anyone is posted
- Employee master, postings and transfers across every site
- Monthly attendance that locks before payroll reads it
- Payroll with PF, ESI, PT and TDS, payslips and bank files
Attendance at the gate, by face.
An Android tablet by the entrance. Staff look, blink, and are punched in, with a spoken confirmation.
- Liveness checks stop photos and screens
- Voice and screen in the site's language
- Punches flow straight into AdminHub attendance

From contract to payslip, in five steps.
Contract
Headcount by role and shift, billing rates and GST. Approved by a second person.
Post staff
People are posted within the contracted headcount; salary comes from the site's rate card.
Attendance
Punches at the NPunch kiosk, or marked by the supervisor. Submitted, approved, locked.
Payroll
Every site imported, computed with statutory deductions, checked and approved.
Pay & file
Payslips for everyone, the bank transfer file, and PF, ESI, PT and TDS returns.
Built around how facility management actually works.
Sites, posts and people on rotation, not a generic HR tool with a site field added on.
Contracts that mean something
Headcount per role and shift decides who can be posted. Revisions add or end posts automatically; GST follows your registered office.
One employee master
Bulk import from Excel, documents, bank and statutory details, postings and transfers across sites, and a full change history.
Attendance that locks
Mark, import or punch. A month is submitted, approved and locked, and payroll only ever reads a locked month.
Payroll with a second pair of eyes
Structures and site rate cards, overtime and arrears. Whoever computes a run cannot also release it, unless that is recorded.
Statutory, done every run
PF, ESI with contribution periods, Professional Tax by state including month overrides, TDS under both regimes, Form T.
Self-service for staff
Every employee gets a login: payslips, their profile, and corrections that HR approves, with an audit trail.
Your data stays yours. Every change is on record.
Salary, bank and identity details are sensitive. AdminHub treats them that way at every layer, not just on the screen.
Isolated at the database
Each organisation's data is separated by the database itself, and a login can be restricted to its own sites the same way.
Roles, not favours
Fine-grained permissions for HR, payroll, operations, site admins and viewers. Nobody can grant a permission they do not hold.
Maker and checker
Contracts, attendance and payroll are approved by someone other than the person who prepared them, or the exception is recorded.
A history of every change
Who changed an employee's bank account, and when, always has an answer. Identifiers in the log are masked.
Close your next month in AdminHub.
We will set up your organisation, load your employee master and walk your team through a month, from attendance to bank file.

