ATOSS vs GFOS

ATOSS

Booking runs via terminal, smartphone, tablet, PC and even the till system, which covers my desk, workshop and field crews — including group bookings for mobile work teams and corrections that are traceably documented. I found no public information on offline capture or GPS/geofenced check-in, which my site crews would rely on, so it stops short of the stronger marks.

GFOS

The GFOS App for iOS and Android, a Terminal App that turns any smartphone or tablet into a shared clock-in point with multi-user PIN or QR login, and booking on the time-tracking terminal give me a path for desk, workshop and field staff. Offline is a designed state — data is stored locally during network outages and synced when the server returns — and GPS capture is opt-in, though we found no public information on geofencing or the vendor stating GPS limits. Corrections run through a correction process, but we found no public information on bulk correction with an audit trail of who changed what.

ATOSS

The pages state fulfilment of all EuGH requirements with lawful capture and documentation of working hours, automated evaluation under defined parameters, enforcement of rest-period and overtime rules, and traceably documented corrections. I found no public information on break rules, warnings at the daily maximum, record retention, or an export laid out for an inspection — all things a German audit will ask me for.

GFOS

The wage-type logic stores collective agreements, works agreements and individual working-time models, overtime is assigned automatically, and the pages claim compliance with working-time regulations in scheduling — a serious German engine under the hood. But we found no public information on break handling, on warnings for the eight- and ten-hour daily maximum or the eleven-hour rest period, or on how the time record itself is retained for an inspection, which is exactly what I must evidence since the BAG ruling.

ATOSS

Absence runs from request through electronic approval to live leave calendars and trend reporting, and rostering is genuinely present: staffing analysis from real-time data, short-notice changes, replacements, a shift-exchange board and work-time wishes from the app. I found no public information on automatic entitlement, carry-over or sickness recording, which keeps it below the stronger marks.

GFOS

Sickness recording is first-class — differentiated case types, certified retrieval of the electronic certificate of incapacity, sickness-trend analytics — and vacation runs through approval workflows with quota monitoring, remaining-leave capping and up to nine vacation accounts. The roster side suits my mixed operation: availability requests via a shift doodle on mobile, a duty exchange platform, a planning book that flags conflicts, and shift suggestions matched to qualifications and time models, though we found no public information on public-holiday calendars per location or pro-rata entitlement. Schedule changes from spontaneous absences flow through the connection to attendance and absence recording.

ATOSS

On the go, staff can record project times and book directly onto cost centres, with allocation of working time to orders and projects — enough for job costing in my workshop. I found no public information on rates, billable status, budgets, per-project reports or any invoice-ready export.

GFOS

Time books to projects, sub-projects, tasks, activities and locations, projects carry a billable flag, and there are target/actual comparisons, project-progress reports, deviation monitoring and an export of evaluated times for invoicing into a connected system. But we found no public information on rates, neither per person nor per project, and none on budget tracking or rate cards — so from public pages I cannot see how recorded time becomes a priced invoice.

ATOSS

DATEV is named as a technology partner alongside ATOSS Time Control and the Staff Efficiency Suite, all data is said to go straight to the payroll system, pay rules apply automatically, discrepancies surface before the run, and corrections after the close are handled. I found no public information on named night, Sunday and holiday surcharge handling, time accounts, or a formal lock before transmission.

GFOS

Certified interfaces to DATEV, PAISY, SAP, LOGA and VEDA — thirty payroll systems plus forty ERP connections — are vendor-maintained, with night, Sunday and holiday premiums, overtime and payroll-relevant absences assigned to wage types automatically and absences re-synchronised on cancellation or extension. Monthly transfer happens at the touch of a button, integrated retroactive accounting covers corrections after the fact, test payrolls can be run beforehand, and a neutral data-record format serves an in-house payroll; we found no public information on a lock or approval step before transmission.

ATOSS

The contracting entity is ATOSS Software SE of Munich with a German commercial register entry, deployment can be Cloud or On Premises, and a data-processing agreement is linked in the site footer. I found no public information on where cloud data is hosted or who the subprocessors are, so the chain above the German entity is unverified.

GFOS

The contracting entity is clearly German — GFOS mbH in Essen, registered at the Amtsgericht Essen with a German VAT number — and the vendor presents itself as ISO 27001 certified. The only named subprocessors are website-side, including HubSpot with servers in Germany and the USA under an Art. 49 derogation and Google services; we found no public information on where the actual time data is hosted or on any subprocessor list for product hosting.

ATOSS

I found no public price information at all — no per-user fee, no module or terminal pricing, no billing period, minimum or VAT treatment; the only commercial step on the pages is scheduling a demo. A buyer with 200 heads cannot compute any part of the annual invoice from what is published.

GFOS

The pages name Base, Professional and Enterprise packages and mention bundles, but we found no public price of any kind — no per-user figure, no billing period, nothing for terminals or modules. Every number would come from a sales conversation, so I cannot compute my annual invoice for 200 heads from public pages.