Customer stories
Six years of payroll, before it was a product
Segnol was built inside a group of manufacturing, agro and services businesses, and every one of them still pays its people through it. These are those deployments — the same payroll we run ourselves every month.
About these stories. These are Dinjan group companies — our own businesses, not third-party customers. We publish them because we can show the detail a customer reference cannot: the actual pay rules, the migration, and the numbers before and after.
Dinjan Spinning Mills
Textile & spinning · Rajkot · 412 peopleThe challenge
Piece rate by the metre, three shifts and contractor PF under separate codes — the hardest payroll in the group, and the reason Segnol exists.
Tally held the books, Excel held the wages and a paper khata held the advances. One wrong lookup formula paid a weaver twice and missed a fitter entirely. Attendance was reviewed for every employee by hand, and a payroll cycle took seven to nine working days.
The rollout
•Week 1 — mapped every pay rule with the accountant: loom-wise piece rates, shift premiums, advances and deductions.•Week 2 — migrated masters: employees, UAN and ESIC numbers, bank details and opening advance balances, verified against source.•Week 3 — ran the month in parallel with the existing process until every difference was explained.•Week 4 — went live. Biometric attendance synced at the gate; the payroll engine took metres woven rather than hours sat.
The result
| Before Segnol | With Segnol |
|---|
| Payroll cycle | 7–9 working days | 2 days |
| Attendance review | Every employee, by hand | Exceptions only — 23 of 412 |
| PF / ESI filing | Re-typed into the portal | ECR & challans generated |
| Payslip delivery | Printed, queued at the office | WhatsApp, same day |
Dinjan Agro Foods
Agro & food processing · Anand · 168 peopleThe challenge
Headcount doubles at harvest and halves again by January. Weekly wage cycles for the harvest gangs have to run beside monthly staff on the same set of books.
Advances move with the festival and mandi calendar rather than the payroll calendar, and ESI has to be mapped to the right rural dispensary for each worker.
The rollout
•Week 1 — mapped the weekly wage cycle for harvest gangs alongside the monthly staff run.•Week 2 — migrated masters and opening advance balances, including the festival and mandi advance ledger.•Week 3 — parallel run across both cycles, through a month where headcount was still climbing.•Week 4 — went live with ESI rural dispensary mapping in place.
The result
| Before Segnol | With Segnol |
|---|
| Wage cycles | Two calendars, two systems | Weekly and monthly in one run |
| Seasonal intake | Re-keyed each season | Onboarded the same morning |
| Advance ledger | Paper khata | Recovered automatically at payout |
| Payslip delivery | Printed, queued at the office | WhatsApp, same day |
Dinjan Infotech
IT & services · Ahmedabad · 54 peopleThe challenge
Monthly CTC, the old and new TDS regimes elected per employee, flexi allowances and LTA declarations, and Form 16 at year end.
This is the part most payroll software already gets right. The problem was that it sat in a different system from the factories, so the group never had one payroll run.
The rollout
•Week 1 — mapped CTC structures, flexi allowances and the per-employee regime election.•Week 2 — migrated masters and year-to-date tax positions.•Week 3 — parallel run against the existing statement, reconciled to the rupee.•Week 4 — went live inside the same run as the factories.
The result
| Before Segnol | With Segnol |
|---|
| Regime handling | Tracked in a side sheet | Old vs new, per employee |
| Form 16 | Assembled at year end | Generated from the same run |
| Professional tax | Checked by hand | Ahmedabad municipal slab applied |
| Group payroll | A separate system | One run with the factories |
Across the group
All fourteen companies moved off spreadsheets by 2023, with per-company PF codes, PT slabs and pay rules treated as first-class rather than exceptions. There have been no missed PF deadlines since, and more than 38,400 payslips have been generated — six years of our own payroll as the test suite.
See how a rollout runs · Read the full story