From month-end anxiety and opaque payslips to exceptions-first validation and plain-language salary breakdowns

For HR managers and accounts managers, payroll is the highest-stakes task in the HRMS cycle — one wrong value affects every employee's salary. For employees, it's the moment of truth each month: did the system get it right? We interviewed both sides and built detailed persona profiles.
Payroll has a hard deadline and zero tolerance for error. Synthesising the research revealed four failure modes across the payroll lifecycle:
The most consequential ideation decision was how to structure the payroll run initiation. We explored three structural models:
Bhavesh's exact quote drove this decision: "It is better to focus on only those employees rather than same effort for all employees." In a 500-person company, typically 10–30 employees have something to resolve. Surfacing only those saves hours and eliminates "did I miss something?" anxiety.
For the employee-facing payslip, we explored two directions: a traditional finance-grid format (familiar to accountants, opaque to employees) vs a plain-language card. Research was clear: employees don't need accountant-grade formatting. They need to know their take-home, what was deducted, and why. We chose plain-language design with expandable detail.
We mapped four views from the same payroll data: Owner (cashflow summary), HR Admin (full control + statutory), Manager (team salary budget view), Employee (personal payslip + tax calculator). Designing each separately — rather than one screen for all — was the key ideation output.
| Phase | Initiate | Validate | Resolve | Lock and Run | Post-Run |
|---|---|---|---|---|---|
| Activity | Select pay period. Review employees in scope. Check previous month variance summary. | System surfaces exception list — pending attendance, missing declarations, new joiners, salary revisions. | Approve/override each exception inline. Request corrections from managers. Verify investment proofs in inline viewer. | Final review of salary totals. Confirm no overlap or gaps. Lock payroll — permanent action with explicit confirmation. | Download payslips. Distribute to employees. Process statutory transfers. Generate compliance reports. |
| Feeling | Routine — familiar monthly process | Relief at seeing only anomalies — not all 500 | Frustration if exceptions are many. Stress with investment proof validation. | Highest anxiety moment — irreversible action | Relief and satisfaction when payroll processes cleanly |
| Design decision | Show month-on-month comparison summary at entry — normalises context immediately | Categorise exceptions by severity and type. Show count before opening list. | Bulk action for common resolutions. Document viewer inline — no separate portal. | Show exact impact preview: employee count, total amount, delta from last month. Require explicit "I confirm" action. | One-click statutory transfer with deadline countdown. Auto-generate challan drafts pre-filled. |
The mobile payroll experience was designed for the employee — not the HR manager. The home card shows net salary with a donut chart at a glance. Deeper screens reveal salary structure, payslip history, and per-payslip detail with a Download PDF CTA. Managers get a separate view with annual CTC breakdown.
The web experience covers the full payroll lifecycle: salary structure configuration with statutory toggles, the payroll run two-step flow (attendance finalization → salary finalization), final salary summary with audit trail, loan management, and the payslip template builder. Each screen was designed to reduce a specific anxiety identified in research.
The payslip PDF was redesigned to lead with what employees care about — Net Pay as the hero, prominently placed top-right. Company and employee identity at top-left. Earnings and Deductions in clear two-column layout with plain-English labels. Month-on-month delta shown at the bottom (↑₹1000 from Apr 2023). Auto-generated footer eliminates signature confusion.
Usability testing with HR managers and accounts managers from 4 companies across manufacturing, IT services, retail, and logistics. Key findings that changed the design: