whats-best.ai
Search Sign in

Time Tracking & Attendance

ZEP

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by provantis IT Solutions GmbH · www.zep.de

Compare with clockodo → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Operations Lead

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Operations Lead

Capture in the real workplace

How this is scored

How time actually gets recorded across the workforces a buyer has — desk staff, field and site crews, shift and deskless workers — and what happens when the network is not there.

0 — One browser timer and nothing else; anyone away from a desk records nothing.

3 — Web plus a mobile app, but no offline capture, no shared terminal, and corrections are an admin task rather than a workflow.

5 — Web, mobile and at least one shared capture point (kiosk, terminal or badge), with offline capture that syncs, and a correction workflow with approval.

8 — Several capture paths including hardware terminals or badge readers, reliable offline handling, GPS or geofenced check-in where the vendor states its limits, and bulk correction with an audit trail of who changed what.

10 — Capture fits the workforce rather than the reverse: desk, deskless, field and shift models all first-class, offline as a designed state rather than a failure mode, and every correction attributable, reasoned and reversible.

Report an error

The Operations Lead

This is what I run an operation on, and the capture breadth holds up: browser, a mobile app for iOS and Android with offline storage that syncs when the connection returns, a tablet multi-user mode that simulates a terminal, and a separate hardware terminal, with GPS documented per stamp event and the vendor stating plainly that this does not restrict stamping to a fixed radius. What decides the deduction is corrections: the help pages show an administrator mode where times are edited, and I found no public information on a correction workflow with approval or on an audit trail of who changed a stamped time. 1 5 6

Report an error

Working-time law & audit record

How this is scored

Whether the record satisfies the German recording duty (BAG 2022, § 3 ArbSchG) and the ArbZG rules around it — breaks, maximum hours, rest periods, retention — and whether it survives being inspected.

0 — Hours are summed and nothing else; no break handling, no limits, no retention statement.

3 — Break deduction exists but is a flat rule; no daily maximum or rest-period checks, and no stated retention period.

5 — Configurable break rules, warnings on the 8/10-hour daily maximum and the 11-hour rest period, and per-employee reports covering the recording duty.

8 — The ArbZG rules are modelled rather than approximated: break and rest enforcement with documented exceptions, overtime and time-account rules, the two-year retention handled by the system, and an export built for an inspection.

10 — The vendor treats the record as evidence: tamper-evident entries with full change history, retention and deletion executed per statute, documented handling of on-call, standby and travel time, and published guidance mapping features to the ArbZG sections they serve.

Report an error

The Operations Lead

Individual working-time models and break rules per employee are documented, with an automatic overtime account, capping and per-employee settings, and the vendor markets 'Gesetzeskonforme Einstellungen' and minute-precise, legally compliant tracking. For a record I may have to hand to an inspector, I found no public information on warnings for the eight or ten-hour daily maximum, the eleven-hour rest period, a stated retention period, tamper-evident change history, or an export built for an inspection. 1 2 7 8

Report an error

Absence & shift planning

How this is scored

Vacation, sickness and the shift or duty roster — the half of attendance that decides whether the time data means anything.

0 — No absence handling; vacation lives in a separate calendar or spreadsheet.

3 — Vacation requests with approval, but entitlement is manual, carry-over is not handled and there is no rostering.

5 — Automatic entitlement and carry-over, sickness recording, an absence calendar, and basic shift planning with availability.

8 — Public-holiday calendars per location, pro-rata entitlement, substitution and swap workflows, shift templates with qualification and rest-period checks, and coverage warnings before publication.

10 — Planning and recording are one system: rosters that respect statutory rest and the works agreement, absence that reflows the plan automatically, and forecast-versus-actual reporting a team lead can act on.

Report an error

The Operations Lead

Absence is genuinely deep: approval by department managers and deputies with status workflow and email notification, sick leave with certificates, entitlement calculated and prorated automatically (their own worked example, 30 ÷ 12 × 5 = 12.5 days), month/week/day calendar views, and scheduling that shows overload warnings and cleans up planned entries on absence days in one go. But the planning evidence is project resource scheduling in hours, percentages and time slots rather than a duty roster; I found no public information on shift templates, swap or substitution workflows, qualification checks, or coverage warnings before a plan is published. 7 8 9 10

Report an error

Project, cost-centre & billing

How this is scored

Whether recorded time can carry the allocation an agency, workshop or professional-services firm needs — project, task, cost centre, billable status — through to an invoice or a client report.

0 — Attendance only; no project, task or cost-centre dimension at all.

3 — A free-text note or a single project field, with no rates, no billable flag and no per-project reporting.

5 — Projects and tasks with a billable flag and per-project reports, plus a rate per person or per project.

8 — Multi-level structure (client, project, task, cost centre), rate cards by person, role and project, budget tracking with warnings, and an invoice-ready export.

10 — Time becomes revenue without re-entry: approval before billing, rate rules that survive a rate change mid-project, client-facing reports, and a maintained handoff into named accounting or invoicing systems.

Report an error

