The Customize captured fields feature enables fine-grained control over which extraction fields are visible and mandatory across your tenant using a four-tier scope hierarchy. Customizations can be applied at section-level (hide/show entire form sections) or field-level (control individual data fields) across four organizational scopes: Global (baseline), Country (regional overrides), Organisation (org-specific rules), and Trading Party (partner-specific rules).
The Primary Party and Secondary Party sections are mandatory and cannot be disabled. Different user roles have restricted access: administrators can customize all scopes, while custom users can only customize Organization and Trading Party scopes.
How It Works
Understanding the Scope Hierarchy
Customizations follow a priority chain where lower scopes override higher scopes:
Global (lowest priority) ↓ overridden by Country ↓ overridden by Organisation ↓ overridden by Trading Party (highest priority)
For any given field or section, the system applies the most specific rule available. If no Trading Party customization exists, it checks Organisation; if that's absent, it uses Country; finally, it falls back to Global.
Global Scope: Defining the Baseline
Navigate to Settings > Customize captured fields
Select the Global tab
View all available sections (Primary Party, Secondary Party, Invoice Details, Line Items, etc.)
Section-level customization:
Toggle sections ON/OFF to show or hide entire form sections
Primary Party and Secondary Party sections cannot be disabled
Example: Hide "Tax Details" section if your org doesn't require tax data
Field-level customization:
Expand a section to see individual fields
Toggle individual fields ON/OFF
Fields within hidden sections are automatically hidden
Click Save to apply Global baseline settings
Country Scope: Regional Overrides
Select the Country tab
Choose a country from the dropdown (e.g., "Sweden", "Netherlands", "Germany")
Customize fields and sections for that country only:
Enable fields required by country-specific regulations
Disable fields not used in that country (e.g., US state codes for European countries)
Example: Enable VAT identification fields for EU countries; disable for non-EU
Settings apply only to documents tagged with that country
Click Save; fields not customized at Country level inherit Global settings
Organisation Scope: Multi-Org Customization
Select the Organisation tab
Use the Multi-organisation Selector to choose one or more organizations (sub-orgs)
Customize fields and sections for those organizations:
Different organizations may have different field requirements
Useful for multi-tenant deployments with varying compliance needs
Example: Parent company requires PO number; subsidiary doesn't
Settings apply to documents routed to selected organizations
Click Save; unselected organizations inherit Country and Global settings
Trading Party Scope: Partner-Specific Rules
Select the Trading Party tab
Choose a specific trading party (supplier, customer, partner) from the dropdown
Customize fields and sections for that partner only:
Enforce specific data from key suppliers (e.g., always require SKU, batch number)
Reduce requirements for low-risk partners
Align with partner's data provision capabilities
Example: Vendor A provides full details; Vendor B provides invoice number only
Settings apply to all documents involving that trading party
Click Save; other trading parties inherit Organisation, Country, and Global settings
Mandatory Sections
The following sections cannot be disabled at any scope level:
Primary Party: Always visible; required for document classification
Secondary Party: Always visible; required for matching and routing
All other sections (Invoice Details, Tax Details, Line Items, etc.) can be hidden if needed.
Duplicate Prevention
The system prevents conflicting customizations:
Same field, different scopes: The highest-priority scope rule applies (Trading Party > Organisation > Country > Global)
Conflicting mandatory rules: If a field is required at one scope and hidden at another, the most restrictive rule applies
Warning indicators: The UI shows which scope a setting comes from and whether it overrides a lower scope
Testing Customizations Across Scopes
Before deploying customizations to production:
Test in sandbox environment:
Create test documents with various combinations of country, organization, and trading party
Verify the correct fields appear at each level
Confirm mandatory fields cannot be skipped
Validate override behavior:
Create a document matching Global settings only → verify Global fields appear
Create a document matching Country settings → verify Country overrides Global
Create a document in a specific Organization → verify Organisation overrides Country and Global
Create a document from a specific Trading Party → verify Trading Party has highest priority
Test with different user roles:
Admins should see all customization levels
Custom users should only see Organisation and Trading Party tabs
Reviewers should see only the resulting field visibility, not customization settings
Supported Configurations and Options
Configuration | Description | Scope Levels | Field-level | Section-level |
Global Baseline | Default field visibility for all documents | 1 (Global) | Yes | Yes |
Country Overrides | Region-specific customizations | 1 (Country) | Yes | Yes |
Multi-org Customization | Organization-specific rules | 1+ (Organisation) | Yes | Yes |
Trading Party Rules | Partner-specific field requirements | 1 (Trading Party) | Yes | Yes |
Mandatory Sections | Cannot disable Primary/Secondary Party | All scopes | N/A | Yes (locked) |
Inheritance Model | Lower-priority scopes inherited if not overridden | All scopes | Yes | Yes |
Conflict Resolution | Highest-priority scope rule applies | All scopes | Yes | Yes |
Other Technical Specifications
Aspect | Details |
Scope Count | 4 levels (Global, Country, Organisation, Trading Party) |
Priority Order | Trading Party > Organisation > Country > Global |
Section-level Control | Show/Hide entire form sections |
Field-level Control | Show/Hide individual extraction fields |
Mandatory Sections | Primary Party, Secondary Party (cannot be disabled) |
Non-destructive | Changes do not affect historical data; only new documents processed after change are affected |
Multi-org Selection | Organisation scope supports multiple organizations in single configuration |
Applied At | Document processing/ingestion; affects field extraction and validation |
Undo/Revert | Previous versions retained; can revert to prior customization state |
Audit Trail | All customization changes logged with user, timestamp, scope, and before/after state |
Notes
No Cross-scope Conflicts: If a field is required at Country level and hidden at Global level, the hidden status is overridden; the system always applies the highest-priority rule
Primary/Secondary Party Protection: Cannot be hidden or disabled; attempting to do so will show an error message
Multi-org Field Conflicts: If two organizations have conflicting customizations for the same field, each document processes according to its assigned organization
Country Matching Sensitivity: Country assignment is case-sensitive and must match exactly; mismatches will cause documents to fall back to Global settings
Large-scale Changes: Modifying Global settings affects all documents not specifically customized at lower scopes; plan changes carefully in production
Historical Data: Customizations apply only to documents processed after the change; historical documents retain their original field visibility
No Bulk Revert: Individual scope customizations must be reverted one at a time; bulk revert across all scopes is not available
Limited Conditional Logic: Customizations cannot be conditional on field values (e.g., "show Tax ID only if Country is EU"); rules are static per scope