The same platform. A different answer for each desk.
Capture is bought by one person, configured by another, operated by a third and audited by a fourth. This page takes each of them in turn, then each industry, then three scenarios worked through from problem to result.
How many invoices pass without a person touching them, whether the totals are right, and whether the month-end close gets shorter.
What you get
Paper, PDF and structured e-invoices through one intake. Line items extracted with per-supplier layout variants. Arithmetic and lookup rules that check totals, VAT and supplier data. Only doubtful invoices reach a reviewer.
Ask us
For a bake-off on your supplier invoices, including the ugly ones, with the result per field and per supplier.
Throughput, exceptions, who is working on what, and whether today's batch will make its deadline.
What you get
A scan desk in the browser with quality flags while the paper is still in hand. Review queues ordered by service level. Keyboard-first verification with click-to-fill. Locking so two people never open the same document. Reports per operator and per stage.
Ask us
For a session where your team lead verifies a real batch and times it.
What you have to install, patch, scale and monitor, and how it connects to what is already there.
What you get
A single Java application on Linux with PostgreSQL. No licence server, no broker, no external OCR service. Scale out by adding nodes with assigned duties. Sixteen saved connection types with a test button. A built-in self-verification suite.
Ask us
For the installation guide and a sizing conversation based on your volumes.
Whether the API covers what the screens do, whether a template change will break your integration, and how much you can customise without waiting for the vendor.
What you get
An OpenAPI 3 specification generated from the running code. A one-call capture endpoint. Template versions you can pin. Scripts in JavaScript, Groovy and Java. A plugin SDK with five extension points. Embeddable hubs and an MCP server.
Documents that never leave, and a trail for every field
You care about
Where personal and financial data is processed, who can see it, what is logged, and how long it is kept.
What you get
Self-hosted processing with local OCR and local models. Air-gapped installation. Role-based access with per-project grants. A central activity log, field-level amendment history and a separate agent audit channel. Retention policies per project. And a plain list of what is missing.
Ask us
To go through your security questionnaire line by line.
What it costs over five years, how dependent you become on the vendor, and how long before it pays back.
What you get
One annual licence per installation, set by your turnover band — unlimited users, projects and pages. Yearly increases capped at 25%. No page meter and no runtime licence gate. Blueprints that create a working project in one step instead of a quarter of consulting.
Ask us
For your number. The calculator on the pricing page gives it without a form.
Serving many clients economically, keeping them apart, and putting your own name on what they see.
What you get
A tenant, organisation and project hierarchy with separate storage. White-labelling at every level, with own domains and mail providers per client. Review and scan screens that embed in your product. Plugins for the connectors only you need.
Ask us
About the partner programme: reseller, OEM and service-provider terms.
Supplier invoices with line items and per-supplier layouts, plus intake of Peppol, Factur-X, ZUGFeRD and XRechnung documents on the same template. Validation rules check totals before anything is exported.
Banking & AML
Bank statements with transaction lines, and transaction reports with validation rules and a filing export — processed on your own infrastructure.
Insurance
Claim forms and policy schedules with damaged-item and coverage tables, routed to adjusters through review hubs. Six insurance blueprints to start from.
KYC & onboarding
Identity documents and proof of address read with local engines, with full human review where regulation demands it and retention set per project.
Logistics & customs
Bills of lading, packing lists and customs declarations: reference numbers, barcodes read on a dedicated path, and container tables that continue across pages.
Capture bureaus & shared service centres
Many client companies or business units on one installation, each with its own projects, templates, operators and exports, separated down to the directory tree.
Software vendors & OEMs
Embed the Verification and Scan Hubs in your own application and offer capture as part of your product, under your brand.
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.
Sovereignty-bound organisations
Healthcare, government and defence-adjacent bodies for whom the deciding question is where the document is processed.
A blueprint creates a project, its workflow and a fully fielded template in a single action. You start from something that runs and adjust it, instead of starting from an empty screen. The field sets are authored for each document type; they are a starting configuration that you tune on your own documents, not a pre-trained model.
Family
Kits
Document types covered
Finance
1
Bank statements with transaction lines
Accounts payable
1
Supplier invoices with line items
Insurance
6
Claim forms, policy schedules
Compliance
7
KYC, AML, KYB, proof of address, CRS/FATCA, sanctions, data protection consent
Logistics
5
Bills of lading, packing lists, customs declarations
Document search
1
Mixed archives
Conversion
6
Scans to editable or archive formats
Three scenarios, worked through
Illustrative examples, not customer case studies
01 · Accounts payable & e-invoicing
Paper, PDF and Peppol invoices through one intake
Challenge
A distributor's accounts payable team retypes scanned and emailed PDF invoices into the accounting package, while structured e-invoices now arrive through a separate channel with their own handling.
Approach
The accounts payable blueprint sets up a project with a line-item invoice template, fed by email import and a hot folder, with alternatives for suppliers whose layout differs. Embedded e-invoice payloads are mapped onto the same template, a cross-check compares the XML with the page, arithmetic rules check totals, and an export goal hands the mapped fields to the accounting system.
Result
Paper and electronic invoices end up in the same structured format, and reviewers only see invoices where a rule or low confidence asks for it.
02 · Logistics & customs
Bills of lading without retyping container tables
Challenge
A freight forwarder receives bills of lading and packing lists as scans and PDFs. Clerks copy reference numbers and multi-page container tables into the transport system by hand, and typing errors surface only at customs.
Approach
A logistics blueprint sets up a project whose template extracts tables with column zones and continuation across pages, and reads barcodes on a dedicated decode path. Validation rules and dataset lookups check the values before an export goal delivers them.
Result
Container tables arrive in the transport system as structured data, and clerks verify flagged fields next to the page image instead of typing every line.
03 · KYC & onboarding
Identity documents read on-premise, every field traceable
Challenge
A financial institution's onboarding team copies data from identity cards and passports by hand, because sending identity documents to a cloud OCR service is not acceptable under its privacy and security policies.
Approach
A KYC blueprint sets up a project that reads identity documents with local OCR and a local model, so nothing leaves the network. Every document passes through the Verification Hub, and a retention policy governs how long files are kept.
Result
Identity data stays on the institution's own infrastructure, and for every field the trail shows the recognised value, the correction and who verified it.
Replacing a legacy suite
Keep the configuration you paid for. Leave the page meter behind.
KognitCapture was built as a modern, self-hosted replacement for classic capture suites. An importer reads an exported ABBYY FlexiCapture 12 project and rebuilds what it can.
01Zip the whole FlexiCapture 12 project folder.
02Upload it and review the plan. The importer creates a project, a template with fields and rules, datasets, ported scripts, retrained classifiers, an alternative per vendor, an export goal and a draft workflow.
03Finish what is approximated: FlexiLayout is encrypted, so extraction is rebuilt from the project's keyword lists and tuned with zones and labels; ported scripts are reviewed before they are activated.
04Test against a set of documents with known results, using the accuracy harness.
05Publish the workflow and move the import sources across.
There is no automatic parallel-run mode that feeds both systems and compares them; run the comparison on a sample set. ABBYY and FlexiCapture are trademarks of their owner; KognitCapture is not affiliated with it.
Common questions
Solutions
01Our documents are not in the blueprint list. Does that matter?
No. A blueprint 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.
02Does it connect to our ERP?
Through the generic channels: a REST call, a database insert, a file on a share or SFTP server, a message on a bus, or a mail. There is no product-specific adapter for any named ERP. For most systems one of those channels is the supported import route anyway; where it is not, a plugin or a script closes the gap.
03How long does a new document type take?
It depends on the document. A fixed form is a matter of drawing zones. An invoice family with many supplier layouts takes longer, because each variant is an alternative. We would rather show you on your documents than quote a number that does not survive them.
04Can it send e-invoices as well as receive them?
No. It reads structured invoice formats and maps them onto your template. It is not a Peppol access point.
05Can we run several business units on one installation?
Yes. That is what the tenant and organisation levels are for. One licence covers unlimited users, projects and organisations inside one tenant.