Sign in Start your 14-day trial
Products
Solutions
EnterprisesStartups Embedded financeFinance automationMarketplaces AccountingBankingHealthcareHospitalityInsuranceMediaReal estateRetail Pricing Docs
Resources
Blog FAQ AboutCompare Contact Start your 14-day trial
Language
English Português (Brasil)
Cogneris platform

One document lifecycle. Seven modules.

Collect documents, classify and extract their data, validate exceptions, route human decisions, act in downstream systems, and retain evidence — with each capability labeled by how it is available.

Platform modules

Seven modules. A connected lifecycle.

Portal, Vision and Governance & Integrations are included in every paid plan and the 14-day trial and spend credits from the same pool. Workflow, ECM, Sign and Templates are contract-configured and require tenant enablement or configuration within the agreed scope; confirm their deployment and availability for your workflow with our team.

Available

Portal

Collect customer documents through a tenant-scoped upload experience with required-document checklists and signed upload links, and connect each completed submission to extraction or to a configured workflow. Included in every paid plan and the 14-day trial; a portal process spends credits only when it completes.

See portal workflows Read portal documentation

Contract-configured

Workflow

Define ordered processing phases, pause a run for configured manual review, record the decision, and continue the workflow. Requires tenant enablement and configured review phases under the agreed contract. Confidence scores do not automatically select the review path.

See document workflows Read workflow documentation

Available

Vision

Classify documents and extract structured fields with confidence and source references for downstream validation. Included in every paid plan and the 14-day trial through the REST API; confidence and source references depend on the extraction output and are not guaranteed for every field.

See document extraction Read extraction documentation

Contract-configured

ECM

Organize documents, versions, tags, access rules, search, and lifecycle events in the document record. Requires tenant enablement and configured access and lifecycle policies under the agreed contract.

ECM scope and availability

Contract-configured

Sign

Create signing envelopes, collect signer events, and validate the resulting signed document through the configured signing flow. Requires tenant enablement and a separately confirmed validation flow under the agreed contract. This contract-configured scope does not establish a public document-validation service or third-party trust-service certification.

Sign scope and availability

Contract-configured

Templates

Manage versioned DOCX templates with named placeholders and render approved template versions to PDF. Requires tenant enablement, a published template version and a configured PDF renderer under the agreed contract. Word add-in availability requires separate deployment confirmation.

Templates scope and availability

Available

Governance & Integrations

Connect the lifecycle through REST APIs and signed webhooks, included in every paid plan and the 14-day trial. Audit and security evidence beyond the public trust center is agreed per contract. Client SDKs are published for TypeScript, Python, .NET and Java; no packaged connector catalogue is claimed.

Explore the REST API Read webhook documentation Review trust and security
Document lifecycle

From collection to evidence.

For a tenant-enabled signing integration, review the eSignature API scope and operations. Sign remains contract-configured.

Configure the stages your workflow requires, with review phases and downstream actions agreed for your tenant.

  1. CollectPortal, API, or workflow intake.
  2. ClassifyIdentify the document type against tenant configuration.
  3. ExtractReturn structured fields with source evidence.
  4. ValidateApply schema and business-rule checks.
  5. ReviewUse an explicitly configured manual-review phase where required.
  6. DecideApprove, reject, or request correction according to workflow rules.
  7. ActDeliver through REST APIs, signed webhooks, or configured downstream steps.
  8. ProveRetain source references and contract-specific audit evidence.
Customer journeys

One lifecycle, three document journeys.

These maps combine available modules with contract-configured stages. Collection, classification and extraction are included in every plan; validation rules, review phases, decisions, downstream actions and retention controls are configured per tenant, and linked guides describe the intended use case rather than confirming a configuration for your tenant.

Accounts payable

