What India Payroll Deadlines Apply to Australian Companies?
- Saransh Garg

- 3 days ago
- 9 min read

If you employ even one person in India, your Provident Fund contribution for that employee is due by the 15th of the following month, every month, with no grace period on the EPFO portal. Miss it and interest starts from the 16th, not from whenever your finance team notices. This is the single deadline that trips up more Australian finance teams than any other, because it doesn't map to anything in the Australian compliance calendar. Knowing exactly which India payroll deadlines apply to Australian companies, and how they differ from BAS cycles, STP reporting, and super guarantee dates back home, is what separates a clean India operation from a growing file of penalty notices.
We manage payroll and compliance calendars for Australian companies hiring in India, and one pattern repeats constantly. The technical setup, registering for PF, ESI, and TDS, rarely goes wrong. What goes wrong is the calendar. Australian teams assume India payroll runs quarterly because that's how BAS and super guarantee reporting largely work at home. India payroll runs monthly, on statute, with almost no tolerance for delay.
Why Do India's Payroll Deadlines Differ So Much From Australia's Compliance Cycle?
Australian payroll compliance is built around quarterly and event based triggers, BAS lodgement, quarterly super payments, and Single Touch Payroll reporting that's continuous but forgiving of small timing slips. India's system is monthly, law driven, and largely intolerant of delay, regardless of how small the India team is.
This catches Australian companies off guard most often when they're scaling engineering or product teams in India's tech hubs. Hiring by Australian firms into Bengaluru, Pune, and Hyderabad has grown steadily as more companies look to build cost efficient, high quality engineering capacity without setting up a full Indian legal entity first. That growth has outpaced how familiar most Australian finance teams actually are with India's statutory payroll structure.
The core issue is that India payroll isn't one deadline, it's a stack of five to seven separate statutory obligations, each with its own portal and penalty structure, running independently every month. An Australian CFO used to one BAS filing covering GST, PAYG, and FBT together isn't prepared for a system where Provident Fund, ESI, Professional Tax, and TDS are four separate filings on four separate dates, sometimes across four different state portals.
What Are the Monthly and Annual India Payroll Deadlines Applying to Australian Companies?
This is the section worth saving. It covers every recurring statutory obligation that applies once you have staff on an Indian payroll, whether through your own entity, a branch office, or an Employer of Record (EOR) arrangement.
Obligation | Governing Law | Frequency | Due Date | Penalty for Delay |
Provident Fund (PF) deposit | EPF and Miscellaneous Provisions Act, 1952 | Monthly | 15th of the following month | Interest at 12% p.a. plus damages up to 25% under Section 14B |
ESI contribution deposit | Employees' State Insurance Act, 1948 | Monthly | 15th of the following month | Interest at 12% p.a., repeated defaults can trigger prosecution |
TDS on salaries deposit | Income Tax Act, 1961 | Monthly | 7th of the following month (30 April for March) | Interest under Section 201(1A) |
TDS quarterly return (Form 24Q) | Income Tax Act, 1961 | Quarterly | 31 July, 31 October, 31 January, 31 May | Late fee of ₹200 per day under Section 234E |
Professional Tax | State specific Acts (Karnataka, Maharashtra, West Bengal, etc.) | Monthly or half yearly, state dependent | Commonly the 20th of the month | State specific interest and penalties |
Form 16 issuance to employees | Income Tax Act, 1961 | Annual | 15 June after financial year end (31 March) | Penalty of ₹100 per day under Section 272A(2)(g) |
ESI half yearly return | Employees' State Insurance Act, 1948 | Half yearly | 11 May and 11 November | Compliance flag on the employer's ESI account |
Gratuity payment | Payment of Gratuity Act, 1972 | Event based, within 30 days of exit after 5 years' service | On exit | Interest liability on delayed payment |
Bonus payment | Payment of Bonus Act, 1965 | Annual | Within 8 months of the accounting year close | Legal claim risk with interest |
Three things stand out for an Australian finance controller reading this table.
None of these deadlines shift based on company size, a two person India team carries the same monthly PF and TDS obligations as a two hundred person one. Professional Tax is state legislation, so hiring across Bengaluru and Mumbai at once means managing two different regimes and due dates in a single payroll run.
And the 15th of the month PF deadline and the 7th of the month TDS deadline both sit inside the same short window, which is exactly where slower, batch based Australian approval workflows tend to create the delay that triggers a penalty.
How Do Contract Hiring and Full Time Hiring Change These India Payroll Deadlines?
This is where a lot of confusion starts. If you're using contract hiring through a staffing partner, statutory deposits are usually the partner's legal responsibility, though your invoice funding timeline still has to support their deadline, not yours. If you're hiring full time employees, whether under your own Indian entity or through an EOR, PF, ESI, TDS, gratuity, and bonus obligations all apply directly and continuously for as long as that person is employed.
Contract engagements through a registered staffing or EOR partner tend to be faster to start and lighter on your internal compliance load, since the partner already carries the registrations and files on schedule. Full time hiring through your own entity gives you more direct control over the employment relationship but means your finance team owns every deadline in the table above, with no partner absorbing the operational risk if a date slips.
Most Australian companies we work with start with contract or EOR hiring to test India as a market, then convert to a subsidiary and full time hiring once headcount justifies the fixed compliance overhead.
What Mistakes Do Australian Companies Make With India Payroll Compliance?
The most common mistake is assuming that using an EOR removes your exposure entirely. It only removes half of it. Your EOR partner processes and files on your behalf, but the obligation to fund those payments in time still sits with you. If your accounts payable process delays releasing funds past your EOR's internal cutoff, usually the 5th to 8th of the month to leave room for the 15th statutory deadline, the penalty still lands, your EOR partner just absorbs the operational headache of explaining it.
We saw this play out with an Australian fintech client running twelve engineers in Pune through an EOR structure. Their finance team approved payroll on the 20th of each month, timed to their Australian pay run, five days after India's PF and ESI deadline had already passed. Across three consecutive months, PF deposits went in nine to eleven days late, and EPFO's automated interest quietly added around ₹34,000 in cumulative interest and damages before anyone checked the portal, because the penalty doesn't reject a payment, it just sits as a growing balance nobody was watching weekly.
A fourth late month would have pushed them into a higher damages bracket under Section 14B. We separated India statutory payments from their general approval batch, moved the cutoff to the 10th, and added a standalone reminder for their Melbourne finance lead five days ahead of every deadline. No late deposits since. AnjuSmriti Global builds this kind of standalone calendar for every Australian client before their first payroll run, not after the first penalty notice.
How Much Does India Payroll Compliance Actually Cost an Australian Company?
Statutory employer contributions are calculated on basic salary, not total CTC, a distinction Australian teams used to Australia's flat superannuation rate on ordinary earnings often miss.
Seniority | Annual CTC (₹) | Approx. AUD Equivalent | Basic Salary (40% of CTC) | PF Employer Contribution (12%) | Gratuity Provisioning (4.81%) |
Mid level | ₹14,00,000 | ~AUD 25,000 | ₹5,60,000 | ₹67,200 per year | ₹26,936 per year |
Senior | ₹28,00,000 | ~AUD 50,000 | ₹11,20,000 | ₹1,34,400 per year | ₹53,872 per year |
Lead or Architect | ₹45,00,000 | ~AUD 80,400 | ₹18,00,000 | ₹2,16,000 per year | ₹86,580 per year |
ESI only applies where gross monthly wages sit at or below ₹21,000, which excludes most mid to senior tech salaries, so it's worth removing from your budget entirely for those roles rather than over-provisioning for it.
On top of statutory contributions, an EOR service fee typically runs AUD 350 to AUD 650 per employee per month for Australian clients, covering payroll processing, statutory filing, and ongoing compliance monitoring across every deadline above.
Compared with the cost of maintaining a subsidiary purely for compliance, company secretary retainer, statutory audit, ROC filings, most Australian companies under twenty five India based staff find the EOR route significantly cheaper on total cost of ownership. Clients who move from manual tracking to a structured payroll process usually redirect the recovered finance hours into faster hiring rather than compliance firefighting.
Conclusion
Compliance management in India is shifting toward cloud based, AI assisted platforms that flag upcoming statutory deadlines automatically, reconcile PF and ESI filings in real time, and reduce the manual tracking that caused the Pune scenario above. More Australian companies are also using this shift to set up formal GCC setups in India rather than running lean remote teams indefinitely, since a Global Capability Center brings payroll, compliance, and talent strategy under one structured operation instead of managing them piecemeal through multiple vendors.
The four new Labour Codes, including the Code on Wages, are being rolled out in stages across states and are expected to change how "wages" are defined for PF and gratuity calculation, likely increasing the mandatory basic salary component for many employers. Companies currently running lean basic salary structures to minimise PF outlay should expect that gap to narrow as rollout completes nationally.
If you're setting up or reviewing an India payroll process for your Australian company, we can review your current calendar and flag exposure before it becomes a penalty: Talk to our team.
Interesting Reads:
FAQs
1.Do these India payroll deadlines apply to Australian companies using an EOR instead of a subsidiary?
Yes, indirectly. Your EOR provider files and processes on schedule, but you still need to fund payments before their internal cutoff, usually the 5th to 8th of the month, so they can meet the 15th statutory PF and ESI deadline. If your fund transfer is late, the penalty still applies, even though the EOR handles the filing itself.
2.What happens if PF contributions are late for just one month?
Interest accrues at 12% per annum from the day after the 15th deadline under Section 7Q, plus damages starting around 5% per annum under Section 14B for short delays. A single late month is recoverable, but repeated defaults push you into higher damages brackets and closer regulatory scrutiny of your broader compliance history.
3.Does Professional Tax apply the same way across every Indian state?
No. Professional Tax is state legislation, not central law, so due dates, rates, and even applicability vary by state. Karnataka, Maharashtra, and West Bengal each run separate systems. An Australian company hiring across multiple states needs separate registrations and calendars per state rather than one uniform national deadline.
4.How does India's financial year affect our payroll compliance calendar?
India's statutory year runs 1 April to 31 March, six months offset from Australia's 1 July to 30 June year. Form 16 issuance, annual PF reconciliation, and the final TDS quarterly return all cluster around this period, which has no equivalent trigger in an Australian company's own fiscal calendar and is easy to miss without a standalone India calendar.
5.Is gratuity a monthly payroll cost or only relevant when someone leaves?
Gratuity itself is only paid out within 30 days of an eligible employee's exit after five years of continuous service. Prudent employers provision for it monthly, around 4.81% of basic salary, as an accruing liability, so it's reflected in India cost projections from day one rather than appearing as a surprise cost years later.
6.Can contract hiring in India reduce our exposure to these payroll deadlines?
Yes, largely. Contract engagements through a staffing or EOR partner shift most statutory filing responsibility to that partner, since they hold the registrations. Your company still needs to fund invoices on time to support their internal deadlines, but the direct legal exposure for PF, ESI, and TDS filings sits with the partner, not your Australian entity.
7.Do PF and ESI apply to every salary level, or only lower income employees?
PF applies broadly regardless of salary level once an employee is enrolled. ESI, however, only applies where gross monthly wages sit at or below ₹21,000, which typically excludes mid to senior tech roles. Many Australian companies over-budget for ESI on higher salaried India hires when it doesn't actually apply.
8.How far ahead should we build our India payroll compliance calendar before hiring?
Ideally at least one full payroll cycle before your first Indian employee's start date. Building the calendar and testing the approval workflow in advance is far less disruptive than retrofitting one after a missed deadline, which is the most common reason Australian companies come to us mid year rather than at the start of their India expansion.
.png)
Comments