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? →

Link to this page

ZEP: AI-assisted analysis on whats-best.ai ZEP: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

ZEP at a glance

Vendor
provantis IT Solutions GmbH
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Default not stated; pages mention Germany source, captured 5 Oct 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates ZEP 3/5, the mean of 6 judges. ZEP, a project time-tracking suite from provantis IT Solutions GmbH of Ditzingen, splits the judges little: no criterion spreads more than two points. how scores are made
As of
Vendor pages captured 30 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

ZEP alternatives, European ones first →

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

The panel's verdict

ZEP, a project time-tracking suite from provantis IT Solutions GmbH of Ditzingen, splits the judges little: no criterion spreads more than two points. Its centre of gravity is project and billing, a flat 8 — time booked to clients, projects and subprojects, rates from price groups per project-employee assignment, automated invoicing in XRechnung and ZUGFeRD 2.1, and DATEV and Lexware exports documented down to encoding and column counts. Pricing transparency follows at 8-9: public annual and monthly per-user prices on every line, VAT stated as excluded, fixed add-ons and a list-price calculator. Sovereignty scores 4 across the bench — hosting and development in Germany and ISO 27001 certification covering ZEP and its cloud hosting partners are stated, but the judges found no public information on a data processing agreement or subprocessor list — and working time law scores 4-5, with no public information found on retention, change history or employee-initiated corrections. The widest spread, payroll export at 5-7, turns on the handoff: holiday and special-time supplements and a read-only month close are shown, but the detailed export pages captured concern travel costs.

Report an error

Speaks for it

  • Time books to clients, projects and subprojects with a billable switch and rates from price groups per project-employee assignment
  • Released invoice items bill automatically in XRechnung and ZUGFeRD 2.1, with consecutive invoice numbering
  • Accounting exports to DATEV and Lexware are documented down to file encoding and column counts
  • Absence handling covers an approval workflow with withdrawal, sickness with certificates and pro-rata holiday entitlement with a worked calculation example
  • All five product lines publish annual and monthly per-user prices with VAT stated as excluded, plus fixed add-on prices, a list-price calculator and a 14-day trial stated without credit card

Report an error

Held against it

  • Unsynced offline entries are lost on logout, per the vendor's own help pages
  • We found no public information on a change log of who edited a stamp, on retention periods, or on an employee-initiated correction flow
  • We found no public information on a data processing agreement, a subprocessor list with locations, or a named data-centre provider
  • The documented planning module is project resource scheduling; we found no public information on shift templates or swap workflows
  • The captured pages give different figures for ZEP Clock's per-user price and for when team pricing becomes individual, and extended onboarding carries no published fee

Report an error

Best for

  • You bill client project time and want invoices generated from the record itself — project and billing scored a flat 8
  • Your accounting runs on DATEV or Lexware and you need the export format documented before you buy
  • You want to compute your monthly cost from public list prices before contacting sales, on a team below the size where pricing becomes individual
  • You need a complete absence workflow — requests, approvals, sickness certificates and pro-rata holiday entitlement — alongside project time capture, where absence and planning scored 6-7

Report an error

Avoid if

  • You plan duty in shift rosters — the documented planning module is project resource scheduling, and we found no public information on shift templates or swap workflows
  • You must evidence working-time records to a works council or auditor — the closest control shown is a month-end lock making closed months read-only, and we found no public information on change history or retention
  • Your payroll export needs night and Sunday surcharges — the pages document holiday and special-time surcharges as time supplements into the overtime account; night and Sunday are not named
  • You need a firm published price for a large rollout — larger teams move to individual offers on the captured pricing pages, and extended onboarding is charged without a published rate

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Capture in the real workplace 3.5 of 5
Working-time law & audit record 2.5 of 5
Absence & shift planning 3 of 5
Project, cost-centre & billing 4 of 5
Payroll handoff 3 of 5
European sovereignty 2 of 5
Pricing transparency 4 of 5

Capture in the real workplace

Show reasoning
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 — Not a time-recording tool; working time cannot be captured in the product.

3 — Clocking in and out or a timer in the browser or an app, with manual entries; offline use, shared terminals and corrections are basic or not described.

5 — Web and mobile apps for clocking in and out, a shared kiosk, terminal or badge option or offline capture that syncs, and corrections requested by the employee and approved by a manager.

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

