EOR Payroll and Tax Compliance in India: The Monthly Cycle Explained

EOR Payroll and Tax Compliance in India runs on a fixed monthly rhythm. It does not bend for holidays, weekends, or a busy quarter. Employers must deposit tax deducted from salaries with the government by the 7th of the following month. Provident Fund and Employees’ State Insurance contributions are due by the 15th. Miss either date, even by a single day, and interest starts accruing automatically. No warning arrives first. This is not a once-a-year filing exercise. It is a recurring operational cycle. It repeats every month, indefinitely, for as long as the company employs anyone in India.

Most global companies underestimate this until they experience it directly. A single missed Provident Fund deposit can trigger interest, statutory damages, and in serious cases, personal liability for company directors. This piece walks through what actually happens every month and the specific deadlines involved. It also covers how a competent EOR keeps that cycle running, without the client ever needing to track a single date themselves.

EOR Payroll and Tax Compliance in India: The Monthly Cycle

Every payroll cycle in India generates several separate statutory obligations. Different legislation governs each one, and a different authority enforces it. None of them are optional, and none of them share a single unified deadline.

Two of these dates deserve particular attention, since they recur every single month without exception. The 7th covers TDS. The 15th covers both Provident Fund and ESI simultaneously. That means payroll teams effectively have two hard deadlines to clear in the first half of every month, on top of running the payroll calculation itself.

What Happens When a Deadline Gets Missed

The consequences scale with how badly a company misses the deadline, but none of them are trivial. A late TDS deposit attracts interest at 1.5 percent per month. The Income Tax Department calculates that interest from the date of deduction, not from the deadline itself, and separate penalty provisions under the Income Tax Act can apply on top.

Late Provident Fund contributions carry their own, arguably harsher, consequences. Interest accrues at 12 percent per annum. Separately, the Employees’ Provident Fund Organisation can levy damages under Section 14B of up to 25 percent of the outstanding arrears, depending on how long the delay runs. Persistent non-payment can place a company on EPFO’s public list of defaulting employers. That reputational consequence often outlasts the financial one.

ESI non-payment carries the most serious theoretical exposure. Beyond the 12 percent annual interest, Section 85 of the Employees’ State Insurance Act allows for prosecution of the employer in cases of non-payment. This remains an extreme outcome. Regulators generally reserve it for persistent, deliberate non-compliance rather than an isolated late deposit.

How an EOR Actually Runs This Cycle Each Month

A properly structured EOR does not simply calculate salaries once a month and call the job done. It runs a coordinated internal calendar that works backward from each statutory deadline. That calendar builds in enough buffer to catch errors before money moves.

Picture how this plays out for a fifty-person team an EOR manages on behalf of a foreign software company. Payroll inputs, new joiners, exits, salary revisions, variable pay, all close by a fixed internal cutoff early in the month. That happens well before the payroll run itself. The EOR calculates gross-to-net figures, generates the TDS challan, and submits it days ahead of the 7th, rather than racing the deadline itself. Provident Fund and ESI contributions follow the same pattern. The EOR calculates and reconciles them against the payroll run, then submits them comfortably before the 15th. None of this requires the client company to track a single date. That is, functionally, what the EOR’s monthly fee is actually paying for.

A payroll operations manager who has run this cycle across hundreds of Indian employees would point out that the real risk rarely comes from the deadline itself. It comes from late or incomplete inputs earlier in the month. A salary revision arrives two days before cutoff. A new joiner’s documentation shows up incomplete. Those small delays cascade forward and put the statutory deadline at risk, through no fault of the payroll process itself. Good EOR providers build input deadlines deliberately earlier than they strictly need to. That buffer exists specifically to absorb last-minute disruption without it ever reaching the 7th or the 15th.

Reconciliation Is the Step Most Companies Never See

Depositing money by a deadline is only half the compliance obligation. The other half is reconciliation. That means matching what the company deducted, deposited, and reported across three separate systems: the payroll register, the statutory challans, and the quarterly TDS return filed through Form 24Q.

Discrepancies here are more common than most companies assume. They show up particularly when an employee’s salary changes mid-year, when the company pays a bonus outside the regular cycle, or when someone joins or exits partway through a month. A competent EOR reconciles these figures every quarter, before filing Form 24Q. That is far better than discovering a mismatch only when an employee complains that their Form 16 does not match what actually landed in their bank account.

Getting the Payroll Calendar Right Every Month

India’s payroll compliance calendar is unforgiving in a specific way. It does not care whether a company is a five-person startup or a five-thousand-person enterprise. It does not offer a grace period for a first-time mistake either. The 7th and the 15th arrive every single month, regardless of how the rest of the business is going.

For a global company without a payroll team already familiar with these dates, that rhythm is exactly what an EOR is built to absorb. The value is not simply processing a payslip once a month. It is running a calendar that catches problems days before a deadline rather than the day of one. For a broader look at how this fits into the wider EOR relationship, our guide to fifty questions on Employer of Record services in India covers the surrounding decisions. Our statutory benefits guide covers what each of these contributions actually funds for the employee.