Skip to main content
A time report is an individual record that describes a period of absence or attendance for a specific employee. Unlike entity properties in the Employee model, time reports are not date-tracked - each record is a discrete event with its own date range.

​
Fields

​
Request status

​
Time types

Every time report references a time type that describes what kind of absence or attendance is being recorded - vacation, sick leave, parental leave, and so on. Time types can be sourced from the external system or defined locally within Twine. Each time type has a name, an optional code, and an optional external identifier. Its behaviour is described by a set of traits:

​
Absence and attendance

Both kinds of record are time reports, but they are not synced on the same terms. Absence - vacation, sick leave, parental leave - syncs with no configuration. Time types are enabled by default, so once a system integration is connected, absence records flow in for every enabled type. You do not need to create time type mappings to sync absence into Twine. Attendance - worked time, and in some systems the breaks within it - is off by default and must be switched on. This is deliberate rather than an oversight: attendance is far higher volume than absence. A year of absence for one employee is typically tens of records; a year of attendance is thousands, because every shift, and often every break, is its own record. To sync attendance, both of the following must hold:
  1. The attendance time types are enabled, the same requirement absence has. In Personio these are WORK and BREAK; other systems use their own codes.
  2. You have opted in, by either:
    • ticking Sync attendance in the system integration’s settings, or
    • mapping an attendance time type to a target time type, which system-to-system integrations do as part of normal setup.
If you are syncing into Twine and reading through the API rather than replicating onward, you will not have time type mappings, so Sync attendance in the settings is the switch you want. Absence will already be arriving without it.
Where a system splits a shift around its breaks - Personio does this - each segment arrives as its own time report, with the break excluded from the surrounding work segments rather than needing to be subtracted. Summing the worked segments for a day gives that day’s worked time.