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.

Use Set up fraud detection for rule configuration and testing steps. This page defines phases, scoring, and access.

• 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 for a document type is reached via Document Types > Configure > Fraud Detection > Edit Rules. Rules can come from pre-built templates, be authored in natural language, or be written as custom logic.

Rule configuration for a document type is reached via Document Types > Configure > Fraud Detection > Edit Rules.

Fraud Detection for a document type, listing each configured rule with its description, Enabled state and weight, and Edit Rules top-right

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.

Fraud Detection Checks — the 22 auto-enabled system checks grouped by category, each tagged Pre OCR with its weight on the 0–10 scale

Workflow

1. Configure — set up fraud rules for a document type by starting from a recommended template, writing a natural-language rule, or defining custom rule logic.
2. Tune thresholds — enable the pre-OCR and post-extraction phases you want, then set category weights and risk thresholds for the document type.
3. AI review — before saving, the assembled rule set is scored by an LLM with an overall score, strengths, and improvement suggestions that can be turned into additional rules.
4. Test — before going live, run the rule set against a previous extraction using the testing panel to confirm expected behavior.
5. Pre-OCR check — when a document is uploaded, visual forensic checks run against the raw file if the pre-OCR phase is enabled.
6. Post-extraction check — once extraction completes, the post-extraction phase evaluates extracted fields against the configured rules.
7. Score and flag — each rule passes, fails, is skipped, or errors. Category scores roll up into an overall score and risk level.
8. Review — open the fraud analysis for an extraction to see the risk level, category breakdown, and details for each failed rule.

Step 1 of Fraud Detection Ruleset under Templates, offering pre-built rules such as P.O. Box Domicile Prohibition and Collateral Asset Eligibility Filter, each with a category tag

The same step under Manual, where selected custom rules are listed with edit and delete controls and New Rule

Rule config → Pre-OCR analysis ⎫
⎬→ Consolidated result → Risk level
Post-extraction analysis ⎭

Owner and Admin have full access to rule configuration, including the AI review step and the testing harness. Member and Viewer can view the same rule set and use the testing harness under Validate, but cannot edit rules.

Related pages

• Set up fraud detection explains rules, testing, and verdict review.
• Document Types defines the document types and recommended templates used during setup.
• Document Extraction provides the extracted fields this flow evaluates after processing.
• Test Dashboard helps validate extraction quality before you tighten fraud rules in production.