Every Month, Someone Asks Why Their PF Was Deducted on ₹15,000 and Not Their Real Salary. Here’s the AI Workflow That Makes Payroll Compliance Faster — Without Cutting Corners.
Payroll compliance in India means juggling three different schemes, three different rule books, and three different filing deadlines — every single month. Here’s how AI for payroll processing and compliance can speed up the routine checks, calculations, and employee queries, while a CA still verifies the numbers by hand.
If you run payroll for an Indian company, you already know the drill. Provident Fund, or PF, covers retirement savings. Employee State Insurance, or ESI, covers medical and sickness benefits. Professional Tax, or PT, is a state-level tax that varies by state. Each one has its own wage limit, contribution rate, and filing deadline. Get one wrong, and you’re looking at interest, penalties, and an awkward call with an employee who wants to know why their payslip looks different this month.
This guide shows how I use AI for payroll processing and AI for payroll compliance — from PF and ESI coverage checks to payroll calculations, filing checklists, and employee questions. The goal isn’t to let AI make the final compliance decision; it’s to use AI as a practical payroll workflow that saves time while keeping human verification at the centre. It’s written for CA and HR teams running payroll for small or mid-sized Indian companies, not a payroll software vendor’s marketing page.
📑 Table of Contents
- PF coverage and the ₹15,000 figure are two different things: coverage decides who must join, ₹15,000 is the ceiling used to calculate the mandatory contribution once someone’s covered. ESI applies up to ₹21,000 gross (₹25,000 for employees with disabilities). Both figures are current as of 2026.
- The Code on Wages caps how much pay can sit in excluded allowances at 50% of total remuneration — if exclusions exceed that, the excess is added back into “wages” for PF and gratuity. This changes the PF calculation base for many companies, even though the 12% rate hasn’t moved.
- AI is genuinely useful for classification checks, filing checklists, and answering routine employee questions — never for the final compliance sign-off.
- Late PF payment can attract interest and damages under Section 14B of the EPF Act. These are not deadlines to treat casually.
PF, ESI, and PT Basics for Payroll Compliance
Before any AI payroll workflow makes sense, the underlying rules and numbers need to be right. Here’s the current picture for payroll compliance in India, as of 2026.
| Scheme | Wage ceiling | Contribution rate |
|---|---|---|
| PF (Provident Fund) | ₹15,000/month statutory contribution ceiling | 12% employee, 12% employer |
| ESI (Employee State Insurance) | ₹21,000/month gross (₹25,000 for employees with disabilities) | 0.75% employee, 3.25% employer |
| PT (Professional Tax) | Varies by state | Varies by state — some states don’t levy it at all |
One change worth knowing about: the Code on Wages, 2019 sets a single definition of “wages” — Basic pay and Dearness Allowance, plus retaining allowance where it applies. But the Code also lists specific items that don’t count as wages, including HRA, conveyance, certain allowances, employer PF/ESI contributions, statutory bonus, and similar items.
Here’s the part that catches companies out: those excluded items are subject to a 50% cap. If the specified exclusions exceed 50% of total remuneration, the excess is added back into “wages” for calculating PF, gratuity, and similar dues. If your company has a large allowance component, the PF calculation base may increase where those specified exclusions cross the threshold. Not because Basic+DA itself must literally equal 50%, but because the add-back mechanism can increase the effective wage figure. The same mechanism can also affect gratuity under the Payment of Gratuity Act, since gratuity is based on wages — worth flagging to clients even though gratuity itself isn’t a monthly filing.
Two more things are worth knowing before you build any AI payroll compliance workflow around these numbers. First, establishment-level coverage thresholds matter — PF generally applies to establishments covered under the EPF framework, including establishments with 20 or more employees, while ESI generally applies to covered establishments with 10 or more employees, subject to the applicable statutory rules. Second, ESI runs on two fixed six-month contribution periods: April to September, and October to March. If an employee’s wages cross the ₹21,000 ceiling partway through a contribution period, they generally remain covered until that period ends — not from the day of the raise. That’s the actual answer to one of the most common ESI payroll questions.
One more practical note: registration itself has gotten simpler. PF and ESI are no longer two separate applications — both can be registered through the Unified Shram Suvidha Portal, which provides a common registration process for the two schemes.
This guide focuses specifically on PF, ESI, and PT. TDS on salary under Section 192 is a related but separate compliance item, with its own rules and filing calendar — worth knowing it exists, but not covered in depth here.
Pro tip
There’s also an active Supreme Court direction, from January 2026, asking the government to decide on raising the PF wage ceiling above ₹15,000. As of writing, the ceiling hasn’t changed — but check the EPFO website before relying on the current PF contribution ceiling.
The Four-Step Monthly Workflow
With the rules in mind, here’s the actual monthly workflow — four steps: confirm who’s covered, get the calculations right, build the filing checklist, and answer whatever questions come up afterward. Each one has a manual process, a place AI genuinely helps, and a check I never skip.
Step 1 — Check who’s covered
Before a single number is calculated, you need to know which employees actually fall under PF and ESI this month — coverage can change every time someone joins or gets a raise.
Every new joiner, and every employee who gets a raise, needs to be re-checked against the PF and ESI wage ceilings. On a payroll of even 50 people, this adds up to a real chunk of time every month.
Where AI entersI paste a list of employees with their gross wage and Basic+DA split, and ask AI to flag who’s newly covered, newly excluded, or unchanged.
Exact prompt I useCHECK
REQ’D
What I still check by hand
Every “Changed This Month” flag gets a manual double-check before it goes into payroll. A wrong PF or ESI status doesn’t just affect one payslip — it can mean a mid-year correction that’s painful for everyone involved.
Step 2 — Get the calculations right
With coverage confirmed, the next job is making sure the actual PF, ESI, and PT figures are correct. This is where the Code on Wages’ exclusion rule most often trips people up.
Once coverage is confirmed, someone still has to work out the actual PF, ESI, and PT amounts. Under the Code on Wages’ exclusion-cap rule, the wage figure used for PF may need recalculating first — not just read off the payslip’s Basic+DA line.
Where AI entersI ask AI to draft the calculation logic as a check against what payroll software has already produced — not as the source of truth, but as a second pair of eyes.
Exact prompt I useStep 3 — Build the monthly filing checklist
Correct numbers don’t help if they’re filed late — the last piece of the cycle is turning this month’s compliance tasks into a dated checklist nobody has to remember from memory.
PF and ESI both have to be filed and paid by the 15th of the following month. Missing that date brings interest and penalties — for PF, that’s up to 12% interest per year plus damages of up to 25% under Section 14B of the EPF Act.
Where AI entersI ask AI to turn a plain list of this month’s compliance tasks into a dated checklist, ready to drop into a shared calendar.
Exact prompt I useStep 4 — Answer employee questions faster
The compliance work is done by this point — the last step is communication, since a change in someone’s PF or ESI status almost always comes with a question attached.
“Why was my PF only deducted on ₹15,000?” “Am I still covered under ESI after my raise?” These questions come up every month, and answering them clearly takes more time than the question itself deserves.
Where AI entersOnce I’ve confirmed the actual figures for an employee, I ask AI to turn the answer into a short, plain-English message I can send directly.
Exact prompt I use
Where this goes wrong
Two mistakes come up again and again in AI-assisted payroll work. Trusting AI’s maths without a manual check. AI is good at applying a rule you give it. It’s not a calculator you should trust blindly — especially with the Code on Wages’ exclusion-cap rule still tripping up payroll software that hasn’t been updated for the add-back calculation. Forgetting that PT rules are state-specific. AI will happily give you a generic PT answer if you don’t specify the state — always confirm the exact state’s slab and due date yourself.
AI Can Make Payroll Compliance Faster. It Still Can’t Take Responsibility for the Final Number.
That’s really the point of using AI for payroll processing and compliance. Let it handle the repetitive work — checking employee classifications, cross-checking calculations, building filing checklists, and drafting replies to routine questions. But when it comes to PF, ESI, and PT, I still want a human to check the rule, verify the number, and take responsibility for the final filing. The rules can change, and the PF ceiling is a good reminder: AI can make the work faster, but staying current with the actual rules is still part of the job.
