Monthly payroll processing and statutory compliance for the people already on your rolls, attendance and variable inputs in, salary register, payslips and filings out, on the same dates every month.
Overview
Payroll services means running your monthly salary cycle end to end: collecting attendance and variable inputs, computing gross to net against your salary structure, producing the salary register and payslips, and completing the statutory work that follows, provident fund, ESIC, professional tax and TDS. Use it when the people are already hired and the administration around paying them has outgrown a spreadsheet.
Payroll is not a difficult calculation. It is an unforgiving one. A missed PF challan date, a professional tax slab applied to the wrong state, a TDS projection that ignores a mid-year joiner's previous employer income, or a full and final settlement that drifts for a quarter each cost far more than the processing itself, in interest, in penalty, and in the goodwill of the person who was paid wrong.
So the work is mostly in the calendar and the inputs. We fix the cut-off date, the input format and who signs off, then run the same sequence every month against it. Payroll that varies month to month is not flexibility, it is where errors get in.
Briefing to closure, depending on role, seniority and location.
From first conversation through to the joining date.
For clients in Mumbai, Thane, Navi Mumbai and other Indian cities.
The right fit
When it isn't
If what you actually need is people rather than a pay cycle, this is not the service. Payroll begins after the hire is made; it does nothing to fill an open role, and outsourcing the cycle will not make a short team less short. It is also the wrong first step if your salary structures themselves are undecided, a payroll run can only apply the structure you already have, and rebuilding CTC breakups mid-year creates more corrections than it removes. Get the hiring done first, then hand the cycle over.
Look at Volume Hiring insteadHow it runs
Onboarding
We take your salary structures, statutory registrations, current headcount and existing payroll history, then agree the monthly calendar: the input cut-off date, the processing window, the payout date and the filing dates that follow. This is done once, in writing, and every month afterwards runs against it. You confirm who signs off the register.
Monthly, by cut-off
Attendance, leave, overtime, new joiners, exits, salary revisions, incentives, reimbursements and any recovery come in on one template by the cut-off date. Late inputs are the single largest cause of a wrong payslip, so anything arriving after cut-off is carried to the next cycle rather than squeezed in, unless you ask otherwise in writing.
Earnings, deductions, PF and ESIC contributions, professional tax by state, income tax as per the employee's declared regime and investment proofs, loans and advances are computed, and the salary register goes back to you for approval before any money moves. Nothing is disbursed on our word alone.
Payout date
Once the register is signed off, payslips are issued to employees and the bank transfer file is prepared in your bank's format. Queries from employees on a specific payslip line are answered with the calculation behind it rather than a restatement of the figure.
PF and ESIC contributions, professional tax and TDS are deposited and returned by their own due dates, which do not move with your payout date. Challans and acknowledgements come back to you as the record. Where a return is annual rather than monthly, it is tracked on the same calendar so it does not surface as a surprise in the last week.
On an exit we compute notice pay or recovery, leave encashment, pending reimbursements, gratuity where eligible and the final tax position, and issue the settlement and Form 16 record. This is the stage that most often drags, so it runs on a stated timeline from the last working day rather than whenever the month allows.
What goes wrong
PF, ESIC, professional tax and TDS each have their own due dates, and none of them shift because a sign-off was late or a key person was travelling. Interest and penalty follow automatically. We work back from the statutory dates rather than from the payout date, so a delay in your approval shows up as a flagged risk days before it becomes a liability.
Professional tax rates and slabs, minimum wages, leave rules and shops-and-establishment requirements differ state by state, and an employee working from a different state to the one they were hired in is a common source of wrong deductions. Location is treated as a payroll input in its own right, not as an HR detail.
Income tax is deducted against a projection for the full year, so a mid-year joiner's previous employer income, an undeclared regime choice or investment proofs that arrive in February all land as one painful March deduction. Declarations are collected at joining and reconfirmed mid-year rather than at year end, when nothing can be spread any more.
Unlike most back-office work, a payroll mistake is seen by the person it affects on the day it happens, and it is read as carelessness about them personally. Corrections are therefore handled as a stated correction with the calculation shown and a date for the adjustment, rather than quietly netted off in the following month.
Settlements stall between the manager confirming the last working day, IT and admin confirming clearance, and finance releasing payment. Each waits for the other. We ask for a single clearance owner on your side at onboarding, and report pending settlements every cycle so an ex-employee is not the one reminding you.
Your side
A search stalls on the client side at least as often as on ours. These are the things that keep it moving.
Your salary structures and CTC breakups as they stand, plus the statutory registration numbers, PF, ESIC, professional tax and TAN, for each state you operate in.
A named person who approves the salary register each month, and a named backup for when they are unavailable.
Attendance, leave and variable inputs in one agreed format by the cut-off date. This is the input that decides whether the cycle is clean.
Clearance ownership for exits: who confirms the last working day, who confirms asset and dues clearance, and by when.
Timely employee declarations, tax regime, investment proofs, previous employer income for mid-year joiners. Payroll can only compute against what has actually been declared.
By sector
The method is the same; what changes is who you are hiring and where they drop out. Each sector page covers the roles, the qualification floors and the locations that matter for it.
Other services
The monthly cycle end to end: collecting attendance and variable inputs, computing gross to net against your salary structures, returning the salary register for your approval, issuing payslips and the bank file, and completing the statutory work that follows, PF, ESIC, professional tax and TDS, along with exits and full and final settlements.
The employer of record remains legally responsible for its own statutory obligations. What outsourcing changes is who does the work and who watches the calendar: computation, deposit, return filing and the challan record are handled on the agreed dates, and any risk of a missed date is flagged to you before it becomes interest or penalty rather than after.
Location is treated as a payroll input, not an HR note. Professional tax slabs, minimum wages and leave rules are applied by the state the employee actually works in rather than the state they were hired in, which is the most common source of wrong deductions in a multi-location payroll.
They are carried to the next cycle rather than squeezed into the current one, unless you ask otherwise in writing. Late inputs are the single largest cause of wrong payslips, and a wrong payslip costs more in trust and correction effort than a one-month deferral of a variable component.
It runs on a stated timeline from the last working day, not from whenever the month allows. The delay is usually clearance rather than computation, the last working day, asset and dues clearance and payment release sit with three different people. We ask for a single clearance owner at onboarding and report pending settlements every cycle.
Yes. A mid-year transition needs the year-to-date earnings, deductions and TDS already recorded for each employee, plus the investment declarations on file. Those are reconciled before the first cycle is run, because an incorrect opening position surfaces as a large and unwelcome correction in March rather than in the month it was created.
Yes. We run payroll for staff anywhere in India, since the cycle is document- and calendar-driven rather than location-driven. What changes by location is the statutory position, professional tax, minimum wages and shops-and-establishment rules, which is applied per state.
Get started
Tell us the role, the numbers and the deadline. We'll come back within one business day with questions and an honest view of what it will take.
Start hiring