Fraud Detection

Screen documents for fraud signals, in two phases, using configurable rules.

Fraud Detection runs alongside document extraction in two background phases so it does not block processing.

• Pre-OCR checks the raw file for visual forensic signals during upload.

• Post-extraction evaluates extracted data against configurable rules such as math or logic checks, compliance checks, and completeness checks.

Rule configuration

A document type is reached via Document Types > Configure > Fraud Detection > Edit Rules.

Capability	Description	Limit
Pre-OCR analysis	Visual forensic checks on the raw file, before OCR	Runs automatically if enabled; background thread
Post-extraction analysis	Rule-based evaluation of extracted field data	Runs automatically if enabled; background thread
Rule categories	math_logic, visual_forensic, social_engineering, compliance, completeness, threshold	Defined categories used in scoring
Rule sources	Pre-built templates, natural-language rules, custom rule logic	70+ document types have recommended templates
Rule weighting	Each rule contributes a weight toward the overall risk score	Weight range documented as 0–100
Risk levels	Aggregate score maps to a risk level	CLEAN, LOW, MEDIUM, HIGH, CRITICAL
Testing harness	Run fraud rules against a previous extraction before enabling them live	Test extraction listing capped at 100 results
Tenant configuration	Enable or disable phases, adjust category weights, and set risk thresholds per document type	Master on or off switch is admin-only

Generic pre-OCR templates apply to all document types automatically when the pre-OCR phase is enabled. Only custom rules can be toggled per document type.

The documented rule weight range of 0–100 does not match the live rule-editing UI, where rule cards and the Create or Edit Custom Rule form both use a 0–10 scale with a default of 5.