Forged, manipulated and AI-generated invoices, bank statements and contracts are getting harder to spot. Nio reads a document’s forensics, its content and its context — then returns a risk score and explains the decision in language an auditor can follow. Delivered as an API. It sits inside your workflow, not beside it.
01 — The problem
Forensic and registry signals routinely disagree. A name differs by legal form or diacritics. A registry address is stale. An IBAN is new — but legitimate. Deciding when that’s normal business change and when it’s an attack — and explaining that decision to an auditor — is the unsolved part.
That decision is what Nio is built for.
02 — The output
Not a verdict.
A reasoned decision.
A document arrives. Within seconds Nio scores it and shows its work — every signal, every contradiction, every reason — ready for your analyst and defensible in front of an auditor.
How it worksinvoice_2026-0912.pdf
Analysing…
Explanation output — every score ships with its reasoning.
03 — What Nio returns
A risk score
A calibrated score per document — not a black-box yes/no, but a measure your policy thresholds can act on.
Forensic signals
File structure, metadata, fonts, compression traces — what changed after the document was made.
Contextual signals
Registry records, IBAN changes, legal forms, addresses — does the document’s story match the world outside it?
An explanation
Every score ships with its reasoning, written for a human reviewer. Explainability is the output — not an add-on.
04 — Who it’s for
If a decision rests on a document, Nio checks the document. API-first — it slots into the workflow you already run.
Calibrated for the Croatian stack
Diacritics, legal forms, registry lag, domestic formats — the details generic tools miss.
05 — The state of the art
Off-the-shelf detection barely beats a coin flip.
0
DocTamper AUC on AI-forged docs — Wu et al., 2026
0
Zero-shot GPT-4o, same benchmark. Chance = 0.5
0
Best multimodal LLM — Liang et al., 2025
0
Methods tested; none reliable out of the box — Zhao et al., 2026
06 — In its lane
Scores. Explains.
Never accuses.
Nio doesn’t block payments and doesn’t make accusations. It measures, explains, and hands the decision to your analyst — with the evidence attached. The judgment stays where it belongs: with people.
- Never a black box
- Never an automatic rejection
- Every score comes with its reasons
07 — Built for trust
Our commitmentsExplainable by design
Every decision is written out, signal by signal, in language an auditor can follow. If we can’t explain it, we don’t ship it.
A full audit trail
Every check, every score, every version — logged and reproducible. Nothing happens off the record.
API-first, data-minimal
We process what verification needs and nothing more. Your documents are never sold or shared.
Accessible by commitment
The interface that shows scores and explanations is built to WCAG 2.2 AA — verified per criterion, not asserted.
08 — How it starts
01
Connect
One REST API. Send documents from your ERP, loan system or back office — no core replacement, no IT project.
02
Score
Each document comes back with a risk score and its full reasoning — forensic, content and contextual signals together.
03
Decide
Your analysts act on explained evidence, and the audit trail writes itself.
09 — Why now
Documents used to be evidence. Generative tools ended that — a convincing forgery now costs a cent and takes a second. We’re building the verification layer that lets a lender trust a PDF again.
Rolled out partner by partner. No public signup.