Skip to content
Recht und Prozesse

Digital time tracking 2026: meeting the mandate cleanly

Recording working time is mandatory; the electronic form arrives in 2026. Implement it digitally: mobile capture, automatic rules, clean handover to payroll.

14 min read ZeiterfassungArbeitszeitgesetzAutomatisierungMittelstandCompliance

The duty to record working time is no longer an announcement but current law: since the ruling of the Federal Labour Court of 13 September 2022 (Federal Labour Court), every employer must capture the start, end and duration of daily working time - with no transition period. What is still missing is the exact statutory form; for that the Federal Ministry of Labour and Social Affairs presented a draft bill on 18 June 2026 (BMAS) that makes electronic recording the rule. For most companies the real question is therefore no longer whether, but how: with paper and a spreadsheet laboriously filled in at the end of the month, or with a digital record that is created where the work happens and passes its data to payroll and time management on its own. This article shows how the duty can be met without media breaks and duplicate data - from mobile capture through automatic rules to a clean handover. How we shape the recording task as an end-to-end workflow is set out under process automation.

Key takeaways

  • The duty already applies: the Federal Labour Court derived it in 2022 from the Occupational Safety Act (Federal Labour Court), based on the 2019 ruling of the European Court of Justice. Waiting for a new law is not waiting for the duty, only for its form.
  • The BMAS draft bill of 18 June 2026 makes electronic recording the rule and staggers the transition periods by company size; companies with up to ten employees are to remain exempt from the electronic form (BMAS).
  • Paper and spreadsheets are permitted but expensive: times filled in at month end are error-prone, and breaches of the recording duty can be penalised with up to 30,000 euros per case (Section 22 ArbZG).
  • The benefit does not come from recording alone but from the end-to-end workflow: capture on the move, review and approve in the system, calculate breaks and premiums by rule, and hand the data to payroll via an interface - without a second list.
  • Time tracking touches personal data and co-determination: the works council, purpose limitation and retention periods belong settled before go-live, not after (project experience).

The legal position is clearer than many companies assume. As early as 14 May 2019 the European Court of Justice ruled in the CCOO versus Deutsche Bank case (case C-55/18) that member states must require employers to set up an objective, reliable and accessible system for recording working time (European Court of Justice). The basis is the Working Time Directive 2003/88/EC and Article 31(2) of the EU Charter of Fundamental Rights (European Court of Justice). The Federal Labour Court translated this into German law in 2022: Section 3(2) No. 1 of the Occupational Safety Act obliges all employers to set up a system for recording the start, end and duration of working time (Federal Labour Court) - and immediately, with no implementation deadline.

What remains open so far is the exact statutory shape. The draft bill of the Federal Ministry of Labour and Social Affairs of 18 June 2026 closes that gap: it provides that the start, end and duration of daily working time are in principle to be recorded electronically (BMAS). Staggered transition periods are planned for the changeover - one year for companies with 250 or more employees, two years for 50 to under 250, and up to five years for smaller companies above ten employees (BMAS). Small companies with up to ten employees are to remain permanently exempt from the electronic form (BMAS). As the draft is still in the legislative process, details may change; the underlying duty is unaffected.

In practice this means: anyone already recording cleanly and digitally need not rush anything in 2026 but at most adjust details. Anyone waiting for the law before starting at all is confusing the form with the duty. The duty to record overtime already exists under Section 16(2) of the Working Time Act (Working Time Act) - general recording is the logical extension of it, not a break with what already applies.

The duty exists, the form follows

Two levels need to be kept apart. Whether working time must be recorded has been settled since 2022 (Federal Labour Court). How it must be recorded - electronically, with which deadlines and exceptions - is only set by the coming law (BMAS). A digital solution that captures start, end and duration in a traceable, exportable way already meets the substantive requirements today and is prepared for the electronic form. This article is a professional orientation and does not replace legal advice in a specific case.

Why paper, spreadsheets and month-end catch-up get expensive

About three quarters of companies in Germany now record their employees' working time (Bitkom) - in 2022, before the Federal Labour Court ruling, it was barely a third (Bitkom). But not every method is practical: 16 percent use a spreadsheet for it, 13 percent a handwritten timesheet (Bitkom). Both meet the duty in principle, yet in daily life they create exactly the manual work that digitisation is meant to remove.

The weak point rarely lies in the capture but in the catch-up. Times transferred from memory or loose slips into a table at the end of the month are inaccurate - and they concern a lot of money. In 2024, Germany recorded almost 1.2 billion overtime hours, of which more than half, around 638 million hours, went unpaid (IAB). According to the microcensus, 4.4 million employees worked more than contractually agreed, that is 11 percent of all employees (Federal Statistical Office). Where working time is not reliably captured, neither the hours worked nor the hours paid can be shown in a dispute.

