Configuring your Inquiry Template for Documents

What is Documents?

Documents is a verification step that you can configure as part of your company’s user diligence or business diligence processes, such as providing proof of address, proof of SSN, proof of EIN, and more. Each Documents collects a document (SSN cards, W2s, IRS notices, utility bills, etc.) from the end user to extract, process, and verify documents according to your specifications.

Learn more about Documents here.

 

Getting Started

To get access to Documents, please reach out to your contact at Persona.

Once you’ve been set up with a Documents step in your Inquiry template, we can use the Dashboard to modify your configurations by clicking Inquiries → Templates.

 

Click on your desired Inquiry template with a Documents flow.

 

From there, click Configure at the top right corner of the screen.

 

Once on the Configurations screen, Click Verifications in the left-hand column, then select Document. Note that you may see multiple Documents if your Inquiry template contains multiple Documents steps.

Congratulations! Now you’re ready to modify a Documents configuration.

 

Verifications Checks

Within the Verification checks section at the top of the screen, you will see a list of verification checks that every document runs through. In addition, the output of each check within an inquiry can be reviewed within Dashboard → Inquiries → All Inquiries.

Next to each Verification check is a checkbox labeled Required to pass. If this checkbox is enabled, the Verification Check will have to pass for the document to be accepted (e.g., in the screenshot above, Compromised submission is Required to pass. This means that if the document is a Compromised submission (i.e., the document is found in a publicly available source), Persona will reject this document). Depending on your business needs, you can configure which verification checks should be required.

You may notice that Extracted properties detection has different settings than other Verification Checks. For example, we can configure Extractions below and add them to this check to ensure that given extractions are found before passing the document.

 

In this example, the extraction named Owner Name 1 is required for the Document checks to pass.

 

Extractions

Persona can extract and verify specific information from a document.

Note: all extraction is dependent on the quality of the images provided.

There are two types of extractions: Guided Extractions and Unguided Extractions.

• Use Guided Extractions when looking for known user information (e.g., user name, address) in a document.
• Use Unguided Extractions when looking for general information (e.g., all names found in the document, regex) in all documents.

Guided Extractions

Guided Extractions leverages user-specific information (e.g., individual’s name, EIN) to match and guide the extraction process. For instance, Persona can compare an individual’s name extracted via a Government ID Verification with the same name found in a utility bill Documents extraction in order to verify that the document belongs to the same individual.

Creating a Guided Extraction

Click Add Extraction → Guided Extraction to get started.

 

 

Under Extraction Field Name, click on the dropdown in order to select a field name. This is a field that will be used as the source for the guided extraction (e.g., an individual’s Address City extracted via a Government ID Verification). This information was previously collected in the inquiry flow.

 

Under Extraction Type, we can select from a variety of pre-configured types. Please choose a description that best fits your Extraction Field Name to improve match quality.

 

Under Match Requirement, we have three options:

• Full: The match should be exact (e.g., abcd is a full match for abcd). Persona can handle most common abbreviations found in street names (e.g., St.) and titles (e.g., Ms.) when considering an exact match.
• Partial: Persona allows for some variations in the text (e.g., abcc is a partial match for abcc).
• None: Any match (or the lack thereof) will be considered a match. This setting should be used sparingly in most Document checks.

Note: Match requirements are not case sensitive.

 

Before we press Done, let’s take a look at the section Add to Extracted Properties Detection. If you want to ensure that this extraction is always found before passing a Documents check, please check the checkbox before pressing Done.

 

Unguided Extractions

Unguided Extractions are used when extracted data does not need to be corroborated with user-specific information. In Unguided Extractions, data extraction from documents is often supplemental.

 

Creating an Unguided Extraction

Click Add Extraction → Unguided Extraction to get started.

 

Under Extraction Field Name, select any field name that best matches the extraction type you’re looking to extract. This property is used as an identifier and does not affect your extraction in any other way.

 

Under Extractor Type, you can select from four different extractor types.

 

• Text: Search for a specific string

  

  • Text Pattern: Input a string you wish to search for in a document.
  • Maximum Edit Distance: Edit distance determines the level of error tolerance permissible in your document. Choosing 0 would require an exact match. It’s recommended that you select a number between 0-2.
  • Extract Action
    • Accept: Finding the Text Pattern constitutes a match.
    • Reject: Matches on the Text Pattern are filtered out from matches that are accepted.

• Regex: Use regular expression to search for a specific text pattern

  • Regex Pattern: Input a valid regex pattern to match against the extracted text from your document.
  • Extract Action
    • Accept: Finding the Regex Pattern constitutes a match.
    • Reject: Matches on the Regex Pattern are filtered out from matches that are accepted.

• Preset: Detect instances of information units like person, organization, and location names and various numerical expressions like time, money, etc.

  Persona uses machine learning models to intelligently detect instances of entity types labeled Preset. Entity types are a variety of information units like person, organization, location names, and various numerical expressions like time, money, etc.

  • Preset:
    • Choose from a variety of different entity types. Persona will automatically extract all instances of selected Presets in a given document.

• Key Value Pair: Scan for search keys, which are a list of field names or labels. Persona will then automatically scan for the value below or to the right of the search key if it is found in the document.

  • Search Keys:
    • Search Keys are a list of field names or labels ****that Persona will intelligently search for in a given document to identify the corresponding value. For instance, if a document contains the text “Name: John Doe,” listing “name” as a Search Key will allow Persona to intelligently scan the document for the corresponding value (i.e., “John Doe”).
    • Persona will automatically configure settings to scan for the value below or to the right of the search key if it is found in a document.

Creating an Unguided Extraction (Cont.)

Before we press Done, let’s take a look at the section Add to Extracted Properties Detection. If you want to ensure that this extraction is always found before passing a Documents check, please check the checkbox before pressing Done.

Publishing your Template

Now that you’ve modified your Verification Checks and created new Guided and Unguided Extractions, you’re ready to publish your changes!

Be sure to Save all of your changes to ensure that you can come back to the Documents configurations just as you’ve left them.

Once you’re ready (and have pressed Save in the step above), you can press Publish. All newly created Inquiries for this Inquiry flow will now reflect the changes you’ve made from the steps above.