There is a path for each of my groups: browser stamping for the desk, iOS and Android apps for the field, a tablet multi-user mode that simulates a terminal for the workshop, and a separate hardware terminal at a fixed monthly per-device price. The vendor is refreshingly explicit that GPS records the position per stamp event rather than fencing a radius. What holds me back: offline bookings not yet synced are lost on logout, and I found no public information on employee-initiated corrections or a change history showing who edited a stamp. 1 6 6 5 6 3

Report an error

The Payroll Officer

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. 6 6 5 6

Report an error

The Works Council Advocate

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. 1 5 6 6 5 6

Report an error

The Agency Owner

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. 1 5 6 5 6

Report an error

The Field Supervisor

Time comes in three ways a crew can actually use: browser, phone app, and a real hardware terminal, plus a tablet multi-user mode that simulates a terminal on site where several people stamp in turn. Offline capture works for project times and receipts and syncs on reconnect, but the vendor's own pages state that unsynced offline entries are lost on logout — that will bite a foreman in a dead-zone basement — and GPS is documented honestly, position recorded per stamp with no automatic radius restriction. Corrections run through an admin PIN on the device; we found no public information on a change log showing who corrected what. 1 5 6 5 6

Report an error

The Skeptic

Capture runs through an app for iOS and Android, the browser, a hardware ZEP Terminal priced at 15 € per terminal and month, and a shared multi-user device that simulates a terminal; the help pages state plainly that GPS records the position per stamp event and does not restrict stamping to a fixed radius. Offline capture of project times and receipts syncs automatically, though the same pages state that unsynced offline entries are lost on logout. We found no public information on employee-requested corrections, bulk correction, or an audit trail of who changed what — editing is described via an admin PIN. 5 6 6 5 3

Report an error

Working-time law & audit record

Show reasoning
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 — A project or task timer that keeps no attendance record of working time (start, end, breaks).

3 — Start, end and break times recorded per day with a working-time report per employee; ArbZG checks and retention are basic or not described.

5 — Start, end and breaks recorded for the recording duty (BAG 2022 or ArbZG named), automatic break rules, warnings on the daily maximum or the rest period, and overtime balances.

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, a change log on entries, 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

Start and stop times, configurable break rules and standard working hours per weekday are documented, with an automatic overtime account, month-end locking, and a statement on the pages that minimum rest, breaks and maximum working time are tracked. But I found no public information naming the 2022 labour-court ruling or the Working Time Act itself, nor on retention periods, a change log on entries, or an export framed for an inspection. 7 2 7 8 9

Report an error

The Payroll Officer

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. 2 7 8 7

Report an error

The Works Council Advocate

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. 1 9 7 2 8 7

Report an error

The Agency Owner

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. 7 2 8 9 9

Report an error

The Field Supervisor

The vendor claims times are tracked to the minute 'rechtssicher', names the statutory concepts — minimum rest, break times, maximum working time — as trackable, and lets you define working-time models and break rules per employee with an automatic overtime account and capping. Holiday and special-time surcharges can flow into the overtime account, and closed months go read-only with a lock that even splits periods at the boundary. We found no public information on retention periods, a change log on entries, or the recording duty and ArbZG cited by name. 1 7 2 8 9

Report an error

The Skeptic

Working-time models, break rules and absence policies are configurable per employee, an automatic overtime account with capping runs against them, working-time reports exist per employee and team, and a captured pricing page states that minimum rest time, break times and maximum working time can be tracked. We found no public information on warnings on the daily maximum, statutory retention, or a change log on entries, and we found no public information naming BAG, ArbZG or ArbSchG. 2 8 7 7

Report an error

Absence & shift planning

Show reasoning
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 — Neither absence handling nor shift planning is part of the product.

3 — Vacation requests with approval and an absence calendar, or a basic shift plan; entitlement rules and rostering are basic or not described.

5 — Absence management with entitlement balances, sickness recording and an absence calendar, plus shift or duty planning with templates or employee availability.

8 — Public-holiday calendars per location, pro-rata entitlement and carry-over, 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

The absence half is deep: full-day, half-day and hourly requests with approval workflow and withdrawal, sick leave, a second reason per day, holiday calendars, deputy sharing, and pro-rata entitlement with a worked calculation example. The planning module is project resource scheduling in a matrix with availability that subtracts absences and an overload warning — I found no public information on shift templates, qualification checks, swap workflows, or a duty roster my workshop crews would recognise. 8 9 10 7

Report an error

The Payroll Officer

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. 9 8 10 10

