Appearance

Document types ​

Recognito ships extraction models for three common document types out of the box, plus a custom-model path for anything else. Each project locks to one document type at creation.

The type you pick determines what fields the engine knows to extract by default, how Studio renders the document, and what line-item tooling is available.

The three prebuilt types ​

Recognito ships three prebuilt models, each with a default field set tuned to its document type:

  • Invoice — the most common type, and broader than its name suggests. It also handles purchase orders, delivery notes, and credit notes — purchasing documents generally.
  • Receipt — for point-of-sale receipts.
  • Handover & Acceptance Certificate — for formal acceptance documents, where a deliverable is signed off on a certificate.

The default field set is what differs between the types. Everything else — line-item editing, field categories, Mapping, workflows, integrations — works the same across all of them.

Custom document types ​

If none of the three prebuilt models match what you're processing — debt reconciliation forms, material testing certificates, engineering drawings, anything specific to your industry — Recognito can build a custom extraction model.

Custom models are added on request. Talk to your account manager or Recognito support. The path involves sharing representative sample documents; Recognito's team trains an extraction model for your document layout. Once complete, the new type appears in your org's project-creation picker and you create a project using it.

Custom models have the same configurability as prebuilt types — field categories, Mapping, workflows, users, integrations all work the same way.

Adding custom fields to a prebuilt type

You don't always need a custom model. If you're using the Invoice type and need one or two extra fields (a Polish VAT number, a custom internal reference), you can add them as Main fields with AI Post Processing enabled. The base model handles the standard invoice fields; AI Post Processing extracts the custom ones via a second-pass LLM call.

This is the self-serve path. Custom-model requests are for cases where the document layout itself is non-standard.

Type is set at project creation ​

You pick the document type when you create the project. It's not changeable afterwards.

If you create an Invoice project and decide you actually need a Receipt project, the path is to create a new project with the right type and abandon the first. The documents in the wrong-type project don't migrate, so pick the type deliberately up front.

Adjusting fields after creation ​

While the type itself is fixed, the field schema is editable. You can:

  • Add custom fields (with optional AI Post Processing).
  • Remove fields you don't use (hide them from Studio).
  • Reorganize categories.

See Field categories for the full guide.

What's next ​