Salaried staff and site labour are tracked differently for a reason — Rebota's HR & Payroll module handles compensation, statutory compliance, and payslips, kept deliberately separate from daily site attendance.
Most construction ERPs either ignore payroll entirely (leaving it to a separate accounting tool) or conflate it with site labour attendance — treating a salaried project manager's compensation the same way as a daily-wage mason's attendance record. Neither is right. Rebota keeps them as two distinct systems: site labour attendance feeds cost tracking and BOQ reconciliation; HR & Payroll handles salaried staff compensation, statutory deductions, and compliance.
Employee lifecycle records, configurable salary structures, automated payslip generation, and statutory deduction calculation for PF, ESIC, and Professional Tax. Leave management and loan/advance tracking against salary are included, so HR doesn't need a separate spreadsheet to reconcile advances against monthly pay.
Compensation and PII data (PAN, bank account, IFSC) are materially more sensitive than general project data — so unlike most other modules, HR & Payroll defaults to hidden even for roles that see everything else on a project (site engineers, QS, storekeepers). Only project directors get full access by default; project managers and accountants get narrower or no access unless explicitly granted. Bank account, IFSC, and PAN fields are encrypted at the application layer (AES-256-GCM), not just protected by TLS in transit.
Construction and project businesses with salaried staff (project managers, engineers, admin) who currently handle payroll in a separate spreadsheet or standalone payroll tool disconnected from project data.
A very small operation with one or two salaried staff and simple compensation may not yet need a dedicated payroll module — a basic accounting tool's payroll add-on can suffice at that scale.
Dedicated payroll-only platforms with deeper statutory filing automation (auto-generated PF/ESIC challans, direct government portal integration) may offer more filing automation than Rebota's current scope — verify against your specific statutory filing workflow before switching entirely away from a dedicated payroll compliance tool.
A single-employee or founder-only operation can reasonably continue with manual payroll a while longer.
For construction businesses that want payroll connected to the same platform as project and cost data — without exposing compensation data to every project role — this module fills a real, commonly-unaddressed gap.
The safest default for HR & Payroll access is the one Rebota ships with: nobody sees it unless explicitly granted, and the access grant is a deliberate decision, not an accident of a broader role template. Treat every access grant to this module as equivalent to sharing compensation data directly — because that is what it is.
