Employee terms and record relationships
| Term | Meaning | Example |
|---|---|---|
| Party | Canonical shared identity | Amira Cole, PERSON |
| Employee master | One tenant employee relationship per Party | BHS-001 |
| User | Login identity, optionally linked | amira.cole |
| Original hire date | Fixed first-hire anchor | 2026-10-01 |
| Seniority date | Recognised prior-service date, no later than original hire | 2026-09-01 |
| Employment period | Dated contract/service episode | First hire, later rehire |
| Employer business unit | Unit associated with employment | BHS-NORTH |
| Assignment | Dated job/organisational record within employment | Support Officer at South |
| Manager employee | Another Employee ID used for reporting | Jonah's employee record |
| FTE | Recorded full-time-equivalent fraction | 0.8000 |
| Weekly hours | Recorded agreed hours | 30.00 |
| Compensation | Effective base-pay agreement | GBP 2,400 per MONTHLY basis |
| Pay basis | Unit in which baseAmount is agreed | HOURLY, MONTHLY, ANNUAL |
| Pay frequency | Agreed cadence, not a generated calendar | FORTNIGHTLY or MONTHLY |
| Benefit enrolment | Dated participation in a plan | HEALTH-A / ENROLLED |
| Effective period | Inclusive start and optional inclusive end | 1–30 November |
| Version | Concurrency token returned with a record | Send current version on update |
| Status event | Retained reasoned status transition | ACTIVE to ON_LEAVE |
Distinctions that prevent errors
Employee number, Employee ID, Party ID, User ID and Employment ID identify different things. Similar numeric values do not make them interchangeable. Assignments use managerEmployeeId, not a manager's login User ID. Compensation and benefits reference a specific Employment ID of the same employee.
Current employee status is an administrative value, not an automatically calculated as-of history. Employment periods are dated evidence. Status history captures transitions but does not make every HR edit an immutable revision.
FTE and weekly hours are separate entered values. No global full-time week is assumed, and the module does not automatically calculate one from the other. Compensation basis/frequency are also separate; a monthly pay frequency does not convert an annual base amount into monthly pay here.
Example: Amira can have Party #101, Employee #201, User #301 and Employment #401. A Payroll snapshot uses the real Employee relationship and its dated source records. Legacy Expense employee references remain User IDs; do not replace them with #201 by numeric guesswork.