Skip to main content

FlexiCapture

Processes documents using ABBYY FlexiCapture for OCR and intelligent data extraction. This node integrates with ABBYY FlexiCapture Engine to automatically recognize, classify, and extract structured data from various document types including invoices, forms, receipts, contracts, and other business documents.

Common Properties

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs

  • Document Path - (string) Path to the document file to process. Supports various formats including PDF, TIFF, JPEG, PNG, BMP, and other image formats supported by ABBYY FlexiCapture.

  • Export Path - (string) Path where processed results will be exported. The extracted data will be saved to this location in the format specified by your FlexiCapture project configuration (XML, JSON, CSV, etc.).

  • FC Project Path - (string) Path to the FlexiCapture project file (.fcproj). This file contains the document definition, field extraction rules, and processing configuration.

  • Customer Project ID - (string) Customer project identifier for FlexiCapture license activation. This is provided by ABBYY and is required for licensed operation.

  • DLL Path - (string) Path to the FlexiCapture engine DLL files. This should point to the directory containing the ABBYY FlexiCapture SDK libraries.

Output

This node does not produce direct outputs. Results are exported to the specified Export Path location based on the FlexiCapture project configuration.

How It Works

The FlexiCapture node processes documents through the ABBYY FlexiCapture Engine by:

  1. Loading the FlexiCapture project configuration from the specified .fcproj file
  2. Initializing the FlexiCapture engine with the customer project ID and DLL path
  3. Reading the input document from the specified path
  4. Performing OCR and intelligent character recognition on the document
  5. Applying document classification rules to identify document type
  6. Extracting structured data fields according to the project definition
  7. Validating extracted data against configured rules
  8. Exporting results to the specified export path in the configured format

Document Processing Capabilities

The node can process various document types:

  • Invoices - Extract vendor info, line items, totals, dates, invoice numbers
  • Purchase Orders - Capture order details, item descriptions, quantities, prices
  • Receipts - Extract merchant info, purchased items, amounts, dates
  • Forms - Read checkboxes, text fields, signatures, barcodes
  • Contracts - Extract key terms, dates, parties, clauses
  • ID Documents - Read names, numbers, dates, addresses
  • Bank Statements - Extract transactions, balances, account info
  • Shipping Documents - Capture tracking numbers, addresses, item details
  • Tax Documents - Extract tax IDs, amounts, filing information
  • Healthcare Forms - Read patient info, diagnoses, procedures

Practical Examples

Example 1: Process Invoice for Accounting

Extract invoice data for automated bookkeeping:

  • Document Path: C:\invoices\incoming\invoice_2024_001.pdf
  • Export Path: C:\invoices\processed\
  • FC Project Path: C:\FlexiCapture\Projects\InvoiceExtraction\invoice.fcproj
  • Customer Project ID: ABC123-INV-2024
  • DLL Path: C:\Program Files\ABBYY\SDK\12\Bin

Use case: Automatically extract invoice details (vendor, date, amount, line items) from PDF invoices and export to JSON for import into accounting software.

Example 2: Batch Process Purchase Orders

Extract data from multiple purchase orders:

  • Document Path: D:\documents\PO_{{order_number}}.tiff
  • Export Path: D:\exports\purchase_orders\
  • FC Project Path: D:\projects\PurchaseOrder\po.fcproj
  • Customer Project ID: XYZ789-PO-2024
  • DLL Path: C:\ABBYY\FCSDK\Bin

Use case: Process batches of scanned purchase orders, extract structured data, and export to CSV for ERP system import.

Example 3: Extract Receipt Data

Process retail receipts for expense tracking:

  • Document Path: /opt/scans/receipts/receipt_{{timestamp}}.jpg
  • Export Path: /opt/exports/expenses/
  • FC Project Path: /opt/flexicapture/projects/receipt/receipt.fcproj
  • Customer Project ID: REC456-2024
  • DLL Path: /opt/abbyy/sdk/lib

Use case: Scan receipts from mobile photos, extract merchant name, date, total amount, and line items for automated expense reporting.

Example 4: Form Processing

Extract data from standardized forms:

  • Document Path: C:\forms\application_{{id}}.pdf
  • Export Path: C:\forms\data\
  • FC Project Path: C:\FlexiCapture\Projects\ApplicationForm\form.fcproj
  • Customer Project ID: FORM789-2024
  • DLL Path: C:\Program Files\ABBYY\SDK\12\Bin

Use case: Process job application forms, extract applicant information, and export structured data for HR system integration.

Example 5: Contract Data Extraction

Extract key information from contracts:

  • Document Path: \\fileserver\contracts\new\contract_{{ref}}.pdf
  • Export Path: \\fileserver\contracts\processed\
  • FC Project Path: C:\Projects\ContractExtraction\contract.fcproj
  • Customer Project ID: CONT123-2024
  • DLL Path: C:\ABBYY\FCSDK\12\Bin

