What payroll systems solve — and what they don't
HR management systems (HRM) are fundamental tools. They handle payroll, benefits, time tracking, leave, and regulatory compliance. No HR department works without them.
But there is a difference between administering payroll and managing the processes HR conducts every day.
Payroll is calculation. HR processes are flow: they have stages, involve multiple people, require documents, approvals, and deadlines. And most of these processes don't fit inside the HRM.
The result is predictable: critical processes live in emails, spreadsheets, and shared folders. They work until someone misses a deadline, skips a step, or can't prove what was done.
6 HR processes that payroll systems don't solve
1. Internal investigations
When a report comes through the ethics channel — harassment, fraud, conflict of interest — HR needs to conduct an investigation. This involves interviewing parties, collecting evidence, recording statements, and issuing a finding.
Why HRM doesn't solve it: payroll systems store employee records. They have no structure to track investigation stages, attach confidential documents with access control, or maintain an audit trail of who saw what and when.
What you need: - Defined stages: report received, fact-finding, interviews, finding, closure - Restricted access control — not everyone in HR can see ongoing investigations - Documents with versioning and approval - Complete, auditable timeline for potential use in labor defense - Custom fields: report type, severity, business unit involved
2. Disciplinary actions
Verbal warning, written warning, suspension, termination for cause. Each disciplinary measure requires formal documentation, employee acknowledgment, and in many cases, legal review before application.
Why HRM doesn't solve it: the payroll system records the outcome — the suspension that impacts pay, the termination for cause. But it doesn't manage the process that led there. There is no way to record the stages of fact-finding, notification attempts, legal analysis, or the history of prior measures for the same employee.
What you need: - Workflow with stages: infraction identified, fact-finding, legal review, measure applied, employee acknowledgment - Link to prior investigations for the same employee - Required documents per stage: warning notice, acknowledgment receipt, legal opinion - Manager and legal approval before application - Deadline tracking — labor law requires immediacy in applying disciplinary measures
3. Headcount requests
A manager needs a new position. Before opening the role, someone must approve the budget, validate the title, confirm the cost center, and record the justification. In larger companies, this goes through three or four levels of approval.
Why HRM doesn't solve it: the HRM enters the picture after the position is already approved — when the candidate is hired and needs to be added to payroll. The headcount approval process comes before recruiting and involves budgeting, not people management.
What you need: - Structured request form with fields: title, department, justification, salary range, cost center - Configurable approval chain: direct manager, executive team, finance - Clear stages: request, budget analysis, approval, position opened - Status visibility for the requesting manager without having to ask by email - Record of denials — why the position wasn't approved and who decided
4. Inter-unit transfers
Transferring an employee from one office to another involves HR at both locations, the origin manager, the destination manager, and sometimes legal. You need to update the contract, verify regional benefits, confirm the collective bargaining agreement at the new location, and depending on the case, arrange relocation support.
Why HRM doesn't solve it: the payroll system records the change of assignment after it happens. But the coordination process — who approves, who is notified, which documents need updating, what the deadline is — has no place in the HRM.
What you need: - Stages: request, manager approvals, legal review (contract amendment), records update, onboarding at new unit - Tasks distributed between origin HR and destination HR - Documents: contract amendment, employee acceptance, integration checklist - Deadlines with SLA — the transfer must be completed before the start date at the new unit - Specific fields: origin unit, destination unit, transfer reason, benefits impact
5. Policy exceptions
Every HR department has formal policies. And every HR department handles exception requests: an employee who needs a benefit outside the standard table, a manager who wants to promote someone before the cycle, a leave type that doesn't fit any standard category.
Why HRM doesn't solve it: the payroll system applies rules. It has no mechanism to log, analyze, and approve exceptions to those rules. The exception happens over email, gets buried in a thread no one can find later, and there is no way to know how many exceptions were granted in the quarter or whether consistent criteria were applied.
What you need: - Standardized form: which policy, what exception, justification, estimated impact - Approval workflow with defined authority levels — low-impact exceptions approved by HR manager, high-impact by executive team - Centralized record of all exceptions granted and denied - Categorization fields for later analysis: policy type, requesting department, value involved - Complete audit — who requested, who approved, when, with what justification
6. Probation period evaluation
Employment contracts often include a probationary period. Before it ends, someone needs to evaluate whether the employee will be confirmed. In practice, this depends on feedback from the direct manager, any incidents during the period, and a formal HR decision.
Why HRM doesn't solve it: the payroll system tracks the probation end date. But the evaluation process — collecting feedback, recording the decision, notifying the employee — doesn't happen inside the HRM.
What you need: - Automatic trigger: the process starts 15 or 30 days before contract expiration - Evaluation form for the manager: performance, adaptation, recommendation (confirm, terminate, extend) - Stages: manager evaluation, HR review, decision, employee communication - Hard deadline — the decision must be made before expiration, or the contract automatically becomes permanent - Documents: formal evaluation, confirmation letter or non-renewal notice
The pattern behind all 6 processes
All these processes share characteristics that HRM doesn't address:
- 1Defined stages: they are not loose tasks but flows with a beginning, middle, and end
- 2Multiple participants: they involve managers, HR, legal, executives — each with a specific role
- 3Controlled documents: they need versioning, approval, and traceability
- 4Chained approvals: one step depends on the previous one, and each decision needs a record
- 5Audit trail: HR needs to prove what was done, when, and who authorized it — especially in labor disputes
- 6Deadlines with consequences: missing an investigation deadline or a probation evaluation creates real legal risk
No payroll system was designed for this. These capabilities won't appear on your HRM's roadmap because they fall outside the tool's scope.
What fills this gap
What's missing isn't another HR system. It's a process orchestration layer that works on top of your HRM.
The HRM keeps doing what it does well: payroll, benefits, time tracking, compliance. The orchestration layer handles the rest — the processes that have stages, deadlines, documents, and decisions.
In CaseFy, each process type becomes a template:
- Internal investigation: template with stages for intake, fact-finding, interviews, and findings. Restricted access per case. Auditable timeline.
- Disciplinary action: template with fact-finding, legal review, and application workflow. Required documents per stage. Links to prior cases for the same employee.
- Headcount request: template with structured form and approval chain. The manager tracks status without sending emails.
- Inter-unit transfer: template with tasks distributed between origin and destination HR. Document checklist. Completion SLA.
- Policy exception: template with standardized form and approval authority levels. Centralized record for pattern analysis.
- Probation evaluation: template with deadline tied to the contract. Manager evaluation form. Decision recorded with justification.
Each template has custom fields, documents with approval, automations for notifications and deadlines, and a timeline that records every action. Granular permissions ensure only authorized people can access a process.
Start with the processes that hurt the most
You don't need to orchestrate everything at once. Identify the two or three processes that cause the most rework, risk, or complaints in your HR today. Configure the templates, run for 30 days, and evaluate.
Your payroll is well served. What needs attention are the processes living outside it.