Employee overview
Employee manages a person's employment relationship: the employee master, employment periods, assignments, agreed compensation and supporting HR records. Shared names and personal identity remain in Party; login access remains in Administration. The current module is an HR administration foundation with a separate Payroll handoff.
This guide follows the application sources reviewed on 8 November 2026. Names, dates, IDs and amounts are invented training examples. Procedures describe implemented screens and rules; recommendations are identified separately from enforced checks.
Choose a task
| Goal | Guide chapter |
|---|---|
| Understand access and prepare setup | Access, checklist |
| Find records and understand terms | Navigation, terms |
| Reuse Party identity and link a login | Identity and login |
| Create or maintain the master | Employee master |
| Complete initial onboarding | First employment and browser limitation |
| Maintain employment history | Employment, effective dates |
| Record job, unit and manager | Assignments, reporting relationships |
| Record pay agreements and changes | Compensation, pay changes |
| Maintain supporting HR information | Emergency contacts, dependants, qualifications |
| Record private evidence and eligibility administration | Documents, work authorisations, benefits |
| Change employment status | Status, leave and suspension |
| Process a departure or return | Termination, rehire |
| Resolve errors and understand retained evidence | Conflicts, privacy and history |
| Understand integrations | Payroll handoff, automatic effects |
| Practise or diagnose | 35 worked examples, troubleshooting |
Running example
Bright Haven Services operates BHS-NORTH and BHS-SOUTH. Amira Cole is employee BHS-001; Jonah Reed manages a team. Farah administers employment, Nadia maintains approved compensation, and Leena reviews supporting HR records. These responsibilities are illustrative, not seeded roles.
The current browser has a first-employment onboarding gap explained prominently in its own chapter. Other chapters assume the employee already has a legitimate unit-linked employment established. No guide step creates a duplicate person, assumes a login was created automatically or treats employee status as historical payroll calculation.