An override trading party is a master record assigned at the organization (sub-org) level that automatically becomes the Primary Party for all documents routed to that organization.
This feature is essential for deployments where a single entity must consistently appear as the primary party regardless of what the document content indicates. It ensures uniform document routing and party assignment across multi-entity implementations.
How It Works
Accessing the Override Trading Party Setting
Navigate to the Main Menu and select Manage Organizations
Locate and click the Edit button for the sub-organization you want to configure
Find the Override Trading Party field in the organization details form
Assigning an Override Trading Party
Click the dropdown in the Override Trading Party field
Select a trading party from the list of available parties under the sub-organization
The dropdown displays party names and alternate names (following the matching hierarchy: alternate name > party name, case-insensitive)
Click Save to apply the override
Effect on Document Processing
Once an override trading party is assigned to a sub-organization:
All documents routed to that sub-organization will automatically have their Primary Party set to the override trading party
The override takes precedence over any party information extracted from the document itself
The assignment applies consistently across all document types and sources
Manual party assignments in individual documents are bypassed by the override
Supported Configurations and Options
Configuration | Description | Scope | Mandatory |
Override Trading Party Selection | Choose a single trading party from sub-org's master records | Per sub-organization | No (optional feature) |
Multi-organization Setup | Different sub-orgs can have different override parties | Organization-level | N/A |
Fallback Behavior | If no override is set, document content determines Primary Party | System-wide | N/A |
Trading Party Pool | Only parties belonging to the selected sub-org appear in dropdown | Sub-organization | Yes |
Other Technical Specifications
Aspect | Details |
Assignment Level | Sub-organization (mandatory organization scope) |
Override Scope | All documents routed to the assigned sub-organization |
Priority in Hierarchy | Overrides document-extracted values and auto-detected parties |
Data Source | Master trading parties under the sub-organization |
Field Mandatory | No; organizations may function without an override |
Soft Delete Impact | Soft-deleted parties are excluded from override selection |
API Interaction | Override status can be queried via Organization endpoints |
Notes
Single Override per Organization: Only one trading party can be set as override per sub-organization; multi-party overrides are not supported
Deleted Trading Parties: If an override party is soft-deleted, new documents cannot use it; existing documents retain the reference but the party becomes inactive
Cross-Organization Movement: Documents cannot be moved between organizations; they process according to their assigned org's override
No Conditional Overrides: The override applies uniformly; conditional logic based on document content or party attributes is not supported
Party Pool Dependency: If the sub-organization has no trading parties, the override dropdown will be empty
Routing Fallbacks: For documents emailed to a Main Organization, the override trading party is one of several routing rules, not the only one. If it does not produce a single match, Docupath also routes to the sole sub-organization when the Main Organization has only one, and to the sub-organization the sender is assigned to when the sender belongs to exactly one, before recording "No sub organization detected." See "Configuring Document Ingestion via Email" for the full precedence.