Connect the documents
See how information in one supporting document relates to another.
Illustration · Fictional data
DOKSIMA · DOCUMENT FRAUD DETECTION
Spot document fraud.See the evidence.
PDF edits, copied glyphs, signs of AI generation: Doksima combines file forensics with cross-document checks. Every alert leads back to what triggered it.
Payslips · Bank statements · French tax notices
Private beta · Join the waitlist
DOKIMASIA
Examine before you conclude.
DOCUMENT FRAUD, UNDER THE MICROSCOPE
Forgeries leave
traces.
An added font. Copied digits. A generated page texture. Doksima examines how a document was made, then connects the findings to the rest of the file.
ENGINE RESULT · SYNTHETIC EXAMPLE
One font stands apart.
The check found an isolated embedded font: it displays just 8 characters among 1,600 characters using four other fonts. A construction anomaly uncovered inside the PDF itself.
Method and scope
Actual output of pdf_police_integree_isolee on a synthetic test PDF. A form or signature can leave the same trace: this check identifies a font anomaly, not a falsified value on its own.
FONT ANOMALY DETECTED
Font resource distribution · diagram
1isolated embedded font
8 / 1608affected characters · page 1
pdf_police_integree_isolee
PDF and glyph examples: saved engine results on test files. This website does not analyse documents live.
Then cross-check the documentsCROSS-CHECK THE DOCUMENTS
Connect the documents.
Uncover the discrepancies.
Walk through a fictional file, compare its amounts and inspect the sources. No account. No documents to upload.
GUIDED DEMO
Prepared scenario · Fictional data · Not live document analysis
EXAMPLE FILE · AUGUST 2026
Same person. Same month.
€3,250 net pay on the payslip. €2,750 salary on the statement. Locate both amounts, compare the calculations and trace the difference to its source.
The source PDFs are fictional and written in French.
From document to finding. From finding to source.
THE PRODUCT, IN PRACTICE
Documents connect.
The picture becomes clearer.
One workspace to track applications, inspect findings and organise the review. Document-check results and human review progress remain separate.
Examine the findings
Separate contradictions, indicators and points that need a better source.
Stay in control
Technical findings inform your review. They do not replace your decision.
AN ORGANISED REVIEW
Know where every application stands.
The review queue separates check results from your team’s progress. A finding to investigate is not a decision made on your behalf.
Prototype screenshots with demonstration data. The current application and source documents are in French. This is a product walkthrough, not live document analysis.
δοκιμασίαDOKIMASIA
Our name draws on dokimasia, the Greek idea of examination.
Understand before you conclude.
Chapter I
Actionable findings
A finding.Its source.Your decision.
A re-exported, scanned or reissued document may show legitimate differences. Doksima distinguishes observations to review from contradictions established within the scope of its checks.
01
Find the source
Return to the excerpt and page that contain the reviewed information.
02
Qualify the finding
Distinguish modification traces from verified contradictions between documents.
03
Decide what happens next
Request the original, seek an explanation or document the outcome of your review.
Chapter II
The promise
Understand beforeyou conclude.
Doksima turns checks into actionable findings: what was detected, where to find it and what to verify next. Your team keeps a clear record of every decision.
01
An explained result.
The main result is a documented conclusion, not a probability of fraud. Coverage indicators remain separate.
02
A sentence for every conclusion.
Each check says what it observed—and what it cannot establish. You know exactly where the evidence stops.
03
When the document is not enough, we do not guess.
An insufficient reading is labelled as such. If the document prevents verification, a better source may be needed. A service failure remains an internal incident.
04
A check you can trace.
Findings are linked to their sources, checks and versions. Reproducing a review also requires retaining the settings and reference data used.
Chapter III
Four verdicts
Four possible answers.
No more than that.
No scale, no quantified grey area. Every verdict has a fixed definition, sample wording and a limit stated plainly.
01
Contradiction established
Contradiction established
Proven consistent
To review
Original required
Contradiction establishedDoksima · report
Document no. —Page 1 / 3
A material contradiction is established within the scope of the check, using readable data. It is identified and located.
Sample wording in the report
« The stated total does not match the sum of its line items. »
What this check does not say
A calculation error does not prove deliberate falsification. This check establishes neither author nor intent.
01
Contradiction established
Contradiction establishedDoksima · report
Document no. —Page 1 / 3
A material contradiction is established within the scope of the check, using readable data. It is identified and located.
Sample wording in the report
« The stated total does not match the sum of its line items. »
What this check does not say
A calculation error does not prove deliberate falsification. This check establishes neither author nor intent.
02
Proven consistent
Proven consistentDoksima · report
Document no. —Page 1 / 3
The required content checks conclude that the document is consistent, with sufficient coverage within the reviewed scope.
Sample wording in the report
« Dates, amounts and issuer match from one page to the next. »
What this check does not say
This check does not say the document is authentic at source. It says it is internally consistent.
03
To review
To reviewDoksima · report
Document no. —Page 1 / 3
An unusual element has been observed. It is not enough to prove falsification. We state it plainly.
Sample wording in the report
« The file creation date is later than the document issue date. »
What this check does not say
This check does not say the applicant lied. A document reissued by its issuer may produce this finding.
04
Original required
Original requiredDoksima · report
Document no. —Page 1 / 3
The supplied copy does not allow a conclusion. We do not guess. We request the original document.
Sample wording in the report
« Photograph of a screen. Structural checks cannot be applied. »
What this check does not say
This verdict says nothing about the applicant's honesty. It says this copy is not enough.
Chapter IV
Checks
From file structureto the figures.Connect the findings.
Editing traces, character anomalies, calculations and cross-document consistency: Doksima combines several lines of analysis to reveal what deserves your attention.
Example checks
10/ 10
Illustrative examples. Applicable checks depend on the document type, its readability and available sources.
“Every alert leads back to its source.”
What it finds
The stated total does, or does not, match the sum of its line items.
What it does not say
Where the amounts come from.
What it finds
Readable pay and deduction entries allow gross and net calculation to be checked.
What it does not say
That the salary was paid.
What it finds
One page’s closing balance is the next page’s opening balance.
What it does not say
That this is the holder’s only account.
What it finds
Document dates follow one another and are possible.
What it does not say
That the transaction actually took place that day.
What it finds
Metadata are compared with visible dates when available; an honest reissue remains possible.
What it does not say
Who created the file.
What it finds
Readable identifiers are checked; external verification depends on available references.
What it does not say
That the issuer produced this specific document.
What it finds
Information covered by the check is sought; this is not a complete regulatory audit.
What it does not say
That its content is accurate.
What it finds
Character or layout breaks may be flagged for review.
What it does not say
That an irregularity is deliberate.
What it finds
Accessible reissue traces may be noted; their absence does not prove no modification occurred.
What it does not say
Who modified it, or why.
What it finds
Name, address and amounts match across documents in the same file.
What it does not say
That the file is complete.
…A checking scope to define for each document.
Chapter V
The independent channel
Consistency can be checked.Origin must be verified.
A consistent document does not, by itself, prove who issued it. Depending on the file, confirmation from an authorised source may complete the review.
In the document
Information to compare.
Dates, amounts and references can be compared when readable. The result specifies which checks were actually performed.
At source
Confirmation to obtain.
The analyst may contact the issuer through a verified, authorised channel. This remains distinct from checking the document; Doksima does not carry it out automatically.
Know what the document allows you to conclude. And what it leaves open.
Chapter VI
The report
A report.Dated. Explainable.
A report brings together the checks, sources and review limits. The example below illustrates how to read it; it is neither a result on a real document nor a legal guarantee.
Doksima
Verification report
Ref. DK-EXEMPLE-001
4 September 2026
10:42:08
Document
Payslip · 3 pages
Requested by
Example organisation
Source
Provided by the applicant
Verdict
To review
An unusual element was found. It is not enough to establish falsification.
What we found
The file creation date is later than the document issue date.
What this check does not say
That the applicant lied. A document reissued by its issuer can produce this finding.
Example · 6 checks illustrated5 with no issue · 1 finding
01 · Line-item totalNo issue noted
02 · Gross and net payNo issue noted
03 · Date sequenceNo issue noted
04 · File dateFinding
05 · Identifiable issuerNo issue noted
06 · Required informationNo issue noted
… other applicable checks
Recommended next step
Consider whether confirmation from the issuer through an authorised channel can clarify this point.
Fictitious example · retain checks and sources.
No score. No percentage.
No score. No percentage.
Page 1 / 2
A reference date
The example shows a date and time to place the review in context. This is not a certified timestamp.
A tracking reference
The example has a reference number to identify the report and link it to the application reviewed.
A traceable review
To compare two reviews, retain the documents, checks, versions and settings. The result can change if any of these change.
Readable without a manual
Written for compliance officers, branch managers and lawyers to read directly, without technical jargon.
Who it is for
Three sectors.The same standard.
IPayslips · Tax notices · Bank statements
Lending
Before approval, not after. A verdict for each document, a sentence for each conclusion, and a list of documents to obtain through another channel.
IIComplete tenant application
Rentals
An honest applicant should not have to defend against an unsupported accusation. Get a clear report that can be shared with the landlord.
IIIInvoices · Claim documents
Insurance
The aim: a dated report with sources and explicit review limits, making it easier for a third party to understand.
First pilots
Let’s build the review
that helps you move forward.
We are preparing initial pilots with brokers and financial teams. The aim is to measure the time needed to understand a file and the back-and-forth a better documented review may avoid.
01
Understand your current review
02
Agree on a scope together
03
Measure the pilot results
For teams that review documents
Forgeries evolve.Your reviewshould too.
Brokers and financial teams: go beyond what the eye can see. Uncover modification traces, cross-check documents and document your decision. Request a place in Doksima’s private beta.
- File and glyph forensics
- Cross-document consistency checks
- Explained alerts, accessible sources
PRIVATE BETA · WAITLIST
Get in on early access.
Join the waitlist for professionals who want to test Doksima. We’ll contact you personally about beta invitations.
Lumelia stores your email, language and consent date in private Vercel storage to manage beta invitations. No newsletter signup. To access or remove your registration: billel@lumelia.io.