Payroll Compliance Calendar 2027 for India

Payroll Compliance Calendar 2027: Statutory Due Dates for Indian Employers

Every payroll team in India runs on a rhythm of deadlines. Provident Fund contributions have a due date. ESI has a due date. TDS deposits, professional tax returns, bonus payments, Form 16 issuance, annual returns under the labour codes — each has its own clock, and each clock is running at the same time as every other one. Miss a single date and you are looking at interest, late fees, notices, and in some cases penal action against the company and its signatories.

The problem is not that these dates are secret. They are published in statutes and circulars that any payroll manager can look up. The problem is that they are scattered across a dozen different laws, administered by different departments (central and state), and they rarely line up neatly in a single place. A payroll compliance calendar solves that by pulling every recurring obligation into one master schedule that your team can plan against for the whole of 2027.

This guide walks through how to build that calendar, what categories of due dates it needs to cover, how to structure it so nothing falls through the cracks between HR, finance, and your registered office address, and how to keep it accurate as rules change through the year. It is written for HR managers, founders, and payroll teams running compliance in India — whether you process payroll in-house, through an HRMS, or via an outsourced provider.

A note before we start: statutory due dates, contribution rates, and thresholds are revised periodically by the central and state governments, and 2027 will likely bring further changes as the labour codes continue to roll out across states. Treat every date and rate in this article as a planning framework, not a final source of truth — always confirm the current due date, rate, and applicable form with the relevant government portal (EPFO, ESIC, the Income Tax Department, your state labour department, and your state professional tax authority) or your compliance advisor before you rely on it.

---

Why a Dedicated Compliance Calendar Matters

Payroll compliance is not one deadline — it's dozens, on different clocks

A mid-sized Indian company with a PAN-India presence is typically tracking at minimum:

• Monthly EPF contribution and return filing
• Monthly ESI contribution and return filing
• Monthly TDS deposit under Section 192
• Quarterly TDS return filing (Form 24Q)
• Monthly or periodic Professional Tax payment and returns (rules vary by state)
• Annual Labour Welfare Fund contribution (varies by state, some are half-yearly)
• Annual bonus payment deadlines under the Payment of Bonus Act
• Gratuity-related filings and trust compliance, where applicable
• Form 16 issuance to employees
• Annual returns under the Shops and Establishments Act or Factories Act
• Statutory registers and returns under the labour codes as they come into force state by state
• Annual health check-up compliance for eligible categories of employees, where mandated

Each of these sits inside a different statute, has a different filing portal, and in several cases has different due dates depending on the state you operate in. Without a single calendar, compliance ends up living in the heads of two or three people — and when they are on leave, on the day a return is due, things slip.

The cost of missing a date

Missing a statutory due date is rarely a one-time inconvenience. Typical consequences include:

• Interest on delayed EPF or ESI deposits, calculated for every day of delay
• Damages/penalties levied by EPFO for delayed contributions, in addition to interest
• Late filing fees under the Income Tax Act for delayed TDS returns, plus interest on delayed TDS deposit
• Prosecution risk in cases of repeated or wilful default under certain labour statutes
• Reputational and audit risk — a pattern of late filings is one of the first things a statutory or customer compliance audit will flag
• Employee trust erosion — a delayed Form 16 or a PF mismatch is often the first sign employees notice that something is off in payroll

None of this is exotic. It is almost always the result of an ordinary administrative gap: nobody owned the date, or the date changed and nobody updated the tracker.

What a good calendar buys you

A well-built compliance calendar does three things:

1. Converts "the law says by the 15th" into an actual task assigned to a named owner with a working-day buffer before the real deadline.
2. Creates a forward view, so payroll and finance can plan cash flow around statutory outflows (PF, ESI, TDS, bonus, LWF) instead of being surprised each month.
3. Becomes your audit trail. When a labour inspector, EPFO officer, or your own internal auditor asks "how do you ensure timely compliance," a documented calendar with sign-offs is a much stronger answer than "we know the dates."

---

