Multi-finger biometric support

This enhancement adds support for enrolling multiple fingerprints per employee on the same type of fingerprint reader. The goal is to improve reliability and convenience when employees use biometric verification at the clock.

Once multi‑finger support is enabled by the clock OS version, an employee can enroll more than one finger. During verification, the clock compares the scanned fingerprint against all templates stored for that employee on that reader type, up to the series‑specific limit. Any matching template is accepted as a valid credential.

This feature does not change timekeeping rules, rounding, or security policies. It only changes how many biometric templates a single employee can store per reader type.

Capacity and behavior by series

The maximum number of fingerprints that can be stored per employee, per fingerprint reader type, depends on the clock series:

9000 series clocks

  • Maximum: 2 fingerprints per employee on the same fingerprint reader type.
  • Behavior at capacity: when an employee already has 2 fingerprints stored for that reader type, additional enrollment attempts for that reader type are rejected. A new template can only be enrolled after one of the existing templates is deleted.

The limit is applied per reader type, not across all devices. If an employee uses different fingerprint reader types. For example, for different sensor modules or models, each reader type maintains its own set of templates, subject to the series limit.

Software requirements

Multi‑finger enrollment is available only when the clock is running a supported OS version or later:

9000 series clocks: OS 17.2 or higher

Clocks running earlier versions continue to operate with single‑finger behavior. To take advantage of this enhancement, upgrade all affected clocks to at least the minimum OS version listed for the appropriate series.

Verification behavior

After multiple fingerprints are enrolled for an employee:

  • Any of the enrolled fingers for the same reader type can be used for verification at the clock.
  • The clock automatically checks the captured fingerprint against all stored templates for that employee on that reader type, within the allowed limit.
  • If none of the templates match, the verification fails in the same way as a standard single‑finger mismatch.

From an administration perspective, no additional configuration flags are required to enable this feature beyond ensuring that clocks are running the correct OS version. Existing enrollment and deletion workflows at the clock continue to be used, but now operate with the updated per‑employee fingerprint limits.