clockodo vs ZEP

clockodo

Browser, desktop and smartphone apps plus a named time-recording terminal give several capture paths, the mobile app records offline and syncs automatically, and employees can book forgotten times themselves, with a note left on every changed entry and digital signatures releasing work records. We found no public information on GPS or geofenced check-in, on badge readers, or on bulk correction with an attributable trail of who changed what.

ZEP

Web, two mobile apps and a genuine hardware terminal are all on the record, with offline stamping that stores locally and syncs, and GPS documented per stamp with the vendor openly stating it does not fence a fixed radius. What I miss is the correction side: times are edited in an admin mode, and I found no public information on bulk correction or any trail of who changed what.

clockodo

Begin, duration and end are recorded minute-accurately with the recording duty cited, break rules are adjustable, breaks can be enforced in company settings, and both employee and employer are warned when working times are not kept. The vendor's own help pages state the automatic break deduction books no break period, so an inspection would not show when the break was taken unless the employee records it, and retention appears only as the privacy policy's four-year default with a ten-year tax archive. We found no public information on daily-maximum or eleven-hour rest-period checks, tamper-evident storage, or an export built for an inspection.

ZEP

Individual working-time models and break rules per employee are evidenced, an automatic overtime account runs off the defined regular hours, and closed absence months are read-only — a real lock. But the captured pages never show the eight and ten-hour daily maximum, the eleven-hour rest period or any retention statement, and "gesetzeskonforme Einstellungen" is a claim rather than a documented check; I also found no public information on change history or tamper-evidence for the record itself.

clockodo

Vacation accounts with remaining leave and holidays are calculated automatically, sickness and a long list of absence types carry per-type approval rules into a team calendar, country-specific public holidays can be stored, and absences sync to Personio. We found no public information on shift or duty rostering, availability, substitution or swap workflows — the planner in view arranges absences by drag and drop, not shifts.

ZEP

Absence is properly run: categories including sickness, approval by administrators or department managers with email notification, sick-leave capture, pro-rata vacation entitlement with worked calculation examples, and a read-only month lock. The planning side is project resource scheduling in percentages, hours or time slots with overload warnings rather than a shift roster — I found no public information on shift templates with qualification or rest-period checks, swap workflows or holiday calendars per location, and carry-over into the new year is not documented.

clockodo

Every entry carries client, project, subproject, service and an hourly rate, hour and money budgets trigger automatic warnings before a project runs at a loss, and invoice drafts pass per click into named invoicing tools — Lexware Office, sevdesk and easybill — without retyping, with approvals by digital signature on the work record. We found no public information on cost centres, role-based rate cards, or rate behaviour when a rate changes mid-project.

ZEP

This is the product's centre of gravity: client, project and task master data, a billable switch on every booking, hourly and day rates plus project price groups, planned revenue from scheduled hours, and invoicing that runs from released items into XRechnung and ZUGFeRD with a maintained DATEV invoice synchronisation and cost centres from project or employee master data. I found no public information on rate rules surviving a change mid-project or client-facing report packs, which is what keeps it a step short of the full mark.

clockodo

A maintained connection to DATEV Lohn & Gehalt exists in the product, with client number, consultant number, personnel-number type and salary-type mapping to configure, and absences and the hours account stand ready for payroll preparation. But the vendor's own setup pages state this export is exclusively for hourly wage earners and excludes any employee who has entered surcharges — so night, Sunday and holiday work leaves the payroll run through no documented path. We found no public information on a lock step before transmission or on corrections after the close; the captured pages show reports leaving as PDF or CSV.

ZEP

Named payroll links exist — DATEV Lohn und Gehalt, LODAS, and a transfer of time bookings to Personio — and surcharges for public holidays and special times can be reported as time supplements into the overtime account, with months locked read-only. But the captured pages document the expense-to-accounting export in DATEV detail and stay silent on what the payroll export actually carries: no wage-type mapping for night, Sunday or holiday supplements, nothing on mid-month changes, and nothing on retro corrections after the close, which is where my month either reconciles or doesn't.

clockodo

Clockodo GmbH is the German contracting entity with German register details, the product stores data on German servers, and the privacy policy names processors with addresses — including a US payment provider processed under the EU-US Data Privacy Framework — alongside a trust centre carrying the data-processing agreement, technical measures and data-centre information. Processor categories such as the conference platforms remain unnamed, and we found no public information on data-centre certification or an on-premises option.

ZEP

German hosting and development are stated plainly, with daily backups in several German data centres and ISO 27001 certification covering the product and its cloud hosting partners. But the copyright names ZEP GmbH while the vendor line names provantis IT Solutions GmbH, and I found no public information on the contracting entity's jurisdiction or on any subprocessor — the hosting partners are mentioned but never named.

clockodo

All plans carry public per-user net prices — Basic at 4 € per user per month, Pro at 8 € for the first twelve months then 10 €, Pro Plus at 10 € then 12 €, the plus package at +2 € — with monthly or annual billing, cancellation at month end, VAT treatment stated, and no base or setup fee. A time-recording terminal is offered as a capture point, but we found no public information on terminal pricing or on a calculator that produces the annual invoice for a given headcount.

ZEP

Per-user prices are public for all three tiers — "Ab 2€ pro User", "Ab 7€ pro User", "Ab 18€ pro User" — with monthly billing, free onboarding and a price calculator advertised. But the three-to-eight add-on modules and the terminals carry no prices on the captured pages, VAT treatment is not stated, and above 25, 50 or 100 users depending on tier the price becomes an individual offer, so the real annual invoice is not computable from public pages alone.