A contract in Tempus is the formal employment relationship between one employee and one company. It is what activates the employee for payroll, time tracking, holiday quotas, and overtime.
Overview
Without an active contract an employee has no holiday quota, overtime accrual, expected hours, or time-attendance scope. An employee can hold several contracts over time, but only currently active ones drive day-to-day computations. The usual way to create one is Employee onboarding, which builds the employee, contract, and first work-shift assignment together. Use the standalone form for mid-employment changes.
What it does
The contract is the gate to the rest of Tempus: holiday quotas use its company and holiday calendar, overtime uses its weekly hours as the baseline, time-point validation compares clock-ins against the work shift assigned under it, and approval routing uses its department to find the manager.
Three settings deserve care:
- Contract type signals which legal rules apply and whether an end date is required (fixed-term types require one).
- Contract start date is the baseline for the work-shift assignment. If the shift starts later, the employee has no expected hours for the gap and time-point validation flags it. Match the two unless deliberate.
- Compensatory balance sets the starting credit or debit of time owed. Set it only when migrating from another system: a wrong value permanently displaces every future overtime calculation.
Contract transfer
When a tenant has two or more companies, a Transfer button appears on each contract row. It closes the source contract on a date you pick, opens a new one on the target company the next day, and preserves work-shift assignments, balances, and history. Use transfer for internal reorganizations and the end-and-recreate flow for unrelated job changes.
How to activate a new employee for time tracking
Until an active contract exists, the employee has no holiday quota, no expected hours, and no overtime accrual, so most "Tempus is not showing anything for this person" questions are a missing or mis-dated contract.
- Use Employee onboarding rather than building the pieces separately. It creates the employee, the contract, and the first work-shift assignment together, which is where they most often end up out of step.
- Pick the contract type first. Fixed-term types require an end date.
- Give the contract start date and the work-shift assignment start the same date unless you mean otherwise. A shift starting later leaves a gap with no expected hours, and time-point validation flags every day in it.
- Leave the compensatory balance at zero unless you are migrating from another system. A wrong opening value displaces every future overtime calculation permanently.
- Confirm the department, since approval routing reads it to find the manager.
- Verify the employee now has a holiday quota and expected hours before moving on.
- For a later change in weekly hours, end this contract and create a new one. Editing the hours in place does not recompute historical overtime.
See also
- Employees - the people contracts belong to.
- Companies - the legal employers.
- Departments - the org unit scoping each contract.
- Work shifts - the rostered pattern the contract's weekly hours must match.
- Employee onboarding - the recommended path for creating an employee and contract together.
- Overtime periods, Overtime declarations - the overtime machinery the contract feeds into.