PeopleDeck Databus PeopleDeck
Databus
PeopleDeck
Features Solutions Use cases Tools Compare Guides Pricing
All products
Education
Finance & Operations
FinDeckAccounting & analytics Soon StockWiseInventory & stores Soon TaskDeckTasks & workflows Soon PeopleDeckHRMS & payroll
Sales & Support
LeadDeckSales & admissions CRM Soon TicketDeckSupport service desk Soon ConnectlyCommunity & messaging LiveLoopVideo meetings
Property & Mobility
AI
AskWiseAI assistant Soon
Blog

HR software for payroll administrators

You are judged on one thing: the run is right, on time, every month. Arrears, mid-cycle revisions, ECR files, challans, Form 16 — PeopleDeck treats these as first-class operations, not edge cases.

What payroll administrators get from PeopleDeck

One system for attendance, leave, onboarding and payroll, with PF, ESI, professional tax and TDS applied to every payslip and upload-ready return files generated from the run. Priced per employee, per month, so it fits before you have scale.

Built around your month

  • ✓ Arrears and salary revisions computed with effect-dates, not manual math
  • ✓ ECR, challan and Form 16 files generated from the run itself
  • ✓ Run-level checks that catch missing attendance before payday does
  • ✓ PF, ESI, PT and TDS applied to every payslip, with upload-ready files, never filed on your behalf
  • ✓ Employee self-service for payslips, Form 16 data and leave balances

Your month, week by week

  1. 1

    Inputs arrive reconciled

    Attendance, approved OT and incentive inputs land where the run reads them; your month starts at review, not at collection.

  2. 2

    Exceptions before payday

    The preview flags variances (unexplained deltas, missing days, new bank details) while there is still time to fix causes rather than apologise for effects.

  3. 3

    Arrears and revisions, computed

    Effect-dated changes compute their own arrears with month-wise workings on the payslip. The hardest arithmetic in your month becomes the most documented.

  4. 4

    Files, not file-building

    ECR, ESI, challan summaries, 24Q accumulation, generated from the approved run. Your deadline pressure shifts from building files to reviewing them.

What this looks like in practice

Concretely: an administrator running 600 employees processes a month containing a grid revision (backdated to the 1st), 14 joiners, 9 exits and one bonus cycle. Revision arrears compute with workings shown; joiners pro-rate; exits settle off-cycle; the bonus enters as an approved input with TDS reprojected. The 15th arrives with files generated and the administrator having reviewed, not rebuilt, the month. The month closes with one artifact the administrator never had before: a variance report showing every payslip that changed, why, and who approved the cause. When the CFO queries the payroll cost jump, the answer takes one filter (the revision, the joiners, the bonus) instead of a weekend of pivot tables.

Built for you if

  • ✓ You personally own runs for 100+ employees
  • ✓ Arrears, revisions and off-cycle runs are your recurring pain
  • ✓ The 15th deadline pressure is file-building, not review

Not the fit if

  • ✕ You want the system to file on the portals — generation is the product; filing stays with the establishment
  • ✕ You need multi-company bureau processing; that is the outsourcing solution's territory

Mechanism deep-dives: the payroll engine · attendance & leave · self-service

Ninety days in

Ninety days in, the 15th has changed character. Your first cycle on the system runs in parallel with your old process — double work, by design, because the reconciliation between the two is what earns trust, and the variances it surfaces are usually your old sheet's rounding habits rather than the engine's errors. The second cycle is when the input chase dies: sites and supervisors have learned that their approvals feed the run directly, so what used to arrive as email attachments on the 8th now sits reconciled in the system by the 5th. By the third cycle you are working exceptions-first: the preview's variance flags are your worklist, and the ninety-five percent of payslips that changed exactly as expected no longer consume attention. The professional shift is real: you stop being the person who assembles payroll and become the person who certifies it, which is also the version of the role that survives an audit gracefully. The role's arc across those ninety days is from operator to certifier, same accountability, radically better evidence, and a month that ends on the 15th instead of consuming it. One habit is worth keeping from the old world: read the variance report before the preview, not after; it turns the approval sitting into confirmation of what you already understood, and it is the fastest way to catch an input that was approved but wrong, which no engine can catch for you.

Where PeopleDeck stops, deliberately

The engine's limits are drawn where an administrator would draw them. It computes anything you can define, but it will not invent policy: ambiguous cases surface as exceptions for your call, not silent defaults, because a computed guess is worse than a flagged question. Approved runs lock; history is never editable in place, and corrections travel as documented off-cycle adjustments, which protects you personally when numbers are questioned. And the files it builds (ECR, ESI, challan summaries, quarterly TDS accumulation) go out under your establishment's authority, not the system's: generation is automated, accountability stays human, and your signature keeps meaning something.

A different seat at the table?

Running a school or college? Staff payroll belongs inside your ERP: SchoolDeck staff payroll or CampusAlly payroll.

Frequently asked questions

How are arrears with back-dates handled?

Set the revision with its effective date: the engine computes arrears across the affected months and shows the working on the payslip.

Which statutory files does it generate?

Upload-ready ECR for PF, ESI contribution files, challan-ready summaries and Form 16 data, generated from the run, never assembled by hand.

How is PeopleDeck priced?

One rate per employee per month, in rupees, covering the whole platform. Headcount is the only variable in the bill; there are no bundles, tiers or per-site charges to decode.

Does PeopleDeck file PF and ESI returns?

The system stops at generation: applied contributions on payslips, portal-format ECR and return files from the run. Filing is deliberately left with the employer and consultant, where the law puts it.

How are bulk inputs handled?

Structured imports with validation (incentive sheets, OT approvals, new-joiner batches) rejected rows reported before anything computes, so bad data never reaches a payslip.

Can I lock a run after approval?

Approved runs are immutable; corrections happen as documented off-cycle adjustments, which is exactly the audit posture you want.

What happens to my existing payroll history?

Prior periods import as opening balances and reference records, enough for continuity of gratuity, leave accrual and TDS projection, so mid-year migration doesn't orphan the year's arithmetic.

Does it support multiple pay cycles or groups?

Yes, separate pay groups with their own calendars, cut-offs and structures can run under one establishment, so staff and worker payrolls, or monthly and fortnightly cycles, stop needing parallel processes.

Your month, minus the spreadsheets.

Per employee, per month: attendance to upload-ready returns.

Start free