Document Ingestion is the entry point for getting documents into the Docupath platform. It provides four flexible ingestion paths (Drag & Drop, Email, API and Mobile App) to accommodate different user workflows and integration scenarios.
Each path supports a range of file types and includes intelligent routing capabilities, particularly for assigning documents to sub-organizations during email ingestion. Smart upload features enhance the user experience by enabling batch uploads, urgent document prioritization, and queue management before final submission.
How It Works
Drag & Drop (Web App)
Users upload documents directly through the web application by dropping files into the designated Upload area or using the browse function. The interface allows users to select which sub-organization should receive the documents. Multiple files can be queued simultaneously, with each file treated as its own primary document. All documents in a single upload batch are assigned to the same selected sub-organization.
On the Upload screen, before processing, supplementary attachments can be added to a primary document, and documents can be marked as "Urgent" to prioritize them. Marking documents urgent requires the Priority Queue permission.
Email Ingestion
When a Main Organization is created, Docupath automatically generates a unique organization email address for document uploads. Documents can also be sent directly to a Sub Organization's email address. Files are attached to emails and sent to these addresses.
Docupath supports two types of email ingestion:
Single Primary Document with Optional Attachments: One attachment is treated as the primary document, and any additional attachments are associated with it as supporting attachments.
Multiple Primary Documents: Each attachment is processed as a separate primary document. This mode uses separate email addresses configured for every organization and sub-organization.
On the Single Primary Document address, when an email has no valid business-document attachment, Docupath processes the email body itself as the document. The Multiple Primary Documents address never turns the body into a document. See Processing the Email Body as a Document.
Sub-Organization Assignment Logic: When documents arrive via Main Org email, the system performs automatic routing based on the document's Primary Party field:
If the Primary Party matches a sub-organization's override trading party → document is assigned to that sub-organization
If no match is found → system displays "No sub organization detected"
If multiple matches exist → system displays "No sub organization detected" (ambiguous routing prevented)
API Upload
Developers can integrate programmatic uploads by generating unique API keys from the Destination Format & APIs section. Docupath provides multiple APIs for this, including ingestion, polling, and webhook APIs. API uploads provide secure document transmission and status retrieval capabilities. A Sub Organization ID must be included in every API request to specify the destination.
Supported Configurations & Options
Supported File Types
Documents: PDF, DOCX, DOC, XLSX, XLS, XML, HTML, TXT
Images: JPG, JPEG, PNG, TIFF, TIF, HEIC
File Size and Page Limits
Maximum file size: 50 MB per document
Maximum pages: 150 pages per document
Batch Composition
Drag & Drop batch limit: Up to 100 documents per batch
Email attachments limit: Up to 10 attachments per email on a Multiple Primary Documents address, where each attachment becomes its own document; on a Single Primary Document address, the primary document plus up to 15 supporting attachments, so 16 files in total
Mixed uploads: Supported - different file formats and document types can be combined in a single batch
Smart Upload Features
File-level attachments: Attach supplementary files to primary documents
Urgent marking: Flag documents as urgent, which requires the Priority Queue permission
Queue management: Delete or re-upload files before batch submission
Queue search: Search within the upload queue by file name or metadata
Skip workflow: "Go to Review" button to proceed to the Review Screen without uploading additional files
Other Technical Specifications
Parameter | Specification |
Ingestion Paths | 4 (Drag & Drop, Email, API, Mobile App) |
Supported Formats | 13 file types (PDF, DOCX, DOC, XLSX, XLS, XML, JPG, JPEG, PNG, TIFF, TIF, HEIC, HTML, TXT) |
Max File Size | 50 MB |
Max Pages per Document | 150 |
Max Drag & Drop Batch | 100 documents |
Max Email Attachments | 10 per email (Multiple Primary Documents); 15 supporting attachments plus the primary document, 16 files in total (Single Primary Document) |
API Authentication | Unique API keys per Destination Format & APIs configuration |
Sub-Org Assignment | Automatic via Primary Party matching (email) or explicit selection (Drag & Drop, API, Mobile App) |
Notes
Urgent marking permission: Marking documents urgent requires the Priority Queue permission. Without it, the option is greyed out rather than hidden. See Working with Urgent Documents
Ambiguous routing: When multiple sub-organizations match a document's Primary Party during email ingestion, the system cannot auto-assign and requires manual intervention
Attachment limit: A Multiple Primary Documents address is capped at 10 attachments per message, and the whole email is refused if it carries more, so larger batches must be split across multiple emails. A Single Primary Document address accepts the primary document plus up to 15 supporting attachments, so an email of 16 files is accepted and one of 17 is refused
Batch size constraint: Drag & Drop is limited to 100 documents per batch; very large operations may require multiple submissions
File size ceiling: Individual files exceeding 50 MB or 150 pages will be rejected during ingestion
API key security: API keys must be managed securely; compromised keys should be regenerated immediately
No automatic retry: Failed API uploads are not automatically retried; manual resubmission required
Mixed file type processing: While supported, mixing document types (invoices, receipts, contracts) in one batch may impact downstream extraction accuracy