Overview
Veridox provides quantified risk assessments for every document analysed, enabling automated decision-making in verification workflows. This guide explains how risk scoring works, how to interpret scores, and how to implement risk-based automation.Risk Score Levels
Veridox uses a four-tier risk scoring system:Informational
No significant concerns identified. Standard documentation with minor or expected variations.
Low
Minor anomalies detected that don’t indicate fraud. May require light review but generally acceptable.
Medium
Moderate risk factors present. Requires additional verification or manual review before proceeding.
High
Significant fraud indicators found. Document shows clear signs of tampering, fabrication, or inauthenticity.
How Risk Scores Are Generated
Risk scores are derived from comprehensive forensic analysis across multiple engines, including metadata examination, compression inconsistency detection (ELA), noise pattern analysis, and AI-powered context understanding. The overall risk score is determined by evaluating all component assessments, with higher-severity findings taking precedence.Confirming or Overriding Risk Scores
As an expert reviewer, you can confirm AI assessments or override them based on additional context using the Confirm Risk Score endpoint.When to Override Risk Scores
Consider overriding when:- Additional context available: External information not visible to AI (customer history, supporting documentation).
- Domain expertise: Specialised knowledge about document types or regional variations.
- False positives: AI flagged expected variations as anomalies.
Best Practices
Score Interpretation
Consider context - Risk scores are one input; combine them with your own business rules and domain knowledge.
Review findings - Don’t rely solely on the overall score; examine specific findings and evidence in the full analysis report.
Understand limitations - AI is a powerful tool but requires human expertise for highly sophisticated or unique fraud cases.
Compliance and Governance
Document decisions - Always provide confirmation reasons for a robust audit trail.
Security - Remember that users can only access and confirm risk scores for files they have created.
Escalation paths - Define clear escalation procedures for documents with “High” or “Medium” risk scores.
Related Resources
Confirm Risk Scores API
API reference for confirming or overriding risk assessments
File Analysis API
Retrieve detailed forensic analysis results
Document Analysis Guide
Complete document analysis workflow
Quickstart
Get started with document verification