clockodo vs ZEP

clockodo

Browser, desktop and smartphone apps plus a shared time-recording terminal, and the apps capture offline and sync automatically once a connection returns — that is the basement test passed. Retroactive entries, a split function to book a missed break afterwards, and an annotation whenever someone changes a time entry give a foreman a correction workflow. We found no public information on GPS or geofenced check-in or on bulk correction.

ZEP

The Clock App punches in single-user and multi-user modes where a tablet on site simulates a terminal with PIN logins, there is a separate hardware terminal, and bookings made offline sit on the device and sync the moment signal returns — kit a foreman can run in a stairwell at 6am. Location is GPS per stamp event with the vendor plainly stating it does not restrict stamping to a fixed radius, and an administrator can edit times on the device itself. We found no public information on an audit trail showing who corrected what after the fact.

clockodo

The vendor names the BAG 2022 duty, records begin, duration and end minute-exact, and offers configurable break rules, an enforce-breaks setting and a warning to both sides when times are not kept, with a change annotation on every entry. Its own help page states the automatic break deduction books no break period, so at an inspection it would not be evident when the break was taken unless the employee records breaks. We found no public information on checks for the daily maximum or the 11-hour rest period.

ZEP

Working time is recorded to the minute with configurable break rules and individual working-time models per employee, an automatic overtime account with capping, and the Clock line is sold with gesetzeskonforme Einstellungen. But we found no public information on warnings for the daily 8/10-hour maximum or the 11-hour rest period, and no stated retention period — for an inspection those are the first questions.

clockodo

Vacation accounts with carry-over and country-specific holidays, ten absence types with per-type approval rules, a team calendar and mobile entry are all evidenced, and sickness runs through the same system. We found no public information on shift or duty rostering, availability, or substitution and swap workflows — the planning half of this criterion.

ZEP

Absence is genuinely handled: full, half and hourly requests with approval statuses and role-based approvers, sick notes with certificates, month-end locking, weekend and holiday blocking, and vacation entitlement prorated by employment period with remaining vacation on the dashboard. Planning is capacity scheduling — percentages of regular working time made day-precise with overload warnings — rather than duty rosters; we found no public information on shift templates with rest-period checks or swap workflows.

clockodo

Every entry carries client, project, subproject, service, employee and hourly rate at capture, hour and money budgets warn before a project runs into loss, and invoice drafts pass at a click into named invoicing tools — Lexware Office, sevdesk, easybill — with PDF and CSV as fallback. We found no public information on a cost-centre field, a billable flag, or how a rate change mid-project is handled.

ZEP

This is the vendor's home ground: customer, project and task master data, cost centres from project or employee, price groups with hourly and daily rates, a billable flag on every booking, release before billing, and automated invoicing with XRechnung and ZUGFeRD feeding DATEV or Lexware. We found no public information on budget tracking with overrun warnings.

clockodo

A documented DATEV Lohn und Gehalt connection exists, with client and consultant numbers, personnel-number type and salary-type mapping, and recorded absences stand ready for payroll preparation. The same help pages state the export is available exclusively for hourly wage earners and excludes anyone with surcharges entered, so night and holiday surcharge work leaves this path. We found no public information on a lock step before transmission or retro handling after the close.

ZEP

A DATEV synchronisation covering Lohn & Gehalt and LODAS is named, and documented DATEV, Lexware and general CSV exports exist — but the export we can read documented carries internal travel expenses rather than hours and overtime, and the accounting export module sits only in the top tier. We found no public information on how night, Sunday and holiday surcharges reach payroll, or on a lock step before transmission.

clockodo

German company, data stored on German servers, a trust centre carrying the processing agreement and data-centre information, and subprocessors named by company and country, including Stripe in the USA with the Data Privacy Framework as the stated basis. The product is presented as a cloud solution; we found no public information on an on-premises or private-cloud option, and the captured pages do not name the data-centre provider behind the application data itself.

ZEP

Hosting and development are stated as Germany, with daily backups across several German data centres, ISO 27001 certification covering ZEP and its cloud hosting partners, and the site copyright names ZEP GmbH. We found no public information on a published subprocessor list or a named data-centre provider, so the chain behind those German servers cannot be checked before signing.

clockodo

Every tier is priced publicly as a net per-user monthly price — Basic 4 €, Pro 10 € with 8 € for the first twelve months, Pro Plus 12 € with 10 € likewise, the Plus package at +2 € — with monthly or annual billing, cancellation to month end and VAT treatment stated. We found no public information on a price for the time-recording terminal hardware, and from 20 users upward the vendor invites individual offers rather than published maths.

ZEP

Per-user prices are public for all three tiers — ZEP Clock Ab 2€ pro User, ZEP Compact Ab 7€, ZEP Professional Ab 18€, monthly billing, no onboarding costs, free premium support — and a price calculator is offered. But the add-on modules and the terminals the plans point to carry no public prices, and above 25, 50 or 100 users depending on tier the price becomes an individual offer, so a larger buyer cannot compute the annual invoice alone.