You are here: Setting up the system > Templates > Document templates: Overview

Document templates: Overview

Built-in document templates are provided for customer order solutions and invoice solutions. These templates are optimally configured for the specific type of documents you need to process. As a result, some document template types may come with built-in field templates or classifier templates.

(For Classify & Index solutions there are no built-in templates – see below.)

When you create a solution, appropriate document templates are automatically added to the Configuration tab of the Administration module. (To see these, expand Templates and click Documents.)

Document specifications that you then create in your solution, with Copy content from a template selected, are initially copies of the selected template at that moment. If you edit a template, the changes do not apply to existing document specifications; they only apply only to new document specifications that you base on that template.

 

Customer order solutions

Document templates for Customer order solutions are used when incoming documents are in different languages. Customer orders in different languages need to be processed in different batches, because documents in different languages cannot be processed at the same time.

For each customer order that you need to process in a different language:

  1. Create a new document specification.

  2. Select Copy content from a template.

  3. Select one of the available Customer Order document specifications.

 

Invoice solutions

There are three types of document templates used for invoice solutions:

Many factors—including whether or not an invoice solution uses master data—affect how specifications copied from Invoice document templates are used, whether or not your GE/PO document specifications should contain classifiers, and so on.

For more information, see Invoice solutions: Overview.

 

Classify & Index solutions

Using document templates for Classify & Index solutions—or for other complicated or generic solutions—is not recommended, and none are provided by default. Using document specifications to create a three-tier document hierarchy is a more effective way of providing a document structure and the necessary parent-child relationship among document types/variants in these solutions. ClosedMore information:

Level 1 in the hierarchy: Folder or category

The uppermost document acts as a category, or type of folder, for the specifications under it. It often has no classifiers and contains few fields (if any). These "folders" are often excluded for classification in Inspect. Do this by selecting Do not allow documents to be manually classified as this document type in the Classification settings of the Document specification dialog.

By grouping documents using folders, you can easily add new document types without having to make changes in the batch specification. In complex solutions, there could be several folder/category levels.

Level 2 in the hierarchy: Document type

The next specification in such a structure is a document type, a complete document specification. All of the fields expected to be on this type are specified, but classifiers may or may not be included.

Level 3 in the hierarchy: Document variant

The most specific level of document specification handles variations of the document types above it. The reason for the variation may be classification and/or extraction differences. There may even be times when a variant itself has one or more sub-variants. Layouts are a kind of document variant that reside in a document specification.

 

Table field templates: Overview

Creating a field template

Creating a classifier template