SmartVendor Templates

Overview

The SmartVendor Templates tab in SmartVendor > Settings allows administrators to review and configure how invoice fields are extracted, matched, and mapped for SmartVendor invoice processing.

Templates define which invoice fields are enabled, how values are interpreted, and how extracted data is mapped for downstream processing.

Navigation to SmartVendor Template

To access this page:

1. Open SmartVendor from the left navigation menu.
2. Select Settings.
3. Choose the appropriate:
   • ERP
   • Mailbox
4. Open the SmartVendor Templates tab.
5. Click Review and Edit on the available template.

Figure 1. Navigating to SmartVendor Templates

SmartVendor Templates

The SmartVendor Templates page contains two main sections:

• Template Settings – Configure field-level extraction and matching behavior.
• Template Preview – View a sample invoice preview and extracted field values.

This page helps administrators control how SmartVendor reads invoice documents and applies field configuration rules.

Figure 2. SmartVendor Templates Overview

Template Settings

The Template Settings section defines how SmartVendor extracts, interprets, and maps invoice data for each template field.

Each row in the grid represents one invoice field, such as Vendor, Due Date, Currency, PO Number, Quantity, or Amount. The first set of columns provides reference information about the field. The remaining columns allow administrators to configure extraction and matching behavior, where supported.

Figure 3. Template Settings

Table 1. Template Settings Column Descriptions

Field Name

Displays the business label of the invoice field represented by the row.

The Field Name column helps identify which invoice field is being configured in the template. Each row corresponds to a specific header-level or line-level invoice field.

Typical values

Examples may include:

• Vendor – Supplier name on the invoice
• Due Date – Invoice payment due date
• Date – Invoice date
• Vendor Bill Ext ID – Supplier invoice number or external bill ID
• Currency – Invoice currency
• Total Amount – Total invoice amount
• Total Tax – Total tax amount on the invoice
• Net Amount – Invoice amount excluding tax
• Payment Terms – Payment terms on the invoice
• Invoice Received Date – Date the invoice was received
• Entity – Legal entity or company associated with the invoice
• Bot Confidence Level – Confidence level of the extracted invoice data
• Freight Amount – Freight or handling charges on the invoice
• Description – Invoice line description
• Service Period Start – Start date of the service period for the line item
• Service Period End – End date of the service period for the line item
• Prepaid – Indicates whether the line item is prepaid
• PO Number – Purchase order number
• PO Line Number – Purchase order line number
• Contract Line Number – Contract line number associated with the invoice line
• Contract Number – Contract number associated with the invoice line
• Line Entity – Entity associated with the line item
• Cost Center – Cost center value
• Spend Category – Spend category value
• Quantity – Quantity on the line item
• Price – Unit price
• Amount – Extended or line amount

Note: The exact fields displayed depend on the selected ERP, mailbox, and template.

Header or Line

Indicates whether the invoice field belongs to the invoice header or to an individual line item.

The Header or Line column helps users understand where the field is located in the invoice structure. This provides context for how the field is extracted and how the configured settings apply.

Typical values

Examples may include:

• Header – The field applies to the overall invoice document
• Line – The field applies to an individual invoice line item

Field Destination

Displays the internal system field to which the invoice field is mapped.

The Field Destination column helps users understand where the extracted invoice value is stored or applied in the system. This is useful when reviewing template behavior, because all configurable options in the same row apply to that mapped destination.

Typical values

Examples may include:

