Catch the Same Document
Twice.
Holofin flags duplicate documents across your dossiers and repeated pages inside a single file, even after re-scans, crops, or format changes. No template setup.
Schedule DemoOne Document.
Three Applications.
Fraud rings and serial applicants recycle documents across dossiers. The same bank statement backs three different loan applications, re-scanned or lightly edited each time. A reviewer working one dossier at a time has no way to see it.
Recycled proofs
One income proof quietly supporting several unrelated applications.
Resubmissions
An applicant sends the same file again instead of the missing one you asked for.
Padded bundles
The same page repeated inside one file to make a bundle look complete.
Double scans
Honest mistakes that still cost review time and clutter the dossier.
Some duplicates are fraud and some are noise. Both belong in front of your team before a decision is made, not after.
Not Just Identical Files.
Exact resubmission
The same file uploaded twice, in the same or another dossier.
Re-scans and photos
A new scan or phone photo of the same paper document.
Crops and rotations
Trimmed, rotated, or reframed copies of a known document.
Format conversions
The same document exported to a different file format.
Different applicant, same document
One source document supporting several unrelated applications.
Repeated pages in one file
The same page appearing twice inside a single document.
Pages shared across documents
A page lifted from one document and reused inside another.
Zero configuration
Detection is always on. Nothing to enable, train, or maintain.
Every Document Remembered.
Every Match Surfaced.
Fingerprinted on arrival
Every document is fingerprinted page by page the moment it enters Holofin. No configuration, no templates, no examples to provide.
Compared against your history
Each page is compared to the other pages of the same file, then to your organization's full document history, across dossiers, workflows, and time.
Flagged with a confidence score
Matches surface as findings with a confidence score and a direct link to the other dossier, ready for your reviewers or your API consumers.
Questions
Duplicate detection, in short
Yes. A re-scan, a phone photo, a crop, a rotation, or a format conversion of a known document all match, because detection reads what the document looks like rather than the bytes of the file. Every match carries a confidence score so your team sets its own bar.
Yes. Every page is fingerprinted individually, so the same page scanned twice into one bundle is flagged, and so is a page lifted from one document and reused inside another.
No. Detection is always on for every document you process. There are no templates to set up, no examples to provide, and nothing to tune before it works.
It surfaces as a finding with a confidence score and a direct link to the matching document and its dossier, in the review screen and in the API response. Your reviewers or your automation decide what happens next.
Yes. Each new document is compared against your organization's full document history, across dossiers, workflows, and time. Documents from other organizations are never part of the comparison.
Built Into the Review.
Duplicate findings appear directly in the dossier review screen and in API responses, alongside fraud and consistency findings. One verdict surface for everything your team needs to trust a document.
See Fraud Detection →