whats-best.ai

Time Tracking & Attendance

Clockify

Rest of world 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 CAKE.com Inc. · clockify.me

Compare with Toggl Track → 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 Payroll Officer

Weighted verdict

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.

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

Scored by The Payroll Officer

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 Payroll Officer

Timer, timesheet and manual entry run on web, desktop and mobile, a kiosk app clocks people in from a shared device, offline tracking syncs on reconnect, and GPS sits in the higher tiers — the capture paths are real. Corrections, though, are plain edits with approval sitting on timesheet submission, and the audit log that would tell me who changed what is an Enterprise-tier item. I found no public information on hardware terminals or badge readers. 1 3 4 2

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 Payroll Officer

The attendance report carries start, end, break 'if enabled', work time, and overtime measured daily, weekly or monthly against capacity, plus a lock-time feature — the shape of a record, but breaks appear only as a column, and I found no public information on rest-period checks, daily-maximum warnings, retention periods, or tamper-evident history outside the Enterprise audit log. Nothing in the captured pages maps any of this to the German recording duty. 5 2

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 Payroll Officer

Sickness, vacation, national holiday and half-day policies, balances with accruals, a leave timeline, approvers you can name, and a scheduling feature for shifts and assignments give a buyer the basics. I found no public information on vacation carry-over, per-location public-holiday calendars, or substitution and coverage checks before a roster is published. The beta overtime-to-time-off conversion at least keeps overtime and time off in one ledger. 7 8 6

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 Payroll Officer

Clients, projects and tasks with billable flags and rates, budgets with progress tracking, and an invoicing engine that imports only uninvoiced billable time, taxes it, and follows it through sent, paid and void — a genuine revenue pipeline rather than a report. Handoffs into named systems exist, QuickBooks and a Peppol e-invoicing add-on among them. I found no public information on cost centres as their own dimension, rate cards by role, budget overrun warnings, or how an open invoice behaves when a rate changes mid-project. 9 10 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 Payroll Officer

The QuickBooks Payroll add-on is named, documented and priced, but what it transmits is a billing payload — user, date, project, duration, description, billable status, billable rate — with no absence totals, no overtime, and above all no night, Sunday or holiday surcharges. The month-end trap is that once sent, entries cannot be sent again, so a corrected entry surfaces in a filter while the fix lands by hand in payroll; a lock-time feature exists, but I found no public information tying the lock to transmission. Everything else leaves as CSV or Excel, which tells me the handoff was never designed. 12 5

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 Payroll Officer

The contracting entity is CAKE.com Inc., a US company, and I found no public information on where the data is hosted or which subprocessors touch it. A data region is sold as a higher-tier feature, but the captured pages do not say which regions. For attendance data feeding a German payroll, that is not a footing I would sign. 2 9

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 Payroll Officer

All five tiers are priced publicly with the billing period stated — Free €0 for up to 5 users, Basic €3.99 per seat/month billed annually or €4.99 monthly, through Enterprise €11.99 or €14.99 — and the QuickBooks add-on carries its own price, $6.99 per month for the whole workspace. The kiosk's limited users come 'for a separate fee' that I found no number for, and I found no public information on VAT treatment or minimum term. The captured pages also give different figures for the per-user price, dollars on one page and euros on another, and I leave both as stated. 2 7 12 2

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 — 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.

Sources (12)

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

  1. 1 Vendor homepage clockify.me Checked 5 Oct 2026 +3 earlier captures: 15 Sep 2026, 30 Aug 2026, 30 Aug 2026 Details →
  2. 2 Pricing clockify.me Checked 5 Oct 2026 +3 earlier captures: 15 Sep 2026, 11 Sep 2026, 30 Aug 2026 Details →
  3. 3 Capture in the real workplace — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  4. 4 Capture in the real workplace — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  5. 5 Working-time law & audit record — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  6. 6 Working-time law & audit record — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  7. 7 Absence & shift planning — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  8. 8 Absence & shift planning — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  9. 9 Project, cost-centre & billing — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  10. 10 Project, cost-centre & billing — found from sitemap clockify.me Checked 5 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  11. 11 Payroll handoff — found from sitemap clockify.me Checked 5 Oct 2026 Details →
  12. 12 Payroll handoff — found from sitemap clockify.me Checked 5 Oct 2026 Details →