Use case: Extract contract parties, dates, terms, and obligations from PDF contracts for contract management system.

Example 6: Healthcare Form Processing

Process patient intake forms:

  • Document Path: C:\medical\scans\patient_{{id}}.tiff
  • Export Path: C:\medical\records\
  • FC Project Path: C:\FlexiCapture\Medical\intake.fcproj
  • Customer Project ID: MED456-2024
  • DLL Path: C:\Program Files\ABBYY\SDK\Bin

Use case: Extract patient information, medical history, and insurance details from intake forms for electronic health record (EHR) system.

Example 7: Bank Statement Processing

Extract transaction data from statements:

  • Document Path: D:\banking\statements\{{account}}_{{month}}.pdf
  • Export Path: D:\banking\data\
  • FC Project Path: D:\Projects\BankStatement\statement.fcproj
  • Customer Project ID: BANK789-2024
  • DLL Path: C:\ABBYY\SDK\Bin

Use case: Process bank statements, extract transactions, balances, and account details for financial reconciliation.

Example 8: Shipping Label Processing

Extract shipping information from labels:

  • Document Path: /var/shipping/scans/label_{{tracking}}.png
  • Export Path: /var/shipping/data/
  • FC Project Path: /opt/projects/shipping/label.fcproj
  • Customer Project ID: SHIP123-2024
  • DLL Path: /opt/abbyy/lib

Use case: Scan shipping labels, extract tracking numbers, addresses, and package details for logistics management.

Tips for Effective Use

  • Project configuration: Create well-defined FlexiCapture projects with accurate field definitions and extraction rules
  • Document quality: Use high-quality scans (minimum 300 DPI) for better OCR accuracy
  • Template training: Train FlexiCapture with sample documents to improve recognition accuracy
  • File formats: PDF and TIFF formats generally provide best results for document processing
  • Batch processing: Use loops to process multiple documents in sequence
  • Path validation: Verify all paths are accessible and have proper permissions
  • License management: Ensure valid FlexiCapture license and customer project ID
  • Export formats: Configure export format in FlexiCapture project based on downstream system requirements
  • Field validation: Define validation rules in FlexiCapture project to ensure data quality
  • Error handling: Implement error handling for documents that fail processing
  • Performance: Process large batches during off-peak hours for better system performance
  • Monitoring: Track processing success rates and identify problematic document types

Common Errors and Solutions

Error: "Document path cannot be empty"

Solution: Provide a valid file path to the document that needs to be processed. Ensure the path is not null or empty.

Error: "Export path cannot be empty"

Solution: Specify a valid directory path where the processed results should be exported. Create the directory if it doesn't exist.

Error: "FC project path cannot be empty"

Solution: Provide the full path to your FlexiCapture project file (.fcproj). Verify the file exists at the specified location.

Error: "Customer Project ID cannot be empty"

Solution:

  • Obtain a valid customer project ID from ABBYY
  • Verify your FlexiCapture license includes the customer project ID
  • Check with your ABBYY account manager if you don't have this information

Error: "DLL path cannot be empty"

Solution:

  • Provide the path to the directory containing FlexiCapture engine DLL files
  • Verify ABBYY FlexiCapture SDK is properly installed
  • Check the installation directory (typically C:\Program Files\ABBYY\FCSDK\<version>\Bin)

Error: File access or permission errors

Solution:

  • Ensure the robot has read access to the document path
  • Verify write permissions to the export path directory
  • Check network path accessibility for UNC paths
  • Run the robot with appropriate user permissions
  • Verify antivirus software is not blocking file access

Error: FlexiCapture engine initialization failed

Solution:

  • Verify the DLL path points to the correct ABBYY SDK installation
  • Ensure all required DLL dependencies are present
  • Check FlexiCapture SDK version compatibility
  • Verify the customer project ID is valid and activated
  • Restart the robot service if licensing issues persist

Error: Project file cannot be loaded

Solution:

  • Verify the .fcproj file path is correct
  • Ensure the project file is not corrupted
  • Check FlexiCapture project compatibility with SDK version
  • Open the project in FlexiCapture Studio to verify it's valid
  • Re-export the project from FlexiCapture Studio if necessary

Error: Document processing failed

Solution:

  • Verify the document file is not corrupted or password-protected
  • Check if the document format is supported by your FlexiCapture project
  • Ensure document image quality is sufficient for OCR (minimum 300 DPI recommended)
  • Review FlexiCapture project settings for document type compatibility
  • Try processing the document manually in FlexiCapture Studio to identify issues

Error: OCR recognition errors