The Building Blocks of a 2027 Payroll Compliance Calendar

Rather than publish a single fixed date list (which will vary by state, deposit mode, and any mid-year rule changes), build your calendar around these recurring categories. For each one, note the statute, the typical periodicity, the portal/authority, and the internal owner.

1. Provident Fund (EPF)

• What: Employer and employee EPF contributions, along with EPS and EDLI components where applicable
• Periodicity: Monthly deposit, with an accompanying Electronic Challan-cum-Return (ECR) filing
• Authority/portal: EPFO unified portal
• Typical pattern: Contribution for a given wage month is due for deposit early in the following month — confirm the exact current due date on the EPFO portal, since it is occasionally revised.
• Internal owner: Payroll lead, with finance sign-off on the funds transfer

2. Employees' State Insurance (ESI)

• What: Employer and employee ESI contributions for eligible employees (wage-ceiling based coverage)
• Periodicity: Monthly deposit
• Authority/portal: ESIC portal
• Typical pattern: Similar cadence to EPF — deposited early in the month following the wage month.
• Internal owner: Payroll lead
• Special note: ESIC also runs half-yearly contribution periods (April–September and October–March) that drive eligibility and benefit continuity — mark the start and end of each contribution period on your calendar even though the deposit itself is monthly.

3. Tax Deducted at Source (TDS) on Salaries

• What: TDS deducted under Section 192 on employee salaries
• Periodicity:
• Monthly deposit of TDS deducted
• Quarterly return in Form 24Q (four filings a year, one per quarter of the financial year)
• Authority/portal: TRACES / Income Tax e-filing portal
• Internal owner: Payroll lead with finance/tax team review
• Calendar tip: Build in an internal "TDS working" checkpoint a few working days before each quarter's Form 24Q due date, where payroll reconciles deductions against actual deposits before the return is filed — this is where most 24Q errors get caught before they become notices.

4. Professional Tax (PT)

• What: State-level tax on employment, deducted from employee salary and remitted by the employer
• Periodicity: Varies significantly by state — some states require monthly payment and monthly or annual returns, others have slab-based annual schemes
• Authority/portal: State commercial tax / PT department portal (state-specific)
• Internal owner: Payroll lead, one per state of operation
• Calendar tip: If you operate in multiple states, professional tax is the single biggest source of calendar fragmentation — build one sub-calendar per state rather than trying to force a single national PT date.

5. Labour Welfare Fund (LWF)

• What: A small, state-mandated contribution (employer and often employee) to the state's labour welfare fund
• Periodicity: Highly state-specific — some states collect half-yearly, others annually, and applicability itself varies by state and establishment type
• Authority/portal: State labour department
• Internal owner: Payroll lead / compliance owner for that state
• Calendar tip: LWF is the line item most commonly missed because the amounts are small and the cadence is irregular. Put an explicit reminder on the calendar even though the contribution itself may only be a few rupees per employee — the filing obligation doesn't scale down with the amount.

6. Statutory Bonus

• What: Annual bonus payable under the Payment of Bonus Act to eligible employees
• Periodicity: Annual, tied to the close of the accounting year, with a statutory outer limit (commonly referenced as within eight months of the close of the accounting year, subject to any extensions — verify the current provision)
• Authority: State labour department (registers and returns)
• Internal owner: Payroll lead with finance and leadership sign-off on the bonus percentage
• Calendar tip: Don't wait until the deadline quarter to start this. Put a checkpoint 2–3 months earlier to finalize eligibility criteria, the allocable surplus calculation, and the payout percentage, so the actual disbursement is a mechanical payroll run rather than a last-minute negotiation.

7. Gratuity

• What: Gratuity payment obligations that crystallize on employee separation (resignation, retirement, termination) once eligibility conditions are met, plus any annual actuarial valuation and trust-related compliance if you fund gratuity through an approved trust or group insurance scheme
• Periodicity: Event-driven for individual payments (must be settled promptly after separation); annual for actuarial valuation and trust compliance
• Internal owner: Payroll lead + finance (for trust/valuation)
• Calendar tip: Even though gratuity payment itself is event-driven, put the annual actuarial valuation on a fixed calendar slot — it feeds your financial statements and is easy to forget because it isn't tied to a specific payroll cycle.

