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 Field Supervisor

Weighted verdict

Supervises crews on sites with no reliable signal and no desks. Judges everything by whether it works in a basement at 6am: offline capture, a shared terminal, corrections a foreman can make without a support ticket. A cloud-only app is a tool that will be filled in from memory on Friday.

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

Scored by The Field Supervisor

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 Field Supervisor

The Clock App punches in single-user and multi-user modes where a tablet on site simulates a terminal with PIN logins, there is a separate hardware terminal, and bookings made offline sit on the device and sync the moment signal returns — kit a foreman can run in a stairwell at 6am. Location is GPS per stamp event with the vendor plainly stating it does not restrict stamping to a fixed radius, and an administrator can edit times on the device itself. We found no public information on an audit trail showing who corrected what after the fact. 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 Field Supervisor

Working time is recorded to the minute with configurable break rules and individual working-time models per employee, an automatic overtime account with capping, and the Clock line is sold with gesetzeskonforme Einstellungen. But we found no public information on warnings for the daily 8/10-hour maximum or the 11-hour rest period, and no stated retention period — for an inspection those are the first questions. 3 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 Field Supervisor

Absence is genuinely handled: full, half and hourly requests with approval statuses and role-based approvers, sick notes with certificates, month-end locking, weekend and holiday blocking, and vacation entitlement prorated by employment period with remaining vacation on the dashboard. Planning is capacity scheduling — percentages of regular working time made day-precise with overload warnings — rather than duty rosters; we found no public information on shift templates with rest-period checks or swap workflows. 6 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 Field Supervisor

This is the vendor's home ground: customer, project and task master data, cost centres from project or employee, price groups with hourly and daily rates, a billable flag on every booking, release before billing, and automated invoicing with XRechnung and ZUGFeRD feeding DATEV or Lexware. We found no public information on budget tracking with overrun warnings. 5 10 11 12

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 Field Supervisor

A DATEV synchronisation covering Lohn & Gehalt and LODAS is named, and documented DATEV, Lexware and general CSV exports exist — but the export we can read documented carries internal travel expenses rather than hours and overtime, and the accounting export module sits only in the top tier. We found no public information on how night, Sunday and holiday surcharges reach payroll, or on a lock step before transmission. 1 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 Field Supervisor

Hosting and development are stated as Germany, with daily backups across several German data centres, ISO 27001 certification covering ZEP and its cloud hosting partners, and the site copyright names ZEP GmbH. We found no public information on a published subprocessor list or a named data-centre provider, so the chain behind those German servers cannot be checked before signing. 1 2 4

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 Field Supervisor

Per-user prices are public for all three tiers — ZEP Clock Ab 2€ pro User, ZEP Compact Ab 7€, ZEP Professional Ab 18€, monthly billing, no onboarding costs, free premium support — and a price calculator is offered. But the add-on modules and the terminals the plans point to carry no public prices, and above 25, 50 or 100 users depending on tier the price becomes an individual offer, so a larger buyer cannot compute the annual invoice alone. 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 →