Back to Blog
Product Launch 10 min read Nov 1, 2025

Launch: The Statutory Payments Agent - Automating India's Compliance Payment Lifecycle

Payroll isn't complete until the government gets paid.

Every month, organizations process payroll successfully. Employees get paid. Everyone celebrates.

Then comes the second wave: statutory payments to government portals.

PF due on the 15th. ESI due on the 15th. PT due on the 15th. TDS due on the 7th. GST due on the 20th.

Different amounts. Different calculations. Different portals. Different deadlines.

This is where payroll goes to die.

The Monthly Panic Cycle

Day 1 (Payroll): Payroll runs. Employees paid. Deductions calculated. Victory declared.

Days 2-14 (The Scramble):

  • "What's the total PF for this month?"
  • Excel sheets multiply
  • Manual calculations start
  • Errors creep in
  • Numbers don't match
  • Blame gets assigned

Day 15 (Deadline):

  • 5:30 PM: "The PF portal is down!"
  • 6:00 PM: "Our amount doesn't match their calculation!"
  • 11:59 PM: Filed. Maybe.

This isn't a process. It's monthly panic institutionalized.

Hard Truths We Learned

1. Statutory Payments Are Aggregate Operations

This sounds obvious. It isn't.

PF Payment calculation:

  • Employee PF = Sum of all employee deductions
  • Employer PF = Sum of all employer contributions
  • Total = Employee + Employer combined

100 employees at Rs. 1,800 each: Rs. 1,80,000

Plus employer matching: Rs. 1,80,000

Total PF payment: Rs. 3,60,000

We've seen systems that report Rs. 1,80,000 because they forgot the employer portion. That's a 50% error in statutory payment.

2. Due Dates Vary by Payment Type

  • PF: 15th of following month
  • ESI: 15th of following month
  • PT: 15th of following month (most states)
  • TDS: 7th of following month
  • GST: 20th of following month

One payroll run generates five payments with three different due dates.

Miss TDS on the 7th while focusing on PF for the 15th? Penalty.

3. Payment Status is Multi-Stage

A payment isn't "done" when you click submit. The lifecycle:

  1. Pending: Created, awaiting approval
  2. Approved: Finance head approved, ready for filing
  3. Paid: Submitted to government portal
  4. Filed: Acknowledgment received, reference number stored

Payment marked "Paid" but missing filing reference? Compliance incomplete. The auditor will find it.

4. ESI is Conditional

ESI only applies when gross salary is below Rs. 21,000.

100 employees:

  • 60 earn below Rs. 21,000 - ESI applicable
  • 40 earn above Rs. 21,000 - No ESI

ESI payment should aggregate from 60 employees, not 100.

Systems that don't handle this correctly either overpay (compliance violation) or underpay (penalty).

5. Professional Tax is State-Specific Chaos

Same 100 employees, different states:

  • Maharashtra: 3 slabs, max Rs. 200/month, total Rs. 15,250
  • Tamil Nadu: 5 slabs, different thresholds, different total
  • Karnataka: 2 slabs, flat Rs. 200 for most, different total

Same payroll data. Three different PT payments based on employee locations.

The Integration: One-Click Compliance

We built the Statutory Payments Agent to eliminate the scramble.

Workflow:

  1. Process payroll: POST /api/payroll/process
  2. Click one button: "Generate Statutory Payments"
  3. Three payments created automatically (PF, ESI, PT)
  4. Approve, pay, file, track

What this eliminates:

  • Manual aggregation (error-prone)
  • Excel calculations (version confusion)
  • Due date lookups (penalty risk)
  • Duplicate data entry (inefficiency)

One payroll run. Three compliance-ready payments. Automatically.

The Results

All statutory payment types tested. All edge cases covered. All calculations verified against official government documentation.

100% pass rate. Production-ready.

Payroll isn't complete until the government gets paid. With the Statutory Payments Agent, that happens automatically.

No more monthly panic. No more deadline scrambles. No more Excel reconciliation.

Ready to automate your statutory compliance payments? Let's talk.