Labour Codes Compliance Calendar for FY2026-27

Labour Codes Compliance Calendar for FY2026-27

If you run HR or payroll for an Indian company, you already know the feeling: just when you think you've mapped out every statutory deadline for the year, a state labour department quietly notifies a new rule, a threshold changes, or a return that used to be quarterly becomes monthly. FY2026-27 is shaping up to be exactly that kind of year. With India's four new Labour Codes — on Wages, Social Security, Industrial Relations, and Occupational Safety, Health and Working Conditions — now operational, and individual states notifying their own implementing rules at their own pace, a single national compliance calendar can no longer be treated as a fixed, one-time document. Employers need a labour codes compliance calendar that is built to be updated, not just filled in once and filed away.

This article walks through why the old "print it and pin it on the wall" compliance calendar approach breaks down under the new codes, how to track state-wise rule changes without losing your mind, a practical month-by-month template you can adapt for your organisation, and how HRMS and payroll software can take the manual tracking burden off your team's shoulders.

A quick but important note before we go further: labour law in India is inherently state-influenced, and the exact dates, thresholds, and forms applicable to your business depend on your state(s) of operation, your industry, your headcount, and rules that keep evolving. Nothing in this article should be treated as a substitute for checking current notifications from your state labour department, EPFO, ESIC, and your income tax and professional tax authorities, or for consulting a qualified compliance professional or labour law advisor. Treat this as a planning framework, not a legal opinion.

Why the Compliance Calendar Approach Has to Change for FY2026-27

For years, HR and payroll teams in India worked off relatively stable compliance calendars. The Provident Fund due date was the 15th of the month, ESI contributions were due around the 15th too, professional tax followed a known monthly or quarterly slab depending on the state, and annual returns fell on predictable dates. Once you built that calendar, you could reuse it year after year with only minor tweaks.

The rollout of the four Labour Codes changes that assumption in a few important ways.

1. Central codes, state-specific rules. The four codes are central legislation, but each state government is responsible for framing and notifying its own rules under these codes — covering things like registration thresholds, working hour limits, appointment letter formats, wage definitions for specific allowances, and administrative procedures. Because states are notifying these rules on a rolling basis rather than all at once, a business with employees in five states may find that three states have notified detailed rules, one has issued a draft, and one is still silent. That means your compliance obligations can differ meaningfully by location, and they can change mid-year as more states catch up.

2. Definitions that ripple through payroll. The Code on Wages introduces a more standardised definition of "wages," with a cap on allowances that don't count toward the wage base. This has downstream effects on how basic pay, PF contributions, gratuity calculations, and overtime pay are computed. If your payroll structure hasn't been reviewed against this definition, your compliance calendar needs a line item just for that review — and potentially for restructuring salary components.

3. New and consolidated registers and returns. The codes are designed to simplify and consolidate multiple older registers and returns into fewer, unified formats. In practice, this means the specific register names, formats, and filing frequencies your team has used for years may be replaced or merged, and the transition period itself needs to be tracked.

4. A moving target requires a living document. Because state rules are being notified progressively, a compliance calendar prepared in April 2026 may already be outdated by August 2026 if a new state notification changes a deadline or introduces a new filing. The right mental model for FY2026-27 is not "build the calendar once," but "build a calendar with a built-in review cycle."

