Skip to main content

Custom Document Insights Intercom Guide

This guide explains what Custom Document Insights are, how they automatically flag documents based on configurable field/metadata conditions and severity levels, and how admins can create, edit, and view these insights in the Decision Engine.

Written by Patrick Cusack

What are Custom Document Insights?

Custom Document Insights are document-level flags that match your team's risk policies. Insights can be created based on document fields (such as document subtype, file type, employer, and account type) and document metadata fields (such as author, title, and creation date).

When a document is processed, any configured Custom Document Insights are evaluated automatically. If all conditions you have defined are met, the Insight will flag alongside other document signals and contribute to the document's risk rating.

Severity

When creating a Custom Document Insight, you must choose a severity level: High, Medium, or Low. This severity will be used when the Insight flags on a document and will contribute to determining the document's overall risk rating.

Examples

High-risk institutions

Flag documents from specific banks or financial providers your team considers elevated risk.

For example, you could flag any bank statement where the document subtype (bank name) is one of a list of known high-risk institutions such as Chime, Green Dot, or OnePay.

Suspicious document metadata

Identify documents with unusual or unexpected metadata that may indicate tampering or fabrication.

For example, you could flag any document where the metadata author contains the name of a known document-editing tool, or where the title does not match expectations.

Outdated documents

Surface documents that fall outside an acceptable date range for your use case.

For example, you could flag bank statements with a start date older than 90 days, or payslips where the end date is more than 60 days in the past.

Risky file formats

Catch documents submitted in unexpected formats that may warrant additional scrutiny.

For example, you could flag identity documents submitted as an Image PDF rather than a scanned image, or flag any PDF that is not a True PDF.

Employer-based flags

Flag payslips from employers known to be associated with fraud rings or synthetic identity activity.

For example, you could flag any payslip where the employer name contains a specific string or matches a list of flagged entities.

How to Create a Custom Document Insight

Navigate to the Decision Engine

Navigate to the Decision Engine in the web app. On the Insights tab, click the New Insight button and select the Custom Document Insight option.

Insight Configuration

Step 1 - Name & Description

Give your Insight a clear name and an optional description that explains what it is designed to detect. These details will appear in the Risk Analysis view when the Insight flags.

Step 2 - Severity

Select the severity level for this Insight: High, Medium, or Low. This determines how much weight the Insight carries when calculating the document's risk rating.

Step 3 - Conditions

Use this section to define the logic that powers your Insight. You can add one or more conditions based on the available document fields. All conditions must be true for the Insight to flag on a document.

For each condition, select:

  • Field – the document attribute you want to evaluate (e.g. Document Subtype, File Type, Employer)

  • Operator – the comparison logic to apply (e.g. equals, contains, is in list, older than)

  • Value – the value to compare against, entered as text, a date, or selected from a predefined list depending on the field

See Available Fields below for the full list of supported fields, operators, and input types.

Once you are happy with your conditions, click Save to create the Insight.

How to Edit a Custom Document Insight

If you need to change the conditions or severity of an Insight, navigate back to the Decision Engine. You will see the Insight you need to edit on the Insights page, in the Custom tab.

Click the edit button on the relevant Insight to be taken back to the configuration page. All updates are versioned, so a full history of changes is preserved.

Permissions

Only users with Admin permissions can create, edit, and delete Custom Document Insights. If you would like the ability to manage Insights, please reach out to your workspace Admins to update your permissions. Alternatively, ask your workspace Admin to create or update an Insight on your behalf.

Available Fields

The table below lists all fields available when configuring Custom Document Insights, along with their supported operators and input types.

Field

Logic

Account Type

equals / not equals

Author

equals / contains / does not equal / does not contain

Create Date

older than / newer than / between

Days since issue

greater than / less than

Days to expiry

greater than / less than

Detector results

must be one of / must not include

Document language

must be one of / must not include

Document software

must be one of / must not include

Document subtype

equals / is in list / does not equal

Document type

must be one of / must not include

Employer

equals / contains / not in list

End date

older than / newer than / between

File type

equals / is in list / not equals

Generated Date

older than / newer than / between

Is Merged Document

is true / is false

Main Insight

Existing logic

Quality Score

must be greater than

Sensitive Information Edited

is true / is false

Start Date

older than / newer than / between

Tags

must be one of / must not include

Text

contains / does not contain

Title

equals / contains / does not equal / does not contain

Trust Score

must be greater than

Note: If a document field is not available for a particular document type (for example, employer on a bank statement), the condition will be treated as not met and the Insight will not flag for that document.

Where can I see Custom Document Insights?

When triggered, Custom Document Insights will appear in the Document View. The Insight will display the name you configured and the severity level, and will contribute to the document's overall risk rating.

Clicking on a triggered Insight will surface further detail about which document and which field values caused the Insight to flag.

Did this answer your question?