Staff start and stop a timer in the app, the time is measured on the server rather than on the phone, the week is visible at a glance, the manager approves or rejects, and the approved result leaves as a CSV file for payroll.
Recorded working time is one of the few pieces of company data that has to be right for legal reasons rather than convenience. It has to be complete, it has to be traceable, and it has to be something other than a number a person wrote down from memory on a Friday afternoon.
A timer in the app solves the memory problem, but only if two further things are true. The time must be measured where it cannot be edited — on the server, not on the device — and it must go through an approval, so that the person who records the hours is not the same person who signs them off.
IDup does both. One running timer per person, measured server side, a week view that shows what has been recorded and what has been approved, and an export that hands payroll a clean file instead of a stack of notes.
All in IDup — one login, no silos.
Start and stop with a single tap on the phone. Only one timer can run per person, which removes the most common source of nonsense in recorded time: two overlapping entries that together claim more hours than the day has.
Start and stop are recorded by the server, not taken from the clock of the device. That is what makes the record hold up when somebody has to explain it later, and it is the difference between recorded time and reported time.
Recorded hours go to the manager, who approves or rejects them with a reason. Nobody approves their own hours. Reading rights and editing rights are separate, so a colleague can see the week without being able to change it.
The week view shows what has been recorded, what is still waiting and what has been approved. The approved result exports as a CSV file, which is the format every payroll system accepts without a project.
Almost every company that fills in hours at the end of the week believes the numbers are roughly right. They usually are — roughly. What they are not is evidence, because a number reconstructed from memory cannot be checked by anybody, including the person who wrote it.
That is fine until it matters: a dispute about overtime, a question from an authority, a client who asks what those twelve hours were spent on. At that point the difference between a measured record and a remembered one is the whole case.
Measuring at the moment costs one tap and produces something that can be shown to a third party. It also tends to produce different numbers, which is uncomfortable the first month and valuable every month after that.
One tap in the app. Only one timer runs at a time and the start is recorded on the server.
The week view shows the recorded hours; the employee submits them for approval.
The manager approves or rejects with a reason, and the approved hours export as a CSV file.
Recorded working time is a record the employer has to keep. It belongs to the company the work was done for, not to the personal account of the person who recorded it, and IDup stores it that way on purpose.
The employee records and sees their own hours through their account, but the record itself lives with the company, together with the approvals and the reasons for any rejection. That is what makes it complete when somebody asks for it years later.
It also keeps the boundary clean in the other direction. Somebody who works for two companies records time for each of them separately, and neither company sees anything about the other.
One login, ein Preis – keine versteckten Zusatzkosten.
Recorded hours go through approval, and reading and editing are separate rights. Nobody approves their own hours, so a correction is always visible as a decision rather than a silent edit.
Only one timer runs per person, so the open entry is obvious in the week view and can be corrected and submitted for approval like any other.
No. Start and stop are recorded on the server, so the record does not depend on the clock or the time zone of the device.
The approved hours export as a CSV file, which every common payroll system can read without a special interface.
Yes, within their rights. Seeing hours and changing hours are two different permissions, so oversight does not require the ability to edit.
It records, approves and exports working time with a traceable record. Whether that is sufficient for your legal obligations depends on your country and your sector — IDup is software, not legal advice.
Start free — the entire IDup platform in one login.
Copyright © 2026 - IDup. All rights Reserved.
