HR software for security agencies
Site and guard rosters, beat-shift attendance, PF and ESI for deployed staff, and principal-employer compliance records.
What does HR software for security agencies do?
It runs attendance, leave and payroll for security agencies — applying PF, ESI and TDS to every payslip and generating upload-ready return files, while handling what makes this industry different: guards deployed on client sites. PeopleDeck prices this per employee, per month.
Guards deployed on client sites
Guards work your clients' gates, not your office — beat shifts, site rosters and reliever management across the city. Their PF and ESI stay your responsibility, and clients will ask you to prove it.
A security agency's payroll problem is that the workplace belongs to someone else. Guards report to client gates across the city; shift discipline is enforced by site supervisors you meet weekly; a reliever system patches absences at dawn; and the client (who sees your guards every day) periodically demands proof that the people at their gate are paid, insured and contributed for. That last demand is existential: agencies lose contracts over compliance doubt more often than over service quality. PeopleDeck runs deployment-shaped payroll (site rosters, beat patterns, reliever tracking) and turns every month into a client-ready evidence pack: who served their site, what they were paid, and the PF and ESI trail behind it. The real test of agency payroll is the month a major client doubles their posts mid-cycle: rosters extend, relievers absorb the gap, and both the guards' wages and the client's first invoice come out of the same clean records.
How PeopleDeck runs it
- ✓ Site and beat rosters with reliever handling
- ✓ Deployment records that evidence PF and ESI for every guard, per client site
- ✓ PF, ESI, professional tax and TDS applied to every payslip — upload-ready return files, never filed on your behalf
- ✓ Self-service payslips, Form 16 data and leave balances for every employee
A month in security-agency payroll
-
1
Deployment rosters per client site
Each site's requirement (day guards, night guards, supervisors) publishes as a roster with beat timings. Guards punch at the site (mobile or device), and the roster-versus-actual gap is visible to control rooms the same day.
-
2
Relievers and rotations tracked
The reliever who covered Gate 3 on Tuesday is recorded at that site with that shift's terms. Weekly offs rotate per site rules, and double shifts (one guard covering two posts) carry their premium into the computation automatically.
-
3
Site months close for billing and wages together
Each site's attendance closes once and feeds two outputs: the guard's wage computation and the client's billing annexure. One record serving both is what keeps invoice disputes short.
-
4
The run pays and proves
Wages compute with night and double-shift premiums; PF and ESI apply on qualifying wages; payslips reach guards on their phones; and per-site compliance summaries (contribution evidence aligned to deployed headcount) generate for whichever client asks this month.
A worked example
A guard on ₹16,000 monthly deployed at a corporate site works 26 days including eight nights at a ₹100 night premium and two double shifts at ₹550 each. Gross computes to ₹17,900 — ESI applies (under ₹21,000) at 0.75% employee and 3.25% employer, PF on basic per structure. The payslip shows base, nights, doubles as separate lines. The client's quarterly vendor audit then asks for proof of compliance for deployed staff: the site's evidence pack exports: guards deployed with dates, wage register extract, ECR and ESI contribution references for those employees. The audit that used to consume the branch manager's week reduces to a filtered export, and the contract renewal stops hinging on a scramble.
At branch level, the same records answer the commercial question: each client site's month closes with deployed-days against billed-days visible, so the invoice annexure and the wage register derive from one source. Disputes shrink to specific dates on specific posts (arguable in minutes with the punch record open) instead of month-long standoffs over totals.
Figures are illustrative, for mechanism only; your structures and rates will differ.
Key terms in security-agency payroll
Deployment roster
The client-site-wise plan of posts, shifts and guards. It is simultaneously the operations tool, the attendance baseline and the billing basis: three documents agencies usually maintain separately, disagreeing.
Reliever
The floating guard covering absences across sites. Reliever pay follows where they actually stood, which requires site-stamped attendance: the detail ad-hoc registers lose first.
Principal-employer demand
Clients engaging your guards can be held liable if your PF and ESI lapse, so they demand evidence. Serving it fast is a commercial weapon, not just compliance hygiene.
Is PeopleDeck the right fit?
Built for you if
- ✓ Guards deploy across client sites, not your premises
- ✓ Relievers and rotations are daily operational reality
- ✓ Clients demand compliance evidence for deployed staff
- ✓ Billing disputes trace to attendance disagreements
- ✓ Night and double-shift premiums are part of the wage structure
Not the fit if
- ✕ You want guard-tour or patrol-monitoring software. This is workforce and wages
- ✕ You supply manpower whose payroll the client runs; then the client needs this, not you
Mechanism deep-dives: the payroll engine · attendance & leave · statutory compliance
Switching without a bad payday
Agencies switch branch by branch, because operations cannot stop. The working sequence: guard master first (with sites, posts and wage structures) then deployment rosters for the branch's client sites, then one wage cycle in parallel with the existing register. The parallel cycle surfaces the usual truths: relievers paid at the wrong site's rate, night premiums applied from memory, ESI missed on wage components that qualified. Each is a rule fixed once, not a recurring correction.
From cutover, evidence accumulates automatically — site-wise deployment, wage registers, contribution references, which changes the client conversation within a quarter: renewal meetings that used to litigate compliance turn into a handed-over export. Branches that follow migrate onto proven templates, and the head office gains what it never had: one live view of every gate the agency guards. Branch managers report one unexpected effect: guard attrition drops when payslips become readable, because the commonest reason guards quit agencies is pay they cannot verify.
One more habit that pays: record each site's agreed billing rate against the site itself at setup. When rates revise at renewal, the effect-dated change keeps old invoices defensible and new ones correct: the same discipline the wage side already follows.
Not your industry?
Running a school or college? Staff payroll belongs inside your ERP: SchoolDeck staff payroll or CampusAlly payroll.
Related industries
Frequently asked questions
What does HR software for security agencies include?
Attendance and rosters, leave, onboarding to full-and-final, and payroll with PF, ESI and TDS applied to every payslip, plus guards deployed on client sites handled natively. Employees get self-service payslips.
Clients ask for compliance proof — can it help?
Yes — site-wise wage and contribution records are exportable per client, which is exactly what principal employers ask their security agency to produce.
How is PeopleDeck priced?
Per employee per month, in rupees. You pay for the headcount you run, no module bundles, no per-site fees.
Does PeopleDeck file PF and ESI returns?
No; it applies PF, ESI, professional tax and TDS and generates upload-ready ECR and return files. Filing stays with you or your consultant.
Can guards punch in without a smartphone?
Yes — site devices, supervisor-marked musters or shared kiosks all capture attendance; the guard's record does not depend on the guard's hardware.
How fast can a new client site go live?
A site is a roster template plus posts, typically minutes of setup. Deploy guards to it and attendance, wages and billing annexures flow from day one.
Does it produce the wage register formats inspections ask for?
Wage and attendance registers export in inspection-ready form per establishment, built from the same records that paid the guards, so the register never disagrees with the payslip.
Can clients be given direct visibility of their site's compliance?
You choose, a per-site evidence pack can be exported monthly, or a client can be given a scoped view of their site's deployment and contribution evidence, which some agencies now offer as a service differentiator.
Payroll for security agencies, without the spreadsheets.
Per employee, per month: attendance to upload-ready returns.
Start free