<!-- TODO: Add the main screenshot for this article here - every L2 article needs one. -->
Docupath enforces specific limits on file sizes, document properties, batch operations, organizational structures, and input field lengths to maintain system performance and stability.
Understanding these constraints is essential for planning document workflows, configuring business rules, and managing data export. This article outlines all hard limits and provides guidance for handling limit-related errors.
How It Works
Understanding Hard Limits
Docupath operates with strict, non-negotiable limits across multiple dimensions of the platform. These limits apply uniformly across all tenants and cannot be increased through configuration or customer requests. Hard limits are enforced at the API and UI level, preventing operations that exceed thresholds. When a user attempts to exceed a limit, the system returns a clear error message indicating which limit was exceeded and provides remediation guidance.
Document and File Size Limits
Individual documents are subject to the following constraints:
File Size: Maximum 50MB per document. Large scans or high-resolution images that exceed this limit must be split into smaller files before upload.
Page Count: Maximum 150 pages per document. Multi-page documents exceeding this count must be separated into multiple uploads.
Line Items: Maximum 500 line items per document. Documents with extensive line item tables (common in invoices and purchase orders) cannot exceed this count.
These limits are applied at upload time. If a document exceeds any threshold, the upload is rejected and the user is prompted to reduce the file size or split the document.
Batch and Bulk Operation Limits
Batch operations allow users to process multiple documents simultaneously or perform bulk actions on existing documents:
Batch Upload: Maximum 100 documents per batch (single upload session)
Email Attachment Batch (Multiple Primary Documents address): Maximum 10 attachments per email, since each one becomes its own document. An email that carries more than 10 is refused in full — none of its attachments are stored — and the sender receives the Document limit reached reply
Email Supporting Attachments (Single Primary Document address): Maximum 15 supporting attachments stored against the primary document, so 16 files in total. The limit counts only the supporting attachments: 16 files are accepted, 17 are refused and the sender receives the Document processing issue reply
Bulk Review: Maximum 50 documents can be reviewed simultaneously in a single bulk review session
Bulk Download: Maximum 50 documents can be downloaded in a single bulk download operation
Bulk Reprocess: Maximum 50 documents can be reprocessed in a single operation
Organization and User Limits
User and organizational structure is constrained by the following limits:
Users Per Tenant: Maximum 500 users across all sub-organizations
Organizations Per Tenant: Maximum 100 parent organizations per tenant (multi-tenancy support)
Sub-Organizations Per Org: Maximum 100 sub-organizations per parent organization
Trading Parties with Alternate Names: Maximum 20 alternate names per organization (for matching variations of supplier/customer names)
Input Field Limits
Text input fields have maximum character lengths. These limits are enforced in both the web interface and the API, and API requests that exceed a cap or fail a format check receive a field-level validation error. Required text fields also reject values that contain only whitespace.
In the web interface a capped field stops accepting input once it reaches its limit, and a message appears below it reading "<Field> is capped to N characters". Pasting text longer than the cap keeps as much as fits and shows the same message, so it is clear the value was shortened rather than saved in full.
The limits below apply to configuration fields that a user types in. They do not apply to the extracted field values shown on the document review screen, which are never truncated so that captured data stays intact.
Instruction Builds are the one exception to this behavior. The instruction box does not stop typing at the cap, so an over-long instruction is rejected when you save it rather than while you write it.
Organizations
Field | Maximum Characters |
Organization name | 150 |
Receiver name | 100 |
Attachment email | 254 |
Alternate organization name | 150 |
Trading Parties
Field | Maximum Characters |
Name | 255 |
Address | 255 |
City | 100 |
Postal code | 10 |
Extra (custom) fields | 255 |
Alternate name | 150 |
Users and Workspace
Field | Maximum Characters |
User email | 254 |
Full name | 150 |
Workspace subdomain | 63 |
Workspace company name | 150 |
Account owner | 150 |
Business Rules and Other Fields
Field | Maximum Characters |
Rule title (Transformation and Rejection rules) | 128 |
Rule description (Transformation and Rejection rules) | 30000 |
Instruction text (Instruction Builds) | 30000 |
Rule condition value | 2000 |
Rule action value | 2000 |
Rejection reason | 2000 |
API key name | 150 |
Region name | 100 |
Supporting file title | 255 |
IP whitelisting description | 1000 |
Rejection notification recipients field | 2000 |
Input Format Rules
In addition to length caps, the following fields must match a required format:
Field | Required Format |
Email addresses | Valid email format (RFC 5321) |
Workspace subdomain | Valid subdomain format (RFC 1035) |
Postal codes | Letters and numbers, with single spaces or hyphens between them. A separator cannot start or end the value, and two separators cannot sit next to each other. |
Organization inbox email (front part) | Letters, numbers and underscores, with single dots between them. A dot cannot start or end the value, and two dots cannot sit next to each other. |
Numeric IDs | Digits only |
Business Logic Configuration Limits
Instruction Builds, Transformations, and Rejection Rules are subject to the following constraints:
Instruction Groups Per Org/Country/Global: Maximum 100 per scope level. This counts instruction groups (scope entries), not the individual instructions inside a group. At country scope the cap is on the number of countries that have instructions configured
Rule Groups Per Organization: Maximum 100 rule groups per organization
Rules Per Group: Maximum 500 individual rules per rule group
Total Rule Groups Per Tenant: Maximum 1,000 rule groups across all organizations
Supporting Files Limits
CSV supporting files (used for data enrichment, validation, and reference lookups) are subject to the following constraints:
Rows Per File: Maximum 100,000 rows
Columns Per File: Maximum 10 columns
File Size: Maximum 50MB per CSV file
CSV Files Per Organization: Maximum 10 CSV files per organization
CSV Files Per Tenant: Maximum 100 CSV files across all organizations in the tenant
Replacement Column Structure: When you replace the CSV of an existing supporting file, the new file must contain every column name present in the last valid version. You can add new columns, but you cannot remove or rename an existing one. Column order is not checked, and the row content is not compared between versions. This constraint applies only to replacements, not to first-time uploads
Replacement Baseline: The comparison is against the most recent version that processed successfully, not the original upload. A column added by an earlier replacement therefore becomes required for every later replacement. Versions that failed are skipped, so a failed replacement does not change what the next one must contain
Supporting files are used to augment document processing with external data sources and are subject to upload and storage constraints.
Supported Configurations and Options
Configuration | Limit | Notes |
Page Count | 150 pages | Per document; split multi-page documents |
Batch Upload | 100 documents | Single upload session |
Email Documents | 10 attachments | Per email on a Multiple Primary Documents address; a larger email is refused in full |
Email Supporting Attachments | 15 attachments | Per primary document on a Single Primary Document address; 16 files in total |
Bulk Review | 50 documents | Single bulk review session |
Users Per Tenant | 500 | Across all organizations |
Sub-Organizations | 100 | Per parent organization |
Instruction Groups | 100 | Per scope (Org/Country/Global); counts scope entries, not instructions within a group |
Rules Per Group | 500 | Individual rules within a group |
Trading Party Name | 255 characters | Longest input field cap for party records |
User Email | 254 characters | RFC 5321 format required |
Rule Title | 128 characters | Transformation and Rejection rules |
CSV Rows | 100,000 | Per supporting file |
CSV File Size | 50 MB | Per supporting file |
CSV Files Per Tenant | 100 | Across all organizations |
Other Technical Specifications
Specification | Value | Notes |
Maximum Page Count | 150 pages | Enforced at processing; exceeds fail gracefully |
Batch Size Limit | 100 documents | Per single upload/batch operation |
Bulk Review Document Limit | 50 documents | Per session |
Maximum Sub-Orgs | 100 per parent org | Enforced at creation |
CSV Column Limit | 10 columns | Enforced at upload |
CSV Replacement Columns | All columns from the current version | Enforced when replacing a file; extra columns are allowed |
Rule Groups (Org) | 100 per organization | Per rule group creation |
Total Rule Groups | 1,000 per tenant | Aggregate across all orgs |
Input Field Validation | UI and API | Field-level error messages; whitespace-only values rejected on required fields |
Session Timeout | 24 hours of inactivity | Session expires and re-authentication required |
Concurrent Uploads | 10 concurrent | Per user session |
Notes
Page Count Calculation: Page count is calculated after document conversion and may differ from the source document's apparent page count (e.g., scanned images counted as one page each).
File Size Measurement: File size is measured in bytes and includes document metadata and embedded images. Compression may not reduce file size significantly for scanned documents.
Batch Upload Partial Failures: If any document in a batch exceeds limits, the entire batch upload fails. Users must remove offending documents and retry.
CSV Special Characters: CSV supporting files containing special characters (unicode, line breaks within cells) may have row/column counts calculated differently. Ensure CSV is properly formatted (RFC 4180 standard).
CSV Replacement Column Check Timing: The column check for a replacement runs during processing, after the file finishes uploading, so the upload itself reports success before the check completes. When the check fails, the replacement is not promoted, the last successful version stays active and continues to serve lookups, and the failed attempt is recorded in the version history.
Concurrent User Limits: While the platform supports 500 users per tenant, simultaneous active sessions may be limited to improve performance. Users attempting to exceed concurrent session limits are prompted to log out other sessions.
Sub-Organization Nesting: Docupath supports only one level of sub-organization nesting (parent > sub). Further nesting is not supported.
Trading Party Limit Impact: Exceeding the 20 alternate names per organization increases name matching complexity and may impact extraction accuracy. Consolidate duplicates regularly.
Rule Group Complexity: Rule groups approaching the 500-rule limit may experience slower execution times. Monitor rule group performance and split overly complex groups into multiple groups if needed.
Input Limits Apply to All Clients: Input field limits are validated server-side, so they apply to direct API integrations as well as the web interface. Integrations that previously stored longer values must truncate them to the documented caps.