On top of that comes the liability risk. A breach of the recording duties of the Working Time Act is a regulatory offence and can be penalised with a fine of up to 30,000 euros per case (Section 22 ArbZG); where health is intentionally endangered or the breach is persistently repeated, it can even become a criminal offence (Section 23 ArbZG). Records of overtime must be kept for at least two years (Section 16(2) ArbZG). A spreadsheet on a single computer meets this requirement for traceability and retention only with difficulty.

AspectPaper and spreadsheetsDigital recording
When it is capturedOften filled in at month endAt the moment of work
Source of errorTransfer, arithmetic, forgettingEntered once, rules automatic
EvidenceA single file, hard to checkA logged, traceable history
Handover to payrollRetyped by handExport or interface
ReportingAdding up hours in the eveningBalances and figures up to date
Mobile workThe slip gets lostThe app captures on site

What digital recording looks like in a business

Digital time tracking is more than a punch clock in the browser. What matters is that it is created where the work happens. For office staff, starting with a click at the desk is enough; on the building site, in the field or in care work, capture via a smartphone app is the practical route - after all, 18 percent of the companies that record already use an app (Bitkom). At the entrance of a workshop or warehouse a terminal with a card or PIN proves its worth. The important thing is that all routes flow into the same data set, so that no second version of the truth arises.

Capturing alone is not enough; the data must be reviewable and correctable. A good solution separates cleanly between recording by the staff and approval by the responsible person: corrections are possible but logged, so the history stays traceable. Breaks, rest periods and premiums can be stored as rules and applied automatically - that takes off the payroll team exactly the arithmetic that otherwise piles up at month end; the balances land at the same time in reporting, without anyone hunting down hours.

For companies with projects or cost centres a second benefit is added: if time is assigned to an order or project straight away, a basis for costing and invoicing arises alongside the plain working time. A duty exercise thus becomes a tool that makes utilisation and profitability visible. How such figures can be evaluated without spreadsheet evenings is described in the article reading processes from system data.

Capture where the work happens

App on the move, terminal at the entrance, browser at the desk - all routes write into the same data set. Times captured offline are reconciled afterwards, so that nobody has to fall back on a paper slip.

Review and approve with a log

Staff capture, the responsible person approves. Corrections are possible but stay traceably documented - that protects both sides and keeps the evidence clean.

Apply rules automatically

Breaks, rest periods, roundings and premiums are stored once and calculate themselves. That replaces the formulas in the monthly list and the queries that come out of them.

Balances and figures at once

Overtime, remaining leave and utilisation are available up to date instead of being gathered at month end - viewable by team, project or cost centre.

From capture to payroll and time management

The greatest time saving arises not at the capture but at the interface afterwards. If the approved times are retyped by hand into payroll, digitisation has stopped halfway - with a new source of error in the transfer. What makes sense instead is an interface that passes reviewed times, premiums and absences directly to payroll and time management. Then every figure exists exactly once and is not maintained in two systems in parallel.

For that to work, master data has to match: personnel numbers, cost centres, premium types and absence reasons need the same meaning in both systems. This is exactly where data integration comes in - it ensures that one record is the reference and that several lists are not maintained side by side. For payroll that means fewer queries, fewer correction runs and a checkable state that can be justified in case of doubt.

Whether a ready-made interface from the payroll program is enough or a bespoke connection is needed depends on the system in use. In both cases the handover should be logged and repeatable, so that a payroll run can be traced. Whatever runs permanently after that - updates, small adjustments, incident handling - belongs in structured operations rather than in the remaining time of a rollout project.

Start, end and breaks arise via app, terminal or browser - where the work happens, and not from memory at month end.

Rule set and handover (simplified example)
Captured (app/terminal)        Rule applied                 Sent to payroll
-----------------------------  ---------------------------  ---------------------
Mon 07:02-16:31, 30 min break  Core time, no premium        8.48 h regular hours
Sat 08:00-12:00                Saturday premium 25 percent  4.00 h + premium
Sick, reported                 Absence, no target time      continued pay
Public holiday, not worked     Target from the roster       paid, 0 actual hours

Principle: each line is created once at the source, the rule calculates
automatically, the handover to payroll is logged and repeatable -
no retyping, no second list.

Data protection and co-determination from the start

Time tracking processes personal data and is therefore a matter for data protection. What may be collected is what is necessary for working time and pay - no more. Purpose, retention period and access rights belong fixed in writing before go-live: who sees which report, how long is data kept, when is it deleted? A sparing, clearly justified record creates trust; one that incidentally captures location or behaviour creates resistance.

