HR & Payroll Compliance Calendar for Indian Employers

Every payroll team in India runs on two clocks. The first is the internal one: attendance cut-off, salary revisions, full-and-final settlements, payslip release. The second is the statutory one, and it does not care how busy your month was. A well-maintained HR and payroll compliance calendar is what keeps those two clocks synchronised, and it is arguably the single highest-leverage document an HR or finance function can own. Without it, compliance becomes a series of last-minute scrambles triggered by a bank reminder, a consultant's WhatsApp message, or worse, a notice.

This guide is a practical, end-to-end walkthrough of how to build and run a statutory compliance calendar India employers can actually use, month after month, across states and entity types. We cover the monthly rhythm (PF, ESI, TDS, professional tax, labour welfare fund), the quarterly rhythm (eTDS returns, certificates, state PT returns), the annual rhythm (Form 16, annual returns, POSH reporting, bonus, gratuity valuation, registration renewals), and the messier reality of multi-state operations where every state adds its own twist.

One important framing note before we start. Due dates, contribution rates, wage ceilings and state-specific slabs change — sometimes with little notice, sometimes retrospectively, and often differently for different states. Everything in this article is written in terms of the typical cadence you should plan around, not as a legal citation. Treat the dates here as planning anchors, and always confirm the current position on the relevant government portal (EPFO, ESIC, the Income Tax e-filing portal, your state's commercial tax or labour department site) or with your compliance consultant before you file or pay. A calendar is a management tool; it is not a substitute for verification.

Why a compliance calendar matters more than most teams assume

Ask ten HR leaders whether they have a compliance calendar and nine will say yes. Ask to see it and you will often get a spreadsheet that was built three years ago by someone who has since left, listing five due dates, none of which have been checked against current rules.

The gap between "we know the dates" and "we have a system" is where problems live. Here is what a real calendar prevents.

It prevents dependency on individuals. In most small and mid-sized companies, statutory knowledge sits in one person's head — usually a payroll executive or an external consultant. When that person is on leave, resigns, or simply forgets, nothing catches the miss. A documented calendar with named owners converts tribal knowledge into an organisational asset.

It prevents cash-flow surprises. PF, ESI, TDS and PT together can be a meaningful percentage of monthly payroll outflow. Teams that do not forecast these as scheduled payments end up funding them reactively, which creates avoidable friction with finance every single month.

It prevents the compounding cost of small misses. This is the part most teams underestimate.

What missing a deadline actually costs

Penalties in Indian statutory compliance are rarely a single flat fine. They tend to stack in layers, and the layers behave differently:

• Interest. Late deposit of statutory dues — PF, ESI, TDS — generally attracts interest for the period of delay. Interest is arithmetic; it accrues whether or not anyone notices, and it does not go away when you eventually pay.
• Damages or penalty levies. Several statutes provide for damages in addition to interest, often scaled by how long the delay ran. Longer delays are treated more harshly than short ones, which is why a two-day miss and a two-month miss are very different animals.
• Disallowance risk. Employee contributions deducted from salary but not deposited within the prescribed timeline can create adverse consequences under income tax law regarding deductibility of that expense. This turns an HR miss into a corporate tax problem, which is how compliance failures escalate from the payroll desk to the audit committee.
• Prosecution exposure. Certain defaults — particularly non-deposit of amounts deducted from employees — carry prosecution risk for the employer and, in some cases, for officers in default. This is rare in practice for genuine short delays but it is the reason your auditors ask about it.
• Certification and due-diligence friction. Many enterprise customers, lenders and investors ask for compliance certificates or evidence of statutory payments. A gap in your filing history is something you will explain repeatedly for years — during due diligence, during vendor empanelment, during tender qualification.
• Employee-level harm. A late PF deposit delays interest credit to employee accounts. A missed Form 16 issuance leaves employees unable to file returns on time. A wrong PT deduction shows up on a payslip and erodes trust. These costs do not appear on any penalty schedule, but they are real.

Rather than quoting specific penalty figures — which change and vary by statute — the useful mental model is this: the cost of a miss is non-linear in the length of the delay. Catching a miss within days is usually a small interest cost. Discovering it a year later during an audit is an expensive, multi-quarter clean-up.

Step one: figure out which laws actually apply to you

The most common mistake in building a compliance calendar is copying someone else's. A 30-person SaaS company in Bengaluru and a 300-person manufacturing unit in Maharashtra with contract labour have almost nothing in common statutorily beyond TDS.

Before you write a single date, map your obligations against these five variables.

1. Entity type and registrations held

Start with what you are legally registered as, and what registrations you already hold:

• Private limited, LLP, partnership, proprietorship, branch office, or a foreign company's Indian entity
• Shops & Establishment registration (state-issued, per premises in most states)
• Factory licence, if you operate a factory as defined under factory legislation
• EPF code, ESI code, professional tax registration (both the employer's own PT and the employer's PT-deduction registration in states that separate these), Labour Welfare Fund registration
• Contract labour licence or registration, if you engage contract workmen above threshold
• TAN for TDS, GSTIN if relevant to reimbursements and vendor payments

Each registration typically implies at least one recurring filing. If you hold a registration you no longer need, you may still owe nil returns — dormant registrations are a surprisingly common source of default.

2. Headcount thresholds

Indian labour law is heavily threshold-driven. The same company can move in and out of scope as it grows. Key thresholds to track (verify current numbers, as these are amended):

• Provident fund applicability typically triggers at a specified employee count, with voluntary coverage possible below it
• ESI applicability triggers at a specified count in implemented areas, with a separate wage ceiling test per employee
• Internal Committee constitution under the POSH law is required once you cross the prescribed employee threshold at a workplace
• Creche, canteen, and welfare officer obligations under state rules and factory legislation kick in at their own thresholds
• Standing orders certification requirements apply to industrial establishments above a prescribed size in many states
• Gratuity applicability generally begins once an establishment crosses its threshold, and importantly, once applicable it usually continues to apply

Build a headcount tracker that flags when you approach a threshold — not when you cross it. Registration takes time.

3. State footprint

This is the single biggest complexity multiplier. Professional tax exists in some states and not others. Labour Welfare Fund exists in some states, with wildly different periodicity — monthly, half-yearly, annual. Shops & Establishment rules differ on working hours, leave entitlement, holiday lists, and registration renewal cycles. Minimum wages are notified separately by every state, usually with periodic dearness allowance revisions.

If you have employees in six states, you effectively run six sub-calendars.

4. Worker categories

Your obligations shift based on who works for you and how:

• Permanent employees on your payroll
• Fixed-term or contractual employees on your payroll
• Contract workmen through a vendor (principal employer obligations apply — you must verify the contractor's own compliance)
• Apprentices under the apprenticeship framework
• Interns and trainees (classification matters, and getting it wrong is a common audit finding)
• Consultants and professionals paid against invoices (different TDS section, no PF/ESI, but misclassification risk if the relationship is effectively employment)
• Remote employees working from a state where you have no establishment — this is an increasingly common grey area worth taking advice on

5. Industry-specific overlays

Some sectors carry additional obligations: factories and hazardous processes, mines, plantations, building and construction workers, motor transport, beedi and cigar workers, inter-state migrant workers, and sector regulators that impose their own HR-adjacent reporting.

Once you have completed this mapping, you will have a list of perhaps 15 to 40 recurring obligations. That list — not a generic template — becomes your calendar.

The monthly rhythm

Most of your compliance workload is monthly, and most of it clusters in the first fortnight after payroll closes. Understanding the sequencing matters as much as knowing the dates, because several items are dependent on each other.

The natural order is: finalise payroll → compute deductions → generate statutory files → make payments → file returns → archive challans.

Provident Fund: ECR filing and contribution payment

The Electronic Challan-cum-Return (ECR) is the workhorse of monthly PF compliance. You upload a file containing member-wise wages and contributions, the portal generates a challan, and you pay through the linked banking channel.

Practical points teams get wrong:

• The ECR must match your payroll register exactly. Mid-month joiners, leavers, LOP days and arrears all need to flow through correctly. A mismatch surfaces later as a member grievance or a reconciliation problem during transfer/withdrawal.
• UAN linkage and KYC. New joiners need a UAN, and their Aadhaar/PAN/bank KYC needs to be approved. An unseeded UAN can block the ECR or cause downstream issues for the employee.
• Exit dates matter. Marking the date of exit for leavers in the portal is a step teams routinely skip. Employees then cannot withdraw or transfer, and you get support tickets months later.
• Wage definition. Which components attract PF is a genuinely contested area. Get a written position from your consultant, apply it consistently, and document the rationale. Inconsistency across months is what draws attention.
• Timing. PF ECR filing and contribution payment is usually due around the 15th of the following month — confirm the current due date on the EPFO portal, since dates and grace practices have changed over time.

ESI contribution

If your establishment is covered and you have employees within the wage ceiling, ESI contributions are computed and deposited monthly.

• Employees crossing the wage ceiling mid-contribution-period generally continue to be covered until the end of that period — this is a rule teams frequently get wrong when giving mid-year increments.
• Contribution periods and benefit periods are fixed six-month blocks; understanding them helps you explain benefit eligibility to employees.
• ESI is applicable only in implemented areas, which means a company with offices in multiple districts may have ESI liability for one location and not another.
• Timing. ESI contribution payment is usually due around the 15th of the following month — verify on the ESIC portal.

TDS on salary deposit

Tax deducted at source from salaries must be deposited into the government account monthly.

• Deposit is via challan referencing your TAN; assessment year and section codes must be correct, because corrections are painful.
• The amount deposited must reconcile to the TDS actually deducted in that month's payroll — including on perquisites, bonus, and any one-off payments.
• Timing. TDS deposit is usually due around the 7th of the following month, with the March deduction typically having a later date (commonly end of April) — confirm on the Income Tax portal.
• Remember that TDS on non-salary payments (contractors, professionals, rent) sits under different sections with different rates and thresholds. If HR processes consultant payments, coordinate with finance so nothing falls between the two teams.

Professional tax

Professional tax is a state levy. It exists in states such as Maharashtra, Karnataka, West Bengal, Tamil Nadu, Telangana, Andhra Pradesh, Gujarat, Madhya Pradesh, Kerala, Assam, Odisha and others; it does not exist in several states including, for example, Delhi and Uttar Pradesh. Rates, slabs, periodicity and portals all differ.

Two distinct obligations often get conflated:

1. PT on employees (PTRC-type registration) — you deduct from salary and remit, usually monthly, sometimes annually for small deductors.
2. PT on the entity/directors (PTEC-type registration) — an annual levy on the establishment itself in some states.

• Timing. Monthly PT is commonly due somewhere between the 10th and the last day of the following month depending on the state — check your state's portal for each state you operate in. Some states move filers to annual periodicity below a threshold.

Labour Welfare Fund

LWF applies only in certain states and union territories, and the periodicity is the most inconsistent thing in Indian payroll compliance: some states collect monthly, some half-yearly (commonly around June and December cycles), some annually. Contribution amounts are typically small fixed sums per employee, split between employee and employer, sometimes with a state share.

Because the amounts are small, LWF is the most-missed item on any calendar. The fix is simple: put it on the calendar with an explicit "not applicable" marker for states where it does not apply, so a future colleague does not have to re-derive that conclusion.

Shops & Establishment and other monthly hygiene

Shops & Establishment legislation is state-specific and mostly imposes standing obligations rather than monthly filings — but they still deserve a monthly checkpoint:

• Registers: attendance, wages, leave, overtime, fines and deductions. Many states now permit electronic registers; some require specified formats.
• Display requirements: abstracts of applicable Acts, minimum wage notifications, holiday list, working hours, weekly off, name of the inspector, POSH policy and IC details.
• Notices of holidays and the annual list of festival/national holidays, which many states require to be filed or displayed early in the calendar year.
• Overtime records and payment at the prescribed rate where applicable.

Master monthly calendar

Every date above is a planning anchor. Confirm current due dates on the relevant government portal before acting.

The quarterly rhythm

Quarterly obligations are mostly tax-driven, plus a handful of state PT and labour returns.

Form 24Q — quarterly eTDS return for salaries

Form 24Q is the return through which you report salary TDS to the tax department. Two things make it consequential:

1. It drives employee Form 26AS / AIS. If your 24Q has wrong PANs, wrong amounts, or unmatched challans, employees see incorrect tax credits and cannot file returns cleanly. This generates a volume of employee queries entirely out of proportion to the effort of getting it right the first time.
2. The Q4 return carries the annexure with full-year salary details, which is what generates Part B of Form 16. Q4 is therefore materially heavier than Q1–Q3 and needs proper planning.

Practical guidance:

• Validate PANs before the quarter closes, not while filing. An invalid or inoperative PAN can trigger higher deduction requirements.
• Reconcile challans to the return before submission; unmatched challans are the leading cause of default notices.
• Watch for short-deduction defaults arising from investment declarations that employees never substantiated with proof.
• Timing. Quarterly eTDS returns are usually due around the end of the month following each quarter, with the Q4 return commonly having a later date (frequently end of May) — confirm the current schedule on the Income Tax / TRACES portal.

TDS certificates

Form 16 Part A (and Part B) for salaried employees is generated from TRACES after Q4 processing, and Form 16A for non-salary deductions is issued quarterly.

• Timing. Form 16A is typically due within about a fortnight after the eTDS return due date each quarter; Form 16 for salary is typically due by around mid-June following the financial year — verify current dates.
• Do not hand-build Form 16 Part A. It must come from TRACES; a manually prepared Part A is not valid.

State-level quarterly items

Some states require quarterly professional tax returns; some require half-yearly or annual instead. Certain state labour departments also require periodic returns under Shops & Establishment or contract labour rules — increasingly consolidated into a single combined annual return in states that have simplified filings, but not everywhere.

Master quarterly calendar

Confirm all dates against current notifications before filing.

The annual rhythm

Annual items are the ones most likely to be forgotten, precisely because they only come around once. They also tend to be the ones auditors and due-diligence teams ask about first.

Form 16 issuance

Once Q4 24Q is processed, download Part A from TRACES, generate Part B, merge, digitally sign and distribute. Build in a buffer: TRACES processing is not instantaneous, and a defective Q4 return will delay Part A availability.

Give employees a channel to raise Form 16 discrepancies, and expect a wave of queries about mismatches between Form 16, Form 26AS and AIS. Most are explainable; a few will reveal genuine errors worth correcting through a revised return.

Annual returns under labour laws

Depending on state and establishment type, you may owe:

• A combined annual return under state Shops & Establishment or labour rules
• Annual returns under factory legislation, where applicable
• Annual return under bonus-related rules, where applicable
• Returns relating to contract labour, maternity benefit, and equal remuneration-type obligations in some states
• Half-yearly or annual returns under the ESI framework in some periods — verify current requirements, as some filings have been discontinued or merged

Several states have moved to unified or self-certification-based annual returns. Check whether yours has, because filing the old form when a new consolidated one exists — or vice versa — creates avoidable back-and-forth.

POSH annual report

Every workplace with an Internal Committee must submit an annual report to the district officer, summarising complaints received, disposed of, and pending beyond the prescribed period. The company's board report also needs a POSH-related statement where applicable.

Related annual items:

• Refresh IC composition (external member tenure, resignations, member training)
• Conduct awareness programmes and maintain attendance records as evidence
• Review and re-publish the POSH policy and display IC contact details

Bonus

Statutory bonus applies to eligible employees in covered establishments, subject to wage eligibility limits and a calculation ceiling — both of which have changed historically, so confirm the current figures. Bonus is typically payable within a prescribed window after the close of the accounting year, commonly understood as within eight months, and many employers align disbursement to the festive season.

Practical steps: compute allocable surplus or set-on/set-off if you pay above the minimum; maintain the prescribed bonus registers; and document your eligibility logic for employees who joined or left mid-year.

Gratuity provisioning and actuarial valuation

Gratuity is a defined benefit obligation. Two distinct annual tasks:

1. Actuarial valuation for financial reporting, typically obtained from an actuary at year-end for the accounting standard disclosure.
2. Funding decision — whether to maintain an approved gratuity trust or an insurer-managed fund, and whether contributions are current.

Some states mandate compulsory insurance of gratuity liability; verify whether your state has notified those rules. Also ensure Form F nominations are collected from employees and stored, because that is a routine audit finding.

Registration renewals and licence cycles

Anything with an expiry date belongs on the annual calendar with a reminder at least 60 days before:

• Shops & Establishment registration renewal (some states are perpetual, others renew annually or on multi-year cycles)
• Factory licence renewal
• Contract labour licences (which are often headcount-specific and need amendment when numbers change)
• Trade licence, fire NOC, lift/pressure-vessel certifications where applicable
• Digital signature certificates used for filings — an expired DSC on the day of a filing deadline is a self-inflicted crisis

Minimum wage revision cycles

State governments typically revise variable dearness allowance components on a periodic cycle (often twice a year in many states, commonly aligned to April and October, though this varies). Central sphere establishments follow the central notification cycle.

You need a process to:

1. Track notifications for every state and every scheduled employment you fall under
2. Compare notified minimum wages to actual wages paid for each category
3. Adjust wages prospectively where a shortfall exists
4. Update your offer letter templates and salary structures so new hires are compliant from day one

This is one of the highest-risk items for companies with blue-collar, security, housekeeping or field staff — including staff supplied by contractors, where you carry principal-employer exposure.

Leave year close and carry-forward

Not a filing, but a hard-deadline HR obligation that interacts with statute:

• Determine your leave year (calendar or financial) and apply it consistently
• Apply the state's rules on earned leave accrual and the minimum carry-forward that must be permitted
• Process encashment where policy or statute requires it, and remember encashment is taxable in the year of receipt for serving employees
• Publish the next year's holiday list within the timeline your state prescribes, including the required number of national and festival holidays

Master annual calendar

All timings above require confirmation against current rules for your state and establishment type.

State-variable items and running multi-state operations

If you operate in more than two states, this section is where your calendar earns its keep.

The core problem

There is no single national payroll compliance schedule. Professional tax exists in roughly half the states, with different slabs, different portals, different periodicity and different return formats. Labour Welfare Fund exists in a different (overlapping but not identical) subset of states with its own periodicity. Shops & Establishment rules differ on working hours, leave, and renewals. Minimum wages differ by state, by scheduled employment, and by skill category.

The result: an employee in Bengaluru and an employee in Noida on identical CTC can have different net pay, and the employer has different filings for each.

How to structure a multi-state calendar

Build a state applicability matrix first. One row per state where you have employees or an establishment; one column per obligation. Fill each cell with Applicable / Not applicable / Threshold-dependent, and cite where you verified it and when.

Then create per-state sub-calendars that roll up into a master view. Each state row should carry: registration number, portal URL, login owner, due date, payment mode, and the person accountable.

Decide your operating model. Three common patterns:

1. Central team + single national consultant. Simplest to govern; risk is that the consultant's local coverage is thin in some states.
2. Central team + local consultants per state. Better local knowledge; more coordination overhead and more inconsistency in evidence quality.
3. In-house across the board. Best control; needs real depth and is only realistic at scale.

Whatever you choose, the calendar stays with you. Outsourcing execution does not outsource accountability — the employer remains liable.

State-variable comparison

Practical tips for multi-state teams

• Keep one credential register for every portal login, with owner and reset process. Access lost at deadline time is a recurring failure mode.
• Map every employee to a work state in your HRMS, not just a location label. PT, LWF and minimum wages all key off this.
• For remote employees, agree a documented position on which state's rules apply, and revisit it if you open an establishment there.
• When you open a new location, run a new-state checklist: registrations needed, timelines, who owns it, and when the first filing falls due. Registration lead times routinely exceed the first payroll cycle.

The payroll month-end close checklist, mapped to the calendar

A compliance calendar tells you what is due and when. A close checklist tells you how the month actually runs. The two need to be joined, because almost every statutory filing depends on payroll being final.

Here is a working sequence you can adapt. Day numbers are relative to your payroll cut-off, not calendar dates.

Phase 1 — Inputs freeze (cut-off day, T)

1. Freeze attendance and leave data; lock the LOP calculation.
2. Close the joiner and leaver list; confirm exit dates and last working days.
3. Capture all salary revisions, promotions and arrears with effective dates.
4. Collect variable pay inputs: incentives, overtime, shift allowance, sales commissions.
5. Collect reimbursement claims approved within the cycle.
6. Confirm one-off items: bonus, retention payouts, notice pay recovery, advances and loan EMIs.
7. Confirm perquisite inputs — company car, accommodation, ESOP exercises, interest-free loans.

Phase 2 — Processing and validation (T+1 to T+2)

1. Run payroll; generate the register.
2. Run a variance report against the previous month, employee by employee. Investigate anything above your threshold. This single control catches the majority of payroll errors.
3. Validate statutory computations: PF wage base, ESI eligibility and ceiling checks, PT slab by work state, LWF applicability, TDS per employee's projected annual income.
4. Reconcile headcount: opening + joiners − leavers = closing. Tie this to the PF and ESI member counts.
5. Check new joiners: UAN generated, ESI IP number generated, PAN captured and valid, bank details verified.
6. Check leavers: full-and-final computed, gratuity eligibility assessed, leave encashment taxed correctly, PF exit date to be marked.

Phase 3 — Approval and disbursement (T+3 to T+4)

1. Route the payroll summary for approval with a documented approval trail.
2. Fund the payroll account; release salary payments.
3. Publish payslips; make tax computation sheets available to employees.
4. Post the payroll journal to the general ledger, with statutory liabilities in their own accounts.

Phase 4 — Statutory execution (following month, days 1–15)

1. Deposit TDS — target well before the usual 7th-of-following-month anchor.
2. Prepare and upload the PF ECR; generate and pay the challan — target ahead of the usual 15th anchor.
3. Compute and pay ESI contributions — same window.
4. Pay professional tax per state, per that state's own due date.
5. Pay LWF where the cycle falls due this month.
6. Download and archive every challan and acknowledgement into the evidence folder for the month.

Phase 5 — Reconciliation and close (following month, days 15–20)

1. Reconcile statutory liability GL balances to challans paid. The closing balance should be explainable line by line.
2. Reconcile PF/ESI member counts to the payroll headcount, with reasons for any difference.
3. Update the compliance tracker: mark each item done, with date, reference number and who did it.
4. Log any exception — a delay, an error, a correction — in an exception register with root cause and preventive action.
5. Roll forward any open item into next month's checklist so nothing quietly disappears.

Close checklist mapped to statutory triggers

Ownership, RACI and escalation

A calendar with no names on it is a wish list. The most common structural failure in compliance is diffuse ownership: everyone assumes the consultant is handling it, and the consultant assumes they were sent the data.

Assign four roles per obligation

• Responsible — the person who actually prepares and files. Often a payroll executive or the consultant.
• Accountable — the single person answerable if it is missed. This must be an employee of your company, never the vendor.
• Consulted — subject matter input, usually legal or the external advisor.
• Informed — typically the CFO or CHRO, via a monthly dashboard.

Sample RACI

Build an escalation ladder with time triggers

Do not wait for a due date to escalate. Use lead-time triggers:

• T-7 days: owner confirms readiness. Any blocker is flagged to the manager.
• T-3 days: if not ready, escalate to the functional head. Funds availability confirmed with finance.
• T-1 day: if still open, escalate to CFO/CHRO with a written plan.
• T+1 day (missed): log it as an incident, compute the exposure, decide on voluntary payment of interest, and document the root cause.

The point of the ladder is to make a miss visible before it happens, which is the only time it is cheap to fix.

Manage vendor risk deliberately

If a consultant or payroll provider files on your behalf:

• Get filing acknowledgements directly, not just a confirmation email. Insist on the portal-generated document.
• Retain portal access yourself; do not let the only credentials sit with a vendor.
• Include compliance SLAs and indemnity language in the contract, and review performance quarterly.
• For contract labour, obtain monthly evidence of the contractor's own PF/ESI compliance for the workers deployed to you. Principal employer liability is real, and "our vendor said it was done" is not a defence.

Documentation and audit-readiness

Compliance you cannot evidence is compliance you did not do — at least as far as an auditor, an inspector, or an acquirer's diligence team is concerned.

Structure your evidence repository

Use a consistent folder structure so any team member can find any document in under a minute:

`` /Compliance /FY2026-27 /Apr-2026 /PF (ECR file, challan, payment confirmation) /ESI (contribution statement, challan) /TDS (challan, computation) /PT (state-wise challans) /LWF /Payroll (register, variance report, approval mail) /May-2026 ... /Quarterly (24Q returns, acknowledgements, Form 16A) /Annual (Form 16, annual returns, POSH report, actuarial report) /Registrations (certificates, renewals, DSC records) /Policies (versioned, with approval dates) ``

Retain the right documents

At minimum, keep for each period:

• Payroll register and payslips
• Statutory computation sheets
• Challans and payment confirmations for every levy
• Filed returns and portal acknowledgements
• Registers required by state rules (wages, attendance, leave, overtime, fines, advances)
• Employee records: appointment letters, KYC, nominations (PF Form 2, gratuity Form F), declarations
• Contractor compliance evidence
• Committee records: IC minutes, safety committee, canteen committee where applicable

Retention periods vary by statute; many labour records are expected to be retained for several years. Set your default retention long and document the policy rather than deleting on instinct.

Run an internal compliance audit twice a year

A light half-yearly self-audit catches problems while they are still small:

1. Pick three months at random and verify every statutory payment against the payroll register.
2. Check that every filing has a retrievable acknowledgement.
3. Verify current registration validity for every location.
4. Test five employee files for completeness.
5. Confirm registers are current and displays are up to date at each site.
6. Review the exception register — are the same root causes recurring?

Write up findings, assign owners, and track closure. That written trail is itself valuable evidence of a functioning compliance system.

When the rules change: staying current, including the labour-code transition

The hardest part of compliance is not executing a known calendar. It is noticing that the calendar itself has become wrong.

Sources to monitor

• Official portals: EPFO, ESIC, Income Tax e-filing and TRACES, state labour and commercial tax departments
• Gazette notifications, central and state
• Your consultant's or auditor's update circulars
• Industry bodies and payroll software release notes

Assign one person to review updates monthly and record the outcome — even if the outcome is "no change this month". A dated log of "we checked" is far more useful during an audit than a vague claim of vigilance.

The labour-code transition

India consolidated a large number of central labour statutes into four codes covering wages, industrial relations, social security, and occupational safety and health. The codes have been enacted, and implementation has been staged, with states framing their own rules on their own timelines. The practical position has been in flux for an extended period.

Two structural changes matter most for payroll planning:

1. A broader statutory definition of "wages." The codes move towards a definition under which excluded allowances are capped as a proportion of total remuneration. Where an employer has structured salaries with a small basic and large allowances, this can increase the base on which PF, gratuity and other benefits are computed.
2. Consolidated registrations, returns and registers. The intent is fewer filings and unified formats, which should simplify calendars over time — but during transition you may be maintaining both old and new formats.

What to do now, without over-committing:

• Model the impact. Run a scenario showing PF, gratuity and bonus costs under a broader wage definition. Know the number before you need it.
• Review salary structures. Compensation designs built purely around minimising the wage base carry the most transition risk.
• Track your states, not just the centre. Applicability depends on state rules being notified.
• Keep the current calendar running. Until a provision is actually notified and effective for your state, existing obligations continue. Do not stop filing something because a code "will" replace it.
• Verify before acting. Because the position keeps evolving, confirm the current status with your consultant or the official notification rather than relying on any article, including this one.

A change-management protocol

When a change is identified, run it through five steps: assess applicability, quantify impact, update the calendar and system configuration, communicate to employees if pay or deductions change, and document the decision with the source notification attached. That last step is what saves you when someone asks two years later why a rate changed in a particular month.

How an HRMS turns the calendar into a system

A calendar in a spreadsheet still depends on someone opening the spreadsheet. Software closes that gap by making the calendar operational rather than informational.

Statutory computation at source. PF, ESI, PT and TDS are computed within payroll using each employee's work state, wage components and eligibility, so the numbers are right before anyone thinks about filing. State-wise PT slabs and LWF rules are configured once and applied automatically.

Automated reminders with lead time. Obligations are configured per entity and per state, with owners and escalation, so the alert reaches the right person days ahead — not on the due date.

Filing-ready outputs. ECR text files, ESI contribution files, challan-ready TDS summaries, 24Q inputs and PT statements generate directly from payroll, removing the manual re-keying step where most errors enter.

Form 16 and employee self-service. Investment declarations, proof submission, tax projections and Form 16 distribution move to a portal, cutting both the query load and the risk of missed proof windows.

A single evidence trail. Challans, acknowledgements and returns attach to the period they belong to, so audit and diligence requests become a search rather than a project.

Multi-state and multi-entity views. One dashboard shows what is due, where, for whom, and whether it is done — which is exactly the view a CFO needs and rarely has.

Registers and reports on demand. Statutory registers, headcount reconciliations and variance reports generate from live data rather than being assembled manually each month.

CozyHR is built around this idea: payroll, attendance, leave and compliance in one place, so the calendar runs itself and your team spends its time on judgement calls rather than data entry.

Common mistakes to avoid

1. Copying a generic calendar without mapping applicability. Your obligations depend on your states, headcount, entity type and worker mix. A borrowed calendar is wrong in both directions — it lists things you do not owe and omits things you do.

2. Treating the due date as the target. If you aim to file on the due date, every small disruption becomes a miss. Set internal deadlines three to five days earlier.

3. Ignoring small-value items. LWF, PTEC, nil returns for dormant registrations. Low value, full penalty exposure, and disproportionate clean-up cost.

4. Not marking exit dates in the PF portal. Costs you nothing to do and creates months of employee frustration when skipped.

5. Assuming the consultant has it covered. Ask for acknowledgements, not assurances. Accountability stays in-house.

6. Letting PAN and KYC quality slide. Invalid PANs, unseeded UANs and missing IP numbers surface as default notices and employee grievances long after the fact.

7. Missing minimum wage revisions. Especially for contractor-supplied staff, where the exposure is yours as principal employer.

8. Forgetting the annual items. POSH report, licence renewals, actuarial valuation, annual returns — once-a-year tasks with no monthly muscle memory.

9. Structuring salaries without stress-testing them. Compensation designs that minimise the wage base need to survive both scrutiny and the evolving wage definition.

10. No documentation trail. Payments made but challans not saved is a genuinely common finding, and it is indistinguishable from non-compliance during diligence.

11. Single-person dependency. No documented process, no backup, no handover file. One resignation and the calendar goes dark.

12. Never verifying dates. Due dates, rates and slabs change. A calendar built once and never re-checked slowly becomes fiction.

Frequently asked questions

What is an HR and payroll compliance calendar?

It is a single, owned document that lists every recurring statutory obligation your organisation carries — monthly, quarterly and annual — with the applicable law, the due date, the responsible owner, the portal used, and the evidence to be retained. A good one is specific to your entity, states and headcount rather than a generic list, and it is reviewed at least annually against current notifications.

Which compliances are monthly for Indian employers?

Typically PF ECR filing and contribution payment, ESI contributions where applicable, TDS deposit on salaries and on non-salary payments, professional tax remittance in states that levy it, and Labour Welfare Fund in states with a monthly cycle. Register maintenance under Shops & Establishment or factory rules runs continuously. Confirm each due date on the relevant portal, since dates and grace practices change.

What happens if we miss a statutory payment deadline?

Consequences generally stack: interest for the delay period, damages or penalty levies under several statutes, potential disallowance issues under income tax law for employee contributions not deposited in time, and in serious or prolonged cases prosecution exposure — particularly where amounts deducted from employees were not deposited. Practically, the cost rises sharply the longer a miss goes undetected, so the priority is early detection and voluntary regularisation with your advisor.

How do professional tax rules differ across states?

Professional tax is levied by states, so it exists only in some of them — and where it exists, the slabs, rates, periodicity, forms and portals differ. Some states require monthly remittance, others allow annual filing below a threshold, and several distinguish between tax on employees (deducted by the employer) and tax on the entity or its directors. Maintain a state applicability matrix and verify each state's current slabs annually.

When should Form 16 be issued to employees?

Form 16 for a financial year is typically issued by around mid-June following that year, after the Q4 Form 24Q return has been filed and processed so that Part A can be downloaded from TRACES. Confirm the current due date, and build buffer time — a defective Q4 return delays Part A availability and pushes the whole distribution.

What should be on a payroll month-end close checklist?

Freeze attendance and LOP, close joiner and leaver lists, capture arrears, variable pay and perquisites, run payroll and review a month-on-month variance report, validate every statutory computation, reconcile headcount, obtain documented approval, disburse and publish payslips, post the payroll journal, then execute the statutory payments and filings, archive challans, and reconcile statutory liability accounts to what was actually paid.

How do the new labour codes change payroll compliance?

The four codes consolidate a large number of central statutes and are being implemented in stages, with states framing their own rules. The two changes with the biggest payroll impact are a broader statutory definition of wages — which can increase the base for PF, gratuity and other benefits where salaries are allowance-heavy — and consolidation of registrations, returns and registers. Because the position keeps evolving, model the cost impact now but confirm current applicability for your states before changing anything.

Can an HRMS handle statutory compliance automatically?

An HRMS can compute statutory deductions accurately at source, apply state-specific rules by work location, generate filing-ready outputs such as ECR and 24Q inputs, send reminders with lead time to named owners, and store challans and acknowledgements against the right period. It cannot make judgement calls — wage-definition positions, worker classification, new-state applicability — so pair the system with an owner and, where the stakes are high, professional advice.

Bringing it together

A compliance calendar is not a document you produce once and file away. It is the operating rhythm of your HR and payroll function — the thing that turns a set of scattered obligations into a predictable monthly routine with named owners, lead times and evidence.

Start small if you need to. Map your applicable laws honestly, write down the fifteen or twenty obligations that genuinely apply to your entity and states, assign a name to each, set internal deadlines a few days ahead of the statutory ones, and create a folder where the proof lands every month. Review it once a year against current notifications, and log every check you make. That alone puts you ahead of most organisations of your size.

And keep the discipline of verification. Every date in this article is a planning anchor, not a legal position. Due dates shift, rates change, states amend their slabs, and the labour-code transition is still unfolding. Confirm the current position on the relevant government portal or with your consultant before you pay or file.

If you would rather not run this from a spreadsheet, that is exactly the problem CozyHR was built to solve — payroll, attendance, leave and statutory compliance in one system, with the calendar, the computations, the reminders and the evidence trail all in the same place. Try CozyHR and see how much of your month-end you can hand over to software.