The goal of the Thin Client Verification user is to review data processed by previous modules and ensure that critical data is accurate.

Solution integrators configure which fields need to be verified. Any fields with verification errors are marked with a Field Not Verified icon and need to be addressed.

Thin Client Verification works on one batch at a time and allows the processing of fields in these modes: confirmation (by pressing a single key to accept the data) or blind double keying (a more comprehensive verification technique).

You are not able to close a batch that contains unverified fields. As a result, you need to do one or more of the following:

• Confirm a field (press a single key to accept the data)

• Blind double keying (re-key the field with no knowledge of the extracted value)

• Refer to Read-only fields to provide context for other fields that require verification.

• Reject a document.