Record employment periods and contract details
Employment records dated service episodes for one employee. Rehires use sequential periods under the same master. Concurrent overlapping employment periods are unsupported.
Fields
| Field | Rule |
|---|---|
| Employment Type | Required: PERMANENT, FIXED_TERM, TEMPORARY, CASUAL, APPRENTICE or INTERN |
| Start Date | Required; no earlier than original hire |
| End Date | Optional inclusive end; not before start |
| Contract Number | Optional, max 100 |
| Contract Signed Date | Optional administrative date |
| Probation End Date / Confirmation Date | Optional; must fall within employment if entered |
| Notice Period Days | Optional integer 0–730 |
| Termination Type | Optional: RESIGNATION, DISMISSAL, REDUNDANCY, RETIREMENT, CONTRACT_END, DEATH or OTHER |
| Termination Reason | Max 1000; required with termination type |
| Last Working Date | Optional; within employment |
| Rehire Eligible | Optional Yes/No decision, not automatic rehire |
| Employer Business Unit Id | Required existing tenant unit you are authorised to use |
Entering a termination type also requires an end date. A finite end date alone is not the same as the master becoming TERMINATED. The software does not infer legal employer registration or jurisdictional notice rules.
Add a period for an accessible employee
- Open detail → Employment and choose Add employment.
- Select the approved employer unit and employment type.
- Enter dates and agreed contract facts.
- Check no existing period overlaps, including an open-ended predecessor.
- Save and reload the records; verify the new Employment ID for linked child records.
First-period onboarding uses the procedure in First employment if detail cannot yet be opened.
Edit or close
Choose Edit / close record, which fetches current values. Preserve every intended field and save the full replacement with its version. Before shortening/closing employment, close contained assignments, compensation and benefits so none extends outside the revised employment.
Example: Employment ends 30 November. An assignment with no end date blocks closure even if its start was valid. End the assignment and other contained records no later than 30 November, then save employment closure.
Recovery
An overlap includes sharing one boundary day: an old period ending 30 November cannot be followed by another starting 30 November. Start the successor 1 December. An end-before-start error needs corrected facts, not an arbitrary shortened period. If another user changed a child record, reload its current state before retrying employment closure.
Editing employment is an audited correction, not an immutable revision chain. Use distinct service episodes for actual rehires and retain the approved internal evidence for material corrections.