Audit validation bypass decisions

When an employee chooses to bypass a validation, the decision is written to the swipe’s extradata. This allows employers to audit which validations were bypassed for each swipe.

Bypass decisions are recorded using tokens in this format: val_<code>=<Y|N>

For example, a bypassed Break Length validation might be recorded this way: val_brkLen=Y

Meanwhile, a Consecutive Types validation that the employee chose not to bypass might be recorded this way: val_conType=N

These extradata tokens are visible in the Clock Admin Console and Employee Timesheet.

If a swipe results in multiple validations and the employee bypasses some of them but later selects No for a subsequent validation:
  • All validations that were bypassed (where the employee selected Yes) remain recorded as val_<code>=Y in the swipe extradata.
  • The validation for which the employee selected No becomes the rejection reason for the swipe and is not stored as a bypass token in extradata.
  • The swipe is rejected based on that validation.

You can use these bypass tokens to drive additional processing, such as unauthorizing timesheets when certain tokens are present or reporting on patterns of repeated bypasses.