18 May The 2027 Deadline: What Belgian Employers Need to Know About Mandatory Time Tracking
The Belgian federal government has committed to making daily working time registration mandatory for all employers from 1 January 2027. The political intent is clear and has been confirmed by multiple sources; the detailed implementing legislation is still being finalised. The underlying legal obligation, however, is not in question: it flows from a 2019 ruling of the Court of Justice of the EU that applies across all member states. For Belgian organizations that have not yet acted, the direction of travel is fixed. The informal practices, manual spreadsheets, and monthly employee declarations they have relied on do not meet the standard the law requires.
Where the Obligation Comes From
The legal foundation predates the Belgian implementation by several years.
In May 2019, the Court of Justice of the European Union ruled in CCOO v. Deutsche Bank SAE (C-55/18) that employers across the EU are required to establish an objective, reliable, and accessible system for measuring each worker’s daily working time. The ruling was grounded in the EU Working Time Directive (2003/88/EC), in force since 2003. For over a decade, that directive set limits on working hours and minimum rest periods without a corresponding requirement to document compliance. The 2019 ruling changed that.
Each EU member state has been responsible for transposing the obligation into national law. Some acted quickly: Spain introduced mandatory daily time recording in 2019, Denmark followed in July 2024. Belgium has taken a sector-by-sector approach, beginning with construction and meat processing, and more recently, the cleaning sector. The federal government’s budget agreement set 1 January 2027 as the date for extending the obligation to all employers across the private and public sectors. As of early 2026, the detailed implementing legislation was still being drafted; the political commitment, however, is firm and widely reported by Belgian employment law specialists. For Belgian companies that have been watching from the sidelines, the direction is not in dispute.
What the Law Actually Requires
The three-criterion standard set by the CJEU ruling is precise, and Belgian employers should understand what it means in practice.
Objective means the record cannot rest on unverified employee self-declaration alone. A system in which employees fill in their own hours without any mechanism for verification or audit does not meet this standard, regardless of how long it has been in use.
Reliable means the system must be resistant to retroactive manipulation. A time record that can be edited without leaving a traceable log of changes is, for compliance purposes, no record at all. Integrity of data, its immutability absent a documented correction process, is a core criterion.
Accessible means the data must be retrievable in a usable format on demand, whether during a labor inspection or in the context of an employment dispute. Records scattered across disconnected spreadsheets, email chains, or payroll exports without structure do not satisfy this requirement.
The scope is broad. The obligation applies to employees working on-site, in hybrid arrangements, and fully remotely. It applies to full-time and part-time contracts. It requires daily granularity: a record of when work began and ended each day, not weekly summaries or rounded monthly totals. Retention requirements add a further dimension; the records must be kept for a defined minimum period and remain available for audit throughout.
What does not qualify as compliant:
- Spreadsheets populated manually by employees without supervisory validation
- Monthly attendance summaries submitted as signed declarations
- Timekeeping embedded in payroll software that does not maintain an auditable change history
- Badge systems recording building entry and exit that do not connect to an HR record

The Business Exposure for Belgian Employers
The regulatory risk is concrete and operates on three levels.
The first is direct compliance risk: administrative sanctions for non-compliance, which can be calibrated per employee and therefore scale with headcount. There is no size threshold below which the obligation does not apply. Belgian SMEs face the same legal requirements as large enterprises; the scale of potential sanctions differs, but the obligation does not.
The second is operational risk in employment disputes. Belgian labor law already places significant weight on employer documentation. An employer that cannot produce a reliable daily time record in a tribunal proceeding, whether the dispute concerns overtime pay, rest period violations, or termination has surrendered its evidentiary position before the hearing begins. The absence of documentation is not neutral; it tends to shift the burden of proof.
The third is organizational risk for companies with cross-border operations. Belgian companies with subsidiaries or workforces in other EU countries already operate under a layered compliance environment. A time registration system that works for Belgian employees but produces incompatible records for employees in the Netherlands, France, or Germany creates audit exposure that a unified system avoids.
Preparing Before January 2027: A Structural Approach
The organizations that will meet the January 2027 deadline without disruption are not those that begin in Q4 2026. They are those that treat this as a process redesign project, not a software purchase.
Audit current state first. Map exactly how working time is currently recorded across every employee category and work model. Where are the gaps between current practice and the objective, reliable, accessible standard? This audit consistently surfaces inconsistencies that predate the regulatory pressure: time records that exist in form but carry no evidentiary weight in substance.
Map the workforce structure. Different employment arrangements require different system configurations. Employees on standard fixed-hour contracts present different tracking requirements than those on variable contracts, part-time schedules, or arrangements that span multiple locations in a single working day. The system must accommodate this variation without creating parallel, disconnected records.
Select a system that produces auditable records. The technical criteria are specific: a change-logged time record, integration between time tracking and the broader HR record (contracts, leave, absences), and a data export capability in a format that regulators and legal counsel can use. These are not optional features; they are the minimum floor.
Test before the deadline, not on it. For Belgian employers, Q4 2026 is the latest responsible start for live deployment. Deploying two or three months before the deadline provides time to identify process failures before they become compliance failures. Employees need to understand what is being recorded and why. Managers need to understand their validation responsibilities. HR and legal teams need to verify that the system’s output would satisfy an inspection.
How MintHCM Addresses the Requirement
MintHCM is an open-source Human Capital Management system with a dedicated time management process built across a set of interconnected modules. The following reflects its documented functionality.
The Work Schedule module allows each employee to maintain a daily work schedule, with a forward-planning mechanism that can be configured to require availability data a minimum number of weeks in advance. Administrators can set notification rules that alert when schedules are left empty, ensuring records are maintained continuously rather than filled in retrospectively.
The Users Actual Effort module (listed in the system as Spent Time) records the hours worked by each employee on individual tasks and assignments. Together with the Work Schedule, it creates a two-layer record: planned time alongside actual time spent. That distinction is relevant to compliance, providing not only a time log but context for how working time was used.
The Working Months module serves as a system-level reference for monthly working time norms. Administrators input the number of working days for a given calendar month; the module calculates the corresponding expected working hours. This normative baseline is what actual recorded time is measured against.
The Overtime dashlet counts time worked each month per employee, surfaces surplus hours, and flags deficits. This makes working-time irregularities visible before they accumulate into legal exposure.
The Absences dashlet records which employees are absent on any given day, with the reason: sick leave, delegation, remote work, annual leave, and others. Absence types are color-coded, allowing managers to assess team availability without navigating separate records.
The Non-Working Days Registry centralizes public holidays, company-specific non-working days, and schedule exceptions – the reference point against which individual daily records are validated.
MintHCM also supports integration with external project and issue tracking tools, including Redmine, allowing time entered in one system to be reflected in both without duplication.
The time management functionality in MintHCM does not exist as a standalone compliance tool. It is part of a broader HR record that includes employee profiles, employment history, contracts, and performance data. For the purposes of Belgium’s January 2027 requirement, integration is relevant: a time record that sits in isolation from the rest of the HR system is harder to defend and harder to produce on demand than one that exists within a coherent data structure.
The Window Is Closing
The legal obligation behind Belgium’s January 2027 deadline has been in place, in principle, since the 2019 CJEU ruling. What the national implementation date represents is the point at which that principle becomes an enforceable requirement with real consequences for non-compliant employers.
Organizations that approach this as an IT project tend to underestimate the process dimension. Those that approach it as a legal project tend to underestimate the operational dimension. The organizations that will navigate it without incident are those that treat it as what it is: a people process, supported by a system, governed by a legal standard.
January 2027 is fixed. The preparation window is not.