ATOSS vs GFOS

ATOSS

Terminals, smartphones, tablets, PCs and till systems are all named capture channels, group bookings cover mobile work crews, and corrections are said to be quickly possible and traceably documented. On what decides a basement at 6am we found no public information: nothing on offline capture that syncs and nothing on GPS or geofenced check-in with stated limits. Real terminal hardware and documented corrections carry it past the middle; the absence of any offline word holds it there.

GFOS

Offline is a designed state here, not a failure mode: bookings store locally when the server is unreachable and sync on return, any phone or tablet becomes a shared terminal with PIN or QR login for several workers on one device, and stationary terminals are named as the alternative, on top of iOS and Android apps with QR-code cost-centre switching. GPS capture is opt-in; I found no public information on its limits, and none on bulk corrections with an audit trail of who changed what.

ATOSS

They claim law-conform capture and ECJ-conform documentation of working hours, evaluation runs automatically against defined parameters, and rest periods and overtime thresholds appear in their compliance description. Beyond the claims we found no public information on break-rule configuration, warnings on the daily maximum, a retention period, or an export built for an inspection. Credible promise, thin on the specifics an inspector asks for.

GFOS

The engine for German working-time rules is visible — collective and works agreements and individual working-time models stored in wage type logic, flextime and vacation accounts, automatic overtime and premium valuation, and a healthcare page claiming compliance with working time regulations. But I found no public information on break rules, daily maximum or rest-period checks, retention of the time record for an inspection, or tamper-evidence on entries.

ATOSS

A shift-exchange marketplace, working-time wishes, replacements and last-minute changes are evidenced, scheduling is said to comply with local laws and union agreements, and leave calendars are visible in real time. On the entitlement side we found no public information on automatic entitlement, carry-over, sickness recording or per-location public-holiday calendars. The plan and the swap are real; the vacation bookkeeping is not on the captured pages.

GFOS

Absence and roster are one connected system: leave via web or app with approval, sickness split into first notification, follow-up and work accident with certified eAU retrieval, entitlements monitored with remaining-leave capping, and a duty roster with a duty exchange platform, availability doodles, shift suggestions matched to qualifications and planning-conflict alerts that rework the plan when someone drops out. I found no public information on public-holiday calendars per location, pro-rata entitlement, or rest-period checks inside shift templates.

ATOSS

Booking time to orders, projects and cost centres is evidenced, including on the road and as group bookings for crews. The captured pages show allocation and stop there: we found no public information on rates, a billable flag, per-project reporting, budgets or an invoice-ready export. The time gets coded; nothing shown takes it to an invoice.

GFOS

Recorded time carries a real allocation — projects, sub-projects, tasks, activities, locations and cost centres — with a billable flag, percentage auto-bookings to master projects, automatic deviation monitoring, target/actual project reports, and a transfer of evaluated times onward for invoicing. I found no public information on rates per person or per project, or on budget tracking with warnings.

ATOSS

DATEV is named as a technology partner for ATOSS Time Control and the Staff Efficiency Suite, all data is said to go directly to the payroll system, pay rules apply automatically, discrepancies surface before the payroll run, and corrections after initial processing are handled. Against the top of the scale we found no public information on night, Sunday and holiday surcharges, time accounts, or an explicit lock before transmission. A named partner path with real pre-payroll control; the surcharge detail is not published.

GFOS

This is the deepest part of the offering: certified interfaces to DATEV, PAISY, SAP, LOGA and VEDA among 30-plus payroll interfaces plus a neutral record format for anything else, night, Sunday and holiday premiums and overtime pushed to wage types automatically from recorded times, flextime and vacation accounts in the data record, absence changes synchronized by cancellation or extension, retroactive accounting and test payrolls before the monthly button-press transfer. I found no public information on a lock or approval step before transmission, or on scoped access for the tax adviser.

ATOSS

The contracting entity is unambiguous — ATOSS Software SE of Munich with a commercial register entry and German VAT ID — and deployment is offered in the cloud or on premises. For the rest we found no public information: no statement on where cloud data is hosted and no published subprocessor list, only a data processing agreement link in the footer. German entity documented, the chain behind it assumed.

GFOS

The contracting party is German to the bone — GFOS mbH in Essen, Amtsgericht Essen register, German VAT number, a named data protection officer and an ISO 27001 certificate — and the privacy policy even names its website subprocessors, including HubSpot servers in Germany and the USA under an Art. 49 derogation. I found no public information on where customer time data is hosted or on subprocessors for the product itself, and that silence is what matters when crews' clockings leave the site.

ATOSS

No price appears anywhere in the captured material — not per user, not per tier, not for terminals or modules. The only commercial path shown is scheduling a demo. A buyer cannot compute their annual invoice from these pages at all.

GFOS

The pages name tiers from Base to Enterprise and list modules, but we found no public prices for any tier, per-user seat, module or terminal hardware. The tier names are public; the numbers are a sales conversation.