ATOSS vs GFOS

ATOSS

Terminals, smartphones, tablets, PCs and even POS systems are all named capture channels, plus a mobile app with group bookings for mobile work crews and corrections that are traceably documented. But we found no public information on offline capture or geofenced check-in, which is what a field crew actually needs when the site has no signal.

GFOS

Terminal, mobile app and a shared tablet running as a multi-user terminal are all first-class capture paths, with offline storage that syncs when the server returns, QR-code and PIN login, and both a correction process for bookings and an approval flow for absences. I found no public information on an audit trail naming who changed which booking, and the GPS option is described as activated on demand without the vendor stating its limits — that keeps it just short of the top band.

ATOSS

The pages claim legally compliant, EuGH-conform recording and even explain the BAG confirmation, and rest-period requirements appear in the pay-rule description. But we found no public information on break rules, daily maximum hours, a retention period, or an export built for an inspection.

GFOS

The pages show working-time models in scheduling, automatic night, Sunday and holiday premium evaluation from recorded times, and a healthcare claim of complying with working time regulations with scheduling documentation — but we found no public information on break rules, daily-maximum or 11-hour rest checks, or a retention period for the time record itself; the privacy policy's retention statements cover website, application and business correspondence data, not the recording duty. If an inspector arrives, I would be assembling the record by hand.

ATOSS

Absence runs from request submission through electronic approval to tracking, with leave calendars and self-service balances, and scheduling covers replacements, shift swaps via the exchange board and manager-side plan changes on the go. We found no public information on automatic entitlement and carry-over, sickness recording, or public-holiday calendars per location.

GFOS

Nine vacation accounts with quota monitoring and remaining-leave capping, sickness split into initial, follow-up and work-accident cases with electronic certificate retrieval from the GKV server, a duty exchange platform with substitutes, and shift planning that matches qualifications, time models and capacities with conflict alerts during planning. We found no public information on public-holiday calendars per location, pro-rata entitlement, or rest-period checks and coverage warnings before the roster is published — that is the gap between here and the top.

ATOSS

Project times and direct booking to cost centres are shown, including from the customer site or the construction site, which is enough for payroll-side allocation. But we found no public information on rates, a billable flag, per-project reporting, or any handoff to invoicing.

GFOS

Bookings run to projects, sub-projects, tasks, activities, cost centres and locations with a billable flag, target/actual comparison, deviation alerts, a standard interface to a controlling system and an outbound transfer of evaluated times for invoicing. I found no public information on rates per person, role or project, nor on budget warnings or client-facing reports — and without rates, the recorded month never becomes an invoice without someone pricing it again.

ATOSS

A DATEV technology partnership is published for Time Control and the Staff Efficiency Suite, all data is said to transfer directly to the payroll system, and pay rules, premiums and overtime are applied automatically with discrepancies flagged before the run and corrections handled after initial processing — retro handling named in public, which I rarely see. We found no public information on night, Sunday and holiday surcharges, time accounts, or a lock step before transmission.

GFOS

Certified interfaces to DATEV, PAISY, SAP, LOGA and VEDA, over thirty payroll interfaces plus a neutral data-record format for anything individual; night, Sunday and holiday premiums are assigned to wage types automatically with competing wage types resolved by stored rules and priorities, absences synchronise downstream including cancellations and extensions, time and vacation accounts travel with the record, and integrated retroactive accounting catches corrections after the close, with test payrolls available before transmission. The piece I would not sign off on yet: we found no public information on an approval-and-lock step before the month is released, or on scoped access for the tax adviser.

ATOSS

A German SE with a published imprint, register and VAT number, a DPA linked in the footer, and a choice of cloud or on-premises deployment. But we found no public information on where the data is hosted or who the subprocessors are, so the chain is assumed rather than documented.

GFOS

The contracting entity is German to the letter — Essen register entry, German VAT number, named managing directors — with ISO 27001 certification and a privacy policy naming marketing subprocessors including HubSpot storing data on servers in Germany and the USA under an Art. 49 exception. But we found no public information on where the hosted time data resides, which data-centre provider runs it, or the product's own subprocessor chain — and for records I must defend to works council and auditor, a certificate is not a location.

ATOSS

No public prices anywhere in the captured pages — the only stated path is scheduling a demo. A buyer cannot compute an annual invoice for their headcount from what is published.

GFOS

Base, Professional and Enterprise packages and a bundles concept are named, but we found no public information on per-user prices, terminal hardware, module pricing, minimum terms or VAT treatment. A buyer cannot compute any part of the annual invoice for their headcount from the public pages; every figure is a sales conversation.