Papershift vs TimeTac

Papershift

App, browser and a shared tablet terminal with PIN or signature are all confirmed, so a site crew can stamp without a desk, and employees can edit their own times with an approval view behind it. Offline use is claimed on the app pages, but nothing captured says what happens to a punch made without signal or when it lands, and we found no public information on bulk corrections or on the limits of the geofencing. A change history exists on the Professional plan, which is the right instinct, but the offline story is one line, not a design.

TimeTac

Three priced hardware terminals with RFID/NFC and fingerprint, mobile capture that works 'auch offline ohne Netz', GPS positioning, and employee self-correction with optional supervisor approval — that is a site-ready setup, not a desk tool. It stays under 8 because the vendor never states GPS/geofence limits, says nothing about terminal behaviour offline, and shows no bulk correction with a who-changed-what audit trail.

Papershift

The vendor cites the 2022 labour court ruling and stores begin, end and pauses revision-secure with a change history on the Professional plan, plus configurable per-employee break rules — the core recording duty is taken seriously. We found no public information on checks against the daily maximum or the eleven-hour rest period, on documented exceptions, or on a stated retention period for the time record itself; the privacy page only promises deletion after retention periods generally. That is a record that starts well and thins out exactly where an inspector would push.

TimeTac

The BAG/EuGH compliance line and 'Rechtssicher Arbeits- und Pausenzeit erfassen' are claims, not modelled ArbZG mechanics — the evidence is silent on rest-period checks, daily maximum warnings, retention, and tamper-evident history, and corrections can run without any approval at all. Working-time models and automatic hour accounting exist, which lifts it above a flat break rule, but nothing here survives an inspection by evidence.

Papershift

Entitlement, carry-over and sickness are computed automatically with approval paths and a team calendar, and absences flow straight into the duty roster, which then fills shifts automatically — one system, not two calendars, which is what I want before a Monday shift. Qualification tags, holiday rules and vacation bans with block periods are confirmed. We found no public information on substitution or swap workflows, pro-rata entitlement, or rest-period checks before a plan is published.

TimeTac

The absence half is genuinely there: automatic leave balances, carry-over or expiry, sickness, international holiday templates and deputy forwarding. But not one word on rosters, shift templates, availability, swaps or coverage — an iCal feed is not a duty plan, so half the criterion is simply missing.

Papershift

Project times can be booked uniquely to a customer or order and carry tags and notes, with reports over costs, hours and metrics. But the hourly wage we see lives in the employee profile for payroll purposes, and we found no public information on a billable flag, client-facing rates or rate cards, budget tracking, or an invoice-ready export built from project time. Time gets attributed; whether it becomes revenue is not shown.

TimeTac

Project and order times are booked with access rights, real-time status and project reports, better than a free-text note. But no rates, no billable flag, no cost centres, no budget tracking, and only generic Excel/PDF/CSV exports — the time never becomes revenue without re-entry.

Papershift

DATEV has its own maintained marketplace page with a „DATEV Detail“ export to the tax office, LODAS and SAGE are named, and night, Sunday and holiday surcharges calculate automatically with wage types, capping, tariff tables and special cases like Kurzarbeitergeld. Payrolls generate automatically at a chosen cutoff date and a red warning triangle flags time entered after generation. We found no public information on a lock step before transmission or retro runs after the close, so the month is not yet sealed by design.

TimeTac

A direct DATEV transfer 'ganz ohne manuellen Export oder Excel-Workarounds' with digital payslips and GDPR-conform transfer is a named, automated path to a major system. It sits below 8 because surcharge handling in the export, a lock step before transmission, and retro corrections after close are all unevidenced.

Papershift

The imprint names Papershift GmbH in Karlsruhe with a Mannheim commercial register entry, EU hosting is stated on the pricing page, and the privacy pages publish the data-processing agreement with annexes for subcontractors and technical measures alongside a public processing register. The hosting claim is a feature bullet, and we found no public information naming the data-centre provider or the subprocessors behind the downloadable annex. Solid German paperwork; the chain underneath sits a download away.

TimeTac

Austrian entity confirmed by register court and VAT number, EU-only hosting with the primary server in Germany in ISO-certified centres — a DACH vendor on DACH soil. But the data-centre operator is never named and no subprocessor list appears anywhere in the evidence, so the chain under the contract is undocumented.

Papershift

Three tiers, the 39,00 € monthly base fee marked plus VAT, the annual billing note with the 10 % saving, a from-price of 3,50 EUR je Mitarbeiter/Monat and a payroll module at €3 or €4 per employee and month are all public. But the per-employee from-price and the tier prices are not mapped to each other, and marketplace add-ons such as the full-service payroll and the reports module have no price we could find, nor terminal hardware. A buyer can estimate the year, not compute it.

TimeTac

Per-user, per-product pricing with a configurator producing monthly and annual totals, terminals priced from €29.90–€49.90 monthly, net prices and included support stated — most of the annual invoice is computable from public pages. Minimum term and setup fees are not stated, and onboarding and the API are 'price on request', which keeps it short of 8.