Capacity coverage, without marketing estimates
Cogneris document classes and extraction schemas are configured per tenant. That makes a single global count misleading. The figures below are limited to capabilities that have a current, traceable product source; variable axes are named explicitly instead of left blank.
Document types
Tenant-configuredThere is no fixed product-wide count. Teams define the document classes their workflows require and validate them against representative files.
Extraction fields
Schema-definedThere is no fixed field total. Each tenant template defines its fields, types, required values, validation rules, and review thresholds.
Interface languages
15 localized languagesThe application interface ships in 15 languages. This is not an extraction-language claim: extraction coverage depends on the configured model, schema, and the customer's validated document set.
Currencies
Schema-definedThere is no fixed product-wide currency allowlist. Currency codes and monetary values are extracted and validated according to the tenant schema.
File and page limits
10 MB per fileThe public synchronous Document AI API accepts files up to 10 MB. There is no single page ceiling across every endpoint; route-specific limits apply, and document splitting has a separate contract.
Evidence checked 26 August 2026: the interface locale registry, the API upload validator, and the machine-readable capacity evidence snapshot.
High-intent document extraction pages
Invoices
Vendor, invoice number, line items, tax, totals, PO references, GL-code hints, and match status.
Open invoice extractionReceipts
Merchant, date, itemized lines, subtotal, tax, tip, payment method, currency, and duplicate signals.
Open receipt extractionBank statements
Account metadata, balances, transactions, statement period, fees, deposits, and reconciliation fields.
Open bank statement extractionChecks
Payer, payee, amount, date, memo, MICR context, remittance data, and payment-review evidence.
Open check OCR APIID cards and passports
Name, date of birth, document number, issue/expiry dates, address, MRZ fields, and source evidence.
Open ID card OCR APITax forms
W-2, 1099, 1040 source documents, K-1, payer/payee fields, wages, withholding, and review flags.
Open tax form extractionMortgage packets
Loan packets, paystubs, statements, IDs, tax forms, disclosures, and underwriting evidence.
Open mortgage extractionACORD forms
Policy, applicant, vehicle, property, coverage, premium, loss data, and insurance workflow checks.
Open ACORD extractionBills of lading
Carrier, consignee, shipment IDs, weights, dates, charges, line items, and logistics handoff data.
Open BOL OCR APIProof of delivery
POD numbers, delivery dates, addresses, carriers, signatures, exception notes, and delivery evidence.
Open POD OCR APIEOBs
Patient, provider, payer, claim, service lines, allowed amounts, adjustments, and denial codes.
Open EOB OCR APIContracts
Parties, term, dates, governing law, clauses, obligations, signatures, and citation-backed answers.
Open contract extractionPurchase orders
PO numbers, vendors, line items, totals, delivery terms, approvals, and three-way-match evidence.
Open PO OCR APIPayroll and W-2
Payslips, W-2s, paystubs, 1099 forms, employer details, income fields, and lending-ready audit trail.
Open payroll extractionProof of address
Names, addresses, issuers, dates, freshness signals, residency evidence, and validation state.
Open proof-of-address APIKYC document packets
IDs, passports, proof of address, business records, beneficial owners, and cross-document validation.
Open KYC document extractionHealth insurance cards
Member and group IDs, payer, plan, coverage dates, copay fields, and eligibility workflow inputs.
Open health insurance card OCRInsurance claims
Claim forms, policies, loss evidence, estimates, invoices, parties, dates, and review-ready fields.
Open insurance claim extractionClaims processing
Mixed claim packets classified and extracted for intake, adjudication, exception routing, and audit trails.
Open claims processing APIFinancial spreading
Statements, tax returns, schedules, normalized periods, ratios, and source-backed credit analysis.
Open financial spreadingHow to choose the right extraction route
| Workflow need | Use this pattern | Start here |
|---|---|---|
| Known document type | Use a shipped template and tenant-specific validation rules. | Extraction docs |
| Unknown upload packet | Classify, split, extract, and return one normalized payload per document. | Classification docs |
| Custom schema | Pass a schema with required fields, field types, and validation expectations. | Document extraction API |
| Reviewable output | Require citations, confidence scores, bounding boxes, reviewer changes, and audit metadata. | Source citations |
Why a document-type hub matters
Competitor pages often rank by document type: invoice OCR API, receipt OCR API, bank statement extraction, ID card OCR, mortgage document extraction, purchase order OCR, proof of delivery OCR, and EOB OCR. This hub gives buyers and search engines a clean map from each document type to the Cogneris page that explains fields, output, validation, review, and integration depth.