Enable Biometric Verification

Before You Begin: Before you can use biometric verification, an administrator or other user with necessary access must enroll at least one supervisor in admin mode. Next, either the administrator or the supervisor can enroll the rest of the employees. See Fingerprint Enrollment.

The Dayforce Touch Clock is equipped with a biometric reader that captures a mathematical representation of employees’ fingerprints when they perform clock entries. When configured, the clock compares the representations of the fingerprints that were saved in the database to those submitted at the time of the clock entry. If the two match, the clock entry is accepted. If they don’t match, it’s rejected.

Note: This section specifies only the changes you need to make to the custom config file to enable biometric verification. For more information about editing config files and publishing your configuration, see Configure the Clock Program. For more information about biometrics, see Fingerprint Enrollment.

To enable biometric verification, complete the following steps in the custom config file for the appropriate config group:

1. In the <system> section, specify the following:
2. <biometric mode="verify">yes</biometric>
3. If necessary, you can also edit the following attributes within the biometric tag:
   • To change the sensitivity of the biometric threshold, edit the threshold attribute. When the clock is configured with a lower sensitivity, it accepts lower quality fingerprints.
   • This attribute can be configured with the values 1 to 4, corresponding to low, medium, high, and very high sensitivity. For example, threshold="3" would configure the clock for high sensitivity.
   • To specify whether the clock prompts users for one finger or two during the enrollment process, edit the enrollment attribute.
   • When configured with enrollment="normal", the clock prompts employees for two finger scans. When configured with enrollment="simple", the clock only prompts employees for one scan.
   • To specify whether the clock prompts users to lift their finger off the scanner between each scan when they enroll for the first time, edit the lift_finger_in_enroll attribute. When configured with lift_finger_in_enroll="yes", the clock prompts users to lift their finger after each scan with a visual and audible alert.
   • Note: The lift_finger_in_enroll attribute is set to "yes" by default.
   • When configured with lift_finger_in_enroll="no", the clock doesn’t prompt users to lift their finger between scans.
   • To specify the number of attempts the clock allows employees, specify attempts="#", substituting the number of attempts you want to allow in place of #.
   • For example, to specify that employees get three attempts, specify "verify_attempts="3". This means that if an employee fails their first attempt at biometric verification, the clock provides two more attempts before it considers biometric verification to have failed.
4. For example, to enable biometric verification with a maximum of two attempts, simple enrollment, and a medium biometric threshold, you would specify:
5. <biometric mode="verify" threshold="2" enrollment="simple" verify_attempts="1">yes</biometric>
2. In the <validations> section, specify the following:
3. <validation name="Biometric Validation"
class="com.dayforce.devices.validationframework.
validation.BiometricValidation" active="yes"
order="22" supervisor="yes" />
4. If necessary, you can also edit the following attributes for the biometric validation:
   • To change the order in which the clock performs biometric verification in relation to the other validation it performs, change the number in the order attribute.
   • To exempt supervisors from biometric verification, specify supervisor="no"
3. If necessary, in the <functions> section, you can specify which for which functions the clock still submits biometric failures.
4. By default, these clock entries are rejected and aren’t sent to the server. However, when you specify submit_bio_failure="yes" for a function, the clock submits clock entries that fail biometric verification to the server so that managers can review them in timesheets.
5. For example, to specify that start shift clock entries that fail biometric verification should still be submitted to the server, you would specify:
6. <function id="in" punchtype="Punch_In"
class="com.dayforce.devices.function.Function"
submit_bio_failure="yes" />