• supplier – Mapped destination for Vendor
• dueDate – Mapped destination for Due Date
• date – Mapped destination for Date
• supplierInvoiceNumber – Mapped destination for Vendor Bill Ext ID
• currency – Mapped destination for Currency
• extendedAmount – Mapped destination for Total Amount or Amount
• paymentTerms – Mapped destination for Payment Terms
• invoiceReceivedDate – Mapped destination for Invoice Received Date
• company – Mapped destination for Entity
• freightHandling – Mapped destination for Freight Amount
• description – Mapped destination for Description
• serviceStartDate – Mapped destination for Service Period Start
• serviceEndDate – Mapped destination for Service Period End
• prepaid – Mapped destination for Prepaid
• purchaseOrder – Mapped destination for PO Number
• purchaseOrderLine – Mapped destination for PO Line Number
• supplierContractLine – Mapped destination for Contract Line Number
• supplierContract – Mapped destination for Contract Number
• interCompanyAffiliate – Mapped destination for Line Entity
• costCenter – Mapped destination for Cost Center
• spendCategory – Mapped destination for Spend Category
• quantity – Mapped destination for Quantity
• rate – Mapped destination for Price
• -- – No mapped destination displayed in this view

Note: The exact destinations displayed depend on the selected ERP, mailbox, and template.

Field Type

Displays the data type of the invoice field.

The Field Type column helps identify what kind of value the field stores and how it is interpreted during extraction and processing. It also helps explain why some configuration options are available for certain fields and not for others.

Typical values

Examples may include:

• Text – Free-form text value
• Date – Date value
• Dropdown – Value selected or matched from a predefined list
• Number – Numeric value

Note: The field type is predefined for each field and cannot be changed in the Template Settings grid.

Standard or Extended

Indicates whether the invoice field is part of the standard template model or an extended field.

The Standard or Extended column helps users understand whether a field is provided as part of the default SmartVendor template or has been added as an extended field for additional configuration.

Typical values

Examples may include:

• Standard – Default system-supported field included in the template
• Extended – Additional field configured beyond the standard field set

Enable

Controls whether the field is active for extraction and processing in the selected template.

The Enable column determines whether SmartVendor uses the field during invoice data extraction and downstream processing. Each row includes a checkbox indicating whether the field is enabled and whether the user can change that setting.

User action

Users can interact with this column as follows:

• Select the checkbox to enable the field, if the checkbox is editable.
• Clear the checkbox to disable the field, if the checkbox is editable.
• If the checkbox is greyed out, the setting is system-controlled and cannot be changed in the Template Settings grid.

Typical values

Examples may include:

• Checked – The field is enabled
• Unchecked – The field is disabled
• Greyed out and checked – The field is enabled and cannot be changed
• Greyed out and unchecked – The field is disabled and cannot be changed

Scenarios

Checked and editable

The field is enabled, and the user can disable it if needed.

Examples may include fields such as:

• Due Date
• Total Tax
• Net Amount
• Payment Terms
• Invoice Received Date
• Freight Amount
• Service Period Start
• Service Period End
• Prepaid
• PO Number

In this state, the field is currently active and can still be modified by the user.

Unchecked and editable

The field is disabled, and the user can enable it if needed.

Examples may include fields such as:

• Contract Line Number
• Contract Number
• Line Entity

In this state, the field is available for configuration but is not currently active.

Greyed out and checked

The field is enabled, but the user cannot change it from this screen.

Examples may include fields such as:

• Vendor
• Date
• Vendor Bill Ext ID
• Currency
• Total Amount
• Entity
• Bot Confidence Level
• Description
• PO Line Number
• Cost Center
• Spend Category
• Quantity
• Price
• Amount

In this state, the field is required or system-controlled and must remain enabled.

Greyed out and unchecked

The field is disabled, and the user cannot enable it from this screen.

This state may appear when the field is present in the template but is not available for manual configuration in the current context.

Note: Enabling a field makes it available for extraction and processing, but other configuration columns still depend on whether that field supports those options.

Allow Predictive Coding

Controls whether predictive coding is enabled for the field.

The Allow Predictive Coding column determines whether SmartVendor can use predictive logic to identify or suggest a value for the field during invoice processing. This option is available only for supported fields.

User action

Users can interact with this column as follows:

