...

The only time data is sent to a human for validation is when the data is hard to read. This typically means the data on the form was hand-written or the document itself may have artifacts on it that obscure the value (e.g. a scan done by a dirty scanner), or many other reasons the data couldn’t be read (e.g. coffee spilled on the document).

Assumptions

Below are some key assumptions that FormXtract relies upon to achieve results.

1. What data or which fields on forms can be extracted?

   FormXtract reads forms using the Quik! Field Definition which has over 1.2 million unique fields defined. Does this mean that every field will be read off a submitted forms? No, only the fields that are defined in the Quik! Field Definition that appear on the form will be returned, however any field can be defined in order to be extracted. If there are fields you want returned that are not defined then we can add fields to the definition and build the form with these additional fields on it.

2. What forms can be used with FormXtract?
   Any form can be used as long as that form exists in the Quik! Library prior to submitting it for processing AND the customer’s account has been assigned that form for use with FormXtract. Any form submitted that is either not in the library and/or not on the customers account will be treated as an unknown document, resulting in page processing costs but no field processing costs or fields returned.

3. What types of documents can be used with FormXtract?
   FormXtract is designed specifically to work with static, structured forms. Our product is not (yet) designed to work with unstructured documents (e.g. invoices, statements, contracts, letters, etc.) even though the underlying technology can be used for such documents (if this is a goal of yours please talk to us about your needs as we can probably solve them with another version or iteration of FormXtract).