Skip to content

Allow missing registration

The Allow missing registration constraint turns off the built-in rule that every working day must have something registered. Use it for groups who are not expected to account for every day.

When to use

Use this constraint when:

  • Some employees only register exceptions, such as overtime or travel, and leave ordinary days empty
  • A group works on a schedule but is not required to register time at all, for example board members or hourly staff who are paid from another system

Parameters

This constraint has no settings. It works the same whether you add it under Blocking constraints or Non-blocking constraints : it never flags anything itself.

How it works

The built-in rule it turns off

Every timesheet checks, without any constraint configured, that each working day has either a check-in or registered work time. The day is flagged with No check-in or time registration on this working day. when:

  1. It is a working day — the employee has working time planned after public holidays are taken off
  2. Approved time off does not cover the whole day
  3. The day has no check-in, and no registered time that counts as work (a lunch-break entry alone does not count)

The built-in rule always blocks submission. Future days are never checked.

What this constraint changes

When Allow missing registration is on any work time policy that applies to an employee, the built-in rule is switched off for that employee. Empty working days are then no longer flagged, and the timesheet can be submitted with them.

Because work time policies stack, one policy carrying this constraint is enough — even if the employee’s other policies do not have it.

It changes nothing else:

  • An open check-in without a check-out still blocks submission. That is a separate built-in rule that cannot be turned off.
  • Mandatory Time Registration and Mandatory Check-in still apply if they are configured. They are explicit rules, not the built-in one.
  • The employee’s flex balance still counts the empty day as a day with no work against the norm.

Examples

Exception-only registration

A team only registers days that differ from the plan:

  1. Go to Settings › Policies and open the team’s work time policy
  2. Under Blocking constraints , click Add Plugin and choose Allow missing registration
  3. Click Save

An employee who registers nothing on Monday to Thursday and two hours of overtime on Friday can submit the week. Without the constraint, Monday to Thursday would each block submission.

To keep the norm intact on those empty days, combine it with the Auto-register norm time plugin, which fills empty completed days with the norm.

Troubleshooting

IssueSolution
Empty days still block submissionCheck the message. No time registrations recorded… comes from Mandatory Time Registration and Missing check-in/out… from Mandatory Check-in; remove those constraints for this group
An open check-in still blocks submissionExpected: an open check-in must always be checked out before submitting
Empty days are no longer flagged for someone who should registerAnother work time policy that applies to them carries this constraint. Narrow that policy’s Availability