• Select the checkbox to enable predictive coding for the field, if the checkbox is editable.
• Clear the checkbox to disable predictive coding for the field, if the checkbox is editable.
• If the checkbox is greyed out, the setting is system-controlled and cannot be changed in the Template Settings grid.
• If the value displays as N/A, predictive coding is not supported for that field.

Typical values

Examples may include:

• Checked – Predictive coding is enabled
• Unchecked – Predictive coding is disabled
• Greyed out and checked – Predictive coding is enabled and cannot be changed
• Greyed out and unchecked – Predictive coding is disabled and cannot be changed
• N/A – Predictive coding does not apply to the field

Scenarios

Checked and editable

Predictive coding is enabled, and the user can disable it if needed.

Examples may include fields such as:

• Currency
• Payment Terms
• Line Entity
• Cost Center
• Spend Category

In this state, SmartVendor can use predictive logic for that field, but the setting remains user-configurable.

Unchecked and editable

Predictive coding is available for the field, but it is currently disabled.

Examples may include fields such as:

• Currency
• Payment Terms
• Line Entity
• Cost Center
• Spend Category

In this state, the field supports predictive coding, but the user has chosen not to use it.

Greyed out and checked

Predictive coding is enabled, but the user cannot change it from this screen.

This state may appear when predictive coding is enforced by the system for a supported field.

Greyed out and unchecked

Predictive coding is disabled, and the user cannot enable it from this screen.

This state may appear when the field supports predictive coding in some contexts, but not for the selected template or configuration.

N/A

Predictive coding does not apply to the field.

Examples may include fields such as:

• Vendor
• Due Date
• Date
• Vendor Bill Ext ID
• Total Amount
• Total Tax
• Net Amount
• Invoice Received Date
• Bot Confidence Level
• Freight Amount
• Description
• Service Period Start
• Service Period End
• Prepaid
• PO Line Number
• Contract Line Number
• Contract Number
• Quantity
• Price
• Amount

Note: Predictive coding availability is determined per field. Not all enabled fields support predictive coding.

Allow Fuzzy Matching

Controls whether fuzzy matching is enabled for the field.

The Allow Fuzzy Matching column determines whether SmartVendor can use approximate matching logic for the field when an exact match is not found. This helps the system recognize values that are close, but not identical, to expected values. This option is available only for supported fields.

User action

Users can interact with this column as follows:

• Select the checkbox to enable fuzzy matching for the field, if the checkbox is editable.
• Clear the checkbox to disable fuzzy matching for the field, if the checkbox is editable.
• If the checkbox is greyed out, the setting is system-controlled and cannot be changed in the Template Settings grid.
• If the value displays as N/A, fuzzy matching is not supported for that field.

Typical values

Examples may include:

• Checked – Fuzzy matching is enabled
• Unchecked – Fuzzy matching is disabled
• Greyed out and checked – Fuzzy matching is enabled and cannot be changed
• Greyed out and unchecked – Fuzzy matching is disabled and cannot be changed
• N/A – Fuzzy matching does not apply to the field

Scenarios

Checked and editable

Fuzzy matching is enabled, and the user can disable it if needed.

Examples may include fields such as:

• Payment Terms
• PO Number
• Contract Number

In this state, SmartVendor can use approximate matching for the field when exact matching is not sufficient.

Unchecked and editable

Fuzzy matching is available for the field, but it is currently disabled.

This state may appear for supported matching fields when the user chooses not to use fuzzy matching.

Greyed out and checked

Fuzzy matching is enabled, but the user cannot change it from this screen.

This state may appear when fuzzy matching is enforced by the system for a supported field.

Greyed out and unchecked

Fuzzy matching is disabled, and the user cannot enable it from this screen.

This state may appear when the field supports fuzzy matching in some contexts, but not for the selected template or configuration.

N/A

Fuzzy matching does not apply to the field.

Examples may include fields such as:

