Employee report configuration¶
Defines one employee report.
Time datasets¶
An employee configuration is built from one or more time datasets. Each dataset is a date range with its own working-time rules, so a change of pensum mid-year stays accurate instead of averaging the whole year.
| Field | Effect |
|---|---|
| From / To | The range this dataset governs |
| Working days | Which weekdays count as expected working time |
| Hours per day | The expected hours used to compute the daily delta |
| Vacation entitlement | Days per year, used for the vacation balance |
| Disclaimer | Printed at the end of the PDF for periods this dataset covers |
| PDF language | The language this employee's report PDF is written in, for periods this dataset covers. Workspace default follows the PDF layout setting |
| Postal address | Optional. Printed as the recipient of this employee's report PDF, so it can be sent by post. It sits on the dataset rather than on the person, so somebody who moves gets a new dataset from the moving date and a report for an earlier period still carries the address that was current then. Left empty, the report is addressed to the employee's name alone — which is what an internal document needs. A street with no town counts as no address: half of one on an envelope looks deliberate |
Defaults come from employee time; a dataset overrides them for its range.
Overtime payouts¶
An overtime payout records hours that were paid out, so they stop counting towards the running balance. Without it, paid-out overtime keeps inflating the total forever.