Where a works council exists, it must be involved early. The introduction of technical facilities capable of monitoring the behaviour or performance of staff is subject to co-determination under Section 87(1) No. 6 of the Works Constitution Act (Works Constitution Act) - and a time tracking system is a typical example of that. Involving the works council before the selection rather than shortly before go-live avoids later blockages and at the same time gains the cases and exceptions that only the people doing the work know.

What matters is the separation between recording and monitoring. A system that documents attendance is something different from one that measures individual staff on processing times. What the data will be used for and what it will explicitly not be used for belongs clearly answered before go-live. Assessing a specific case under data protection law and drafting a works agreement belong in professional hands; this article does not replace them.

Recording is not surveillance

The most common resistance to digital time tracking feeds on the fear of total monitoring. That fear can be defused by framing the purpose narrowly and naming it in writing: working time and pay, not performance profiles of individuals. Where recording is project or order related, it helps to commit that what is evaluated is how busy a team is - and not how fast a single person works. Transparency takes the ground from the rumour.

A time record that nobody works around is rarely a question of technology but of purpose. Once it is clear what the data serves and what it does not, a fear of control turns into routine.

Project experience

Rolling it out step by step without slowing the business

A time record touches every workstation - and is therefore accepted or worked around at every workstation. As with any changeover, the rollout decides more than the choice of system. Starting with one area or one team, whose experience flows into a corrected quick guide before the next follows, makes sense. Switching every site over on the same day bundles the queries into a mountain that reaches no one. How a rollout that actually lands is built - with named key people and training on a real case - is covered in the article bringing staff along with new workflows.

Two points are special about time tracking: the rules and the exceptions. Before a solution is rolled out, break arrangements, premium types, roundings and the handling of business trips, on-call duty or short-time work belong described cleanly once. Those rules are the actual core; the user interface is the easier part. We record them in a process analysis before any talk of tools, and support the changeover with training and rollout on a real working day.

  1. Fix the rules: describe breaks, rest periods, premiums, roundings and special cases such as business trips or on-call duty before go-live.
  2. Settle data protection and co-determination: define purpose, retention period and access, involve the works council early (Section 87 BetrVG).
  3. Choose capture routes: app, terminal or browser per workstation, so that nobody has to fall back on a slip.
  4. Set up the interface to payroll and check it with a trial run against real cases before it goes live.
  5. Start with one area, collect the queries, sharpen the quick guide, then connect the remaining areas in stages.
  6. Review after about four weeks: where does it snag, which rule is missing, which exception was overlooked (project experience)?

What a company can prepare on its own

The larger share of a successful changeover sits with the company, not with the technology. A lot can be prepared before any solution is even in the house: collecting the working time rules that apply, noting the special cases that actually occur, and deciding which reports are needed. A company that goes into a project with this clarity saves rounds of coordination and gets a record that fits the business rather than the other way round. The same principle - capture once, apply rules automatically, pass on without a media break - also carries other recurring back-office workflows such as automated dunning.

An honest choice of date pays off just as much. The turn of the year, the previous month's payroll or a seasonal peak are poor moments to start. Postponing by two weeks costs little; starting in the middle of the payroll peak costs trust. And anyone already using industry or project software should check early whether its time module is enough or whether a connection to further systems is the better route. An overview of the possible building blocks is given on the services page.

  • Collect the working time rules that apply: breaks, core times, premiums, roundings and collective-agreement specifics.
  • Gather the special cases that actually occur: business trips, on-call duty, short-time work, split shifts, trust-based working time.
  • Decide which reports are needed and who should see them - from the overtime balance to project utilisation.
  • Check which payroll and time management system the data is handed to and whether a ready-made interface exists.
  • Record purpose, retention period and access rights in draft and - where one exists - agree them with the works council.
  • Choose a realistic start date outside payroll peaks and seasonal highs.
This article is based on data from: the Federal Labour Court (ruling of 13 September 2022, 1 ABR 22/21), the European Court of Justice (ruling of 14 May 2019, C-55/18), the Federal Ministry of Labour and Social Affairs (draft bill of 18 June 2026), the Working Time Act (Sections 16, 22, 23 ArbZG), the Works Constitution Act (Section 87), Bitkom, the Institute for Employment Research (IAB), the Federal Statistical Office and our own project experience.

Related Articles

Prozesstransparenz

Reading processes from system data: where it snags

How to reconstruct the actual workflow - loops and special paths included - from the timestamps your systems already record, instead of guessing or estimating.

13 min read
Forderungsmanagement

Automating dunning: reach the money in the bank sooner

How a rule-based dunning run staggers reminders automatically, links invoicing and accounting and shortens days sales outstanding - explained step by step.

13 min read
Automation & interfaces

Interface or manual work: doing the maths

When does an interface pay off and when is manual work cheaper? A decision framework based on volume, frequency and error rate, plus the interim steps.

13 min read