• Vendor
• Due Date
• Date
• Vendor Bill Ext ID
• Currency
• Total Amount
• Total Tax
• Net Amount
• Invoice Received Date
• Entity
• Bot Confidence Level
• Freight Amount
• Description
• Service Period Start
• Service Period End
• Prepaid
• PO Line Number
• Contract Line Number
• Line Entity
• Cost Center
• Spend Category
• Quantity
• Price
• Amount

Note: Fuzzy matching availability is determined per field. Not all enabled fields support fuzzy matching.

Decimals

Controls the number of decimal places used for supported numeric fields.

The Decimals column determines the decimal precision applied to numeric values extracted for the field. This setting is available only for fields with a Field Type of Number.

User action

Users can interact with this column as follows:

• Enter or update a numeric value to define the number of decimal places, if the field is editable.
• If the value is displayed in a disabled input box, the decimal precision is controlled by the system and cannot be changed in the Template Settings grid.
• If the value displays as N/A, the setting does not apply to that field.

Typical values

Examples may include:

• 2 – Use two decimal places
• N/A – Decimal precision does not apply to the field

Scenarios

Editable numeric value

A decimal value is shown and can be updated by the user.

Examples may include supported number fields with configurable decimal precision.

In this state, the user can define how many decimal places SmartVendor uses for the field.

Read-only numeric value

A decimal value is shown, but the input box is disabled.

Examples may include fields such as:

• Total Amount
• Total Tax
• Net Amount
• Freight Amount
• Quantity
• Price
• Amount

In this state, the field uses a defined decimal precision, but the value cannot be changed from this screen.

N/A

Decimal precision does not apply to the field.

Examples may include fields such as:

• Vendor
• Due Date
• Date
• Vendor Bill Ext ID
• Currency
• Payment Terms
• Invoice Received Date
• Entity
• Bot Confidence Level
• Description
• Service Period Start
• Service Period End
• Prepaid
• PO Number
• PO Line Number
• Contract Line Number
• Contract Number
• Line Entity
• Cost Center
• Spend Category

Note: Not all number fields are necessarily user-editable in this column, even if a decimal value is displayed.

Extract from Bill File

Controls whether the field value is extracted directly from the invoice document.

The Extract from Bill File column determines whether SmartVendor reads the field value from the bill file during invoice extraction. This option is available only for supported fields.

User action

Users can interact with this column as follows:

• Select the checkbox to extract the field value from the bill file, if the checkbox is editable.
• Clear the checkbox to prevent the field value from being extracted directly from the bill file, if the checkbox is editable.
• If the checkbox is greyed out, the setting is system-controlled and cannot be changed in the Template Settings grid.
• If the value displays as N/A, extraction from the bill file is not supported for that field.

Typical values

Examples may include:

• Checked – The field value is extracted from the bill file
• Unchecked – The field value is not extracted from the bill file
• Greyed out and checked – Extraction from the bill file is enabled and cannot be changed
• Greyed out and unchecked – Extraction from the bill file is disabled and cannot be changed
• N/A – Extraction from the bill file does not apply to the field

Scenarios

Checked and editable

The field is configured to be extracted from the bill file, and the user can disable it if needed.

Examples may include fields such as:

• Total Tax
• Net Amount
• Payment Terms
• Description
• Service Period Start
• Service Period End
• Price

In this state, SmartVendor attempts to read the value directly from the invoice document.

Unchecked and editable

The field is not currently extracted from the bill file, and the user can enable extraction if needed.

This state may appear for supported fields where document extraction is optional.

Greyed out and checked

The field is extracted from the bill file, but the user cannot change the setting from this screen.

Examples may include fields such as:

• Vendor
• Due Date
• Date
• Vendor Bill Ext ID
• Currency
• Total Amount
• Freight Amount
• PO Number
• Contract Number
• Quantity
• Amount

In this state, extraction from the bill file is required or fixed for the field.

Greyed out and unchecked

The field is not extracted from the bill file, and the user cannot enable it from this screen.

This state may appear when the field exists in the template but direct extraction is not supported in the current configuration.

N/A

Extraction from the bill file does not apply to the field.

Examples may include fields such as:

• Invoice Received Date
• Entity
• Bot Confidence Level
• Prepaid
• PO Line Number
• Contract Line Number
• Line Entity
• Cost Center
• Spend Category

In this state, the field value is not expected to be read directly from the invoice document.

Note: Extracting a field from the bill file means SmartVendor attempts to capture the value directly from the invoice document, but other configuration settings may still influence the final value used.

Fallback

Controls the fallback behavior used for the field when the primary extraction or matching behavior does not provide the required value.

The Fallback column allows users to select field-specific fallback logic. Available options vary by field, so the values shown in this column are not the same for every row.

User action

Users can interact with this column as follows:

• Select a value from the dropdown to configure fallback behavior, if the dropdown is editable.
• If the dropdown is greyed out, the fallback setting is displayed but cannot be changed in the Template Settings grid.
• If the value displays as N/A, fallback is not supported for that field.

Example fallback values by field

• Due Date –
  • Extract first and auto generate if not available
  • Extract from invoice only
• Service Period Start –
  • Extract first and auto generate if not available
  • Extract from invoice only
• Service Period End –
  • Extract first and auto generate if not available
  • Extract from invoice only
• Entity –
  • Default to entity of last bill
  • Predictive Coding
• Freight Amount –
  • Do not write freight to SoR
  • Write freight at header level
  • Write freight at invoice line level
• Description –
  • Extract from invoice
  • Extract from invoice and translate to English
• Price –
  • Auto update on edits
  • Do Not auto update on edits
• Amount –
  • Auto update on edits
  • Do Not auto update on edits

Note: Additional field-specific fallback values may appear depending on the selected ERP, mailbox, and template.

Scenarios

Editable dropdown

A fallback value is available and can be changed by the user.

Examples may include fields such as:

• Due Date
• Entity
• Freight Amount
• Description
• Service Period Start
• Service Period End
• Price
• Amount

In this state, the user can choose the fallback behavior for that field.

Disabled dropdown

A fallback field is shown, but the value cannot be changed.

Examples may include fields where fallback is present but controlled by system behavior or template rules.

In this state, the selected fallback logic is visible but not user-editable.

Blank dropdown

A fallback control is present, but no value is currently selected.

Examples may include fields such as:

• Payment Terms

In this state, fallback may be supported for the field, but no fallback behavior has been configured yet.

N/A

Fallback is not supported for the field.

Examples may include fields such as:

• Vendor
• Date
• Vendor Bill Ext ID
• Currency
• Net Amount
• Invoice Received Date
• Bot Confidence Level
• Prepaid
• PO Number
• PO Line Number
• Contract Line Number
• Contract Number
• Line Entity
• Cost Center
• Spend Category
• Quantity

In this state, no fallback logic is available for the field.

Note: If needed, fallback values can also be documented separately by field so each dropdown option has its own description.

Subselections

Displays additional configuration options for the selected fallback behavior.

The Subselections column provides field-specific secondary settings that refine how the selected Fallback option works. This column is populated only when the selected fallback requires additional input or selection.

User action

Users can interact with this column as follows:

• Select a value from the dropdown when a secondary option is required.
• Enter a value when the fallback requires a user-defined input.
• If the control is greyed out, the subselection is displayed but cannot be changed in the Template Settings grid.
• If the value displays as N/A, no subselection is required for that field.

Typical values

Examples may include:

• Numeric input for a time period, such as 23
• Days as the associated unit for a numeric fallback value
• Blank dropdown when a fallback supports subselection, but no value has been selected yet
• Greyed-out dropdown when the subselection exists but is not editable
• N/A when no additional selection is required

Example subselection behavior by field

• Due Date: When the fallback is Extract first and auto-generate if not available, the subselection may include:

  • a numeric value, such as 23
  • a unit label, such as Days

  This allows the due date to be generated based on a specified number of days when extraction is not successful.

