FTP - OpenText Core Capture Services Integration and Automation

Common Integration Use Cases Between FTP and OpenText Core Capture Services

1. Automated invoice intake from supplier FTP drops to accounts payable capture

Suppliers place scanned invoices, credit notes, and supporting PDFs on a secure FTP/SFTP folder. OpenText Core Capture Services retrieves the files, classifies document types, extracts invoice fields such as vendor name, invoice number, PO number, tax, and totals, then routes the data to downstream AP approval and ERP workflows. This reduces manual indexing, speeds up invoice processing, and improves straight-through processing rates.

2. Digital mailroom processing for scanned correspondence and forms

Branch offices, service centers, or outsourced mail vendors upload daily batches of scanned mail to FTP. OpenText Core Capture Services ingests the files, separates multi-page batches, identifies document categories such as claims, applications, complaints, or HR forms, and extracts key metadata for routing to the correct business team. This creates a centralized digital mailroom with faster triage and fewer misplaced documents.

3. Customer onboarding document collection from partner or branch systems

Channel partners or branch applications deposit onboarding packets on FTP, including application forms, identity documents, proof of address, and signed agreements. OpenText Core Capture Services captures and validates the documents, extracts customer details, and passes structured data to CRM, case management, or KYC review systems. This shortens onboarding cycle times and improves compliance consistency across distributed intake channels.

4. Claims document ingestion from external service providers

Insurance adjusters, repair vendors, or third-party administrators upload claim forms, photos, estimates, and supporting evidence to FTP. OpenText Core Capture Services classifies the incoming content, extracts claim identifiers and key claim attributes, and prepares the data for claims adjudication workflows. This helps claims teams process high-volume submissions more quickly and with less manual handling.

5. Purchase order and remittance document capture from trading partners

Trading partners send purchase orders, remittance advice, or order-related documents through FTP as batch files. OpenText Core Capture Services extracts order numbers, line items, payment references, and partner identifiers, then forwards the data to order management, ERP, or reconciliation processes. This supports faster order confirmation, cleaner cash application, and better partner coordination.

6. Legacy document exchange for organizations without API-based integration

Many enterprises still rely on FTP for integration with legacy scanners, print vendors, BPO providers, or regional offices. OpenText Core Capture Services can consume these file-based inputs directly, enabling document capture automation without replacing existing transfer mechanisms. This is especially useful when modernizing document workflows while preserving established file exchange processes.

7. Batch processing of high-volume forms from remote locations

Retail stores, clinics, warehouses, or field offices can upload daily batches of forms, applications, or compliance documents to FTP at scheduled intervals. OpenText Core Capture Services processes the batch, extracts required data, and sends results to operational systems for review or approval. This supports distributed operations where local sites need a simple, reliable transfer method.

8. Exception handling and reprocessing of failed capture batches

When document batches fail validation or require manual review, OpenText Core Capture Services can export exception files, audit logs, or corrected document sets back to an FTP location for downstream teams or external processors. This creates a controlled handoff for rework, quality assurance, or archival purposes and helps operations teams manage exceptions without disrupting the main workflow.