Documents to Reliable Data.
Without friction.

Pre-trained models, or your own families

Common types work out of the box. For the forms specific to your business, a classifier trains on your examples.

Looks at the page, not at a text layer

Layout and marks, read the way a person reads them. Phone photos and tenth-generation photocopies included.

The type routes the rest of the pipeline

Each type takes its own branch: its extractor, its rules, its destination.

Cut where the document actually changes

Mixed bundles, pieces stapled back to back, pages out of order. The boundary comes from the pages themselves.

Each piece attached to the person it concerns

With several participants in one case, completeness is counted per person, not per pile.

Described in plain language, not configured per issuer

Zone OCR needs a template per sender. Here the layout is read, so one schema covers senders you have never seen.

Fields, tables, handwriting, stamps

A figure in the margin, a date in a stamp, line items across a page break. If a person can read it, it can be a field.

Every value traceable to its source

Each value keeps the page and the box it came from.

Companies, from the INPI register

A SIREN or a SIRET returns the registered name, legal status, capital, head office and directors.

Addresses, in the AFNOR postal format

Checked against the Base Adresse Nationale and returned in the AFNOR postal format, next to the printed line.

The type of the field decides its source

Address, company number, 2D-Doc seal. Each comes back verified, not found or unchecked, never as a score.

Your rules, written as sentences, compiled to Hololang

Describe the check as you would to a new colleague. It becomes one readable line of Hololang, yours to correct.

A 2D-Doc seal is verified, not just read

Tax notices, payslips and attestations carry a signed barcode. We check that signature against the issuing authority.

Checks that cross documents and participants

The name on the bank details against the identity document, the balance against the lines. One verdict for the case.

A person sees only what needs a decision

A review step fires only when a rule fails. The rest keeps going, with the trail kept for the audit.

One call, values and verification together

Post the document, read back the fields, the verdicts and the rules that failed in the same REST response. A webhook fires when a case changes state.

Batches and files, in your format

SFTP drop and pickup, a pivot file shaped the way you describe it, and the split documents handed back typed and named.