HR software for finance teams
Payroll is a ledger problem wearing an HR costume. You need cost-centre allocation, clean reconciliation against the bank run, and outputs your books can absorb without re-keying.
What finance teams 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
- ✓ Cost-centre and department-wise salary reporting, every run
- ✓ Reconciliation-ready outputs that tie payslips to the bank transfer
- ✓ PF, ESI, PT and TDS applied per employee with the workings visible
- ✓ 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
Close with reconciliation built in
The bank-transfer sheet derives from the same computation as the payslips: the transfer total ties to the run line by line, so salary-account reconciliation is a check, not an investigation.
-
2
Cost the workforce like any other ledger
Cost-centre and department tags on every employee turn each run into a costed entry: salary spend by unit, project or location, exportable in the shape your books consume.
-
3
Provision what accrues
Gratuity accruals, leave liability and bonus provisions report from live records: the numbers your auditors ask for at year-end, available at any month-end.
-
4
Answer audits from the system
Statutory payment trails, contribution files and payslip histories export per period. The audit sampling that used to take a week of pulling files becomes a filtered export.
What this looks like in practice
Concretely: at quarter-close, a finance controller pulls salary cost by cost centre, reconciles the quarter's transfers against runs in one sheet, and hands the auditor contribution files with challan references attached. The leave-liability provision comes from live balances, not an estimate. What the quarter used to cost in assembly, it now costs in review. The following quarter, the same controller closes the books two days earlier, not through heroics, but because the payroll-shaped holes in the close checklist were the slowest items, and they no longer exist. Early closes compound: forecasting starts sooner, and the board pack stops waiting on salary numbers.
Built for you if
- ✓ You book salary costs by cost centre and reconcile the salary account monthly
- ✓ Provisions and statutory trails are your year-end pain
- ✓ Payroll numbers reach your books through re-keying today
Not the fit if
- ✕ You want the payroll engine to post journal entries directly into your ledger; it produces reconciliation-ready outputs; posting stays in your accounting system
- ✕ You want vendor payments here — supplier spend belongs to accounts payable
Mechanism deep-dives: the payroll engine · attendance & leave · self-service
Ninety days in
Ninety days in, the month-end has a different texture. The first close after go-live still runs your old checklist; you tie the transfer sheet to the run, the run to the registers, and file the evidence the way you always have, except each tie-out takes minutes because both sides come from one computation. By the second close, the checklist has shrunk: reconciliation items that used to be investigations are now checks that pass silently, and the cost-centre report that HR used to assemble for you arrives as an export you filtered yourself. The third close is when the year-end stops being frightening — provisions, contribution trails and payslip archives have been accumulating in audit-ready form all quarter, so the auditor's PBC list maps to exports rather than to archaeology. Finance teams tend to measure tools in reconciliation hours; the honest number here is that the hours move from building agreement between systems to confirming it. The residual work (judgment on provisions, treatment calls on edge cases) is the part of the close that actually needed a finance mind, which is a reasonable definition of the tool doing its job.
Where PeopleDeck stops, deliberately
The boundary is drawn where finance systems should draw it: PeopleDeck is the source of truth for what people were paid and why, and your ledger remains the source of truth for the books. Outputs are shaped to land cleanly (costed, tagged, period-stamped) but posting is your accounting system's job and approval hierarchies over spend remain yours. It prepares statutory files and never files them; challan payment happens in your banking, under your controls. And it will not forecast or accrue by estimate where a fact exists: liability numbers come from live balances and recorded structures, which is precisely what makes them defensible in front of an auditor.
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
Can salary costs map to our cost centres?
Yes: employees carry cost-centre tags, so every run produces department and cost-centre-wise salary reports your books can absorb directly.
How does reconciliation work after a run?
The run produces a bank-transfer sheet that ties to payslip totals line by line, so what left the account and what the payslips say never drift apart.
How is PeopleDeck priced?
You pay for the headcount you actually run, per month, in rupees. No feature sits behind a higher plan, and seasonal teams pay for the season rather than a licence sized to their peak.
Does PeopleDeck file PF and ESI returns?
It prepares, you file. Contributions are applied at current rates and the ECR and return files generate from each approved run, but filing authority remains with the establishment and its consultant.
Can outputs match our ledger structure?
Cost-centre tagging and export formats are configurable, so the run's outputs map to your chart of accounts without manual reshaping.
How do off-cycle payments appear?
As their own runs with their own trails — settlements and corrections stay visible and reconcilable instead of hiding inside a monthly blend.
Does it handle multiple pay entities under one group?
Yes, each entity runs under its own registrations with its own registers and files, while reporting can consolidate across them. Your books stay entity-clean; your view of the group stays whole.
Can we restrict who sees salary data?
Fully — role-scoped access means finance sees costs and registers without HR's employee files, and auditors see evidence without edit rights. Segregation of duties is a configuration, not a promise.
Your month, minus the spreadsheets.
Per employee, per month: attendance to upload-ready returns.
Start free