Employee master
Maintain separate, controlled records for employment, addresses, dependants, education, experience, bank accounts and emergency contacts.
Centralise employee records, organisation structures, dated lifecycle changes and policy scope so downstream attendance, leave, payroll, performance and access decisions use the same governed foundation.
Addresses, dependants, prior experience, bank details and documents remain attached to the same employee identity.
Business unit, department, location, grade, employment type and reporting line can guide policy, access and workflow.
Transfers, promotions, manager changes, salary revisions and exits retain the date from which each change applies.
Use this page as a product-evaluation path: start with the operating problem, inspect the representative interaction, then verify the exact policy and output in the live product.
Configure the module around your structures, policies, ownership and approval model—not a generic process diagram.
Maintain separate, controlled records for employment, addresses, dependants, education, experience, bank accounts and emergency contacts.
Configure business units, departments, functions, locations, cost centres, grades, designations and employee groups.
Record confirmation, transfer, promotion, manager change, role change, salary revision and exit with effective dates.
Apply policies through employee group, department, location, business unit, grade or employment type.
Link employee documents, letters, assets and expiry reminders to the governed record.
Validate organisation and employee data before commit, with clear error reporting instead of silent partial imports.
The exact screens differ by module, but the operating principle remains the same: the applicable rule, current owner, status, effective date and history stay visible.
These examples are illustrative product patterns grounded in the supported product material. Use the live product to validate the exact screen, policy and output required for your organisation.
Organisation dimensions influence policy, workflow and access.
Use a representative employee, workforce group and effective date. Follow the transaction through owner, status and downstream impact.
Recruitment and resume parsing are not presented as native duoHR capabilities. Candidate handoff can come from Impact Hire or another ATS.
The example measures below are illustrative. Definitions and thresholds should be configured around the operating cadence and evidence your team uses.
Configure attendance, leave, payroll, approvals, permissions and notifications around the way your organisation actually works, while keeping every policy scoped, dated and reviewable.
ExploreConnect effective-dated salary structures, attendance and leave inputs, earnings, deductions, reimbursements, recoveries and statutory calculations in a payroll run that can be reviewed and rolled back before finalisation.
ExploreGive employees a responsive, mobile-first web workspace for attendance, leave, payroll documents, claims, profile changes, HR letters and helpdesk requests.
ExploreBring headcount, movement, people cost, attendance, payroll, performance and HR service data into role-based dashboards with consistent definitions and explainable drill-down.
ExploreUse your actual workforce groups, approval paths and edge cases during product evaluation.
Yes. Rules can be segmented by entity, location, department, grade, employment type and other employee attributes, with role-based approvals and effective dates.
Yes. duoHR can be introduced module by module. The implementation team maps your current policies, identifies dependencies and agrees a controlled rollout so business-critical cycles continue without disruption.
Bring one representative workflow or current process challenge. The demo will show the operating path, controls and connected outcomes.