Fields & TablesField Setup

Required Fields

Mark fields as required for extraction

Required Fields

A required field is one that DigiParser treats as essential: the system tries to extract it whenever it’s in the document, and the field stays in your schema and exports even when some documents have no value for it.

Note: A Required field toggle may appear in Fields & Tables for some parsers. If you don’t see it, Enable AI extraction is the main control for each field; use it with clear field names and AI Description to control what gets extracted. The Required setting is supported in the schema but may not be visible in the UI everywhere.

What “required” means

  • Required: The field is part of your core data. DigiParser aims to always extract a value when it’s present in the document. If it’s not found, the value can be empty, but the field remains in your schema and in exports.
  • Not required: The field is optional. It’s fine if the document doesn’t contain it; the value can often be left empty.

Required fields are useful when you always want a certain piece of information (e.g. Invoice Number, Total Amount) and you want it to appear in exports and integrations even when it’s missing for a given document.

When to use required fields

Use required for fields that:

  • You always need in exports or reports (e.g. Invoice Number, Vendor Name, Total).
  • Are central to your workflow (e.g. Payment Date, Amount).
  • You use in integrations (e.g. Xero, Google Sheets) and don’t want to drop.

Use optional (not required) for fields that:

  • Sometimes appear in your documents (e.g. Notes, Discount Code).
  • Are nice to have but not essential for every document.

How required fields affect your workflow

  • Extraction: Required fields are still extracted by AI when the information is in the document. “Required” doesn’t guarantee a value—it signals that the field is important.
  • Exports and integrations: Required fields typically stay in your export format and integration mappings, even when some documents have empty values. That keeps your spreadsheets or Xero/Sheets structure consistent.
  • Review: You can filter or sort by “missing” values to find documents where important fields weren’t found, then fix them manually if needed.

Tips

  • Don’t mark everything required: Use it only for fields you truly need every time. Too many required fields can make it harder to handle unusual documents.
  • Use with clear names and types: Required works best when the field has a clear name, the right type (e.g. Number for amounts), and a good AI Description so the system knows what to look for.

Next steps

How is this guide?

On this page