PayGrid
Custom payroll management software
Salary structures, statutory deductions and payslips, correct every month.
For organisations where payroll is not one salary structure but several - monthly staff, day-rate labour, piece-rate workers and contractors - and where attendance, advances and arrears all have to land in the same run. Built to compute from records rather than from a spreadsheet someone maintains.
Screens
What it looks like
4 screens from the working demo — the same data you will see if you open it.
The problem
Why this gets built
Payroll is the one system where a rounding error becomes a legal problem. It also has to be right on a deadline, every month, regardless of who is on leave.
Who it is for
Fit
Businesses of 20 to 2,000 staff who need payroll to be defensible, not just fast.
Capabilities
What the system does.
Salary structures
CTC breakup across basic, HRA and allowances, defined once and applied consistently.
Statutory compliance
PF, ESI, professional tax and TDS computed by rule, with the registers you need at filing time.
Approve & lock pay runs
A locked month cannot be silently edited. Corrections become adjustments with an audit trail.
Payslips
Generated, stored and distributable, with a persisted snapshot so a later rate change cannot rewrite history.
Arrears & adjustments
Mid-month joiners, revisions and carry-forwards handled explicitly rather than by manual override.
Exact arithmetic
Money held as fixed-point decimal throughout, because floating point in wages is a dispute waiting to happen.
See it running
PayGrid is a clickable demo — open the modules, browse the tables, see how the screens fit together.
Buying decision
Why off-the-shelf falls short here.
Payroll packages assume a workforce of salaried employees on a monthly cycle. Many businesses have that plus day-rate labour paid on attendance, plus piece-rate workers paid on output, plus contractors billed against a rate. Each has different statutory treatment, and only one of them fits the package.
So payroll is run in the package for staff and in Excel for everyone else, and the Excel one is the larger number. Advances tracked in a notebook are netted off by hand, arrears are recalculated from memory, and a locked pay period is a convention rather than a constraint - last month's figures can still change.
A custom build handles the mix in one run. Attendance and output feed the computation directly, advances are already ledgered against the person, statutory deductions apply per category, and approving a period locks it so history stops drifting.
Comparison
Packaged product vs a custom build.
The differences that decide it, for this sector specifically.
| Aspect | Packaged product | Custom build |
|---|---|---|
| Workforce types | Salaried employees | Monthly, day-rate, piece-rate and contract in one run, each with its own statutory treatment |
| Attendance link | Imported summary | Computed from the same attendance records the supervisor marked, with overtime rules applied |
| Advances | Tracked outside | Ledgered against the person and netted automatically, with the balance carried forward |
| Statutory | PF and ESI for staff | PF, ESI, PT and TDS by applicability, including workers who cross thresholds mid-year |
| Arrears | Manual recalculation | Recomputed against the affected periods with the difference shown before it is paid |
| Period control | A soft close | Approve and lock, after which a change is an auditable adjustment rather than an edit |
Integrations
What it connects to.
A system that cannot reach the tools already in use becomes another island. These are the connections this sector normally needs.
Attendance hardware
Biometric, RFID and phone-based marking as the input to the computation.
Accounting
One reviewed journal into Tally or Zoho Books, split by cost centre.
Banking
Bulk transfer files in your bank's format, with a reconciliation of what actually cleared.
Statutory portals
ECR, ESI and TDS return files produced in the format the portal accepts.
Payslip delivery
Payslips to email or WhatsApp, and a self-service view for staff who ask the same questions monthly.
How it runs
From first conversation to cutover.
Indicative for a build of this shape. The parallel run is not optional — nothing is retired until the numbers agree.
- 1 week
Discovery
We take your salary structures, statutory profile, overtime and advance rules, and one real month's payroll.
- 3-5 weeks
Core build
Structures, attendance linkage, statutory computation and the approve-and-lock cycle.
- 2 cycles
Parallel run
Two full months computed both ways and reconciled to the rupee before anything is retired.
- 1 week
Cutover
Opening advances and arrears loaded, bank files and payslip delivery switched on.
After rollout
What changes day to day.
- One run covers the whole workforce instead of a package for staff and a spreadsheet for everyone else.
- Advances are netted from a ledger rather than a notebook, so disputes have a record behind them.
- A closed period stays closed, which makes the year's figures reconcilable.
- Statutory files come out in the format the portal accepts, rather than being reshaped each month.
Described qualitatively on purpose. We do not publish percentage improvements we cannot attribute to a named client with their agreement.
Questions
Common questions.
Does it handle PF, ESI and TDS?
Yes. Statutory deductions are computed by rule and the supporting registers are produced at filing time.
Can a completed payroll month be edited?
No, and that is deliberate. Once a pay run is approved it locks, and corrections are recorded as adjustments with an audit trail rather than as silent edits.
How is rounding handled on salary calculations?
All money is held as fixed-point decimal and computed with an exact arithmetic library. Floating point is never used for wages, because rounding errors in salary become disputes.