Plustek AICapture guides documents from intake through extraction and review to a configured output. Profiles define fields, rules, and processing steps.
Documents are accepted from a configured input folder and moved into the workflow in a controlled manner.
Profiles describe document types. Routing profiles can classify documents and pass them to a suitable extraction profile.
Document pages are evaluated and recognized content is combined into structured data according to the profile schema.
Downstream rules and scripts can check, normalize, supplement, and prepare results for the next workflow step.
Document images and schema-based fields are shown together so recognized values can be checked and corrected before approval.
Approved results can be prepared for downstream systems and passed to the output configured for the workflow.
Profiles and workflow configuration determine which optional steps a document actually passes through.
Desktop file flow, profiles, and workflow control can operate in a controlled local environment. With a locally operated LLM provider, AI processing can also take place within that environment.
If a cloud provider is configured instead, the document content required for processing is transferred to that provider. The appropriate operating model therefore depends on the organization's requirements and approved provider configuration.
Administrators configure the LLM connection, allowing compatible locally operated or remote services, including cloud-based services, to be used.
Provider, model, and request configuration must be reviewed for the specific deployment. The desktop app does not imply general privacy, region, or retention guarantees.
The desktop app processes pages sequentially and combines extracted content into one document result. Users can review all relevant pages alongside the recognized fields.
Depending on the profile and workflow, pages can also be assigned to business units or converted into separate documents by an approved separation step.
Profile scripts can normalize extracted values, perform business checks, add calculated fields, and make decisions for subsequent workflow steps.
Desktop scripting includes document-related workflow functions and is broader than the deliberately restricted, stateless post-processing available in the web demo.
Exports can be prepared per profile and can produce multiple named output files. Without specialized export logic, the document and its structured data are passed through.
Formats, filenames, and destinations are configured for each workflow. This page does not promise generally available external connectors.
One document type is extracted with a profile, reviewed in the form, and approved for the configured output.
Classification or recognized values provide the basis, and an approved script rule prepares the decision for the next processing step.
A script derives a total, flag, or normalized key from recognized values and adds it to the result.
A batch or multi-page document is divided into business units according to approved rules, processed appropriately, and output separately.
Choose which categories you want to allow. You can change your selection at any time via the “Cookie settings” link in the footer.