8. Form 16 and Annual Tax Documentation

• What: Issuance of Form 16 (TDS certificate) to employees for the previous financial year
• Periodicity: Annual, after the fourth quarter's Form 24Q is filed and processed
• Internal owner: Payroll lead
• Calendar tip: Form 16 depends on Form 24Q Q4 being filed and the TRACES portal generating the certificate — sequence these as dependent tasks, not parallel ones, so you're not promising employees a date you can't hit.

9. Annual Returns and Registers Under State Shops & Establishments Acts / Labour Codes

• What: Annual returns, statutory registers (attendance, wages, leave, overtime), and license renewals under the Shops and Establishments Act, Factories Act (if applicable), and progressively under the four labour codes as states notify their rules
• Periodicity: Mostly annual, with some registers requiring ongoing maintenance rather than periodic filing
• Internal owner: HR compliance lead
• Calendar tip: As labour code rules continue to be notified state by state through 2027, build a quarterly "regulatory scan" task into the calendar — a recurring checkpoint where someone explicitly checks for rule notifications in every state you operate in, rather than relying on ad hoc news.

10. Mandatory Health Check-Ups (Where Applicable)

• What: Periodic health check-up obligations that apply to specific categories of employees under certain state factory or shops and establishments rules
• Periodicity: Annual, where applicable
• Internal owner: HR / admin, with payroll tracking attendance impact
• Calendar tip: Applicability is establishment- and state-specific — confirm whether this obligation applies to your establishment type before building it into the calendar as a blanket requirement.

11. New Joiner and Exit-Linked Statutory Actions

These aren't calendar dates in the traditional sense, but they belong on your compliance calendar as SLA-based recurring tasks:

• UAN generation/activation and PF, ESI enrolment for new joiners within a defined number of days of joining
• Full and final settlement, including PF/gratuity processing, within a defined window after an employee's last working day
• Relieving letter and experience letter issuance timelines

Track these as rolling SLAs measured against each joining or exit date, reviewed weekly, rather than fixed calendar entries.

---

Building the Calendar: A Practical Template

Rather than a single national grid, structure your 2027 calendar as a layered spreadsheet (or a compliance module inside your HRMS) with these columns:

Populate this once as a master template, then generate month-by-month task lists from it at the start of each quarter. Most HRMS and compliance tools can auto-generate reminders from a structure like this; if you're doing it manually, a shared calendar with recurring events tied to each row works almost as well, provided ownership is explicit.

Set an internal buffer, always

The single highest-leverage change most payroll teams can make is moving the internal target date 3–5 working days before the statutory due date. This absorbs:

• Bank processing delays on the day of transfer
• Portal downtime (both EPFO and ESIC portals see periodic slowdowns near deadlines, when filing volumes spike)
• Last-minute data corrections (a missed new joiner, an incorrect LOP adjustment)
• Approver unavailability

A calendar with no buffer is a calendar that treats the statutory due date as the working deadline — which means any single hiccup causes a genuine miss, not just a scare.

Assign a named owner and a named backup

"Payroll team" is not an owner. Every row needs one person's name against it, plus a backup who can act if that person is on leave. This single practice eliminates a large share of missed filings, because ambiguity about ownership — not lack of knowledge of the date — is the most common root cause of a late filing.

Build in a monthly compliance review meeting

A 30-minute monthly meeting between payroll, finance, and HR compliance — reviewing the calendar for the month just closed and the month ahead — catches issues (a rate change, a new state of operation, a new registration requirement) long before they become a missed deadline.

---

Quarter-by-Quarter Planning for 2027

While exact statutory dates need to be verified against current notifications, here is how to think about the shape of the year so your calendar has the right emphasis at the right time.

Q1 2027 (January–March)