The Operations Lead

Recorded time carries a billable flag, notes and favourites, hourly and daily rates with price groups per project and employee, cost centres drawn from project or employee master data, and flows on to invoices: released items from multiple projects billed in a single automated run, XRechnung and ZUGFeRD 2.1 output, and a DATEV or Lexware export. I found no public information on budget-tracking warnings or how rates are handled when they change mid-project, so I stop short of the top. 5 10 11 12 14

Report an error

Payroll handoff

How this is scored

How the recorded month reaches payroll — DATEV, Lohn und Gehalt, an in-house system or the tax adviser — and how much of it is automated rather than retyped.

0 — No payroll path stated; the month leaves as a spreadsheet someone retypes.

3 — Generic CSV said to be usable for payroll, with no named system, no defined format and no handling of surcharges.

5 — A named payroll integration or a documented export format for at least one major system, covering hours, absences and overtime.

8 — Vendor-maintained integration with a named provider, covering night, Sunday and holiday surcharges, time accounts and mid-month changes, with a lock step before transmission.

10 — Payroll is designed for, not exported to: several named systems maintained, an auditable approval and lock, retro handling for corrections after the close, and the tax adviser given their own scoped access.

Report an error

The Operations Lead

A named payroll path exists in headline form — synchronisation of 'Lohn & Gehalt' and LODAS with DATEV, and transfer of ZEP time bookings to Personio — which is more than a generic CSV claim. But the documented export formats I can actually read are about travel expense reports going to accounting, write-protected after export and feeding DATEV finalisation, and I found no public information on how hours, overtime, or night, Sunday and holiday surcharges reach payroll in a defined wage-type format. 1 7 13 14

Report an error

European sovereignty

How this is scored

Where the data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.

0 — Non-EU vendor and contracting entity, hosting region unstated or non-EU, subprocessors not named.

3 — EU hosting offered as an option, but the contracting entity is non-EU or the subprocessor list is absent.

5 — EU hosting as standard and an EU contracting entity, but the subprocessor chain includes non-EU providers without an explained safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, data-centre certification published, and an on-premises or private-cloud option for buyers who need it.

Report an error

The Operations Lead

Hosting and development in Germany, daily backups in several German data centres, and ISO 27001 certification covering ZEP and its cloud hosting partners are all stated plainly — that is the baseline I want for my workforce data. The chain is what is missing: the data-centre provider is not named, I found no published subprocessor list, and the contracting entity appears only as ZEP GmbH in a copyright line. 1 4 7

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual invoice for their headcount — including terminals, modules and minimums — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A per-user headline exists, but hardware, modules or a minimum seat count are unpriced or unmentioned.

5 — Per-user prices public for the main tiers with the billing period stated, but at least one commonly needed piece (terminal hardware, planning module, payroll export) sits in an unpriced bundle.

8 — Every tier and module priced publicly with per-user maths, billing period, minimum term and VAT treatment stated; only genuinely custom work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount and module selection, including hardware, setup and renewal terms.

Report an error

The Operations Lead

Per-user headline prices are public and monthly billing is stated — ZEP Clock 'Ab 2€ pro User', ZEP Compact 'Ab 7€ pro User', ZEP Professional 'Ab 18€ pro User' — alongside a free 14-day trial, no onboarding costs and monthly contract adjustments. But I found no public pricing for the add-on modules or terminals, including the absence module my roster depends on, and for teams above twenty-five or fifty users the pages move to an individual offer, so I cannot compute the annual invoice for 200 people from public pages alone. 1 2 3

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined — uncited Report an error

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about ZEP? Tell us Report an error on this page

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.zep.de Checked 5 Oct 2026 Details →
  2. 2 Pricing www.zep.de Checked 5 Oct 2026 +1 earlier capture: 30 Aug 2026 Details →
  3. 3 Features www.zep.de Checked 5 Oct 2026 +1 earlier capture: 30 Aug 2026 Details →
  4. 4 Security / trust page www.zep.de Checked 5 Oct 2026 Details →
  5. 5 Capture in the real workplace — found from sitemap support.zep.de Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  6. 6 Capture in the real workplace — found from sitemap support.zep.de Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  7. 7 Working-time law & audit record — found from sitemap www.zep.de Checked 5 Oct 2026 Details →
  8. 8 Working-time law & audit record — found from sitemap support.zep.de Checked 5 Oct 2026 Details →
  9. 9 Absence & shift planning — found from sitemap support.zep.de Checked 5 Oct 2026 Details →
  10. 10 Absence & shift planning — found from sitemap support.zep.de Checked 5 Oct 2026 Details →
  11. 11 Project, cost-centre & billing — found from sitemap support.zep.de Checked 5 Oct 2026 Details →
  12. 12 Project, cost-centre & billing — found from sitemap www.zep.de Checked 5 Oct 2026 Details →
  13. 13 Payroll handoff — found from sitemap support.zep.de Checked 5 Oct 2026 Details →
  14. 14 Payroll handoff — found from sitemap support.zep.de Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →