KognitCapture · Solutions · Use cases

Every use case, every vertical, on one page.

Twenty-seven starter kits ship with the product. Each one creates a working project for one document type. This page lists all of them, the industries they serve, the uses that cut across industries, and what a kit leaves for you to set.

Test it on your documents →Solutions by role

Use cases by document type

27 starter kits · 20 capture · 1 search · 6 conversion

A starter kit, called a blueprint in the product, creates a project, its workflow and a template with its fields in one step. The twenty capture kits share one route: import, read, recognise, review, learn from the corrections, export. They differ in the fields, the table, how much is reviewed and the export format. "On doubt" means a reviewer sees a document only when a check fails or confidence is low.

Finance 2 kits

Use case	Document	Fields read, among others	Table	Review	Export
Finance	Bank statement	Account holder, account number, bank, BIC, opening and closing balance	Transactions	On doubt	JSON
Accounts payable	Supplier invoice	Invoice number and date, supplier, supplier VAT number and IBAN, tax amount, total. Format checks on VAT number and IBAN	Line items	On doubt	XML

Insurance 6 kits

Use case	Document	Fields read, among others	Table	Review	Export
Insurance claims	Insurance claim	Claim number, policy number, insurer, date and type of loss, claimed amount	Damaged items	On doubt	JSON
Policy administration	Insurance policy	Policy number, policyholder, insurer, effective and expiry date, sum insured, total premium	Coverages	On doubt	JSON
Underwriting submissions	Insurance proposal	Application number, proposer, cover type, sum insured requested, previous claims, estimated premium	Risk items	Model check, then on doubt	JSON
Health insurance claims	Health insurance claim	Claim number, member, provider, diagnosis code, admission date, total claimed. Format checks on diagnosis code and IBAN	Treatments	On doubt	XML
Motor claims	Motor accident statement	Date and place of the accident, driver and registration of each vehicle, circumstances, liability admitted	Damages	Model check, then every document	JSON
Certificates of insurance	Certificate of insurance	Certificate number, insured, insurer, certificate holder, effective and expiry date, aggregate limit	Coverages	On doubt	CSV

Compliance 7 kits

Use case	Document	Fields read, among others	Table	Review	Export
KYC onboarding	Identity document	Document number, surname, given names, date of birth, expiry date, issuing country, machine-readable zone, barcode	None	Every document	JSON
Anti-money laundering	Transaction monitoring report	Report reference, reporting entity, subject, suspicion category and narrative, total amount. Format check on IBAN	Transactions	Every document	XML
Proof of address	Proof of address	Issuer, document date, account holder, address, postal code, city, country	None	Every document	JSON
KYB business onboarding	Company registry extract	Company name, registration number, registry, legal form, VAT number, LEI, share capital. Format checks on VAT number and LEI	Officers; beneficial owners	Model check, then every document	JSON
Tax transparency (CRS / FATCA)	Tax self-certification	Form type, account holder, financial institution, entity classification, US person, US TIN, GIIN. Format checks on TIN and GIIN	Tax residences	Model check, then every document	XML
Sanctions and PEP screening	Screening report	Screening reference, subject, screening tool, lists screened, sanctions match, PEP match, disposition	Matches	Every document	JSON
Data protection consent	Data protection consent form	Controller, data subject, lawful basis, marketing consent, third-country transfer, retention period as written on the form	Processing purposes	Model check, then every document	JSON

Logistics 5 kits

Use case	Document	Fields read, among others	Table	Review	Export
Supply chain and logistics	Bill of lading	Bill of lading number, shipper, consignee, carrier, vessel, port of loading and of discharge. Format check on container numbers	Containers	On doubt	CSV
Goods receipt	Delivery note	Delivery note number and date, shipper, consignee, carrier, tracking number, received by, signature as a picture	Delivered items	On doubt	CSV
Warehouse and packing	Packing list	Packing list number, shipper, consignee, Incoterms, total packages, gross weight, volume	Packages	On doubt	CSV
Customs brokerage	Customs declaration	Declaration number, MRN, customs office, exporter and importer EORI, customs value, duty. Format checks on MRN, EORI and HS code	Items	Every document	XML
Air freight	Air waybill	Waybill number, issuing carrier, airport of departure and of destination, flight number, chargeable weight, total prepaid, barcode. Format check on the waybill number	Rate lines	On doubt	JSON

Document search 1 kit

Use case	Document	What it does	Review	Output
Document search	Mixed archives: any document you want to find again or ask questions about	Reads title, date, reference, author and type where present, then cuts each document into pieces per page and per table row, with page and confidence attached	None	A vector store you connect

Conversion 6 kits

Use case	From	To	Notes
Searchable PDF/A archive	Scans and image PDFs	Searchable PDF/A	Compressed for long-term storage. The output is written as PDF/A; it is not run through a conformance validator
Editable Word documents	Scans and PDFs	Word (DOCX)	Editable layout, pictures kept
Markdown for a knowledge base	Scans and PDFs	Markdown	Formatted text without pictures, headers or footers
Tables to Excel	Scans and PDFs with tables	Excel (XLSX)	One sheet per page
Scanned books to e-books	Scanned books	EPUB 3	Editable layout, pictures kept
Handwritten notes to Word	Handwritten pages	Word (DOCX)	Read by a vision model that you choose and connect; there is no separate handwriting engine

