Validators

Validators let you define rules that check whether extracted fields meet your requirements — so you only review documents that actually need attention. This helps you reduce manual work and improve data quality at scale.

---

​

Available Validators

• Confidence threshold
  Flags a field when the model’s confidence is below a percentage you set. The main dial between automation rate and accuracy.
• Cannot be empty
  Flags the document when a required field is missing or empty. Use this to make sure essential information is always extracted.
• Logical expression
  Checks a numeric relationship between fields, such as net_amount + vat_amount = total_amount. Catches documents where the numbers don’t add up.
• RegExp
  Checks that a value matches a regular expression. Good for reference numbers, postal codes and other fixed shapes.
• Format validators
  Ready-made checks for well-known identifiers: IBAN, BIC/SWIFT, VAT ID, Tax ID, email, URL, phone number, passport number, license plate and freight container ID.

​

Settings

Every validator has the same two settings, so you control how strict it is and what the reviewer sees. If validation fails decides what happens when the check does not pass:

• Show warning — the reviewer sees the message but can accept the value anyway. Use for rules that are usually right but have legitimate exceptions.
• Show error — the value must be corrected before the review can be completed. Use for rules that must always hold.

Customize the message replaces the default text with your own, which is what the reviewer reads in the validation interface. A specific message such as “The line items don’t add up to the total — check for a missing row” is easier to act on than a generic one.

​

Validators and formatters

Validators check values; formatters change them. Formatters run first, so a validator always sees the formatted value — which is why a numeric check works on 1 234,56 only if a Numeric formatter has turned it into 1234.56 first.