What is statutory compliance in Indian payroll?

Six recur, whatever the specific law. Registration: enrolling the establishment, and sometimes each location, with the relevant authority. Deduction: withholding the right amounts from pay. Remittance: paying those amounts, along with any employer share, to the right authority. Returns: filing the periodic statements that report what was deducted and remitted. Records and displays: maintaining registers and putting up whatever notices are required at the workplace. Inspection: being able to produce all of it when asked. Thinking in categories rather than in the names of individual laws makes the work manageable, because a new obligation almost always slots into one of the six.

Provident fund, administered through the Employees' Provident Fund Organisation. Employees' State Insurance, administered by the Employees' State Insurance Corporation. Professional tax, which is levied by state governments, differs from state to state, and does not exist everywhere. Tax deducted at source on salary, which sits with the income tax department. Gratuity and statutory bonus, which are payments to employees rather than remittances to an authority but still carry conditions and records. Each has its own rates, thresholds, eligibility conditions and deadlines, all of which change, so treat any figure you have inherited as unverified and confirm the current position with a qualified advisor or the relevant authority before configuring your payroll software.

Because most other obligations are meaningless without it, and because registration carries the longest lead time. You cannot remit for an establishment that is not enrolled, and you cannot enrol without accurate details of the entity, the location and often the employees attached to it. That is why a new office, a new entity or a restructuring becomes a compliance project rather than an administrative update. Keep registration details, certificates and credentials somewhere findable and owned, alongside accurate establishment and headcount data in your employee records, since renewals and returns both depend on them being current.

Because several obligations are state subjects. What is due, whether it is due at all, how it is filed and what must be displayed at the workplace can all differ across the states where you employ people, and the differences are not variations on a single template. A single national calendar therefore does not exist; you have a calendar per state, plus the obligations common to all of them. Adding a state is not a configuration change but a set of registrations, a new set of deadlines and a new authority to deal with. This is the main reason payroll grows harder as a company expands, and it is worth planning before the first hire in a new location rather than after.

A list of every obligation with its frequency, its owner, the system or portal it is filed through, the input it depends on, and the evidence you keep afterwards. Build it from your own registrations rather than from a generic template, because a template will include obligations you do not have and omit ones specific to where you operate. Order it by when the work must start rather than when it is due, since a filing that depends on a payroll run cannot begin before that run closes. Keep it alongside your HR and payroll operations rather than in someone's personal spreadsheet, and make sure a second person can run it.

A named individual, not a team and not a role nobody currently holds. The owner is responsible for the item being done, for knowing when it changes, and for saying so when they cannot do it. Ownership can sit with an internal person, with a provider or with an advisor, and splitting it is perfectly reasonable provided the split is written down item by item rather than assumed. The failure pattern is an obligation everybody believes somebody else has. Review ownership when people leave, when you engage or drop a provider, and whenever you enter a new state.

Assume they will, and build the review in rather than waiting to be surprised. Decide who watches for change and what they are watching, whether that is a provider's bulletin, an advisor's update, an authority's own notifications, or some combination. Set a periodic review of the calendar itself, not only of the items on it, so a new obligation gets added rather than discovered during an inspection. Record when each item was last verified and against what, because the useful review question is not whether an item is on the list but when somebody last checked it was still correct. Anything you cannot verify goes to a qualified advisor rather than into the calendar as an assumption.