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 Works Council Advocate
Has co-determination over how working time is recorded (BetrVG §87 (1) 6) and will not approve a system that watches more than it measures. Asks what GPS actually stores, who can read an individual's day, what is logged and what can be switched off. Reads "productivity insights" as a warning.
clockodo
This judge's pick
ZEP
Criterion by criterion
Capture in the real workplace
clockodo
Clock-in runs across browser, desktop and phone apps, a one-click punch clock and a terminal connection, with the mobile app storing everything offline and syncing on its own — offline here is a designed state, not a failure mode. Retroactive entries, a split function to book a forgotten break afterwards, and a permanent note whenever anyone changes an entry cover the correction side; we found no public information on bulk correction, nor on GPS or geofenced check-in and its limits.
ZEP
Capture runs through the browser, two mobile apps, a shared multi-user device mode and a hardware terminal, with offline entry that syncs automatically — though the documentation itself warns that unsynced entries are lost on logout in offline mode. On the point I always press first: location transmission is off by default, records one GPS position per stamping event as location documentation rather than a geofence, and the vendor states that limit itself; but the switch sits with the administrator, and once it is on an employee cannot stamp without granting location. Corrections are described as administrator edits via admin PIN; we found no public information on an employee-initiated correction flow or on a log of who changed which entry.
Working-time law & audit record
clockodo
The vendor itself cites the EuGH and BAG rulings, records start, end and duration, models break rules that can be enforced in company settings, and warns both the employee and the employer when working times are breached — a symmetry a works council can live with. I especially value the candour that automatic break deduction books no break period, so an inspection would not show when the break was taken and staff must record breaks themselves; hours accounts, edit locks and digital signatures round off the record. We found no public information on the statutory retention of the working-time record being handled by the system.
ZEP
Working time is stamped to the minute with configurable working-time models, break rules and an automatic overtime account, and the pages state that minimum rest time, break times and maximum working time under the statutory provisions can be tracked well. Before I co-sign such a record I would need more than that: we found no public information on retention of entries, on a tamper-evident change history — the closest control shown is a month-end lock that makes closed months read-only — or on handling of on-call and standby time.
Absence & shift planning
clockodo
Absence management is deep: vacation quotas with remaining leave calculated automatically, country-specific holidays, ten absence types including sickness and child sickness, approval configurable per absence type, and a team calendar where only approved absences appear. Push messages carry no names and no absence reasons, and sensitive absence data stays out of the AI features — exactly the restraint co-determination asks for. We found no public information on shift or duty rostering, so the planning half of this criterion rests on an absence planner alone.
ZEP
Absence handling is mature: requests with approval by administrators or department managers, withdrawal until decided, sickness with certificates, a second absence reason per day, and a pro-rata entitlement engine the vendor documents down to a worked example. Planning is a resource matrix against availability from which absences and holidays are subtracted, with an overload warning when a day exceeds available hours — and where an absence collides with a plan, deletion happens through a visible notice block rather than silently, which I rate positively. We found no public information on shift templates, substitution or swap workflows, or carry-over rules.
Project, cost-centre & billing
clockodo
Every entry carries client, project, sub-project, service, person, description and hourly rate, with billable status part of the recorded data, budgets and interval budgets with automatic warnings, and flat rates such as travel costs. Invoicing is a handoff rather than an island: the report builder and an invoice toolkit pass positions to named tools — Lexware Office, sevdesk, easybill — where the draft is created. We found no public information on cost centres or on rate rules surviving a mid-project rate change.
ZEP
This is the product's centre of gravity: time booked to project, task and activity with a billable switch, hourly and daily rates, price groups per project-employee assignment, cost centres per project with an employee fallback, and plan-versus-actual figures per project. Billing flows from the record itself — released invoice items, automated invoicing, hourly, flat and fixed-price methods, XRechnung and ZUGFeRD 2.1, and a documented DATEV and Lexware handoff. We found no public information on budget-overrun warnings, client-facing reports, or how a rate change mid-project is treated.
Payroll handoff
clockodo
A documented DATEV Lohn und Gehalt connection exists, with client and consultant numbers, the personnel-number type and wage-type mapping described step by step, and recorded absences explicitly made available for payroll preparation. But the export is available exclusively for hourly-wage earners, and anyone who received surcharges in the export period is skipped — a stated limitation every buyer with shift premiums must check against their payroll. We found no public information on a lock step before transmission.
ZEP
A payroll accounting export is included in every product line and DATEV is named for synchronisation of Lohn & Gehalt and LODAS, while holiday and special-time surcharges are reported as time supplements and a month-end closing makes entries read-only. We found no public information on night and Sunday surcharges in the export, on mid-month changes, or on a defined lock step immediately before transmission.
European sovereignty
clockodo
Contracting entity and vendor are German, hosting sits in Microsoft datacentres in Frankfurt and Berlin with emergency backups at Hetzner, the Article 28 agreement is downloadable, the cloud servers are ISO 27001 certified, and subprocessors are published with names, countries and purposes. The non-EU links are named and given a legal basis — Stripe in the USA for payments, Sentry in the USA under the Data Privacy Framework and standard clauses — and subprocessor changes come with two weeks' notice and a two-week objection right. AI features are opt-in, processed in Europe, never trained on customer data, and locked out of sensitive absence reasons; this is a chain I can negotiate a works agreement around.
ZEP
Hosting, development and daily encrypted backups are placed in Germany across several data centres, with ISO 27001 certification extending to the cloud hosting partners — for a works council that is the reassuring half. We found no public information on a data processing agreement, on the full subprocessor list with locations, or on the establishment of the contracting entity beyond a copyright line naming ZEP GmbH; the hosting partners themselves are referenced without names.
Pricing transparency
clockodo
Four tiers carry public per-user prices with the billing period, cancellation terms and VAT treatment stated, no base fee is claimed, the single-user tier is permanently free, and the plus package is listed at a stated +2 € per user per month. The captured pages give different figures for the Pro and Pro Plus per-user prices, so a buyer should confirm the current number before computing the year, and we found no public price for the terminal hardware.
ZEP
Every product line carries a public per-user price with annual and monthly billing stated, VAT stated as excluded, add-ons priced individually including the ZEP Terminal at 15 € per terminal per month, cancellation at any time, and a price calculator showing the result for a chosen line, team size and add-ons. The captured pages give different figures for the entry price of the attendance line — an "Ab 2€ pro User" on the homepage against 4,50 € on annual and 6 € on monthly contracts on the pricing page — and extended onboarding as well as larger teams are quoted individually.
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.