Define each extracted field

Open Configuration and select a document class you can manage. Create a draft version when the published schema needs to change. Give each field a business label, a stable key and an appropriate type.

  1. Add the labels and synonyms used by the source documents. Use a capture pattern only when it reliably identifies the required value.
  2. Set required values, confidence and review thresholds. Enable structured parsing or address processing only where applicable to that field.
  3. Save the draft, test representative text and inspect every result before publication.
Local product example · sample dataClick to enlarge ↗
Configure the value, its meaning and review requirements

This invoice-reference field uses a stable key and matching labels. Structured parsing is off in this example. Required values and review thresholds are field-specific; confirm them for your business process rather than copying sample settings unchanged.

Test extraction without assuming accuracy

A text sample test previews recognition and extracted values for that sample. It does not run a full production acceptance exercise or prove OCR performance on scanned layouts. Include competing classes, missing values and difficult examples in your testing.

Published versions are immutable. A new version affects subsequent processing according to the applicable configuration; existing runs retain their recorded schema and version.

Check source, extraction and index together

  1. Open Review & QC, then Index review. Choose the document or processing job you are authorised to inspect.
  2. Compare extracted values with the source page and review status. An approved extracted field is not by itself evidence of a successful index update.
  3. Inspect Current index and the recorded revision. Use the lookup check to find text in the verified governed index values.
  4. If the source or indexed values are wrong, use the available governed correction or fresh-index request. Follow its approval path and verify the subsequent receipt.
Local product example · sample dataClick to enlarge ↗
Verify the current index against the source version

The fictional invoice has approved extracted values and a current verified index receipt. Compare the source/version binding, extracted-value table and indexed fields. The Not assessed badge refers to a separate human quality assessment; it does not contradict the index receipt.

Understand what the checks confirm

The index inspection checks the platform’s governed index projection. It does not verify a separate external search engine or confirm that a downstream system ingested an exported package.

Human accuracy estimates describe the inspected sample. They do not approve indexing, replace recorded receipts or turn a heuristic AI score into measured production accuracy.

Recover a stale projection

  1. Compare source, reviewed extraction and Current index for the same record.
  2. Identify whether the issue began in extraction, a changed source or a stale index request.
  3. Follow the permitted correction/fresh-index approval route.
  4. Verify revision, receipt and lookup result; retain failed attempts as history.