Report an error

The Works Council Advocate

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. 8 9 10 8 9 10

Report an error

The Agency Owner

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. 9 9 8 10 3

Report an error

The Field Supervisor

The absence half is done properly: requests with approval by admins and department managers, withdrawal before decision, sick notes with certificates attached, colour-coded calendars with holiday calendars and team views, and pro-rata vacation entitlement per employment period with a worked calculation example. What is documented as planning is project resource planning — a scheduling matrix whose availability subtracts absences and holidays and flags overload with a red marker — not a shift or duty roster. We found no public information on shift templates, swap workflows or qualification checks. 9 8 9 10

Report an error

The Skeptic

Absence handling is complete: request workflow with statuses and email notification, sickness with certificates, holiday and team calendars, and pro-rata holiday entitlement with a worked calculation example for mid-year joiners. Planning is resource allocation rather than rostering — standard and specific scheduling in percent, hours or time slots with overload warnings and availability that subtracts absences, offered as a 5 € per-user add-on — and the vendor documents that schedulings on absence days are removed through a manual link rather than automatically reflowed. We found no public information on shift templates, qualification or rest-period checks, or swap workflows. 9 8 10 3

Report an error

Project, cost-centre & billing

Show reasoning
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; the product records time without any project, task or cost-centre dimension.

3 — Time booked to projects or clients with a report per project; rates and billable status are basic or not described.

5 — Projects and tasks with a billable flag, hourly rates, reports per project and client, and an export or integration toward invoicing.

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

This is the vendor's home ground: time books against customers, projects, subprojects and tasks with a billable switch, rates via price groups per project and employee, cost centres per project with an employee fallback, and invoicing automated from released items with XRechnung and ZUGFeRD 2.1 output plus a DATEV invoice-data synchronisation. I found no public information on budget warnings or client-facing reports. 5 1 1 10 11 12

Report an error

The Payroll Officer

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. 1 10 14 11 12

Report an error

The Works Council Advocate

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. 2 11 5 14 10 11 12

Report an error

The Agency Owner

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. 1 5 10 11 14 12

Report an error

The Field Supervisor

This is the vendor's home ground: time books against customer, project and subproject with a billable switch, hourly and daily rates with price groups per project-employee assignment, and cost centres taken from the project with an employee fallback. Released invoice items are billed in one automated run across projects and customers, invoices go out as XRechnung and ZUGFeRD 2.1, and DATEV or Lexware exports hand the result to accounting without retyping. We found no public information on budget tracking with warnings or on rate rules surviving a rate change mid-project. 11 1 10 14 12

Report an error

The Skeptic

Time books against clients, projects and subprojects with a billable toggle, cost centres per project with an employee fallback, and hourly and daily rates via price groups per project-employee assignment, with plan-versus-actual figures and planned turnover in the scheduling matrix. Released invoice items are billed automatically with XRechnung and ZUGFeRD 2.1 formats, and the DATEV and Lexware handoffs are documented down to file encoding and column counts. We found no public information on rate cards by role or budget warnings. 1 10 11 12 1

Report an error

Payroll handoff

Show reasoning
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 — Payroll is outside the product: it records client or project time only and prepares nothing for payroll.

3 — An export (CSV, Excel or PDF) of hours and absences for the payroll office; named formats and surcharges are basic or not described.

5 — A named payroll integration or a documented export format for at least one major system (e.g. DATEV LODAS/Lohn und Gehalt), 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 payroll accounting export is included in every product line, DATEV Lohn und Gehalt and LODAS are named synchronisation targets, holiday and special-time surcharges can be carried as time supplements into the overtime account, and closed months are read-only. I found no public information on night and Sunday surcharges, corrections after the month closes, or scoped access for my tax adviser. 9 1 8 14

Report an error

The Payroll Officer

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. 1 14 8 9

Report an error

The Works Council Advocate

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. 9 1 8 14 3

Report an error

The Agency Owner

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. 1 14 3 9 8

Report an error

The Field Supervisor

A payroll accounting export is in every product line, DATEV is named for Lohn & Gehalt and LODAS, and Personio receives time bookings and master data — the month can be locked read-only before the close. Surcharge handling exists for public holidays and special times, reported as time supplements into the overtime account. We found no public information on night and Sunday surcharges, mid-month changes, or retro corrections after the close. 1 8 9 14 3

Report an error

The Skeptic