• Payment Terms: A subselection control may appear as a dropdown, but it can remain blank or disabled until a supported fallback option is selected.
• Entity: The subselection may display N/A if the selected fallback requires no additional configuration.
• Service Period Start and Service Period End: These fields may display an info icon with the fallback, while Subselections remains N/A if no secondary option is required.

Scenarios

Editable input or dropdown

A subselection is required and can be configured by the user.

Examples may include:

• Due Date, where the user enters a numeric value such as 23 and the unit is Days

In this state, the subselection refines how the fallback behavior is applied.

Disabled control

A subselection is present, but the user cannot change it from this screen.

Examples may include:

• fields where the fallback supports subselections, but the selected value is controlled by the template or system behavior

In this state, the subselection is visible for reference only.

Blank control

A subselection field is available, but no value has been selected yet.

Examples may include:

• Payment Terms, where a dropdown is present but no subselection has been set

In this state, the fallback may support additional configuration, but it has not yet been defined.

N/A

No subselection is required for the selected field and fallback combination.

Examples may include fields such as:

• Vendor
• Date
• Total Amount
• Net Amount
• Entity
• Freight Amount
• Description
• Service Period Start
• Service Period End
• PO Number
• Price
• Amount

In this state, the fallback works without any additional secondary input.

Note: Subselection values are field-specific and depend on the selected fallback behavior.

Allow Override with PO/Contract value Upon Match with PO/Contract

Controls whether the invoice field value is replaced by the corresponding PO or contract value when a PO or contract match is found.

The Allow Override with PO/Contract value Upon Match with PO/Contract column determines whether SmartVendor uses the value extracted from the invoice or overrides it with the matched value from the purchase order or contract. This option is available only for supported fields.

User action

Users can interact with this column as follows:

• Select the checkbox to allow the field value to be overridden by the matched PO or contract value, if the checkbox is editable.
• Clear the checkbox to retain the extracted invoice value even when a PO or contract match is found, if the checkbox is editable.
• If the checkbox is greyed out, the setting is system-controlled and cannot be changed in the Template Settings grid.
• If the value displays as N/A, PO/contract override is not supported for that field.

Typical values

Examples may include:

• Checked – Override with the matched PO or contract value is enabled
• Unchecked – Override with the matched PO or contract value is disabled
• Greyed out and checked – Override is enabled and cannot be changed
• Greyed out and unchecked – Override is disabled and cannot be changed
• N/A – Override does not apply to the field

Scenarios

Checked and editable

Override is enabled, and the user can disable it if needed.

Examples may include fields such as:

• Entity
• Description
• Line Entity
• Cost Center
• Spend Category
• Price

In this state, when SmartVendor finds a matching PO or contract, it can replace the extracted invoice value with the matched value for that field.

Unchecked and editable

Override is disabled, and the user can enable it if needed.

Examples may include fields such as:

• Payment Terms
• Quantity
• Amount

In this state, SmartVendor keeps the extracted invoice value even if a matching PO or contract value exists.

Greyed out and checked

Override is enabled, but the user cannot change it from this screen.

This state may appear when override behavior is required by the template or controlled by the system for the selected field.

Greyed out and unchecked

Override is disabled, and the user cannot enable it from this screen.

This state may appear when the field exists in the template, but override behavior is not available for manual configuration in the current context.

N/A

PO/contract override does not apply to the field.

Examples may include fields such as:

• Vendor
• Due Date
• Date
• Vendor Bill Ext ID
• Currency
• Total Amount
• Total Tax
• Net Amount
• Invoice Received Date
• Bot Confidence Level
• Freight Amount
• Service Period Start
• Service Period End
• Prepaid
• PO Number
• PO Line Number
• Contract Line Number
• Contract Number

In this state, the field is not configured to use PO- or contract-based override behavior.

Note: This setting does not control whether a PO or contract is matched. It controls only whether the matched value is allowed to override the extracted invoice value for the field.

