Appearance

Reviewing extracted fields ​

Studio is the screen where field validation happens. Three panes — document preview on the left, fields panel on the right, line items below — give you everything in one view.

You arrive in Studio by clicking any row in the Documents view. This page covers the read-only part of the work: knowing what you're looking at. The next page covers the editing.

The three-pane layout ​

Studio splits the screen into three regions:

  • Left pane — the document preview, rendered as a scrollable PDF or image. Colored bounding boxes overlay each extracted value.
  • Right pane — the extracted fields, grouped by category. Main on top, then Payment, Tax, Metadata.
  • Bottom pane — the line items table. Each row is one line item.

The fields panel scrolls independently of the preview. Click a field name and the preview jumps to that field's location on the document — useful when you can't immediately see where a value came from.

Field categories ​

Fields organize into five categories by convention. The categories show as headings inside the right pane:

  • Main — primary fields. Invoice number, total amount, dates, vendor identifier.
  • Table — represented as columns in the bottom pane (line items).
  • Payment — bank account, IBAN, due date, payment method.
  • Tax — tax rate, tax amount, VAT codes.
  • Metadata — vendor name, project name, GL accounts, departments, anything your admin set up as a Mapping target.

The convention is that Main / Payment / Tax / Table come from the document (extraction-fed), and Metadata comes from your reference tables (Mapping-fed). In practice, projects often mix the two. Either way, you read every category the same way — look at the value, decide if it's right.

Bounding boxes ​

Each extracted value has a colored rectangle drawn over the document showing where it came from. Colors match field categories, so the overlay is also a visual category map.

Click a field in the right pane and the preview scrolls to its bounding box on the document. It's the fastest way to check where a value came from — read the field, jump to the source region, confirm it matches.

Bounding boxes don't appear for Mapping-fed fields

Only fields the engine read from the document have bounding boxes. Metadata fields filled in by Mapping (like a GL code looked up from your chart of accounts) have no rectangle to draw — they don't come from a region of the document.

Reading values ​

For most fields, the value the engine produced is what you see. There's no per-field confidence meter or colour-coded certainty marker in this panel — the engine does score its own confidence, but Studio doesn't surface that as a visual cue here. So read the values themselves rather than waiting for the screen to flag the shaky ones.

Run your eye down the right pane top to bottom. Most fields will look right. Anything that looks off — a misread digit, a wrong category, a date in the wrong format — is what you'll fix on the next page.

What —Not set— means ​

When a field's value is —Not set—, the field has no value yet. There are two common reasons:

  • Extraction didn't find anything. The field's value isn't on the document, or the engine couldn't read it confidently. Common for fields that aren't always present (e.g., a discount line on invoices that don't have one).
  • Mapping hasn't filled it in yet. Metadata fields often start —Not set— and wait for either a workflow to populate them or the assignee to pick a value manually.

Mandatory —Not set— blocks Validate

If a mandatory field shows —Not set—, you can't click Validate. The button stays disabled until every mandatory field has a real value. This is intentional — the system prevents incomplete documents from moving forward.

To fill in a —Not set— field, click it and pick a value (for Select fields) or type one (for text / numeric fields). The next page covers this in depth.

Line items ​

The bottom pane shows the document's line items as a table — one row per item. Columns mirror the table-category fields: description, quantity, unit price, amount, plus any custom columns your project added.

Each line item is editable independently. Misread digits in the Quantity column are common; fix them inline. Studio also gives you tools to split, aggregate, and bulk-edit rows so the line items reconcile to the document's subtotal — covered on the next page.

When the document is locked ​

Depending on your project's configuration, fields may become read-only when the document reaches certain statuses (Validated, Approved, Rejected, Exported). The fields appear greyed out and the cursor doesn't focus when you click them.

If you need to edit a locked field, ask an admin — users with the Override permission can bypass the lock.

When fields update on their own ​

When you change a field that has a workflow watching it (a vendor name, a department code, a total amount), the related lookups re-run in the background. You'll see other fields update a second or two after your edit. This is the Mapping engine doing vendor lookups, GL coding, and approver routing in response to your change.

You don't need to refresh, save, or click anything to trigger it. The cascade runs automatically; the fields settle in 1–2 seconds.

What's next ​