Conversion kits have no template, no fields and no review step: read the pages, write the file. "Model check" is a workflow step that asks a language model to verify the extracted fields before review; it needs a model you connect, local or remote.

Templates and tables Validation rules Review Export Conversion Vector stores

Verticals

Twelve markets and the kits behind them

Accounts payable
Supplier invoices with line items and a layout variant per supplier, with format checks on VAT number and IBAN before export. Accounts payable kit.
E-invoicing recipients
Peppol, Factur-X, ZUGFeRD and XRechnung documents read next to scanned paper and mapped onto the same template. Intake only: it does not send e-invoices.
Banking & finance
Bank statements with transaction lines, and document sets that may not go to a public cloud, processed on your own infrastructure. Finance kit.
Anti-money laundering
Transaction monitoring reports, sanctions and PEP screening reports, and CRS / FATCA self-certifications, each reviewed by a person. Compliance kits.
KYC & onboarding
Identity documents down to the machine-readable zone, proof of address and company registry extracts with officers and beneficial owners. Compliance kits.
Insurance
Claims, health and motor claims, policies, underwriting proposals and certificates, with tables for damaged items, treatments and coverages. Six insurance kits.
Logistics & customs
Bills of lading, delivery notes, packing lists, customs declarations and air waybills: reference numbers, barcodes and tables that continue across pages. Five logistics kits.
Capture bureaus & BPO
Many client companies on one installation, each with its own projects, templates, operators and exports, separated down to the directory tree. Partner programme.
Shared service centres
One platform for many business units, each with its own projects and exports, run by one operations team.
Software vendors & OEMs
Embed the Verification and Scan Hubs in your own application and offer capture as part of your product, under your brand. Embedding.
Public sector & archives
Searchable PDF and PDF/A renditions in the languages you install, with a documented air-gapped deployment for material that may not leave the network. Conversion kits.
Sovereignty-bound organisations
Healthcare, government and defence-adjacent bodies for whom the deciding question is where the document is processed. Data residency.

Use cases across industries

Not tied to one vertical

Digital mailroom
Paper from the scan desk, mailboxes, watched folders and SFTP into one intake, split into single documents and classified by type, each type mapped to its template. Capture · Classification.
Review only what is doubtful
Rules and confidence decide which documents a person sees. Reviewers check flagged fields next to the page image instead of typing every line. Review.
Search and question answering over archives
Documents cut into pieces with page, position and confidence, written to a vector store you connect, ready for your own search or assistant. Document search kit.
Back-scanning and archive conversion
Paper and image PDFs turned into searchable PDF/A, Word, Markdown, Excel or EPUB without a template. Conversion kits.
Capture inside your own application
Submit documents over the REST API and receive structured data, or show the Verification and Scan Hubs inside your own screens. Capture API.
Processing that stays on your network
Local OCR and local models, on your own servers, with a documented deployment for networks without internet access. Deployment.
Documents for software agents
An MCP server gives an agent curated, scoped tools instead of screens to scrape. It ships switched off, and every agent read and write is audited. MCP server.
Replacing a legacy capture suite
From FlexiCapture 12, an importer carries fields, rules and layouts into a project you can test before you switch. Migration.

What a kit leaves to you

A starting configuration, not a finished deployment

The workflow is created as a draft. You publish it after you have tested it on your own documents.
The export format is set; the destination is not. You choose the folder, server, database, API or message bus.
The recognition language is English until you change it and install the language you need.
The fields are authored per document type. They are not a model trained on your documents: expect to tune them and to add a layout variant where a supplier, insurer or carrier differs.
Checks in a kit are per field: a format, a range, a number of decimals. Rules across fields, such as totals that must add up, are yours to add.
No retention period is set. You set it per project.
The model check step, the document search kit and the handwriting kit each need a model or a vector store that you connect.

Common questions

Use cases

01Our document type is not in this list. Can it be read?

Yes. A kit is a shortcut, not a limit. Any document type is a template you draw on a sample page, or let the template assistant propose from one, then test and publish.

02Can we change a kit after creating the project?

Yes. What a kit creates is an ordinary project, workflow and template. Add or remove fields, change the review route, replace the export: nothing is locked.

03Do the kits learn from corrections?

The twenty capture kits do. Each has a learning step after review and a field that tells layouts apart, such as the supplier, the insurer or the carrier, so a correction improves the variant it belongs to. The search and conversion kits have no review step and nothing to learn from.

04Are these customer references?

No. This page lists what ships in the product and the markets it is built for. It names no customers. The three scenarios on the solutions page are illustrative examples.

05Is a compliance kit enough to be compliant?

No. A kit reads the document and puts every field in front of a reviewer with a trail of who changed what. Whether your process meets a regulation is decided by your own policies, controls and auditors.

Send us the document that worries you most.

We start from the nearest kit and show you what it reads, field by field.Start the conversation →