Field Types
Every field you add to a Document Type has a type, which determines what kind of value is extracted and which input control appears when someone reviews a document. All fields share a common set of settings, plus extra settings specific to their type.
Settings shared by every field
- Field Type - see the table below.
- Field Name - the label shown to reviewers.
- Field Description - guidance shown under the label, and also used to help the extraction understand what to look for.
- Required Field - if on, this field must have a value, and it's the fields checked when calculating a document's confidence badge.
- Review Required - if on, a person must always check this field's value during review, regardless of how confident the extraction was.
- Field Rules - optional, administrator-defined extraction instructions. See Field Rules & Identifiers.
Available field types
| Type | Icon label | What it captures | Type-specific settings |
|---|---|---|---|
| Text | Text | Free-form text (names, reference numbers, addresses, etc.) | Optional Minimum Length and Maximum Length. |
| Number | Number | Numeric values (totals, quantities, etc.) | Optional Minimum Value and Maximum Value. |
| Date | - | Calendar dates | None - shown to reviewers as a date picker. |
| Switch | Switch | A yes/no or true/false value | None - shown to reviewers as a toggle switch. |
| Catalog | Catalog | A value looked up from one of your Catalogues | Catalog - which catalogue to match against. Return Value - whether the field should store the catalogue's Tag (key) or its Value. |
| List | List | Multiple values of the same underlying type | List Item Type - Text, Number, or Catalog. If Catalog, the same Catalog/Return Value settings as above apply to each item. |
note
On the review screen, List fields are shown as a small table - each row is one item, with a matching input for the chosen item type, and buttons to add or remove rows.
Choosing the right type
- Use Catalog whenever a value should come from a known, finite list (departments, cost codes, statuses) - this improves both accuracy and consistency, since the platform is matching against known values rather than guessing free text.
- Use List when a document can contain a variable number of the same thing, such as multiple invoice line items or multiple reference numbers.
- Reserve Required for fields that genuinely must be present - every required field with a low-confidence value will show up in review, so marking too many fields as required can make review noisier than necessary.
- Use Review Required sparingly, for fields where correctness matters enough that a person should check every single time (e.g., payment amounts), even when the platform is highly confident.