Skip to main content
When designing a journey, the Document Classification module must always be the first documents module, as other modules depend on successful document classification to work properly.

​
Required module order

The v2 document modules must run in the following order:
  1. Document Classification
  2. Document Extraction
  3. Document Authentication
Document Extraction depends on Document Classification, and Document Authentication depends on both. Document Authentication can’t run in parallel with Document Extraction, because it checks the extracted fields against the document image.
Document Classification produces the anchor image, so a Facematch Verification module can run in parallel with Document Extraction and Document Authentication. To learn more, refer to the Combine document and biometric modules guide.
There are two ways to group document modules in the Journey builder.

​
Example 1: Evaluation node after classification module 

You can use an evaluation node after the classification node, like this: 
Document Evaluation Pn
In the screenshot above, Document Classification comes first after the Start of journey node, and an evaluation node follows next. If the document is classified, Document Extraction runs, followed by Document Authentication. Otherwise, the journey ends.

​
Example 2: Without an evaluation node after the Document Classification module 

Document modules can be run without an evaluation node first, as described in the previous section. This time, classification runs first, followed by Document Extraction and then Document Authentication, with evaluation occurring after all modules complete, like this:
Document No Evaluation Pn

​
Best practices for document module grouping 

  • Start with the Document Classification module. The module scans the submitted document to determine its type and validity. 
  • Add evaluation after Document Classification. You can include an evaluation step after the Document Classification module as a best practice. If a document is classified successfully, then the other modules run.
  • Keep Document Extraction before Document Authentication. Authentication depends on the extracted fields, so it can’t run first or in parallel with extraction.
The required order of the document modules is fixed, but the evaluation steps around them are provided as examples. Choose the evaluation and routing that best fits your use case.
Read the Set up evaluation documentation to learn more about evaluations.