People, attendance and payroll in one record.
Onboarding, attendance, shifts, leave and payroll built on one employee record — with PF, ESI, TDS and professional tax computed from it rather than reconciled against it.
In build — early access through 2026 · PF, ESI, PT and TDS computed in-product · Hosted in Indian data centres · Support in IST
Attendance, leave and payroll cannot disagree if they are the same record.
In most HR stacks they are three systems that meet once a month over a spreadsheet. That hand-off is where the wrong number enters, and it is the reason March gets corrected in May. Comsky HRMS removes the hand-off rather than automating it.
One employee, one record
Personal details, documents, reporting line, location, grade and job history sit in one place. A transfer or a salary revision moves the approval chain, the leave policy and the payroll input together, because they were never separate copies.
Attendance is an input, not a report
The pay run reads the attendance ledger directly. There is no muster roll to export on the 25th, no CSV to email to whoever runs payroll, and therefore no version of the month that only one person has.
Leave balances payroll believes
Accrual, carry-forward, encashment and loss of pay live in the ledger the run consumes. A leave approved on the 28th changes the payslip without anyone being told about it.
Statutory falls out of the record
PF, ESI, professional tax and TDS are computed from wages, posting state and the declaration on file — derived at run time rather than reconciled against a separate compliance sheet at month end.
Maker and checker are different people
Whoever prepares the run cannot approve it. Variance against the previous month is surfaced before approval, so an outlier is caught while it is still cheap to fix.
One audit trail over all of it
Every edit to attendance, leave, a salary structure or a run is stamped with who changed what and when. A closed month stays closed and stays readable.
Comsky HRMS is in build. Nothing on this page is running for customers yet. Tell us your headcount and your current stack and we will tell you honestly which release you fit into.
Four steps, and a correction that does not reopen the month.
The month closes once. Everything after that is an off-cycle run against the same record, which is how a February correction stops being a February argument.
| Step | What happens | On the screen |
|---|---|---|
| STEP 01Close the month | Attendance and leave lock on the cut-off date. Pending regularisation and leave requests are listed as blockers, so the run starts from a ledger nobody is still editing. | Open regularisations shown by manager Unapproved leave flagged before lock Lock date set per pay group |
| STEP 02Compute | Salary structures, loss of pay, arrears, scheduled earnings, statutory bonus and loan recoveries are evaluated in one pass, and the statutory deductions come out of the same evaluation. | Formula-based salary components Arrears with an effect date Loans and advances with a recovery schedule |
| STEP 03Check | The preparer hands the run to an approver who is a different person. Variance against last month, new joiners, exits and zero-pay cases are listed on the approval screen rather than buried in a report. | Maker-checker separation Month-on-month variance per employee Multi-level approval where you need it |
| STEP 04Pay and publish | Bank advice comes out in the format your bank wants, payslips reach employees in the self-service app, and the statutory workings are ready for whoever files them. | Payslips on the phone and by email Bank advice file per pay group Statutory workings exported with the run |
A missed payout, a late incentive or an attendance correction found in April is an off-cycle run for the difference. The March run stays closed, stays approved and stays auditable.
The deductions are computed, not reconciled.
Indian payroll is mostly arithmetic that nobody disputes and edge cases that everybody does — the employee who crosses the ESI threshold in October, the one posted to a different state, the one whose proofs arrived in February. Those live in the engine, not in a consultant’s head.
| Statute | What the engine computes | What comes out |
|---|---|---|
| Provident Fund (EPF) | Employee and employer contribution from basic, against the wage ceiling, with mid-month joiners pro-rated | ECR file, formatted for the EPFO portal |
| ESI | Eligibility at the wage threshold, contribution on gross, and the rule that an employee who crosses mid-period stays in until the contribution period ends | Contribution statement per period |
| Professional tax | The slab of the state the employee is actually posted in, not the state the company is registered in | State-wise PT working |
| Labour Welfare Fund | Employee and employer share on each state’s own deduction cycle | LWF challan working |
| TDS on salary | Annual projection from the salary structure, the employee’s declaration and the proofs actually approved | Quarterly return working and Form 24Q data |
| Form 16 | Part A and Part B assembled from the year’s own payslips and deposits | Issued to the employee at year end |
Declarations and proofs in one workflow
The employee declares at the start of the year and uploads proofs against each head. Approved proofs change the projection immediately, so the February shock is a smaller number by design.
State rules, not one national rule
Professional tax and Labour Welfare Fund follow the state the employee is posted in. A company with people in four states gets four workings, not one average.
Form 16 built from your own payslips
Part A and Part B are assembled from the runs the system itself processed, which is the only version that can agree with the payslips an employee already has.
To be plain about scope: Comsky HRMS computes and prepares. Filing on the EPFO, ESIC, state and income-tax portals stays with your team or your consultant at launch. We are not claiming to file on your behalf.
Everything else, without the paragraphs.
Employee and org
- Employee master with documents and job history
- Departments, locations, grades and cost centres
- Reporting lines and dotted-line managers
- Probation and confirmation tracking
- Role-based access to fields, not just to modules
- Letter templates — offer, salary, experience
- Asset allocation and recovery against the record
Onboarding and exit
- Per-role checklists with owners and sequence
- Document collection before day one
- Provisioning tasks raised automatically
- Exit clearance across every department
- Responsibility handover checklist
- Full and final settlement from the same record
- Access revoked on the last working day
Attendance and shifts
- Biometric and facial-recognition device capture
- Geo-fenced punch from the mobile app
- IP-restricted punch from the browser
- Shift definitions with break and payable-time rules
- Rosters by role and location, with swaps
- Overtime captured against the shift
- Regularisation with an approval chain
Leave
- Leave types scoped by location, grade or department
- Accrual by week, month or year
- Carry-forward, encashment and lapse rules
- Holiday calendars per location
- Single or multi-level approval
- Balance visible to the employee and the manager
- Loss of pay passed straight to the run
Pay
- Salary structures and reusable templates
- Formula-based earnings and deductions
- Scheduled earnings and statutory bonus
- Loans and advances with recovery schedules
- Revisions and arrears with effect dates
- Off-cycle runs for corrections and bonuses
- Payslips, tax worksheets and bank advice
Employee experience
- Self-service apps for iOS and Android
- Expense claims with receipt capture and policy limits
- Travel advances settled against the claim
- KRA and goal setting with review cycles
- HR helpdesk with SLAs and a knowledge base
- Recruitment pipeline with resume parsing
- Offer approval chain and e-signed offer letters
Most people should never open the HR system.
An employee has about a dozen reasons to touch HR in a year. All of them are on the phone, and a manager approves from the same screen instead of from an email thread nobody can find in August.
HRMS is being built on the rest of the suite rather than beside it. It runs on Comsky Cloud, so employee data and payslips stay on machines in Indian data centres. Payroll documents can be pushed into Comsky Backup, where the machine that wrote them has no permission to delete them. When Comsky Chat ships, the HR helpdesk will share that inbox instead of being a second ticketing tool nobody checks.
Against a suite, and against how it is actually done today.
Two honest comparisons. One is the established HR suite you are probably evaluating. The other is attendance in one spreadsheet, salary in another, and a consultant who files the returns — which is what most Indian companies under 300 people are really running.
| An established HR suite | Spreadsheets and a consultant | Comsky HRMS | |
|---|---|---|---|
| Where payroll gets its days | A module in the same suite — if you bought that module | A muster roll emailed around the 25th | The attendance ledger itself. There is no export step, so there is nothing to mismatch. |
| Attendance corrected after the run | Adjusted into the next month, or the run is repeated | Found in April, fixed in May, argued about in June | An off-cycle run for the difference. The closed month stays closed and stays auditable. |
| Statutory deductions | Computed by the payroll module, checked against a compliance report | Computed outside the company, from figures sent by email | Derived from the same record at run time. There is no second sheet to agree with. |
| Attendance and leave in the plan | Often the top tier, sometimes a separate SKU | Two spreadsheets and the person who maintains them | In the product from the first tier. They are the spine, not an upsell. |
| Who can approve their own payroll | Configurable, frequently left open | One person prepares it and one person signs it, and they are often the same person | Nobody. Maker-checker separation is on by default, not a setting you remember to switch on after the audit. |
| Multi-state professional tax | Supported, usually well | A slab table someone maintains by hand | Computed from the posting state on the employee record, per state, every month. |
| Where the data sits | A vendor region you may or may not choose | A finance laptop and a consultant inbox | Indian data centres, on Comsky Cloud. |
| Getting your data out | Export per module, on request | It is already a spreadsheet, which is the one thing this approach gets right | Employee master, attendance, leave ledger and every processed run, exportable in full. You keep the year-to-date you need for Form 16. |
The Comsky column describes what the first release is being built to do, not software you can buy this morning. We would rather you hold us to it than be surprised by it.
Priced per employee, per month, in rupees.
The shape is settled. The numbers are not, and we would rather show you a dash than a figure we have to walk back.
Starter
Teams who need attendance, leave and payslips to finally agree with each other.
- Employee master with documents
- Web and mobile attendance punch
- Leave types with accrual and balances
- Monthly pay run with payslips
- PF, ESI, PT and LWF computation
- Self-service apps for iOS and Android
Standard
The full HR and payroll operation for a company with shifts, states and an auditor.
- Everything in Starter
- Biometric and geo-fenced attendance
- Shifts, rosters, swaps and overtime
- TDS, IT declarations and Form 16
- Onboarding and exit workflows
- Expense claims and travel advances
- Maker-checker and off-cycle runs
Complete
HR teams running hiring, reviews and an internal helpdesk on the same record.
- Everything in Standard
- Performance, KRAs and review cycles
- Recruitment pipeline and offer approvals
- HR helpdesk with SLAs
- Asset register and recovery
- Custom workflows, webhooks and API access
- Priority support in IST
Pricing is being finalised before the first release. When it is published it will be per employee per month, in rupees, with GST shown on the invoice — and attendance and leave will be in the first tier rather than gated to the top one. Send us your headcount and we will quote against it as soon as the numbers are signed off.
What people ask before they let us near payroll.
Can I buy Comsky HRMS today?
No. It is in build and going out to an early-access cohort through 2026. You can put your name down and we will show you the product as it stands rather than a slide deck. If you need payroll running next month, we will say so instead of taking the order.
Why make so much of attendance, leave and payroll being one record?
Because that join is where the money goes wrong. When attendance lives in a device export, leave in a shared sheet and payroll in a third tool, the month has three versions and whoever reconciles them is the single point of failure. Deriving the pay run from one ledger removes the disagreement rather than automating the argument about it.
Will you file our PF, ESI and TDS returns?
No, and be careful with anyone who says they will as a software feature. Comsky HRMS computes the contributions, produces the ECR file for EPFO, the ESI contribution statement, the state-wise professional tax working and the quarterly TDS data, and builds Form 16 from your own processed runs. Submitting on the portals stays with your team or your consultant at launch.
Do you work with the biometric devices we already own?
That is the intent, and it is the integration we are most careful about promising. Tell us the make and model you have installed and we will confirm before you commit, rather than listing a generic device compatibility claim here.
What happens when an attendance error is found after payroll has run?
The closed month stays closed. The correction becomes an off-cycle run for the difference, against the same employee record, with its own approval and its own audit entry. You do not reopen a month that has already been paid and reported.
Can we switch mid-year?
Yes, but it needs the year-to-date. We import the employee master, opening leave balances, salary structures and the year-to-date earnings and deductions already paid, because without those Form 16 cannot be assembled correctly. A switch at the start of a financial year is simpler, and if you can wait for April we will tell you to.
Where will our employee data be stored?
In Indian data centres, on Comsky Cloud. Payroll documents can be written into Comsky Backup, where the machine that produced them has no permission to delete them. Salary and statutory data is some of the most sensitive data a company holds, and it should not be somewhere you have to look up on a map.
Do employees need training?
An employee should need the app for about a dozen things a year: punch, shift, leave, balance, payslip, claim, proof upload and a question to HR. If any of those needs explaining, that is our defect and not their training gap. Managers approve from the same screen.
Start with Comsky HRMS.
Grow into the ecosystem.
One account opens every Comsky product — and one invoice covers them, however many you run.