As of 18 Nov 2026, the panel rates clockodo 3/5 and ZEP 3/5 in Time Tracking & Attendance. Weighted by what each judge cares about, 2 of the 6 judges pick clockodo and 4 pick ZEP. clockodo scores higher on 2 of 7 criteria (European sovereignty and Working-time law & audit record). ZEP scores higher on 5 of 7 criteria (Absence & shift planning, Pricing transparency, Project, cost-centre & billing, plus 2 more). Provenance — clockodo: EU-Made, Germany; ZEP: EU-Made. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
By criterion, the bench splits down the middle. clockodo is ahead on working-time law (6.3 vs 4.8; 6 judges lean clockodo, 0 lean ZEP) and sovereignty (8.0 vs 4.0; 6 to 0): clockodo's attributes show a German contracting entity, data residency listed as EU only, and a self-serve Article 28 agreement with a published subprocessor list, while for ZEP the judges found no public information on a data processing agreement or subprocessor list. ZEP is ahead on absence and planning (6.2 vs 4.3; 6 judges lean ZEP), pricing transparency (8.3 vs 7.0; 6 to 0), project and billing (8.0 vs 7.3; 4 lean ZEP, 2 tie) and payroll export (6.0 vs 5.5; 4 to 1). Time capture is close, 6.8 vs 6.7, with 3 ties. Weighted totals split too: of the judges with numeric totals, three land on ZEP and two on clockodo — there is no overall winner.
Choose clockodo if
You must evidence working-time-law compliance: 6 judges lean clockodo there (6.3 vs 4.8), while the ZEP verdict found no public information on retention, change history or employee-initiated corrections.
Your procurement requires a contracting entity in Germany: clockodo's jurisdiction attribute is listed as DE, and ZEP's is listed as unknown.
You need data residency within the EU only: clockodo's attribute lists EU-only data residency.
You want a data processing agreement you can sign without negotiation: clockodo lists a self-serve Article 28 agreement, and 6 judges lean clockodo on sovereignty (8.0 vs 4.0).
Choose ZEP if
You plan absences and duties for your team: 6 judges lean ZEP on absence and planning (6.2 vs 4.3), while the clockodo verdict found no public information on shift or duty rostering.
You need published prices before talking to sales: ZEP leads pricing transparency 8.3 vs 7.0 with 6 judges leaning ZEP, showing annual and monthly per-user prices, VAT stated as excluded, fixed add-ons and a list-price calculator.
Your invoicing must emit XRechnung and ZUGFeRD 2.1: ZEP leads project and billing 8.0 vs 7.3, with 4 judges leaning ZEP and 2 tying.
Your payroll needs holiday and special-time supplements and a read-only month close: ZEP leads payroll export 6.0 vs 5.5 (4 judges lean ZEP, 1 leans clockodo), and clockodo's vendor page states its DATEV export serves hourly-wage recipients only and skips anyone who received surcharges.
You book time to clients, projects and subprojects with rates from price groups: ZEP edges time capture 6.8 vs 6.7, with 2 judges leaning ZEP, 1 leaning clockodo and 3 tying.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Operations Lead
Runs a 200-person operation with office, workshop and field staff, and has to record all of them since the BAG ruling. Wants capture that fits each of those groups and a roster that reflects reality. Unmoved by a beautiful desktop timer that half the workforce cannot use.
clockodo
ZEP
This judge's pick
Criterion by criterion
Capture in the real workplace
clockodo
Browser, desktop and iOS/Android apps with documented offline capture and automatic sync, a one-click punch clock that keeps running across project changes, and a terminal connection named on the pricing page give my office, workshop and field crews real paths. For GPS or geofenced check-in, a described kiosk or badge mode and bulk corrections we found no public information; changed entries do carry a note, though the help text does not say who made the change.
ZEP
There is a path for each of my groups: browser stamping for the desk, iOS and Android apps for the field, a tablet multi-user mode that simulates a terminal for the workshop, and a separate hardware terminal at a fixed monthly per-device price. The vendor is refreshingly explicit that GPS records the position per stamp event rather than fencing a radius. What holds me back: offline bookings not yet synced are lost on logout, and I found no public information on employee-initiated corrections or a change history showing who edited a stamp.
Working-time law & audit record
clockodo
Start, end and breaks are recorded with the 2022 BAG duty and the September 2022 obligation named, break rules are known and enforced with warnings to employee and employer, and hours accounts with overtime balances, edit locks and digital signatures on the work record are documented. For statutory retention of the record and for on-call, standby or travel time we found no public information, and the help centre itself states that with automatic break deduction an inspection would not show when the break was taken.
ZEP
Start and stop times, configurable break rules and standard working hours per weekday are documented, with an automatic overtime account, month-end locking, and a statement on the pages that minimum rest, breaks and maximum working time are tracked. But I found no public information naming the 2022 labour-court ruling or the Working Time Act itself, nor on retention periods, a change log on entries, or an export framed for an inspection.
Absence & shift planning
clockodo
Absence is genuinely covered: ten absence types from sickness to quarantine, automatic holiday accounts with remaining leave, per-country public holidays, approval duties configurable per absence type, a shared team calendar and mobile requests. For the shift or duty roster itself — templates, qualification or rest checks, coverage warnings — we found no public information, and with office, workshop and field staff that half decides whether the whole record means anything.
ZEP
The absence half is deep: full-day, half-day and hourly requests with approval workflow and withdrawal, sick leave, a second reason per day, holiday calendars, deputy sharing, and pro-rata entitlement with a worked calculation example. The planning module is project resource scheduling in a matrix with availability that subtracts absences and an overload warning — I found no public information on shift templates, qualification checks, swap workflows, or a duty roster my workshop crews would recognise.
Project, cost-centre & billing
clockodo
Entries carry customer, project, subproject, service, description and hourly rate at capture; budgets with warnings and interval budgets, lump sums such as travel costs, and a report builder with PDF and CSV export are documented. Released time becomes an invoice draft handed to named tools — Lexware Office, sevdesk, easybill — so workshop jobs and client projects bill without retyping.
ZEP
This is the vendor's home ground: time books against customers, projects, subprojects and tasks with a billable switch, rates via price groups per project and employee, cost centres per project with an employee fallback, and invoicing automated from released items with XRechnung and ZUGFeRD 2.1 output plus a DATEV invoice-data synchronisation. I found no public information on budget warnings or client-facing reports.
Payroll handoff
clockodo
A documented DATEV Lohn und Gehalt connection with client and consultant numbers, personnel-number type and wage-type mapping, plus recorded absences held ready for payroll preparation, reaches the named-integration level. The help centre states the export is exclusively for hourly-wage recipients and skips anyone who received surcharges in the period, so night, Sunday and holiday money stays manual; for a lock step before transmission and retro corrections we found no public information.
ZEP
A payroll accounting export is included in every product line, DATEV Lohn und Gehalt and LODAS are named synchronisation targets, holiday and special-time surcharges can be carried as time supplements into the overtime account, and closed months are read-only. I found no public information on night and Sunday surcharges, corrections after the month closes, or scoped access for my tax adviser.
European sovereignty
clockodo
Clockodo GmbH in Unna is the contracting entity, hosting runs on named Microsoft datacentres in Frankfurt and Berlin with ISO 27001 and emergency backups at Hetzner in Germany, and the subprocessor list published across the privacy policy and the processing agreement names locations, with the US entries (Stripe, Sentry, Perspective) tied to the Data Privacy Framework and standard contractual clauses. A self-serve Article 28 agreement with audit rights and 48-hour breach notification is public; we found no public information on an on-premises or private-cloud option.
ZEP
Hosting and development in Germany are stated across several pages, with daily backups in multiple German data centres and ISO 27001 certification stated to cover the cloud hosting partners. Beyond that the chain is thin: I found no public information confirming a data processing agreement, and no subprocessor list or named data-centre provider appears on the pages I read.
Pricing transparency
clockodo
Basic at 4 € per month per user, no base fee, monthly or annual terms (annual 5 % cheaper), net prices plus statutory VAT and a permanent free single user let me compute a headcount invoice; the captured pricing pages give different figures for the paid tiers — Pro at "10 €" with "8 €" for twelve months and Pro Plus at "12 €"/"10 €" in one capture, "9,50 €" and "11,40 €" in later ones. We found no public price for terminal hardware, and from 20 users the vendor points to an individual offer.
ZEP
Every product line carries a published annual and monthly per-user price, VAT is stated as excluded, and the planning, ticket-system and terminal add-ons each carry a fixed monthly figure, with a calculator showing the cost of a chosen setup at list prices. For my own size the caution is real: the pages state individual pricing for teams above 100 users, so my 200-person annual invoice would be a negotiated number, and extended onboarding such as data migration is charged without a published rate.
Sovereignty, side by side
Dimension
clockodo
ZEP
Legal entity
Incorporated in DE
Not determined
Hosting location
EU only
Not determined
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Published, self-serve
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 18 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 2 of the 6 judges pick clockodo and 4 pick ZEP. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is clockodo or ZEP European?
clockodo is European (EU-Made, Germany). ZEP is European (EU-Made). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do clockodo and ZEP store customer data?
Per the vendors’ own pages as captured — clockodo: In the EU. ZEP: Default not stated; pages mention Germany.