Document working time. Prove every change. Close the period.
EU working-time rules require reliable records of hours and breaks. iXTime supports you in meeting them: first start, last end and breaks documented per day, every change logged, closed periods locked — with an export for inspections.
Document. Prove. Close.
Three steps that turn time tracking into reliable working-time records.
Break capture
A Pause button on the timer: one click interrupts work and starts the break. Enabled per workspace — teams that don’t track breaks notice nothing.
Working-time report & export
Per member and day: first start, last end, work time and breaks — as CSV, Excel or PDF for inspections. Without break capture, time between entries counts as break time; with capture on, unrecorded gaps are shown separately. A day spent fully absent carries its reason as the label.
Source of every entry
Every entry keeps how it came about: timer, manual, import or terminal — including the device, e.g. “Terminal (Reception)”. Set by the server, unchangeable afterwards, a column in the working-time report and its export.
Change history
Every change to a time entry is logged: who, when, what (old → new). Members see admin corrections right on the entry — and acknowledge them with one click.
Changelog report
All changes and deletions as a dedicated report — transparent for both sides: admins see the workspace, members their own entries.
Close the period
Month reviewed? One click locks the period for the whole team — admins included. Later corrections are deliberate, logged, and visible to the member.
How it works
Track as usual
Timer or manual — with break capture enabled, one click interrupts work and starts the break.
Review
The working-time report shows first start, last end, work and breaks per member and day — gaps stand out immediately.
Close
Lock the period: from now on the month is immutably documented. Export as CSV, Excel or PDF — anytime.
Frequently asked
Does iXTime fulfil the legal recording obligation?
iXTime supports you in fulfilling it: first start, last end and breaks are documented per day, every change is logged, closed periods are locked, and the report exports per member and period.
Does everyone have to track breaks?
No. Break capture is enabled per workspace. With capture off, the working-time report counts the time between two entries as break time. With capture on, recorded breaks count as break time — and unrecorded gaps are shown separately as “untracked”.
Can an admin change entries unnoticed?
No. Every change lands in the history (who, when, old → new), the affected member sees the correction right on the entry and acknowledges it with one click. The changelog report additionally lists all changes and deletions.
What happens when a period is closed?
All entries up to the closing date are locked for the entire team — admins included. A deliberate single correction remains possible for admins, but is doubly logged and shown to the member. Only the owner can lift the lock — also logged.
How can I tell how an entry came about?
From its source: timer, manual, import or terminal with the device’s name. It shows in the entry details and as a column in the working-time report and its export; entries from before show “—”. The source classifies — it does not prove who stood at the device.
Time clockWhat about vacation and sickness?
Absences are recorded separately and never count as working time; in utilisation against target time they only reduce the available target time. In the working-time report a day spent fully absent carries its reason as the label instead of computing work and break time.
Absence & leaveHow long is the data retained?
For as long as your workspace is active — which covers the usual two-year retention period. Even after a trial expires, all data remains accessible read-only.