Contract-configured journey: from supplier invoice intake to a recorded payment decision and an agreed downstream handoff. Business approval remains with your authorized team.

  1. CollectCollect supplier invoices through the tenant-scoped portal or the REST API.Invoice intake portal
  2. ClassifyIdentify invoices and supporting documents against your document types.Classification configuration
  3. ExtractExtract invoice fields for your schema; source references depend on the extraction output.Invoice extraction
  4. ValidateDefine the invoice comparisons and reference data needed for matching, subject to confirmation of the agreed checks. Requires tenant configuration.Invoice matching scope
  5. ReviewPause for configured manual review for the tenant under the agreed contract. Requires tenant configuration. Authorized reviewers record approval, rejection, or a correction request.Configured review workflow
  6. DecideRecord the authorized team's invoice disposition in the workflow. Requires tenant configuration; a recorded decision does not execute a payment.Accounts payable workflow
  7. ActDeliver the agreed event to a downstream endpoint through signed webhooks, with webhook signing and receiving-system behavior confirmed. Requires tenant configuration.Webhook handoff
  8. ProveAgree which source references, review decisions, and events support the invoice record under contract-specific retention controls. Requires tenant configuration.Evidence and trust scope

KYC and KYB onboarding

Contract-configured journey: collect identity and company documents, review the agreed checks, and record an onboarding decision. Your authorized team defines acceptance policy.

  1. CollectRequest identity and company documents through a tenant-scoped portal or the REST API.KYC document portal
  2. ClassifyIdentify submitted document types against your onboarding document set.Classification configuration
  3. ExtractExtract the identity and company fields defined for the document set; field coverage and source references depend on the extraction output.KYC document extraction
  4. ValidateDefine required fields and cross-document checks for onboarding, subject to confirmation of supported checks. Requires tenant configuration; a document check alone does not establish regulatory compliance.Document verification scope
  5. ReviewPause for configured manual review for the tenant under the agreed contract. Requires tenant configuration. Authorized reviewers inspect the document record and record their decision.Configured review workflow
  6. DecideRecord the authorized team's onboarding disposition against its acceptance policy. Requires tenant configuration; business approval is not autonomous.Banking onboarding context
  7. ActSend the agreed onboarding event to a receiving service through signed webhooks, with webhook signing and the downstream action confirmed. Requires tenant configuration.Webhook handoff
  8. ProveAgree the document references, decisions, and access controls needed for the onboarding record under contract-specific retention controls. Requires tenant configuration.Security and evidence controls

Insurance claims

Contract-configured journey: assemble claim documents, review the agreed checks, and hand off a recorded disposition. Coverage and settlement decisions remain with your authorized claims team.

  1. CollectCollect the claim packet through the tenant-scoped portal or the REST API.Claims document processing
  2. ClassifyIdentify the document types in the claim packet against your categories.Classification configuration
  3. ExtractExtract the claim fields defined for the document set; source references depend on the extraction output.Claims document extraction
  4. ValidateConfirm the supported checks for the claim packet separately. Validation requires tenant configuration. Fraud detection is not established by the platform evidence and is not promised for this journey.
  5. ReviewPause for configured manual review for the tenant under the agreed contract. Requires tenant configuration. Authorized claims reviewers inspect the record and request corrections or record their decision.Configured review workflow
  6. DecideRecord the authorized claims team's disposition under its coverage and settlement policy. Requires tenant configuration; the workflow does not make an autonomous settlement decision.Insurance workflow context
  7. ActDeliver the agreed claim event to a downstream endpoint through signed webhooks, with webhook signing and the receiving action confirmed. Requires tenant configuration.Webhook handoff
  8. ProveAgree which claim documents, review decisions, and lifecycle events support the record under contract-specific retention controls. Requires tenant configuration.Evidence and trust scope
Supported types

Classification configured for your workflow.

Each one calibrated for the formats, languages, currencies and local rules your customers actually use.

Payslip
HR
Bank statement
Credit
Tax return
Tax
Tax invoice
Tax
Articles of incorporation
Legal
Driver's license
Onboarding
National ID
Onboarding
Proof of address
Onboarding
Bill / invoice
Finance
Service invoice
Tax
Receipt
Finance
Purchase order
Finance
Developer experience

Three lines of code. One clean JSON.

API and webhook samples for common development stacks. Signed webhooks, async jobs, and documented REST requests support custom integrations.

