How it works — in development
How Nio is designed to decide.
Three families of signals, one calibrated score, and an explanation a human can act on. Intended for delivery as a B2B API inside your workflow. Currently in development — not yet available.
01 — Three signal families
A forged document rarely fails one test. It fails the agreement between tests.
Forensic
The file itself: internal structure, metadata, fonts, compression traces. What was changed after the document was made — including edits invisible in the rendered image.
Content
What the document says: amounts, dates, VAT logic, references, internal consistency. Does the document agree with itself?
Contextual
The world around it: court and business registries, IBAN history, legal forms, addresses. Does the document’s story match reality — including Croatian specifics like diacritics and registry lag?
The score comes from how these signals agree — and, more importantly, how they disagree. A stale registry address next to a fresh IBAN and a subtly different legal form is a very different situation from any one of those alone.
02 — The explanation
Designed to show
its work.
The score is the headline; the explanation is the product. Each finding is to name its signal, what was expected, what was found, and how it moved the score — so an analyst can agree, override, or escalate with evidence in hand.
invoice_2026-0912.pdf
Analysing…
Illustration — the explanation output Nio is designed to return.
03 — The boundary
Nio measures. People decide. A score is evidence, not a verdict — the call stays with your analysts, with the reasoning attached.
Never
A silent verdict
No unexplained rejections. Every score carries its reasons, or it doesn’t ship.
Never
An automatic block
Nio doesn’t stop payments or close accounts. It routes documents to the right level of human attention.
Always
An audit trail
Every check and every score is logged and reproducible — defensible months later, not just at decision time.
04 — Integration
An API, not another portal. The intent: your team keeps their tools, and the documents arrive verified.
01
Send
A document POSTed from your ERP, LOS or back office. PDF, scan or structured e-invoice.
02
Receive
A risk score with structured findings and a human-readable explanation, per document.
03
Route
The score feeds your own rules: auto-clear, review queue, or escalate — your thresholds, your policy.
In development. Early-access conversations welcome.