Appearance
What Vetanika is, and who does what
Vetanika runs Indian statutory payroll: it computes salaries from a structure, deducts PF, ESIC, Professional Tax and TDS the way the law says, freezes every month so it can never silently change, and produces the files the portals ask for (PF ECR, ESIC monthly contribution, bank transfer, registers and annual forms).
This manual is written for the person who runs payroll. It assumes no technical knowledge. Every page follows the same shape: who does the task, what to have ready, the steps in order, what happens next, and the other cases you may meet.
Two ways companies use Vetanika
| Self-managed company | Consultancy / provider | |
|---|---|---|
| Who runs payroll | The company's own admin | Your firm, for several client companies |
| Where you work | In your own company | Inside each client, one switch away (Ctrl K) |
| Who pays Vetanika | The company | Your firm, one pooled bill across all clients |
| Registrations (PF, ESIC, PT) | Yours | Each client's own |
If you run payroll for anyone other than yourselves — even one company — register as a consultancy. If you are not sure, register as self-managed; a platform administrator can promote you later without re-registering (see Companies and company type).
Who does what inside a company
Every person who signs in is a member of one or more companies, and what they can do is decided by permissions granted on the Members page. The usual split:
| Role (how companies tend to use it) | Typically holds |
|---|---|
| Owner / administrator | Everything: Configurations, Members, Salary Structures, Payslip Designer, Billing |
| Payroll operator | Employees, Payroll Runs, Attendance Register, compliance downloads |
| HR | Employees, Offers, Import from sheet — no payroll processing |
| Viewer / auditor | View-only on employees and runs, Audit Trail |
| Employee (optional) | Only their own workspace: payslips and salary snapshot |
Permissions are not roles — they are individual switches per service (employee management, attendance & run, compliances, administration), so any mix is possible. See Members & permissions.
The sidebar
The menu on the left is grouped the way the work is grouped. Groups collapse and expand; the group holding the page you are on stays open.
| Group | Pages |
|---|---|
| Dashboard | Headcount, monthly gross, estimated employer cost, the roster, the compliance context for the year |
| Company | Configurations · Members · Salary Structures · Payslip Designer · (consultancies) Client Companies |
| People | Employees · Offers · Import from sheet |
| Payroll | Payroll Runs · Attendance Register · Bonus · Advances & Deductions |
| Reports | Compliance Reports · Registers |
| Help & Support | Rectifications · Audit Trail · Support |
Items you have no permission for are simply not shown — a hidden item is never a bug, it is a missing grant.
Your name at the bottom of the sidebar opens the user menu: Keyboard shortcuts, Theme, Billing & credits, Account & security, Sign out.
What "frozen" means
A payroll month, once processed, is a record: the salary structure version, the statutory rates in force, the attendance you entered and the payslip design are all stored with it. Nothing you change later — a revised salary, a new PF ceiling, a redesigned payslip — reaches back into a processed month by itself. Changes go forward from their effective date; corrections to the past are made deliberately, through a re-run, and every one is written to the Audit Trail with before and after.
This is why Vetanika asks for effective dates, why some screens are read-only after a run, and why the figures on a payslip from last year are still the figures on that payslip today.