Start with the document extraction overview, then use the document extraction API, parse layout and sections with the document parsing API, or use the OCR API when scans and photos need to become validated data.

C# / .NET Python Node.js Go cURL
extract.cs 
// REST API sample — C#
using var form = new MultipartFormDataContent();
form.Add(new StreamContent(File.OpenRead("payslip.pdf")), "file", "payslip.pdf");

http.DefaultRequestHeaders.Authorization = new("Bearer", apiKey);
var response = await http.PostAsync(extractionUrl, form);
response.EnsureSuccessStatusCode();
What ships in the box

Six capabilities, one orchestration.

The full document AI stack runs as one orchestrated pipeline. Every page goes through the same agentic flow — classify, extract, validate, score, audit — and lands as structured JSON ready for your downstream system. For API-first teams, these capabilities map to the document extraction API, document parsing API, and OCR API.

Capability What it does
Ingestion PDF (digital and scanned), JPEG, PNG, TIFF, DOCX, and email attachments. Multi-page documents stitched automatically. Inbox monitoring, webhook intake, and direct API upload.
Classification Tenant-configurable classification and zero-shot extraction return confidence scores and routing decisions. Validate each configured type against representative documents before production use.
Extraction ReAct-architected agents pull structured fields with per-field confidence. Cross-field math, date, and entity validation runs in the same pass. Span pointers preserve provenance to the source paragraph.
Validation Schema validation, cross-document reconciliation, and configurable business rules. Low-confidence fields are flagged with their confidence score and source citation; a manual review step queues the document for a reviewer.
Contract-specific checks Schema rules, reference-data checks, and cross-document consistency can be configured for a contracted workflow. Fraud detection is not established by the current capability evidence; any proposed fraud check requires separate verification before use.
Audit trail Configured workflows can retain tamper-evident metadata with model version, prompt and response hashes, reviewer identity, and per-field confidence. Retention is tenant-configurable and contract-specific.
By document type

Pre-trained extractors for the documents you already process.

Extractors return structured JSON with schemas and validation rules. Connect downstream steps through REST APIs and signed webhooks, configured for the contract; a packaged or pre-built connector catalogue is not implied.

Finance / AP
Invoice extraction
Vendor, line items, GL-code hints, totals. Fields support customer-configured matching and delivery through APIs or webhooks.
Banking / lending
Bank statement extraction
Transactions, balances, recurring deposits. Sub-3-second parsing on US and Canadian statements for cash-flow underwriting.
Legal / CLM
Contract extraction
Parties, term, governing law, liability caps, named clauses. Span pointers to source paragraph for legal review.
Onboarding / CIP
KYC document extraction
Government IDs, proof of address, beneficial-ownership certifications. MRZ parsing and sanctions/PEP screening hooks.
HR / lending
Payroll extraction
Pay stubs, W-2s, 1099s. Gross, deductions, net pay, and YTD reconciliation for income verification.
Tax / lending
Tax return extraction
1040s, K-1s, schedules. AGI, deductions, credits, refund or amount owed — with cross-schedule math validation.
T&E / expense
Receipt extraction
Itemized receipts with merchant, line items, tax, and tip handling. Outputs can be mapped into customer-configured expense workflows through APIs or webhooks.
Logistics
Bill of lading OCR
Carriers, consignees, shipment IDs, weights, charges, and freight line items for logistics workflows.
Payments
Check OCR API
Payer, payee, amount, date, MICR context, and remittance fields for payment operations.
Insurance
ACORD forms extraction
Policy, applicant, vehicle, property, coverage, premium, and loss data from insurance packets.
Insurance
Insurance claim extraction
FNOL, police reports, medical bills, repair estimates. Cross-document reconciliation for claim adjudication.
Integrations

Lives where your systems already run.