Solution:

  • Improve scan quality (use higher DPI, better lighting)
  • Clean up scanned images (remove noise, straighten skew)
  • Train FlexiCapture with more sample documents
  • Adjust OCR settings in the FlexiCapture project
  • Use appropriate language settings for the document content

Error: Export failed

Solution:

  • Verify export path exists and is writable
  • Check available disk space at export location
  • Ensure export format is properly configured in FlexiCapture project
  • Verify no other process is locking the export directory
  • Check export template configuration in the project file

FlexiCapture Project Setup

To use this node effectively, you need to:

  1. Install ABBYY FlexiCapture SDK - Download and install from ABBYY
  2. Create a FlexiCapture Project - Use FlexiCapture Studio to:
    • Define document layouts and templates
    • Configure fields to extract (text, dates, numbers, checkboxes, etc.)
    • Set up validation rules for data quality
    • Define export formats and templates
    • Train the system with sample documents
  3. Export the Project - Save as .fcproj file for use in automation
  4. Obtain License - Get customer project ID from ABBYY for your license

Data Extraction Best Practices

  • Field definitions: Create clear field definitions with appropriate data types
  • Validation rules: Implement validation rules to catch extraction errors
  • Quality control: Review processed results periodically to identify accuracy issues
  • Template matching: Use template matching for structured documents (forms, invoices with fixed layouts)
  • Flexible recognition: Use flexible recognition for variable document layouts
  • Training data: Provide diverse training samples for better accuracy across document variations
  • Language settings: Configure correct language settings for OCR accuracy
  • Region definition: Define precise field regions for better extraction accuracy
  • Data formatting: Configure output data formats to match downstream system requirements
  • Confidence scoring: Set appropriate confidence thresholds for field acceptance

RPA Use Cases

  • Accounts Payable: Automate invoice processing and data entry into accounting systems
  • Accounts Receivable: Process customer orders and payment receipts
  • HR Onboarding: Extract data from job applications, resumes, and employment forms
  • Claims Processing: Extract information from insurance claims and supporting documents
  • Contract Management: Process contracts and extract key terms and obligations
  • Compliance: Extract data from regulatory documents and reports
  • Customer Onboarding: Process KYC documents, ID verification, and application forms
  • Supply Chain: Process purchase orders, shipping documents, and packing lists
  • Healthcare: Extract patient data from medical forms and insurance documents
  • Banking: Process loan applications, account opening forms, and statements
  • Tax Processing: Extract data from tax forms and supporting documents
  • Document Archival: Convert paper documents to searchable digital archives
  • Mailroom Automation: Process incoming mail and route based on content
  • Expense Management: Extract receipt and invoice data for expense tracking

Integration Patterns

Pattern 1: Invoice Processing Workflow

1. Monitor folder for new invoice PDFs
2. For each invoice:
- FlexiCapture node: Extract invoice data
- Parse exported XML/JSON
- Validate extracted amounts and dates
- Write to accounting system database
- Move processed invoice to archive
- Send email notification

Pattern 2: Form Processing with Validation

1. Receive scanned form via email
2. Save attachment to processing folder
3. FlexiCapture node: Extract form data
4. Validate extracted data:
- Check required fields are present
- Verify data format (dates, emails, phone numbers)
5. If validation passes:
- Import to CRM/database
- Send confirmation email
6. If validation fails:
- Queue for manual review
- Alert supervisor

Pattern 3: Batch Document Processing

1. Scan batch of documents to folder
2. Get list of files to process
3. For each document:
- FlexiCapture node: Process document
- Parse exported data
- Insert into data table
4. After batch completion:
- Generate processing report
- Export data table to CSV
- Import to business system

Performance Considerations

  • Processing time: Document processing time varies based on page count, complexity, and quality
  • Resource usage: FlexiCapture processing is CPU and memory intensive
  • Concurrent processing: Limit parallel FlexiCapture operations based on system resources
  • File size: Large multi-page documents take longer to process
  • Network paths: Local paths process faster than network paths
  • Disk I/O: Use local SSD storage for best performance
  • License limits: Check FlexiCapture license for concurrent processing limits
  • Batch optimization: Process similar documents together for better performance

Supported Document Formats

  • PDF - Single and multi-page PDF documents
  • TIFF - Single and multi-page TIFF images
  • JPEG/JPG - Standard JPEG images
  • PNG - Portable Network Graphics images
  • BMP - Bitmap images
  • Other formats - Support depends on ABBYY FlexiCapture SDK version and configuration

Windows Platform Requirement

This package is Windows-only and requires:

  • Windows operating system (Windows 10, Windows Server 2016 or later recommended)
  • ABBYY FlexiCapture SDK installation
  • Valid ABBYY FlexiCapture license
  • .NET Framework 4.7.2 or later