Field names are important
Field names are used to match the data from the source document. This means that using descriptive, self-explaining field names is crucial for good results. You don’t have to avoid spaces in field names, but it is recommended. Don’t try to be clever.Good example: invoice_number
Bad example: the text from the 3rd row on the left side
Use descriptions to clarify intent
Descriptions act as an additional layer of instructions to help match data from the source document. You can add a description to any object, field or column to help the engine with extracting the correct data.Good example: Full name of the individual
Field name: “Tax ID”
Description: “Can also appear as VAT ID or EIN number”
Description: “Can also appear as VAT ID or EIN number”
Use descriptions for data manipulation and filtering
You can also use the description to perform filtering and/or data manipulations, such as “Format the date in YYYY-MM-DD” or “Skip rows containing X”Don’t overuse data manipulations, especially with smaller models