A payroll export is included in every product line, DATEV Lohn & Gehalt and LODAS are named as synchronization targets, time bookings transfer to Personio, and time supplements for holidays and special times exist as a settings option. The export documentation captured in detail concerns travel-cost accounting rather than payroll; we found no public information on the payroll export's exact contents, night, Sunday and holiday surcharges, or a lock step before transmission. 14 1 8 9

Report an error

European sovereignty panel opinion

Show reasoning
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. Dimensions not proven either way are unknown, not non-European.

0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.

5 — An EU contracting entity and EU hosting stated, with a data processing agreement; the subprocessor list is not published in full or includes non-EU providers without a stated safeguard.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, the full subprocessor list published with locations, 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 are stated across several pages, with daily backups in multiple German data centres and ISO 27001 certification stated to cover the cloud hosting partners. Beyond that the chain is thin: I found no public information confirming a data processing agreement, and no subprocessor list or named data-centre provider appears on the pages I read. 1 4 7 3

Report an error

The Payroll Officer

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. 4 4 1

Report an error

The Works Council Advocate

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. 1 4 4 7 7

Report an error

The Agency Owner

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. 4 1 7 1 7

Report an error

The Field Supervisor

The vendor's own pages state hosting and development in Germany, daily backups across several German data centres, GDPR conformity, and ISO 27001 certification covering ZEP and its cloud hosting partners — that is more than one European element proven from the source. We found no public information on a data processing agreement, the contracting entity's jurisdiction, or any subprocessor list. 1 4 4

Report an error

The Skeptic

The vendor's own pages state hosting and development in Germany, daily backups in several German data centres, and ISO 27001 certification covering ZEP and its cloud hosting partners, with the vendor given as provantis IT Solutions GmbH of Ditzingen. We found no public information on a data processing agreement, the named data-centre provider, or a published subprocessor list with locations. 1 7 4 7

Report an error

Pricing transparency

Show reasoning
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 public "from" price per user or one priced tier; how cost scales with modules, hardware or minimum seats is unclear.

5 — Per-user prices public for the main tiers with the billing period stated and the main inclusions given; some pieces (terminal hardware, planning module, payroll export) may be unpriced.

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

Every product line carries a published annual and monthly per-user price, VAT is stated as excluded, and the planning, ticket-system and terminal add-ons each carry a fixed monthly figure, with a calculator showing the cost of a chosen setup at list prices. For my own size the caution is real: the pages state individual pricing for teams above 100 users, so my 200-person annual invoice would be a negotiated number, and extended onboarding such as data migration is charged without a published rate. 2 2 3 3

Report an error

The Payroll Officer

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. 3 2 3 2

Report an error

The Works Council Advocate

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. 1 2 2 3 3

Report an error

The Agency Owner

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. 3 2 2 2 3

Report an error

The Field Supervisor

A price calculator shows list prices for the chosen line, team size and add-ons, every line carries both a monthly and an annual per-user price, VAT is stated as zzgl. MwSt., and even terminal hardware is listed at 15 € per terminal per month with fixed-price add-ons. Terms are spelled out: monthly contract adjustments, cancellation anytime, annual contract up to 25 % cheaper, 14-day trial with no credit card. The captured pages give different figures for ZEP Clock ('Ab 2€ pro User' versus 4,50 € and 6 € in the line table), and we found no public number for the extended onboarding and migration fee. 1 2 2 3

Report an error

The Skeptic

Every product line carries a per-user price for annual and for monthly billing with VAT treatment stated, the three paid add-ons and the terminal at 15 € per terminal and month are public, a calculator is offered on list prices for a chosen setup, and onboarding is stated as free of one-off costs. The captured pages give different figures for ZEP Clock's per-user price and for the team sizes at which pricing becomes individual, and the fee for extended onboarding carries no number. 3 2 2 2

Report an error

European sovereignty — proven facts

0 of 6 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.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about ZEP

Is ZEP European?

Yes. whats-best.ai classifies ZEP as EU-Made.

Where does ZEP store data?

The default storage location for customer data is not stated on the vendor’s pages as of 16 Nov 2026. The vendor’s pages mention Germany as hosting location, per the vendor’s page captured 5 Oct 2026.

Does ZEP have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to ZEP?

As of 18 Nov 2026, the panel rates TimeTac (3.5/5), clockodo (3/5) and GFOS (3/5) highest among the other 32 Time Tracking & Attendance products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is TimeTac (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: ZEP alternatives.

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.

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