Template Preview

The Template Preview section shows how the selected template applies to a sample invoice. It helps users review the invoice document, the extracted field values, and the line-item data based on the current template settings.

This section is useful for validating template configuration before saving changes.

Note: The preview is intended for validation and review. Users cannot edit invoice values directly in this section.

Table 2. Template Preview components

Figure 4. Template Preview

Invoice Document

Displays the source invoice document used in the preview.

The Invoice Document panel allows users to visually compare the invoice file with the extracted values shown in the preview.

Figure 4. Invoice Document

Standard Fields

Displays the extracted header-level invoice values identified by SmartVendor for the selected template.

The Standard Fields section in Template Preview helps users verify whether SmartVendor has correctly extracted and interpreted the key invoice values.

Field descriptions

• Vendor – The supplier name identified on the invoice.
• Due Date – The payment due date for the invoice.
• Date – The invoice date.
• Vendor Bill Ext ID – The supplier invoice number or external bill identifier.
• Currency – The currency in which the invoice is issued.
• Total Amount – The total invoice amount.
• Total Tax – The total tax amount identified on the invoice.
• Net Amount – The invoice amount excluding tax.
• Payment Terms – The payment terms identified on the invoice.
• Invoice Received Date – The date the invoice was received by the system or recorded for processing.
• Entity – The legal entity or company associated with the invoice.
• Bot Confidence Level – The confidence level assigned by SmartVendor for the extracted invoice data.
• Freight Amount – The freight or handling amount identified on the invoice.

Notes: 

Note 1: These fields are displayed for preview and validation purposes only.

Note 2: The values shown depend on the selected template configuration and the sample invoice used in the preview.

Note 3: The exact fields shown in the Standard Fields section may vary depending on the selected ERP, mailbox, and template.

Extended Fields

Displays additional extracted invoice values configured beyond the standard field set.

The Extended Fields section in Template Preview helps users review any custom or template-specific fields that SmartVendor extracts from the invoice.

Field descriptions

• Extended field name – The label of the custom or additional field configured for the template.
• Extended field value – The value extracted for that custom field from the invoice.

Notes:

Note 1: If no extended fields are configured, this section may be blank or display no values.

Note 2: These fields are displayed for preview and validation purposes only.

Note3: Extended fields are template-specific, so the names and values displayed in this section can vary across environments.

Note 4: The fields shown in this section depend on the selected ERP, mailbox, and template configuration.

Figure 5. Standard and Extended Fields

Line Items

Displays the extracted line-level invoice details identified by SmartVendor for the selected template.

The Line Items section in Template Preview helps users verify whether SmartVendor has correctly extracted and interpreted invoice line-item values.

Field descriptions

• Description – The description of the invoice line item.
• Service Period Start – The start date of the service period for the line item.
• Service Period End – The end date of the service period for the line item.
• Prepaid – Indicates whether the line item is marked as prepaid.
• PO Number – The purchase order number associated with the line item.
• PO Line Number – The purchase order line number associated with the line item.
• Contract Line Number – The contract line number associated with the line item.
• Contract Number – The contract number associated with the line item.
• Line Entity – The entity associated with the line item.
• Cost Center – The cost center assigned to the line item.
• Spend Category – The spend category assigned to the line item.
• Quantity – The quantity for the line item.
• Price – The unit price for the line item.
• Amount – The total amount for the line item.

Notes: 

Note 1: Each row in this section represents one invoice line item.

Note 2: The values shown depend on the selected template configuration and the sample invoice used in the preview.

Note 3: If template settings are updated, the values shown in Line Items may change accordingly.

Note 4: The exact fields shown in the Line Items section may vary depending on the selected ERP, mailbox, and template.

Figure 6. Line Items

Actions

Review and Edit

Opens the selected template so administrators can review and update field settings.

Save

Saves changes made to the template configuration.

Cancel

Discards unsaved changes and exits the editing view.