When a document is submitted to Affinda, we apply our document classification model to classify the document into the different types of documents that we process (or other). Our classification model considers both the text within the document as well as the look and feel of the document or image to classify.
This document classification is used in two different ways.
If a document is sent to a Workspace, Affinda will use the document classification to route the document to the relevant Collection where the data will be extracted. For example, you may have an Accounts Payable workspace that you send all of your documents to. Affinda will classify the documents into a relevant invoice, credit note or receipt Collection to ensure you get the most relevant and accurate data extracted.
If a document is misclassified by our model, you can simply move the document from one Collection to another, either from the list view or from within the validation interface. We will re-parse the document with the model on the new Collection.
Workspaces can be configured so that Affinda automatically rejects documents that are not of the right type. These documents will be sent to the 'Rejected' list in the app, where they can be reviewed and moved to the appropriate Collection by a user.
Document rejection will occur when:
- If a document is sent to a Workspace and no relevant Collection is found within the Workspace
- If a document is sent to a Collection and the document classification doesn't match the type of Collection
Similar to document rejection based on classification, Workspaces can also be configured to reject documents that have already been processed. When a document is uploaded, Affinda will determine if this exact document has already been processed. If it has and the setting to reject duplicates is enabled, the document will be sent to the 'Rejected' list, where it can be forced back into a Collection if required.