• Close out calendar-year-linked compliance items (where applicable in your states)
• Prepare for the financial year-end: reconcile PF, ESI, and PT contributions for the outgoing financial year
• Begin collecting investment proof/declarations from employees for final TDS computation of FY 2026–27
• Plan the annual bonus calculation process so it isn't compressed into the last month before the statutory deadline

Q2 2027 (April–June)

• New financial year begins — update payroll systems for any revised tax slabs, PF/ESI wage ceilings, or professional tax slabs announced in the Union or state budgets
• File Q4 (Jan–Mar) Form 24Q for the previous financial year
• Begin the Form 16 issuance process once Q4 24Q is processed
• Renew any annual licenses/registrations that fall due at the start of the financial year in your state(s)
• ESIC's April–September contribution period begins — refresh eligibility lists

Q3 2027 (July–September)

• File Q1 (Apr–Jun) Form 24Q
• Mid-year review of the compliance calendar itself: has your headcount crossed a new PF/ESI/PT threshold in any state? Have you opened a new office that triggers fresh registrations?
• Continue the quarterly "regulatory scan" for labour code notifications

Q4 2027 (October–December)

• File Q2 (Jul–Sep) Form 24Q
• ESIC's October–March contribution period begins
• Finalize the statutory bonus calculation and payout, if your accounting year aligns with the calendar year
• Year-end planning: gather updated investment declarations, plan for any year-end compensation actions (increments, one-time bonuses) and their payroll/compliance sequencing

Treat this quarter-by-quarter view as a rhythm, not a fixed schedule — always cross-check the live due dates for TDS, PF, ESI, PT, and LWF against the respective portals as each quarter approaches, since specific dates can shift.

---

Multi-State Complexity: Don't Build One Calendar — Build a Base Calendar Plus State Overlays

If you operate in more than one state, resist the temptation to build a single flattened calendar. Professional tax, LWF, and Shops and Establishments Act obligations are genuinely different state to state — different due dates, different forms, sometimes different periodicity entirely (monthly PT in one state, annual slab-based PT in another).

The cleaner structure:

1. A base calendar covering everything that's the same regardless of state: EPF, ESI, TDS/24Q, Form 16, statutory bonus.
2. A state overlay for each state of operation, covering PT, LWF, and state-specific Shops and Establishments / labour code obligations.

This keeps the base calendar simple and lets you onboard a new state of operation by adding one overlay, rather than rebuilding the whole calendar.

---

Automating the Calendar Instead of Tracking It Manually

Spreadsheets work, but they degrade over time — someone forgets to update a due date after a rule change, or a formula breaks silently. A payroll and compliance platform like CozyHR is built to keep this from happening by:

• Maintaining a living compliance calendar tied directly to your payroll runs, so due dates update automatically when statutory rules change
• Generating monthly, quarterly, and annual filing reminders per state and per compliance category, assigned to named owners
• Storing filing evidence (challans, acknowledgements, returns) against each calendar entry, so your audit trail is built as you go rather than reconstructed under pressure
• Flagging when a new hire, a new office location, or a headcount threshold change introduces a new compliance obligation you haven't set up yet

For a growing company, the real risk in 2027 isn't that nobody knows the rules — it's that the rules and your team's bandwidth to track them manually grow at different rates. Automating the calendar is what keeps compliance reliable as headcount and geography scale.

---

Common Mistakes Payroll Teams Make With Compliance Calendars

1. Treating the statutory due date as the working deadline, with no internal buffer — leaves zero room for error.
2. Building the calendar once and never revisiting it — rates, thresholds, and even due dates change; a calendar frozen in January 2027 is unreliable by mid-year if nobody updates it.
3. No named owner, or ownership living only in one person's head — a single point of failure that shows up the moment that person is unavailable.
4. Ignoring event-driven obligations — new joiner enrolment and exit settlement timelines are just as much "compliance" as monthly filings, but they don't sit naturally on a fixed calendar and get missed as a result.
5. Underestimating multi-state complexity — assuming PT or LWF works the same way everywhere is one of the most common sources of state-specific non-compliance.
6. No evidence trail — filing on time but not storing the acknowledgment/challan in a retrievable, organized way, which becomes a real problem the moment an inspector or auditor asks for proof.
7. Skipping the mid-year threshold check — a company that crosses the ESI wage ceiling headcount, or opens an office in a new state, often doesn't realize a new obligation has been triggered until well after it should have started.

