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 Agency Owner
Bills forty people's hours to clients and lives on the gap between recorded and billable. Wants project structure, rate cards that survive a mid-project change, budget warnings before the overrun, and an export the invoicing system takes. Attendance compliance is the floor, not the product.
clockodo
ZEP
This judge's pick
Criterion by criterion
Capture in the real workplace
clockodo
Browser, desktop and mobile apps with a punch clock that runs through project changes, a terminal connection, and offline capture that syncs automatically — that covers my desk staff and my site visits. Retroactive entries are supported and a note is left when someone changes an entry, and timesheets can be locked and digitally signed; we found no public information on GPS or geofenced check-in, badge readers, or bulk correction.
ZEP
Time comes in through the browser, the iOS and Android apps, a shared multi-user device mode and a separate hardware terminal — the mix a desk-and-field workforce needs. GPS is documented honestly as position capture per stamp event rather than a geofence, and offline bookings sync on reconnect, though the pages state unsynced offline entries are lost at logout. We found no public information on employee-requested corrections with an audit trail of who changed what.
Working-time law & audit record
clockodo
The vendor names the BAG ruling of 2022 and the duty in force since September 2022, records start, end and breaks to the minute, and lets me configure and enforce break rules with warnings to both employee and employer, alongside overtime hours accounts. A change annotation on edited entries and lockable, digitally signed timesheets strengthen the record, but the vendor itself states the automatic break deduction books no break period, so an inspection would not show when a break was taken unless the employee records it.
ZEP
Break rules and individual working-time models are configurable per employee, an overtime account with automatic capping runs against regular working hours, closed months become read-only, and the pages state that minimum rest, breaks and maximum working time are tracked. We found no public information naming the statutory basis of the recording duty, retention periods, or a change log on individual entries.
Absence & shift planning
clockodo
The absence half is solid: ten absence types, automatic vacation accounts with remaining leave, country-specific holidays, approval configurable per absence type, a team calendar and Outlook or Google sync. We found no public information on shift or duty planning — no rosters, templates or coverage — so the planning half of the criterion rests on nothing published.
ZEP
Absence is thoroughly handled: approval workflow with withdrawal, sickness with certificates, holiday calendars, pro-rata entitlement across multiple employment periods, and deputy and team calendars. The resource planning module schedules capacity with an availability figure that subtracts absences and holidays and flags overload, though it is capacity planning rather than shift rostering — we found no public information on shift templates with qualification or rest-period checks, or on swap workflows.
Project, cost-centre & billing
clockodo
This is what I bill on: customer, project, sub-project and service with the hourly rate and billable status set right at capture, time and money budgets with warnings and interval budgets, lump sums for things like travel costs, and a click-handoff of invoice items into Lexware Office, sevdesk or easybill where the draft is built. We found no public information on cost centres, on rate cards per person or role, or on how a rate change mid-project is handled.
ZEP
This is the core of the product: time books to customer, project and task with a billable flag, rates come from price groups on the project-employee assignment, released invoice items feed automated invoicing with XRechnung and ZUGFeRD formats, and the accounting export covers DATEV, Lexware and generic CSV with cost centres and multi-company internal charging. We found no public information on budget overrun warnings or how a rate change applies mid-project.
Payroll handoff
clockodo
A DATEV Lohn und Gehalt connection is documented in detail — client and consultant numbers, wage-type mapping, personnel-number type — and recorded absences stand ready for preliminary payroll. But the vendor states the export is available exclusively for hourly-wage recipients and skips anyone who received surcharges in the period, which pushes my night and holiday work outside the export; we found no public information on a lock step before transmission.
ZEP
A payroll export is included in every product line, the pages name synchronisation with DATEV Lohn und Gehalt and LODAS, and the month-end closing locks entries while holiday and special-time supplements are tracked on the overtime account. We found no public information on how night, Sunday and holiday surcharges or mid-month corrections travel in the payroll handoff itself.
European sovereignty
clockodo
Clockodo GmbH in Unna is the contracting entity, customer data sits in ISO 27001-certified Microsoft datacentres in Frankfurt and Berlin with emergency backups at Hetzner, and the Article 28 data processing agreement downloads as a PDF. The subprocessor list is published with locations, and the US processors Stripe and Sentry are named with the Data Privacy Framework and standard contractual clauses as their basis; we found no public information on an on-premises or private-cloud option.
ZEP
Hosting, development and daily backups are stated to be in Germany across multiple data centres, the vendor and its cloud hosting partners are ISO 27001 certified, and GDPR conformity is claimed throughout. We found no public information on a data processing agreement, the full subprocessor list, or a named data-centre provider.
Pricing transparency
clockodo
Per-user prices for three tiers, a plus package at a stated +2 € per-user surcharge, no base fee, monthly and annual terms with the annual discount of 5 %, auto-renewal, net prices plus statutory VAT, payment methods and a permanent free single user are all public — I can nearly compute my annual invoice. Two caveats: the captured pricing pages give different figures for the Pro and Pro Plus tiers, and we found no public information on the price of the terminal connection.
ZEP
Every product line carries a public per-user price in both annual and monthly variants, VAT treatment is stated, the add-ons and the terminal have fixed published prices, and a price calculator shows list prices for a chosen team size and module selection. The captured pages give different product line names and figures at different dates, but both sets are fully public; only extended onboarding carries a fee without a published amount. I can almost compute my forty-person invoice from these pages alone.
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.