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 Payroll Officer
Turns the recorded month into an payroll run and answers for it. Cares about surcharges for night, Sunday and holiday work, time accounts that reconcile, and corrections that arrive after the close. Treats "export to CSV" as an admission that the handoff was never designed.
clockodo
ZEP
This judge's pick
Criterion by criterion
Capture in the real workplace
clockodo
Browser, desktop and smartphone apps plus a shared time-recording terminal are documented, offline capture runs in the background and syncs automatically once a connection exists, and retroactive entries carry a change vermerk with edit locks and digital signatures on the work record. We found no public information on GPS or geofenced check-in or on bulk correction, which holds this below the top band.
ZEP
Clocking runs in the browser, in iOS and Android apps and on a hardware terminal, and the Clock App's multi-user mode turns a tablet into a shared terminal with an administrator PIN. Location per stamp is documented with the vendor's own limits — position recording, not a geofence — and offline entries sync automatically, though the vendor states that unsynced offline data is lost on logout. Corrections appear only as an administrator editing employee times; we found no public information on bulk correction with an audit trail of who changed what.
Working-time law & audit record
clockodo
The EuGH 2019 and BAG 2022 rulings are cited, begin, end, duration and breaks are recorded, break rules are configurable and can be enforced with warnings to employee and employer, and hours accounts show overtime balances live. But the vendor's own help centre states the automatic break deduction books no break period, so at an inspection it would not be evident when the employee took a break unless it is recorded manually — a candid gap which, together with no described handling of the statutory retention or of documented exceptions, keeps this in the middle band.
ZEP
Start and end are stamped minute-exact with configurable break rules, individual working-time models and an automatic overtime account, and the vendor's pricing page claims tracking of minimum rest time, break times and maximum working time. Surcharges for public holidays and special times can be reported as time supplements into the overtime account, which is what a payroll run needs. We found no public information on retention, a change log on entries, or an export built for an inspection.
Absence & shift planning
clockodo
Ten absence types from vacation through quarantine to maternity protection, automatically calculated leave accounts with remaining leave, country-specific public holidays, approval configurable per absence type, a shared team calendar, and absences standing ready for preparative payroll. We found no public information on shift or duty roster planning, so only half of this criterion is proven.
ZEP
Absences are handled properly: requests with approval by administrators, department managers or deputies, sick leave with certificates, month/week/day calendar views, team calendars and holiday calendars, and pro-rata entitlement calculated per started month with a worked example. What sits beside it is project resource planning — availability that automatically subtracts absences and holidays, with overload warnings — not a shift or duty roster. We found no public information on shift templates, qualification checks, or substitution and swap workflows.
Project, cost-centre & billing
clockodo
Client, project, subproject and service sit directly on the time entry together with hourly rate, billability, flat rates and budgets with warnings, and invoice drafts arise in Lexware Office, sevdesk or easybill from the recorded times without retyping. We found no public information on cost centres or on how a rate change mid-project is handled, which keeps the top band out of reach.
ZEP
Time is booked to clients, projects, sub-projects and activities with a billable switch, cost centres per project with a per-employee fallback, and hourly rates from the price group of the project-employee assignment. Released invoice items feed automated invoicing with XRechnung and ZUGFeRD 2.1, consecutive invoice numbering and a handoff to DATEV and Lexware accounting. Budget tracking is the gap for an agency buyer: project controlling and revenue and cost calculation are documented, but we found no public information on budget warnings.
Payroll handoff
clockodo
The DATEV Lohn und Gehalt connection is documented down to client and consultant numbers from the tax adviser, the personnel-number type and the wage-type mapping, with hours and absences covered. But the vendor's own documentation states the export is available exclusively for hourly-wage recipients and that employees who received surcharges in the export period are skipped — for a month with night, Sunday or holiday work, precisely the people I must surcharge travel another route — and no lock step before transmission is described.
ZEP
DATEV is named for payroll — synchronisation of Lohn & Gehalt and LODAS — and the payroll accounting export is included in all product lines, which clears the bar of a named major system. The detailed export documentation I read concerns expense bookings rather than the payroll file; night and Sunday surcharges are not named, only surcharges for public holidays and special times added to the overtime account. We found no public information on mid-month changes, a lock step before transmission, or retro handling after the close — closed months are simply read-only.
European sovereignty
clockodo
A German contracting entity and named Microsoft Azure datacentres in Frankfurt and Berlin with ISO 27001 certification, emergency backups at Hetzner, a self-serve Article 28 data processing agreement, and a published subprocessor list with locations in which the US processors Stripe and Sentry are named with the Data Privacy Framework and standard contractual clauses. We found no public information on an on-premises or private-cloud option, so the record stops at the strong band.
ZEP
The captured pages state hosting and development in Germany, daily automatic backups in several German data centres, GDPR conformity, and ISO 27001 certification for ZEP and its cloud hosting partners — more than one proven European element, and hosting as the standard rather than an option. We found no public information confirming the contracting entity's jurisdiction, a data processing agreement, or the subprocessor list.
Pricing transparency
clockodo
Every tier carries a public net per-user price with billing period, term, cancellation, VAT treatment and payment methods, no base fee, and a stated two-euro package surcharge per user per month. The captured pages give different figures for Pro and Pro Plus — first-year discounted prices on one, 9,50 € and 11,40 € per month per user on others — and the terminal is listed as a feature without a price, so a buyer still cannot compute one certain annual invoice.
ZEP
All five lines carry public per-user prices for annual and monthly payment with VAT stated as excluded, and the three surcharge positions are fixed prices: Ressourcenplanung 5 €, Ticketsystem 4 €, ZEP-Terminal 15 €. A price calculator shows list prices for a chosen line, team size and add-ons, and onboarding is stated as cost-free. Full computability stops at larger teams, which move to individual offers, and we found no public information on renewal terms.
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.