---

A Worked Example: How a 40-Person Company Might Structure Its Calendar

To make this concrete, consider a hypothetical Indian SMB — 40 employees, offices in two states, no factory license, standard Shops and Establishments registration in both states. Here's how their base calendar plus overlays might look, purely as an illustration of the structure (not as a source for actual dates or rates):

Base calendar (applies company-wide):

• EPF: monthly deposit + ECR filing, owner = Payroll Executive, backup = Payroll Manager
• ESI: monthly deposit + return, same owners, tracked against the twice-yearly contribution periods
• TDS on salary: monthly deposit, owner = Payroll Manager; Form 24Q, quarterly, owner = Payroll Manager, reviewer = Finance Controller
• Form 16: annual, sequenced after Q4 24Q, owner = Payroll Executive
• Statutory bonus: annual, planning checkpoint 3 months before payout, owner = HR Head, sign-off = Founder/CFO
• Gratuity actuarial valuation: annual, owner = Finance Controller

State overlay — State A:

• Professional tax: monthly payment + return, owner = Payroll Executive
• Labour Welfare Fund: half-yearly, owner = HR Compliance Lead
• Shops & Establishments annual return: annual, owner = HR Compliance Lead

State overlay — State B:

• Professional tax: annual slab-based payment, owner = Payroll Executive
• Labour Welfare Fund: not applicable in this illustration — but the "not applicable" status itself is recorded and reviewed annually, since applicability rules can change
• Shops & Establishments annual return: annual, owner = HR Compliance Lead

Rolling SLAs (not fixed dates):

• New joiner PF/ESI enrolment: within X working days of joining (confirm current SLA), owner = Payroll Executive
• Full and final settlement: within X days of last working day (confirm current guidance and any company policy commitment), owner = Payroll Executive, reviewer = HR Head

Even a company this size ends up with roughly 15–18 distinct tracked items once you separate the base calendar from the state overlays and the rolling SLAs. That's exactly why a flattened, single-list calendar tends to break down — the structure needs to reflect the fact that these obligations genuinely come from different sources with different rhythms.

Coordinating Across HR, Payroll, and Finance

Compliance calendars fail almost as often from coordination gaps as from missing information. A few practices help:

Make the calendar visible, not siloed

If the compliance calendar lives only in the payroll manager's personal spreadsheet, the rest of the organization has no way to plan around it — finance can't forecast the cash outflow for PF and TDS deposits, and HR can't tell a departing employee when their full and final settlement will land. Publish the calendar (or the relevant slices of it) to a shared location that HR, payroll, and finance can all see.

Separate "who files" from "who approves"

Every statutory filing should have two names against it: the person who prepares and files it, and the person who reviews and approves before submission. This isn't bureaucracy for its own sake — a second set of eyes is consistently what catches a wrong contribution amount, an outdated wage ceiling, or a miscalculated bonus percentage before it goes out the door.

Escalate variances immediately, not at month-end

If a filing is going to be late — because of a data issue, a bank delay, or a portal outage — the owner should flag it the moment they know, not wait until the monthly review meeting. A calendar is only useful as an early-warning system if delays are surfaced in real time.

Keep a change log for the calendar itself

Whenever a due date, rate, or threshold changes — a new PF wage ceiling, a revised PT slab, a newly notified labour code rule in one of your states — log the change and the date you updated the calendar. This turns your calendar into a record of your team's diligence, which is exactly what you want to be able to show in an audit.

Why 2027 Specifically Needs Extra Attention

Two things make 2027 a year where payroll teams should treat their compliance calendar as a priority project rather than routine maintenance:

