Employee troubleshooting and quick reference
Check the exact record, requested action, feature/permission and date facts before changing data. A failed read can be a scope decision; a failed save does not prove all previous requests rolled back.
Common problems
| Symptom | Check and recovery |
|---|---|
| Employees unavailable | EMPLOYEE/PARTY/ORGANIZATION and employee.view |
| New employee absent from directory/detail | First-period visibility gap; use approved support/API establishment, not duplicate creation |
| Name search returns nothing | Directory matches employee numbers |
| HR tab missing | Optional feature and area read authority; manage alone does not open a tab |
| Add/Edit action missing | Area manage right or master/status-specific authority |
| Employee not found | Correct tenant/ID and any accessible employment/assignment relationship |
| Salary inaccessible despite master access | Linked employer-unit access plus compensation feature/permissions |
| Person selection refused | Existing active PERSON Party required |
| Duplicate Party conflict | Use existing master and employment history for rehire |
| Employee number conflict | Trim/uppercase tenant uniqueness; investigate existing number |
| Linked user unavailable/conflict | Discovery/protected-target access or already linked elsewhere |
| Party/original hire read-only | Fixed master anchors; approved correction support required |
| Seniority rejected | Must not follow original hire |
| Employment start rejected | Must not precede original hire |
| Employment/assignment/pay overlap | Inclusive endpoints; close predecessor before successor |
| Employment closure refused | Open/later-ending contained assignment, compensation or benefit |
| Manager rejected | Accessible Employee ID and no dated direct/indirect reporting cycle |
| FTE/hours validation | FTE 0.01–1.0; hours 0.01–168; precision limits |
| Salary seems unconverted | Base amount remains in pay basis; no automatic annual/monthly calculation |
| Missing required Yes/No | Select explicit value; No differs from None |
| Dependant date refused | Birth date cannot be future; correct actual evidence |
| Verified authorisation refused | Verification Date required with Verified Yes |
| Same benefit plan overlap | Review exact plan code and period, including suspended/ended records |
| ENDED benefit refused | End date required and contained in employment |
| Document upload/download missing | Metadata/storage reference only |
| Expiry caused no notification | No scheduled reminder/renewal workflow |
| Closed marker on future period | Marker checks entered end date; read the actual date |
| ACTIVE/leave/suspension refused | Employment must cover server today |
| TERMINATED refused | All periods must end strictly before today; at least one must exist |
| Login still enabled after termination | Expected separation; use Administration |
| Payroll covering-record error | Split at employment/assignment/pay changes; inspect gaps |
| HR edit did not alter Payroll | Stored Payroll snapshots are separate historical evidence |
| Stale version | Preserve intended change; cancel/reopen and reconcile |
| Save outcome uncertain | Reload/search before repeating; no stored original-intent replay promised |
| History lacks old phone/salary values | Other row edits are audited corrections, not full immutable revision history |
| Transfer did not hide master | Historical unit relationships also satisfy visibility |
Frequently asked questions
Can we complete new onboarding entirely through the current browser? The first-period visibility gap can block detail before adding employment. Use the documented authorised API/support route and verify the existing master; do not recreate it.
Does Employee create a login? No. Linking a User does not create credentials, roles or unit grants.
Does moving an assignment revoke old HR visibility? Not automatically. Historical employment/assignment relationships also count in current master visibility.
Can one person have simultaneous employment periods? This release rejects overlapping employment and primary assignments. Use approved separate workflows for requirements outside that model.
Does FTE calculate hours or salary? No. FTE, hours and pay agreement are separate source facts.
Does a review date create a task or reminder? No scheduled follow-up is implemented in this workspace.
Can we delete an obsolete record? No hard-delete endpoint is provided. Use supported end/activity/status fields and the approved data-management process.
Is Verified independent approval? No. The administrative fields are not a generic four-eyes or external-verification workflow.
Does TERMINATED remove the EMPLOYEE Party role or disable login? No. Review operational eligibility and User lifecycle separately.
Does Employee calculate or pay Payroll? No. It provides source records; Payroll owns its own preparation and approval process.
Support handover
Tenant: BHS (training example)
Employee number / ID: BHS-001 / verified tenant Employee ID
Area / child ID: Assignment / verified record ID
Requested action: add successor from approved change date
Observed message: exact non-secret error
Current parent period: approved dates, no personal evidence attached
Reloaded record/version: yes / no
Earlier saves already committed: describe observed state
Internal approved request: BHS-HR-014
Keep salaries, dependant/contact facts, raw evidence and credentials out of shared support notes. Record intended versus actually saved state separately. Do not broaden permissions, duplicate identities or rewrite dates merely to make an error disappear.