whats-best.ai
Search Sign in

Time Tracking & Attendance

GFOS

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 dimensions proven

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

by GFOS mbH · www.gfos.com

Compare with ATOSS → 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 Skeptic

Weighted verdict

Has read a great many pages claiming to be "BAG-konform" and wants to know which feature makes that true. Reads compliance claims for what they do not say: which module, at which tier, and whether the terminal in the photograph costs extra.

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

Scored by The Skeptic

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 Skeptic

The Terminal App pages show a designed offline state — bookings stored locally during network outages and synced when the server returns — plus shared-device multi-user mode with PIN or QR login, and GPS recording the vendor states must be explicitly activated. Capture paths multiply across the GFOS app, a smartphone or tablet turned into a terminal, and stationary terminals referenced with QR-code clocking, while project times carry a subsequent correction process. We found no public information on bulk correction or an audit trail attributing who changed which booking. 4 5 8

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 Skeptic

For a German vendor whose whole pitch is wage types and collective-agreement logic, we found no public information on the recording duty, break rules, rest periods or daily maximums; the closest is a healthcare claim of complying with working time regulations. Retention figures on the privacy page concern website and accounting data, and we found no public information on retention of the time record itself, change history, or an export built for an inspection. Overtime valuation, time accounts and working-time models are real infrastructure, but the ArbZG mechanics are unevidenced. 1 9 10 3

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 Skeptic

Entitlement monitoring with up to nine vacation accounts and configurable remaining-leave capping, differentiated sickness cases with eAU and EEL handling, substitution, and a duty-exchange platform sit beside conflict warnings, qualification-matched shift suggestions and a planning book — planning and recording are visibly one connected system. We found no public information on per-location public-holiday calendars, pro-rata entitlement for part-timers, or rest-period checks before a roster is published, which is precisely the compliance-adjacent half of rostering. 5 6 7

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 Skeptic

Working times book to projects, sub-projects, tasks and locations with a billable flag, per-project reports, deviation monitoring, cost-centre aggregation and a defined transfer of evaluated times to another system for invoicing. We found no public information on rate cards per person, role or project, or on budget tracking with warnings — the two pieces that turn booked time into a priced invoice without re-entry. 8 10

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 Skeptic

Certified, named interfaces to DATEV, PAISY, SAP, LOGA and VEDA among over thirty payroll connections, automatic night, Sunday and holiday premiums assigned to wage types, absence synchronisation on cancellation or extension, retroactive accounting and click-through test payrolls make this the most thoroughly evidenced capability across these pages. We found no public information on an approval or lock step before the monthly transmission, or on scoped access for the tax adviser. 9 10

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 Skeptic

The contracting entity is German — GFOS mbH in Essen, registered at the Essen court with a German VAT number — and the privacy policy names its website processors, including HubSpot with data stored in Germany and the USA under an Art. 49 derogation. We found no public information on where the workforce data itself is hosted, on a data-centre provider, or on the product's own subprocessors; "Made in Germany" and ISO 27001 certification do not state a hosting region. 2 3 1 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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 Skeptic

Tier names — Base, Professional, Enterprise — and bundle language appear on the product pages, but we found no public prices at all: no per-user figure, no billing period, no hardware price for the terminals the product references, no minimum seat count, no VAT treatment. A buyer can learn that tiers exist, not what any of them costs, so nothing about the annual invoice can be computed from what is published. 1 7 9

Report an error

European sovereignty — proven facts

1 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 ⚠ unverified — 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 GFOS? Tell us Report an error on this page

Sources (10)

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

  1. 1 Vendor homepage www.gfos.com Checked 17 Sep 2026 +1 earlier capture: 30 Aug 2026 Details →
  2. 2 Imprint www.gfos.com Checked 17 Sep 2026 Details →
  3. 3 Privacy policy www.gfos.com Checked 17 Sep 2026 Details →
  4. 4 Capture in the real workplace — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  5. 5 Capture in the real workplace — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  6. 6 Absence & shift planning — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  7. 7 Absence & shift planning — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  8. 8 Project, cost-centre & billing — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  9. 9 Payroll handoff — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →
  10. 10 Payroll handoff — found from sitemap www.gfos.com Checked 1 Oct 2026 Details →