First, the continued rollout of the four labour codes. As more states notify their rules, definitions that touch payroll directly — particularly the wage definition that affects PF, gratuity, and bonus calculations — are likely to keep evolving. A calendar that assumes "the process is the same as last year" is the single biggest risk factor for a payroll team in this environment.

Second, cumulative threshold creep. Companies that have grown through 2025 and 2026 may have quietly crossed headcount or wage thresholds that trigger new obligations — ESI applicability, gratuity applicability, LWF applicability in a state where it wasn't relevant before. These thresholds don't announce themselves; they only show up if someone is actively checking. Build that check into your Q1 2027 calendar review rather than discovering it during an inspection.

Frequently Asked Questions

1. Do statutory due dates change every year, or can I reuse the same calendar as 2026? Periodicities (monthly, quarterly, annual) tend to stay stable, but specific due dates, rates, and thresholds are revised periodically by the central government, state governments, and regulatory bodies like EPFO and ESIC. Use your 2026 calendar as a structural template, but verify every date and rate against the current notification before relying on it for 2027.

2. Is Professional Tax applicable in every state? No. Professional tax is a state subject, and not every state levies it. Where it applies, the rate structure, due dates, and return frequency vary by state. Always check your specific state's professional tax rules rather than assuming a national standard.

3. What happens if we deposit EPF or ESI contributions late? Late deposits typically attract interest for the period of delay, and in the case of EPF, additional damages/penalties can apply. Beyond the direct cost, repeated delays increase scrutiny in future inspections and audits. Confirm current interest and penalty provisions with EPFO/ESIC rather than relying on prior-year figures.

4. How far in advance should we start preparing for the annual statutory bonus payout? Most payroll teams benefit from starting the allocable surplus and eligibility calculation 2–3 months before the statutory deadline, so leadership sign-off on the payout percentage doesn't become a last-minute bottleneck that risks a delayed payment.

5. Do the new labour codes change our existing PF, ESI, and TDS due dates? As the four labour codes are implemented, several compliance processes — wage definitions, registers, and returns in particular — are being reshaped, and specific procedural due dates may be revised as state rules are notified. Treat this as an evolving area through 2027 and build a recurring "regulatory scan" into your calendar rather than assuming today's process will be unchanged.

6. Should a small company with fewer than 20 employees still build a full compliance calendar? Yes, though the calendar will be shorter. Applicability thresholds for PF, ESI, gratuity, and bonus are based on headcount and wage levels, so a small company may not owe all of these yet — but as soon as you cross a threshold, the obligation begins, and a calendar helps you notice that crossing before it becomes a compliance gap.

7. Who should own the compliance calendar — HR, payroll, or finance? In most organizations, payroll owns the calendar operationally (since most obligations are payroll-linked), HR compliance owns the labour-law and registers side, and finance reviews the calendar for cash flow planning and sign-off on payments. The calendar itself should be a shared, visible document rather than something any one function keeps privately.

8. What's the single most useful change we can make to reduce missed deadlines? Assign a named owner and a named backup to every recurring compliance item, and set your internal target date several working days before the actual statutory due date. These two changes alone eliminate most of the "we knew the date but still missed it" failures payroll teams run into.

---

Conclusion

A payroll compliance calendar is not a document you build once and file away — it's a living operating system for how your company meets its statutory obligations across PF, ESI, TDS, professional tax, LWF, bonus, gratuity, and the evolving labour codes. The teams that handle 2027 smoothly won't be the ones who memorized every due date; they'll be the ones who built a structure — categories, owners, buffers, and a review rhythm — that keeps working even when the specific dates shift underneath it.

If you're currently tracking compliance across spreadsheets, sticky notes, and a few people's memory, that's the moment to move to a system that keeps the calendar current for you. CozyHR's payroll and compliance platform ties your statutory calendar directly to your payroll runs, tracks state-specific obligations automatically, and keeps a clean evidence trail for every filing — so your team spends less time chasing dates and more time on the work that actually needs a person's judgment. [Explore how CozyHR can run your 2027 compliance calendar for you.]