Capture Flow Designer
Visual designer for end-to-end capture workflows — ingestion, classification, extraction, validation, routing. Flows designed per document type, not per vendor.
Intelligent Capture
OpenText Intelligent Capture Implementation Services
Most AP teams still re-key 60-80% of invoices manually because legacy OCR mis-classifies non-standard vendor formats. Template-based capture fails when mid-size enterprises see 500-2,000 unique invoice layouts and the layouts change. OpenText Intelligent Capture (formerly Captiva) uses continuous machine learning that adapts to each vendor and form variant without template maintenance. BCS implements the capture flows, the training pipeline, and the routing into SAP and Extended ECM so accuracy starts high and improves automatically.
Vendor variety solved
CONTINUOUS ML
No invoice template maintenance. The system learns each vendor format on the first three to five samples and adapts as layouts change.
Native SAP routing
CORE CAPTURE FOR SAP
Captured invoices, HR documents, and work orders land directly in the matching SAP business object with one posting path.
AP cycle compression
STRAIGHT-THROUGH PROCESSING
Routine invoices post without human handling. Exception queues shrink to the cases that need real judgement.
Architecture
Four Layers Of OpenText Intelligent Capture
An AI-driven capture platform built for the long tail of vendor formats
Legacy capture platforms were template-based: each vendor invoice layout needed a configured template that broke when the layout changed. Mid-size enterprises with 500 to 2,000 vendors faced a template maintenance burden that consumed the value the platform was supposed to deliver.
Intelligent Capture replaces template configuration with continuous machine learning. The platform sees three to five samples of a new vendor format and trains the extraction model. Layout changes trigger retraining automatically.
01 - Capture Flow Designer
Visual end-to-end capture workflow
Visual designer for the capture workflow — ingestion, classification, extraction, validation, routing. Designed once per document type (invoice, work order, claim, HR document), not once per vendor.
02 - Continuous Machine Learning
Auto-improving classification and extraction
Classification and extraction models that improve from operator feedback continuously. New vendor formats train in three to five samples; layout changes trigger automatic retraining.
03 - Core Capture For SAP
Native SAP-anchored capture
The SAP-anchored capture variant. Invoices, work orders, and HR documents post directly into SAP business objects with the matching Extended ECM Business Workspace generated automatically.
04 - Operator Workstation
Verification UI for exceptions
The interface where AP operators handle the exception queue — single-click entry, table auto-complete, side-by-side verification. The operator only sees the cases continuous ML could not handle straight-through.
Why Intelligent Capture
The Four Triggers That Move Intelligent Capture From Consideration To Programme
Capture programmes start when one of four operational realities forces the decision.
01 - AP capacity ceiling
Invoice volume is up, headcount is flat, cycle time is slipping
The AP shared services team is at capacity. The CFO has approved AP automation. The procurement evaluation includes Intelligent Capture, ABBYY, Tungsten (formerly Kofax), and Hyperscience. The decision criteria include SAP-certified routing, vendor format coverage, and continuous-ML approach.
02 - SAP migration trigger
RISE or GROW migration forces the AP automation conversation
The SAP migration is in flight. The new SAP estate needs a capture path. Core Capture for SAP is the SAP-certified option and ships in the same OpenText estate as Extended ECM. The capture workstream lands inside the SAP programme.
03 - Legacy template platform retirement
The existing template-based OCR maintenance is unsustainable
An incumbent template-based platform (Captiva pre-rebrand, ABBYY FlexiCapture, Kofax KTM) is consuming the AP team in template maintenance. The CIO needs a continuous-ML platform that eliminates the template burden.
04 - HR or claims expansion
AP automation is in production; the next document type is HR or claims
Intelligent Capture is in production for invoices. The next operational target is HR document capture (onboarding documents, payroll evidence, employee records) or claims documents for insurance. The same platform handles both with new capture flows.
Business Impact
Who Benefits From The Intelligent Capture Implementation, And Through Which Operational Lever?
Intelligent Capture has a narrower buyer panel than general-purpose ECM. The accordion below names the specific lever per role.
Head of Shared ServicesAP cycle time, exception queue volume
For Shared Services, the question is whether straight-through processing is high enough that the team can absorb the next 30% of invoice volume without headcount addition. Intelligent Capture moves straight-through processing by adapting to vendor variety automatically.
- Straight-through processing rates above 80% for routine invoices after the first three months of operation.
- Exception queue shrinks to genuine judgement cases — not vendor template gaps.
- AP operators move from data entry to exception handling and process improvement.
CFOAP automation ROI, audit posture
For the CFO, AP automation is a labour cost line and an audit posture line. Intelligent Capture moves both: cycle time compresses, supporting documents land in the SAP record automatically.
- Invoice-to-post cycle time compresses with measurable timestamps per process step.
- Audit evidence retrieves from the SAP record with the supporting invoice attached in the workspace.
- Duplicate invoice detection and three-way match exception handling become workflow steps, not manual checks.
CIOCapture platform consolidation, OpenText estate
For the CIO, Intelligent Capture replaces the template-based incumbents with a continuous-ML platform that lives in the OpenText estate. The integration to Extended ECM and SAP is native rather than custom code.
- Capture platform consolidates onto OpenText — one vendor for capture, ECM, and archive.
- Core Capture for SAP routes captured documents into the SAP business object natively.
- Continuous ML eliminates the template maintenance backlog the previous platform created.
Head Of HR OperationsOnboarding documents, employee record completeness
For HR Operations, employee documents arrive in varied formats from background check vendors, government bodies, and educational institutions. Capture routes them into the Employee Central workspace automatically.
- Onboarding documents capture and land in the employee workspace at hire.
- Statutory documents (work permits, regulated training certificates) capture with retention class assigned.
- Background check evidence binds to the employee record with audit trail.
Chief Compliance OfficerDocument evidence retrievability
For Compliance, supporting evidence for SAP transactions retrieves from the Business Workspace tied to the SAP entry. Capture makes that linkage automatic.
- Every captured document carries the SAP business object reference in metadata.
- Audit sample retrieval is one workspace lookup, not an email and file-share search.
- Retention class assigned at capture — documents purge on schedule by default.
Head Of Claims OperationsInsurance claim document handling
For insurance Claims Operations, claim documents (medical reports, witness statements, police reports, repair quotes) drive case turnaround. Capture routes them into the claim workspace in Process Automation.
- Claim documents land in the claim case workspace automatically.
- Continuous ML adapts to the variety of supporting documents per claim type.
- Exception handling becomes routing rather than data entry.
CTOCapture architecture, integration boundaries
For the CTO, capture sits at the integration boundary between inbound documents and downstream business systems. Intelligent Capture standardises the boundary with the same OpenText repository the rest of the content estate uses.
- Native SAP-certified routing through Core Capture for SAP — no custom integration code.
- Capture output binds to Extended ECM Business Workspaces with the SAP business object reference.
- Cloud capture (SaaS) available for high-volume estates without infrastructure footprint.
Chief Data OfficerCaptured-document semantics, AI grounding
For the CDO, captured documents become a structured data source feeding analytics and AI. Intelligent Capture extracts fields with confidence scores Datasphere can consume.
- Extracted fields with confidence scores feed Datasphere — AP analytics ground on real captured data.
- Aviator answers can ground on captured invoice content for AP query patterns.
- Document-type classification feeds content semantic layer for cross-product retrieval.
Capabilities
Components Of OpenText Intelligent Capture
Five product components organised across capture flow design, machine learning, SAP routing, operator UI, and cloud deployment.
Continuous Machine Learning
Auto-improving classification and extraction models. Each operator correction trains the model. New vendor formats train in three to five samples; layout changes trigger automatic retraining.
Core Capture For SAP
SAP-anchored capture variant. Invoices, work orders, contracts, and HR documents post directly into SAP business objects with matching Extended ECM Business Workspace generation.
Operator Workstation
Verification UI for the exception queue — single-click entry, table auto-complete, side-by-side document and field verification. Operators only see exceptions continuous ML could not handle.
Cloud Capture (SaaS)
Core Capture available as multi-tenant SaaS for high-volume orgs without on-premise infrastructure. Cloud and on-premise variants share the same capture flow definition format.
Content Cloud Integration
Captured documents bind to the OpenText repository natively — Extended ECM Business Workspaces, Documentum cabinets, or Content Hub workspaces depending on the destination.
RPA Compatibility
Pre-built connectors and SDK for UiPath, Automation Anywhere, and Microsoft Power Automate. Capture output flows into RPA processes for downstream automation.
How BCS Implements This
The Six Workstreams — What BCS Owns, What The Client Owns, When Each Runs
An Intelligent Capture programme typically runs 12-20 weeks for the first document type. BCS sequences six workstreams.
01Weeks 1-3
Document Type Discovery And Volume Analysis
The first document type for capture is selected (typically AP invoices). Volume by vendor, current cycle time, current straight-through rate, current operator effort are baselined.
BCS owns: discovery tooling, baseline metrics, prioritisation. Client owns: AP operational data, vendor master, document samples.
02Weeks 2-6
Capture Flow Design
Capture flow designed for the document type. Document classes, extraction fields, validation rules, routing logic configured. Flow tested against representative document samples.
BCS owns: flow design, configuration, sample testing. Client owns: AP operational sign-off on the flow.
03Weeks 4-9
Continuous ML Training Pipeline
Training data pipeline set up so capture accuracy starts high and improves automatically. Representative vendor formats trained pre-go-live. Routing of operator corrections back into training configured.
BCS owns: training pipeline, initial training data preparation. Client owns: vendor document samples, training data access.
04Weeks 6-12
SAP And Extended ECM Routing
Core Capture for SAP routing configured. Captured invoices post into SAP with the matching Business Workspace in Extended ECM. Three-way match logic activated where relevant.
BCS owns: SAP routing configuration, Extended ECM workspace mapping. Client owns: SAP and Extended ECM administrator access.
05Weeks 8-15
Operator Workstation Configuration And Anugal Access
Operator Workstation views configured for the AP exception queue. Anugal IGA extends access governance over the operator interface so segregation of duties is enforced. Pilot operators trained.
BCS owns: Operator Workstation setup, Anugal policies, training materials. Client owns: AP operator enablement, SoD sign-off.
06Weeks 14-20
Production Cutover And Continuous Improvement
Production cutover. Straight-through rate measured against the baseline. Continuous-ML feedback loop active — operator corrections retrain the models automatically. Next document type roadmap scoped.
BCS owns: cutover, measurement framework, next-type roadmap. Client owns: production sign-off, future scope decisions.
About BCS
BCS — The Agentic System Integrator For Content
Content programmes that ship as an operating model, not an event
BCS implements Intelligent Capture as part of the broader OpenText practice. The capture team understands the difference between a platform with high benchmark accuracy and a platform that actually moves the AP team's straight-through rate.
The agentic system integrator model means three operating platforms travel with every Capture programme.
Anugal
AP segregation of dutiesIdentity governance over the Operator Workstation and the AP routing. Segregation of duties enforced for invoice approval thresholds, vendor-specific routing, and exception handling rights.
deKorvai
Vendor master data qualityVendor master validation that runs before capture binds. Duplicate vendors, inconsistent vendor data, and dormant vendors are remediated so capture classification lands on accurate vendor identity from day one.
Symphony
AP cycle orchestrationSymphony orchestrates the AP cycle from capture through approval through SAP posting through Extended ECM workspace creation. The cycle becomes one workflow rather than three integrations.
Recent Updates
What Has Changed In Intelligent Capture In 2026?
Three updates that shape the Intelligent Capture conversation in 2026.
IDC MarketScape: Worldwide Intelligent Document Processing
OpenText recognised as a Major Player in the IDC MarketScape: Worldwide Intelligent Document Processing 2024. The recognition spans Captiva-lineage technology now rebranded as Intelligent Capture.
Source: OpenText IDC MarketScape recognitionCore Capture for SAP — certified for S/4HANA Public Cloud
Core Capture for SAP is the intelligent capture solution natively certified for SAP S/4HANA Public Cloud archiving and document flow. The certification removes the integration risk premium for AP automation on the SAP-supported destination.
Source: Core Capture for SAPCaptiva is now Intelligent Capture
The Captiva product name was retired in 2018; the codebase continues as OpenText Intelligent Capture. Buyers and analysts still reference Captiva in scoping conversations. Both names appear in product documentation.
Source: OpenText Intelligent Capture rebrandFrequently Asked Questions
The five questions that decide the Intelligent Capture programme.
How does Intelligent Capture compare to ABBYY, Tungsten (Kofax), or Hyperscience?
Each vendor has strengths. ABBYY FlexiCapture remains template-strong. Tungsten KTM has deep SAP integration history. Hyperscience leads on continuous-ML accuracy benchmarks. OpenText Intelligent Capture differentiates on the integrated end-to-end story: capture into Extended ECM Business Workspaces with the SAP business object linkage, on the same OpenText estate. For enterprises with Extended ECM (or planning it), the integration overhead of using a separate capture platform typically tips the decision.
What straight-through processing rate should we expect?
Realistic expectations: 65-75% in month one, 80-85% by month four after continuous-ML training cycles, 85-90%+ for routine vendors and document types after six months. The numbers are sensitive to vendor variety, document quality, and the rigour of the training pipeline. Programmes that skip the training pipeline land closer to 60-70%.
Can we capture documents other than invoices?
Yes. The same platform handles HR documents (onboarding evidence, work permits, training certificates), insurance claim documents (medical reports, witness statements, repair quotes), legal documents (contracts, signed records), and engineering documents (drawings, specifications). Each new document type is a new capture flow but uses the same continuous-ML approach.
Do we need Extended ECM to use Intelligent Capture?
Not strictly required, but Extended ECM is the natural destination for captured documents tied to SAP business objects. Without Extended ECM, captured documents can route to SAP attachments, SharePoint, or other content stores — but the auditable workspace pattern and the records governance is lost. Most BCS programmes pair Capture with Extended ECM or Content Hub.
What is the commercial engagement model?
Most Intelligent Capture engagements run as fixed-milestone delivery for the first document type (12-20 weeks) with a discovery phase priced separately. The team typically includes a programme lead with Captiva/Intelligent Capture experience, two to three capture engineers, an SAP integration engineer (if Core Capture for SAP), an identity engineer running Anugal, and a cutover lead.
Scope The Intelligent Capture Implementation In 30 Minutes
BCS runs a 30-minute readiness session covering the document type priority (AP invoices, HR documents, claims), the current straight-through rate, the SAP and Extended ECM state, and the continuous-ML training pipeline.
30-minute discovery session*