REST APIs and signed webhooks support custom integrations with systems of record. Integration scope and field mapping are defined for each customer workflow.

  • ERP and financeNetSuite, SAP S/4HANA, Oracle Cloud ERP, Workday Financials, QuickBooks Online, Xero, Sage Intacct.
  • CRM and revenueSalesforce, Salesforce Financial Services Cloud, HubSpot. Customer records, opportunities, and applicants land as structured objects.
  • Lending and core bankingnCino, Encompass, Mambu, Alloy, Q2, Jack Henry, Fiserv, FIS, Plaid, MX.
  • CLM and legalIronclad, Agiloft, ContractWorks, Concord. Clauses, parties, and term data flow with span pointers preserved.
  • HR and payrollWorkday HCM, ADP, The Work Number, Gusto, Justworks. Wage and YTD data flows into HRIS and verification workflows.
  • T&E and expenseExpensify, Concur, Brex, Ramp, Pleo. Receipts and reimbursements route to the right policy and ledger code.
  • Onboarding and KYCPersona, Alloy, Sumsub, ComplyAdvantage. ID verification and CIP/CDD packets with sanctions screening triggers.
  • Custom integrationsREST APIs, signed webhook events, and API or webhook samples for common development stacks. Enterprise contracts can include scoped integration engineering.
Security & compliance

We treat your documents the way you would.

Privacy by design

Configurable retention, automatic PII anonymization and proper data-processing agreements out of the box.

End-to-end encryption

TLS 1.3 in transit. AES-256 at rest. Keys managed by a dedicated KMS instance per customer.

Private deployment roadmap

Private cloud, BYOC, and on-premises deployment are not generally available. Contract-dependent evaluation requires explicit technical and operational confirmation.

FAQ

Common questions.

Can I run Cogneris on document types you don't list?
Yes. Custom document types ship from sample documents in 1 business day on Enterprise — send 10 to 50 examples, get a calibrated extractor with the right schema, validators, and confidence thresholds. The same agentic pipeline handles them; the only thing that changes is the schema you target.
What's the synchronous vs. async limit?
Synchronous extraction is bounded by the 10 MB file limit and the request timeout, not by a page count. For long documents or high volume, submit a document job and receive a signed webhook callback: same per-page rate, just a different request shape.
How does Cogneris handle multi-language documents?
Thirty-plus languages are supported with field-level localization. Currency conversion, date format normalization (DD/MM vs. MM/DD), and address parsing follow the source-document locale. Output JSON normalizes to ISO formats (ISO 4217 for currency, ISO 8601 for dates, ISO 3166 for countries) so downstream systems get consistent data regardless of source language.
What happens to documents that fail validation?
Low-confidence fields and schema/business-rule failures are flagged on the extraction result, each carrying the extracted value, its confidence score, the validation error, and the source region it was read from. A manual review step sends the document to a review queue, where reviewers correct values against the original page and approve or reject. Cogneris can preserve tamper-evident audit metadata with model version, prompt and response hashes, and reviewer identity.
Can Cogneris run in our cloud or on-premises?
Private cloud, BYOC, on-premises deployment, customer-managed keys, AWS PrivateLink, and Google Cloud Private Service Connect are roadmap capabilities, not generally available services. Any contract-dependent evaluation requires explicit technical and operational confirmation before architecture or procurement planning.
How fast is the integration?
Integrate through REST APIs and signed webhooks. Scope, endpoints, authentication, webhook signing, and receiving-system behavior must be configured for the tenant under the agreed contract. See the docs or the API reference.
Walkthrough

Six capabilities, one recording.

Everything above is a description. The walkthrough is a screen recording of the product doing the work on a real document — including the field it was not sure about, which is the part a scripted demo leaves out.

The recording is not published yet, so there is nothing to play here. We would rather leave the space empty than fill it with a reel that is not the product.

  • Upload — a real invoice or bank statement, running at the speed the platform actually processes it.
  • JSON output — the response envelope, with each value's bounding box drawn back onto the source page.
  • Confidence — the per-field scores, including the one field the model hesitated on.
  • Human review — the same document waiting in a workflow’s review queue, a reviewer correcting the flagged value, and the change recorded against them.
  • Webhook — the signed delivery landing, carrying the document id from the first step.
Let's talk

Ready for your first extraction?

In 30 minutes we'll show you the platform running on your own documents.

Book a demo See pricing