Fraud checks need source evidence
A fraud score is only useful when reviewers can see why it changed the workflow. Cogneris attaches evidence to risk signals so teams can inspect suspicious edits, mismatched fields, duplicate documents, and values that do not agree across a packet. Fraud verification is opt-in per tenant; extraction also requires template enablement. Results are advisory, and broken or unverifiable PDF signatures set a minimum review level.
Signals with a reason
Invalid CPF/CNPJ, impossible dates, PDF re-saves and metadata anomalies, error-level analysis, duplicate files, and C2PA and PDF signatures verified on the original upload.
Cross-document checks
Compare names, addresses, account numbers, dates, totals, and IDs across files.
Review thresholds
Route only high-risk documents or fields to human review.
Where fraud detection fits
Use document fraud detection in onboarding, lending, insurance claims, AP automation, tenant screening, KYC, vendor setup, and customer portals where a forged file can create downstream financial or compliance risk.
Verification before approval
Pair fraud scoring with document verification rules: expected document type, required fields, cross-document consistency, duplicate checks, expiry dates, and review thresholds. The output should explain whether a document is approved, rejected, or waiting on a reviewer.
Related pages
Summarize this page with an AI assistant
Open this page in an assistant with the summary prompt already written. We publish the whole site as plain text at llms-full.txt, so an assistant can read what we actually wrote instead of inferring it.
Assistants summarize, and they get things wrong. Check anything that matters against this page, or ask us directly.