5. Higher stakes for centralising compliance ownership. With more moving parts, informal tracking (a spreadsheet updated occasionally, or reliance on one person's memory) becomes riskier. Missed deadlines can mean late fees, interest, notices, loss of good standing with authorities, and in some cases restrictions on business operations — the exact consequences vary by law and by the nature of the default, so treat this as a general risk rather than a fixed number.

The rest of this guide is built around this shift: instead of a static calendar, you need a living compliance calendar framework — a monthly cadence of recurring statutory tasks, a mechanism for catching state-level updates, and a review rhythm that keeps the calendar current all year.

Understanding the Four Labour Codes and Their Compliance Impact

Before building your calendar, it helps to have a working mental map of what each code covers and where it touches your day-to-day HR and payroll operations. This is a simplified overview for planning purposes — always refer to the latest official text and your state's notified rules for exact obligations.

Code on Wages

This code consolidates earlier wage-related laws and standardises the definition of wages, minimum wage setting, payment of wages timelines, and bonus payments. For compliance calendars, this is the code most directly tied to:

• Minimum wage revision cycles (often linked to cost-of-living adjustments notified by state governments)
• Timely disbursal of wages within prescribed timelines after the wage period ends
• Bonus computation and payment timelines, typically linked to the financial year
• Salary structuring in line with the revised wage definition

Industrial Relations Code

This code deals with matters like standing orders, dispute resolution, retrenchment, and conditions for layoffs and closures, and it also affects requirements around fixed-term employment and issuing appointment letters. From a calendar perspective, this shows up as:

• Periodic review and updating of standing orders/service rules where applicable
• Ensuring appointment letters and employment documentation reflect current requirements
• Tracking any state-specific thresholds for applicability (based on establishment size)

Code on Social Security

This is the code most closely tied to PF, ESI, gratuity, maternity benefit, and other social security schemes, and it also extends certain protections toward gig and platform workers. Calendar-relevant items include:

• PF and ESI contribution and return filing cycles
• Gratuity eligibility tracking and payment timelines on separation
• Maternity benefit compliance and record-keeping
• Emerging obligations related to gig/platform worker contributions, where applicable to your business model

Occupational Safety, Health and Working Conditions Code

This code consolidates rules around working conditions, health and safety, working hours, leave, and welfare facilities, and it also governs licensing and registration for certain categories of establishments and contract labour. Calendar-relevant items include:

• Registration and licensing renewal tracking
• Statutory registers related to working hours, overtime, leave, and welfare facilities
• Health and safety committee requirements for applicable establishments
• Contract labour compliance where you engage contractors or staffing agencies

The practical takeaway: each code touches a different slice of your HR and payroll calendar, but they overlap heavily in payroll processing, statutory registers, and record-keeping. That overlap is exactly why a unified, centrally maintained calendar — rather than four separate mental checklists — makes sense.

How to Track State-wise Rule Notifications Without Losing Track

Since state rules are being notified progressively, the biggest operational risk for FY2026-27 isn't a lack of information — it's the information arriving in scattered, unpredictable bursts across multiple state gazettes and departmental circulars. Here's a practical process to stay on top of it.

Step 1: Map your "state footprint"

Start with a simple list of every state where you have:

• Registered employees (including remote workers on your payroll)
• A registered office, branch, warehouse, or factory
• Contract labour or third-party staffing arrangements

This list becomes your monitoring scope. There's no point tracking notifications from states where you have no establishment or employees.

Step 2: Assign a notification-tracking owner per state or per code

For smaller companies, one person (often the HR head or a compliance lead) can own this end-to-end. For larger, multi-state organisations, consider assigning ownership either by state (one person tracks all Karnataka updates) or by code (one person tracks Social Security Code updates across all states). Either model works — what matters is that no notification falls into a gap where "someone else was supposed to be watching for it."

Step 3: Set a recurring review cadence

Don't wait for a notification to surprise you. Build a recurring review — monthly at minimum, and ideally tied to a fixed date (for example, the first working day of every month) — where the assigned owner checks for updates from:

• The relevant state labour department
• EPFO and ESIC circulars
• Your state's professional tax and labour welfare fund departments
• Industry associations or chambers of commerce that often summarise regulatory changes for members

Step 4: Maintain a "state rules status" log

A simple log — even a spreadsheet — that records, per state, whether rules are notified, in draft, or pending, along with the date last checked and a link or reference to the source, gives your organisation an at-a-glance view of where your risk and uncertainty is concentrated. This log should feed directly into your compliance calendar: states with recently notified rules trigger a calendar review for that location.

Step 5: Loop in a compliance professional for interpretation

Tracking that a notification happened is different from understanding what it means for your specific payroll structure or HR processes. Build a periodic (quarterly is reasonable for most SMBs) check-in with a labour law consultant, chartered accountant, or company secretary who can translate notifications into concrete action items for your calendar.

Step 6: Push updates into your HRMS or tracker immediately

A notification that sits in someone's inbox doesn't protect you. As soon as a change is confirmed and understood, it should be reflected in your live compliance calendar — whether that's a shared tracker or your HRMS's compliance module — with a clear owner and due date assigned.

Building Your FY2026-27 Compliance Calendar: The Framework

A useful way to think about your calendar is in three layers.

Layer 1: Fixed recurring compliance. These are obligations that repeat every month or every quarter regardless of state-level changes — PF and ESI contributions, TDS deposits, professional tax payments, and routine statutory register updates. These form the backbone of your calendar and change the least.

Layer 2: Periodic/annual compliance. These occur once a year or on a fixed cycle — annual returns, bonus payments, minimum wage revision reviews, POSH annual reporting, license renewals, and audits. These need to be pre-scheduled well in advance because they often require data compilation over several weeks.

Layer 3: Event-triggered and state-variable compliance. These are obligations that depend on specific events (a new hire, a separation, a workplace complaint, opening a new branch) or on state-specific notifications that may not apply uniformly. This layer is the one that requires the ongoing monitoring process described above, because it cannot be fully pre-scheduled at the start of the year.

Your FY2026-27 calendar should visibly separate these three layers so that your team knows which parts are "set and reviewed quarterly" versus "watch actively for changes."

Month-by-Month Compliance Calendar Template

Below is a practical, generalised month-by-month template covering the recurring statutory and HR compliance activities most Indian employers need to plan for across FY2026-27 (April 2026 to March 2027). Treat the "typical timing" column as a planning guide only — always confirm exact due dates with the relevant authority or your compliance advisor, since some deadlines vary by state, by establishment size, and by any extensions authorities may notify during the year.

A few notes on using this table:

• The PF/ESI monthly filing and payment row is a placeholder for your organisation's actual due dates, which are set by EPFO and ESIC and should be confirmed each year, since administrative timelines can shift.
• TDS deposit timelines follow the Income Tax Act's monthly and quarterly cycles, which are separate from the Labour Codes but sit in the same payroll compliance calendar for most HR/payroll teams.
• Professional tax cycles (monthly, quarterly, or annual) vary significantly by state — some states require monthly payment with an annual return, others differ. Confirm your specific state's cycle.
• Labour welfare fund contributions are notified state-by-state, with different contribution amounts and periodicity (some are half-yearly, some annual). Not all states have an LWF scheme.
• POSH (Prevention of Sexual Harassment) committees are required to submit an annual report; the exact timeline should be confirmed against the applicable Act and any state-specific guidance, and internal committee meetings should happen more frequently than just once a year as a matter of good practice.
• Minimum wage revisions are typically notified by state governments periodically (commonly linked to consumer price index movements), and the timing is not uniform across states — this is exactly the kind of item that belongs in your ongoing state-tracking process rather than a fixed calendar date.

Key Recurring Compliance Areas Explained

Provident Fund (PF) and Employee State Insurance (ESI)

PF and ESI remain central pillars of payroll compliance under the Code on Social Security. Every month, employers need to:

• Compute employee and employer contributions accurately, based on current wage definitions
• Deposit contributions within the prescribed timeline
• File monthly returns (Electronic Challan cum Return for PF, and the corresponding ESI return)
• Reconcile new joiners and exits promptly so contribution records stay accurate

With the Wages Code's standardised definition of wages potentially affecting how much of an employee's CTC counts toward PF-eligible wages, FY2026-27 is a good year to have your payroll or compliance advisor re-verify that your PF base calculation aligns with current rules, rather than assuming last year's structure still holds.

TDS and Salary Compliance

TDS on salaries under the Income Tax Act runs on its own monthly deposit and quarterly return cycle, independent of the Labour Codes, but it's inseparable from your payroll compliance calendar in practice. Key recurring tasks:

• Monthly TDS deduction and deposit
• Quarterly TDS return filing (Form 24Q)
• Issuing Form 16 to employees after financial year-end
• Reconciling investment declarations and proof submissions during the December–February window

Any changes to salary structuring driven by the Wages Code (for example, adjustments to allowance components) can also affect taxable salary computation, so payroll and tax teams should coordinate closely when structures change.

Professional Tax

Professional tax is a state-level levy, and both the applicability and payment cycle differ by state — some states have monthly deductions with an annual return, others have different slabs and frequencies, and a few states don't levy it at all. For multi-state employers, this is one of the areas most prone to being missed because there's no single national cycle to memorise. Maintain a state-wise professional tax reference sheet as part of your calendar, and revisit it whenever you open operations in a new state.

Labour Welfare Fund (LWF)

LWF is another state-specific contribution, typically a small amount contributed by both employer and employee, with contribution periodicity varying (some states collect it half-yearly, others annually). Because contribution amounts and due dates are set independently by each state's labour welfare board, this is a natural candidate for inclusion in your state-notification tracking process rather than treating it as fixed.

Statutory Registers and Returns Under the New Codes

Historically, employers maintained multiple registers — for wages, attendance, overtime, leave, and fines/deductions — often in formats prescribed by different older laws. The new codes aim to simplify and consolidate these into fewer, unified registers, but the transition means employers should:

• Confirm which consolidated register formats apply once their state has notified rules
• Avoid discontinuing older registers until the transition is clearly confirmed by your compliance advisor
• Build a simple internal checklist for which registers are maintained physically vs. digitally, and who updates them

POSH Committee Reporting

The Prevention of Sexual Harassment (POSH) framework sits outside the four Labour Codes but remains a core statutory HR obligation with its own annual reporting cycle. A robust compliance calendar for FY2026-27 should include:

• Quarterly Internal Committee (IC) meetings, even if no complaints are pending, to review policy awareness and training status
• Annual training/awareness sessions for employees and the IC itself
• Timely preparation and submission of the annual report as required under the applicable rules
• A clear escalation and timeline tracker for any complaints received during the year, since POSH complaint handling has its own strict internal timelines separate from the annual reporting cycle

Minimum Wage Revisions

Minimum wages in India are set and revised by state (and sometimes central, for specific scheduled employments) governments, and the frequency and timing of revisions differ across states. Rather than assuming a fixed month for revisions, build a recurring quarterly check into your calendar specifically to review whether any state where you operate has issued a new minimum wage notification, and update your payroll base pay structures promptly when they do.

How to Build an Internal Compliance Tracker

Even before you adopt specialised software, you can build a workable internal tracker with a structured, disciplined approach. Here's a step-by-step method:

Step 1: List every applicable compliance obligation. Start with the recurring items from the table above, then add state-specific items based on your footprint. Don't try to be exhaustive on day one — start with what you know applies, and expand as you confirm more.

Step 2: Assign an owner and a backup for every item. Every line in your tracker should have a named person responsible and a backup who can step in during leave or transitions. Compliance items with no clear owner are the ones most likely to be missed.

Step 3: Set a due date and a "review by" date. The review date should typically fall a few days before the actual due date, giving your team buffer time to catch missing documents or approvals.

Step 4: Build in a status field, not just a due date. A simple status column (Not Started / In Progress / Filed / Verified) turns a static list into an active tracker your team can glance at weekly.

Step 5: Attach evidence. For every completed item, store proof of filing or payment (acknowledgement receipts, challans, filed forms) in a consistent, easily searchable location — this becomes invaluable during audits or inspections.

Step 6: Run a monthly reconciliation meeting. A short, recurring meeting (30 minutes is often enough) where the compliance owner walks through the tracker with HR/payroll leadership keeps accountability visible and catches issues early.

Step 7: Build a change log. Whenever a state notifies new rules or a due date shifts, log the change with a date and source. Over a year, this change log becomes a valuable institutional record, especially useful when onboarding new compliance staff or during audits.

Step 8: Review and refresh the entire tracker quarterly. Don't just add new items — actively check whether old assumptions still hold. A quarterly refresh catches drift before it becomes a missed deadline.

This structure works whether you're using a shared spreadsheet, a project management tool, or a dedicated compliance module — the discipline matters more than the tool, though the tool can make the discipline much easier to sustain.

The Role of HRMS and Payroll Software in Automating Compliance

Manually tracking dozens of recurring and state-variable compliance items across a growing team is time-consuming and error-prone, especially for lean HR teams in startups and SMBs who are also handling recruitment, onboarding, performance management, and employee queries. This is where a good HRMS and payroll platform earns its keep.

Automated statutory calculations. A well-configured payroll system computes PF, ESI, professional tax, TDS, and other statutory deductions automatically based on current rules, reducing the manual calculation errors that often lead to compliance gaps.

Centralised reminders and deadline tracking. Instead of relying on someone's calendar app or memory, an HRMS can maintain a shared compliance calendar with automated reminders sent to the right owners ahead of each due date, so nothing depends on one person remembering everything.

Configurable rules by state. For multi-state employers, a platform that lets you configure professional tax slabs, LWF contributions, and other state-specific parameters independently per location removes a major source of manual tracking error.

Audit-ready record keeping. Digital statutory registers, payslip archives, and filing acknowledgements stored in one searchable system make it far easier to respond to inspections or audits than digging through paper files or scattered folders.

Faster adaptation to rule changes. When state rules or thresholds change, a platform that's actively maintained can push configuration updates centrally, rather than requiring every payroll processor to manually adjust formulas.

Visibility for leadership. Dashboards that show compliance status across locations give founders and HR leaders a quick way to spot risk areas — for example, a location where filings are consistently late — before it becomes a bigger issue.

None of this replaces the need for human judgment and periodic expert review, especially in a transition period like FY2026-27 when rules are still being notified. But it does mean your team spends less time on repetitive tracking and more time on the judgment calls that actually need attention.

This is precisely the kind of workflow CozyHR is built to support — helping Indian HR and payroll teams centralise their compliance calendar, automate statutory calculations, and get proactive reminders as deadlines approach, so that keeping up with a shifting regulatory landscape doesn't fall entirely on manual effort.

Common Risks and Penalties of Missing Compliance Deadlines

It's worth being clear-eyed about why this matters beyond good governance. While this article won't quote specific penalty figures — those are set by statute and rules, can change, and vary by the nature and duration of the default — it's useful to understand the general categories of risk employers face when compliance deadlines slip:

• Monetary consequences. Late payment of statutory dues like PF, ESI, professional tax, or TDS typically attracts interest and, in many cases, additional penalties or late fees, which compound the longer the default continues.
• Legal and administrative action. Persistent or serious non-compliance can lead to show-cause notices, inspections, or in more serious cases, prosecution under the relevant statute.
• Reputational risk. Compliance lapses that surface during due diligence (for funding rounds, acquisitions, or major client contracts) can slow down or jeopardise those processes.
• Employee trust and retention impact. Delayed PF deposits or incorrect statutory deductions can directly affect employees' financial security and trust in the organisation, which has knock-on effects for retention and employer branding.
• Operational disruption. In some cases, non-compliance with registration or licensing requirements can restrict an establishment's ability to operate certain functions until rectified.

The exact consequences depend on the specific law, the nature of the lapse, and how quickly it's rectified — so the right approach is always to consult the applicable statute or a compliance professional if a deadline has been missed, rather than assuming a generic outcome. The larger point for planning purposes is simple: the cost of prevention (a well-maintained compliance calendar) is consistently lower than the cost of remediation.

Frequently Asked Questions

1. What exactly is a labour codes compliance calendar, and why do I need a new one for FY2026-27? A labour codes compliance calendar is a structured, month-by-month (and often state-by-state) schedule of statutory HR and payroll obligations — filings, payments, renewals, and reporting deadlines. You need an updated one for FY2026-27 because the four Labour Codes are now operational and states are notifying their own implementing rules progressively, which means deadlines, formats, and even applicability can shift during the year in ways a static, once-a-year calendar can't capture.

2. Do the four Labour Codes apply uniformly across all Indian states? The codes themselves are central legislation, but many procedural and administrative details are governed by rules that each state notifies independently. This means practical compliance requirements can differ from state to state, and the pace at which states have notified their rules has also varied. Always confirm the current status for each state where you have employees or establishments.

3. How often should we update our internal compliance calendar? At minimum, do a full review quarterly, but maintain a lighter monthly check specifically for new state notifications relevant to your footprint. Treat the calendar as a living document rather than something finalised once a year.

4. Our company operates in only one state — do we still need to worry about state-wise variance? Yes, though the tracking burden is lighter. Even single-state employers need to actively watch for updates from their own state's labour department, since the notification of new rules under the codes is ongoing, and a single state's rules can still change more than once during a financial year.

5. What's the difference between compliance under the old laws and compliance under the new codes? The new codes consolidate multiple older laws into four umbrella codes, aiming to simplify definitions (like "wages"), reduce the number of registers and returns, and standardise certain processes. In practice, this means some of your older forms, register formats, or filing frequencies may be replaced by newer, consolidated versions as your state's rules take effect — which is why a one-time compliance calendar update isn't enough; you need an ongoing review process.

6. Can HRMS software fully automate labour code compliance? HRMS and payroll software can automate a large share of the repetitive work — calculations, reminders, record-keeping, and configurable state-specific parameters — but human oversight remains essential, especially during a transition period when rules are still being notified and interpreted. Use software to reduce manual effort and error, and pair it with periodic review by your internal team or an external compliance advisor.

7. What happens if we miss a compliance deadline? Consequences vary by the specific law and the nature of the default, and can include interest, late fees, penalties, notices, or in serious or repeated cases, more significant legal consequences. If you've missed a deadline, the best course of action is to address it promptly and consult a compliance professional about rectification, rather than waiting.

8. Where should we go to verify the exact, current compliance dates for our business? Always verify against official sources — your state labour department's notifications, EPFO and ESIC circulars, the Income Tax Department for TDS, and your state's professional tax and labour welfare fund departments — or work with a qualified compliance consultant, chartered accountant, or company secretary who tracks these updates professionally. This article is a planning framework, not a substitute for that verification.

Conclusion

FY2026-27 marks a genuine shift in how Indian employers need to think about statutory compliance. With the four Labour Codes operational and states notifying their own rules at their own pace, the days of a fixed, print-it-once compliance calendar are behind us. What works now is a living framework: a clear month-by-month structure for recurring obligations like PF, ESI, TDS, professional tax, and LWF; a disciplined process for tracking state-wise rule notifications; and a well-owned internal tracker that gets reviewed and refreshed throughout the year — not just in April.

Building and maintaining this manually is possible, but it takes real time and discipline away from the other priorities on an HR or founder's plate. That's exactly the gap a good HRMS is meant to close — turning a maze of recurring deadlines and shifting state rules into automated reminders, accurate statutory calculations, and a single source of truth your team can rely on.

If you'd like to see how CozyHR can help your team automate compliance tracking, PF/ESI and TDS calculations, and payroll — so your FY2026-27 calendar stays current without becoming a full-time job — we'd love to show you around. Explore CozyHR to get started.