Highlights
3 years in a row named a Leader First to achieve iBeta Level 3 on iOS and Android Introducing GovFaceMatch Privacy is the architecture
01/04
01/04
Non-ID Document Validation

Verify proof-of-address documents

Capture or upload utility bills, bank statements, and other supporting documents, with the address read into clean, structured fields.

0B+

identity checks processed on the Incode platform

0

structured fields extracted from every proof-of-address document

Image + PDF

formats accepted, captured with any camera or uploaded as a file

The problem

Address verification is stuck in manual review

Proof-of-address documents arrive as phone photos of paper bills and bank-statement PDFs. Layouts change with every country, issuer, and document type, capture quality varies, and manual transcription is slow and error-prone — friction that shows up as drop-off.

0%

of consumers abandoned a digital onboarding process in 2022

Signicat, 2022

0+

distinct proof-of-address layouts to read — every issuer and country formats documents differently

Incode, 2026

How it works

Four steps from paper to structured data

A guided module inside your verification flow: the user hands over the document, the module reads it, and the data lands in the same session as the identity check.

Pair it with Deepsight for Documents

Need to know the document is genuine? Add Deepsight

Non-ID Document Validation collects the document and reads its data. When the question is whether that document is real, Deepsight for Documents adds AI forgery detection to the same document layer — catching the forged bills and statements that manual review misses.

Its AI forgery detection identifies documents created or altered by generative tools through visual artifacts, font inconsistencies, and layout anomalies invisible to the human eye.

0x

more fraud caught than document-based checks alone

0x

growth in AI-generated document fraud over two years

0%

of synthetic document fraud caught

Use cases

Where supporting documents enter the flow

Account opening

Collect the proof of address regulators require alongside the ID, in the same session.

Lending and income

Collect pay stubs and bank statements in the same flow as the identity check.

Business onboarding

Collect the registration and operating documents behind a business account.

Ongoing compliance

Re-collect an up-to-date proof of address when regulation or risk demands it.

FAQ

Frequently asked questions

The questions buyers ask most about Non-ID Document Validation, answered straight.

Still have questions? Talk to an expert
What is non-ID document validation?

It is the collection and reading of supporting documents that are not identity documents: proof of address such as utility bills, bank statements, and telecom agreements, plus income and business documents. Users photograph or upload the document, and AI-powered OCR extracts its data as structured fields attached to the verification session.

Which documents can be captured?

More than 100 proof-of-address document types are supported, including utility bills, bank statements, and telecom agreements. The module also captures other supporting documents — pay stubs, voided checks, letters of authorization, business records — with the processing configurable per document type.

Can users upload a file instead of taking a photo?

Yes. The module accepts both camera capture and file upload, in image or PDF format, and can be configured as capture-only, upload-only, or both — whatever fits the channel and the audience.

Does it handle multi-page or two-sided documents?

Yes. The module can request the second side of a document or additional pages, each configurable as mandatory or optional, so multi-page bank statements and two-sided documents come through complete.

How is the data on the document extracted?

AI-powered OCR built for real-world captures, not flatbed scans. With processing enabled, it reads the document and returns structured fields — document type, full name, address, and dates — ready for your systems to consume.

Does it work together with identity verification?

Yes. It runs as a module inside the same verification flow, so the document and its extracted data land in the same session as the identity check — one flow for the user, one record for you.

What's next

Collect every document behind the decision