Login
VAAS · Claims & Onboarding

The team reviews exceptions, not PDF stacks.

Fraud signals in claims with a ready dossier, DMHO tampering detected in seconds, and PJ seller onboarding with UBO and restrictive lists. Analysis goes straight to the critical case.

The problem

Fraudulent claims hide in volume.

Three pain points that stall insurance claim review and PJ onboarding.

Volume

Reading document by document does not scale.

The team receives a PDF stack: report, invoice, DMHO, receipt. Reading each one manually to find tampering is slow and exhausting, and the fraudulent claim slips through mixed with legitimate ones that need fast payment.

Seconds
is how long AI reading takes where manual review spends hours per case
Tampering

Altered dates and amounts pass the human eye.

Edited hospital medical document, document resubmission, altered amount: the fraud is subtle and repeated. Without tampering detection with an audit trail, a PDF edit becomes a paid claim and recurring loss.

3x
the same document resubmitted is a pattern that only appears with cross-referenced history
PJ onboarding

PJ seller onboards without UBO or list check.

Onboarding a legal entity looking only at CNPJ ignores shareholders, ultimate beneficial owner, and exposure in restrictive lists. The marketplace or insurer accepts a structure carrying risk no one mapped.

UBO
shareholders, beneficial owner, and lists must close before onboarding becomes a relationship
What we cross-check

Everything in a single call.

Public and private sources queried in parallel, normalized and weighted by the use-case matrix.

Medical document OCRTampering detectionResubmissionCorporate registry and UBOPEP and sanctions listsAdverse media
Regulations covered
Circ. SUSEP 612CP art. 171COAF · ReportingLGPD
Anatomy of a finding

One DMHO. Signal in seconds.

The engine reads the hospital medical document, detects date and amount tampering, cross-references resubmission and provider recurrence, and returns the case to the team with a finding and an auditable trail.

FINDING · SIN-2026-04812 · Jun 09 14:22
Claim · DMHO · repeat provider
signal · review
Document
TypeDMHO_2026.PDF
OCR consistency96.4% signal
Tampering detectedDate + amount
Audit trailComplete
Cross signals
!Date tampering
!Amount tampering
!Document resubmitted · 3x
!Repeat provider
!Amount above average
Beneficiary · lists
Insured registration
!File metadata
Score · claim risk
Tampering signalHigh · 96.4%
Provider recurrenceConfirmed
Amount deviationAbove average
Global score79/100 · yellow
AI-generated summary

Recommendation: Send to review team with fraud hypothesis. DMHO with tampering signal on date and amount (96.4% consistency), document resubmitted 3 times, and repeat provider. Amount above category average. Consolidated evidence and auditable trail attached to the finding.

1
DMHO tampering detected by AI

Hospital medical documents with altered dates or amounts are flagged in seconds, with the document region that triggered the signal highlighted for the team to verify.

2
PJ onboarding resolves shareholders and UBO

PJ seller onboarding does not stop at CNPJ. Shareholders, ultimate beneficial owner, and PEP, sanctions, and adverse media lists all feed the same decision.

3
Team receives a finding, not a raw PDF

The critical case arrives with a fraud hypothesis and consolidated evidence. The team reviews the exception with context, and the legitimate claim moves to fast payment.

Regulatory

Claims and onboarding regulators require.

Insurance fraud prevention and onboarding due diligence are requirements from the sector regulator and AML rules. Four instruments underpin the control.

612
SUSEP Circ. · 2020

AML/CFT in the insurance sector

Insurers follow a risk-based approach with monitoring and identification of suspicious operations. Claims analysis feeds detection.

171
Penal Code · §2, V

Insurance fraud

Fraud to receive insurance indemnification is a crime (art. 171, §2, V of the Penal Code). Tampering detection with an auditable trail supports evidence for investigation and denial.

COAF
Report · UIF

Suspicious activity reporting

Relevant fraud signals in claims or onboarding may feed a COAF report under art. 11 of Law 9.613/1998. The auditable trail backs the decision to report.

LGPD
Law 13.709

Health data processing

Health data in DMHO is sensitive. Processing has a fraud prevention basis, defined purpose, and retention per policy.

Rollout

From kickoff to go-live in 4 weeks.

The architecture is multi-tenant. What changes are the document types, tampering thresholds, and each client's review policy.

01
Week 1

Discovery & scope

Mapping document types (DMHO, invoice, report), PJ onboarding flow, and cases that go to review.

02
Week 2

Calibration

Tuning tampering thresholds, recurrence rules, and PJ onboarding matrix. Validation on historical cases.

03
Week 3

Directed pilot

Analysis of a slice of claims and onboardings in parallel. First findings for review team validation.

04
Week 4

Go-live

Document analysis in production. PJ onboarding with active UBO. Review team receiving ready findings with auditable trail.

Ready?

Decide in seconds.
Start with a meeting.

In 15 minutes we show how VAAS works in your scenario, with your rules, your data, your volume.

Explore the platform