← All customer stories
Illustrative scenarioAuto components · 2,400 employees · Pune

Meridian Gearworks

Payroll close: 4 days → 6 hours

with maker-checker approval and NEFT files generated in-app

The challenge

Month-end payroll took four days across spreadsheets and a legacy tool: statutory math checked by hand, approvals over email, and a bank file assembled manually — with no record of who changed what.

What changed

  • The statutory engine computes gross, PF, and TDS per employee on a job queue — 2,400 people in minutes, not days.
  • Maker ≠ checker is enforced by the platform: the admin who creates a run physically cannot approve it.
  • A month-on-month variance gate (net-pay delta, headcount, joiners/exits) must read 'in line' before money moves.
  • The NEFT bank file is generated in-app — download, upload to the bank, done.

6 hrs

payroll close, down from 4 days

100%

of runs dual-approved (enforced)

0

manual bank-file edits since go-live

Seen in the product

Approved — maker ≠ checker ✓, with the variance gate beside the audit trail
Approved — maker ≠ checker ✓, with the variance gate beside the audit trail
The NEFT file, generated in-app: 12 records, ready for the bank
The NEFT file, generated in-app: 12 records, ready for the bank

The engine computes PF and TDS per person, a second admin has to approve the run, and the bank file is one click. Our auditors asked fewer questions this year than ever.

VP, Finance Operations

Every claim above maps to a flow you can click through.

See Folkgrove running on your numbers.

A 30-minute walkthrough with a real payroll cycle and your org structure. No slides — the actual product.