HRMS buyer's guide
HRM Buyer's Guide: Employees, Leave, Payroll & Suite Interop
How to evaluate HR software — employee lifecycle, leave workflows, payroll runs, performance, GDPR erase, and scheduling provider webhooks.
HRM Buyer's Guide: Employees, Leave, Payroll & Suite Interop
HR teams need hire → leave → payroll → compliance in one system — not contracts in folders, leave in Slack, and payroll in a separate tool.
Tekvers ships HRM as a standalone suite module with GDPR erase and scheduling provider webhooks — linked through Suite Platform, not shared people databases.
Product: /products/hrm · Finance: /products/finance · Platform: /products/platform
Related articles: HRM use cases · Scheduling & GDPR interop
Who needs this HRM module?
- HR managers — records, leave, compliance
- Payroll admins — period runs and posting audit
- Department leads — leave approval, performance reviews
- Operators entitling HRM alongside Projects and scheduling
- Teams tired of re-keying approved leave into payroll
If you only need workforce supply deployments and client billing, see Manpower ERP. If you need employee lifecycle + leave + payroll, evaluate HRM.
Core capabilities checklist
| Capability | Why it matters |
|---|---|
| Departments & employees | Org structure and single source of truth |
| Documents & contracts | Hire paperwork in-system |
| Leave types & balances | Policy-driven accrual |
| Leave requests | Approve/reject/cancel workflow |
| Payroll runs | Period processing with post + audit |
| Training & performance | Records tied to profiles |
| Time entries | Hourly and project workers |
| GDPR erase | Right-to-erasure with audit log |
| Scheduling webhook | Provider-changed sync |
Pain points this HRM addresses
Scattered employee records
No single source across contracts, leave, and payroll.
Manual leave → payroll
Managers approve in chat; HR re-keys; balances drift.
Payroll audit gaps
Unclear who was included and when runs posted.
Scheduling out of sync
Role changes in HR do not update booking availability.
GDPR multi-system hunt
Erasure touches HR, CRM, and scheduling separately.
Solution moments
New hire. Employee record, department, documents, contract, leave balances from policy.
Leave approved. Portal workflow; balance decrements; payroll excludes days.
Payroll posted. Period run reviewed and posted with audit trail.
Provider change. HR updates status; scheduling webhook refreshes availability.
GDPR erase. Compliance triggers purge with audit log.
Integrations (no shared DB)
| Sibling | Flow |
|---|---|
| Scheduling | Provider-changed webhook |
| Projects | Resource allocation references |
| Finance | Payroll journal posting intent |
| Suite Platform | Entitlements, handoff, service links |
Honest scope
- Payroll runs and posting scaffolded; external tax filing not in scope today
- Recruitment and benefits depth follows roadmap — validate must-haves in demo
- Separate GraphQL HRM codebases may exist elsewhere; this is the suite module
Implementation phases
- Departments & policies — Org structure, leave types, balances
- Onboard employees — Records, documents, contracts
- Leave & payroll cycles — Approve leave; post payroll
- Connect siblings — Scheduling webhook; Projects links
- Compliance — GDPR erase procedures
FAQs
Standalone without scheduling? Yes. Webhooks add value when scheduling is linked.
Tax filing? Not in current scope — payroll runs scaffolded.
GDPR? Yes — erase with audit logging.
Next steps
- Map your leave approval path today
- List payroll period rules and audit requirements
- Decide if scheduling provider sync is v1