Automatic effects and module boundaries
Use this map to plan complete work. A saved Employee action often records one administrative fact; related login, provider and Payroll actions remain separate.
| Action | Implemented effect | Separate responsibility |
|---|---|---|
| Create employee | DRAFT master; ensures EMPLOYEE role on existing Party | First employment, assignment and login setup |
| Add employment | Saves dated service episode | Current status change and contained HR setup |
| Add assignment | Saves job/unit/manager/hours facts | Login grants, attendance schedules and actual worked hours |
| Add compensation | Saves dated agreement | Payroll calculation and payment |
| Record overtime/bonus flags | Stores eligibility/target | Actual approved earnings and quantities |
| Record benefit/dependant eligibility | Stores participation/facts | Provider enrolment, valuation and deductions |
| Enter review/expiry date | Stores date | Follow-up review, renewal and any notifications |
| Change ON_LEAVE/SUSPENDED | Saves status/event | Leave balances, pay decisions and login review |
| Close employment | Validates child containment and saves end | Later permitted TERMINATED action |
| Terminate employee | Saves status/event | User disabling and operational handover |
| Rehire | New period under existing master | Reactivation, new child records and approved login restoration |
| Edit HR source | New source version | Payroll snapshot/run handling remains separate |
Current scope limits
There is no recruitment funnel, leave-balance engine, attendance clock, performance appraisal, training scheduling, asset custody, employee self-service, electronic signing or automatic expiry notification in the reviewed Employee workspace.
Document handling is metadata/reference only. Work-authorisation and qualification flags do not decide legal eligibility or validate external credentials. Plan/department/location/reference codes are entered text, not proof that a master-data workflow exists elsewhere.
No single offboarding or transfer transaction updates all HR records and login permissions. There is no automatic Payroll run creation, salary conversion, tax calculation or bank transfer on an Employee save.
Compatibility reminders
Party display name is resolved for Employee responses, not stored as a second operational identity. Employer-issued work channels are intentional Employee fields. The optional User link does not change User identity or permissions.
Expense's existing employee references remain User IDs; existing Purchase buyer/approver references are not silently migrated. A numeric value must be validated according to the receiving module's contract. Payroll deliberately uses real Employee IDs and source snapshots through its own boundary.
Example: Moving Amira's assignment to South changes her recorded workplace. It does not grant amira.cole access to South, transfer open orders or create a new salary payment. Complete the approved separate tasks and verify each saved result.