Skip to main content

Integration, Implementation and Output

The organizational data model, configuring how validated data is delivered to downstream systems, controlling field-level outputs, and monitoring platform performance

Integration, Implementation and Output covers the layer of Docupath responsible for defining the organisational data model, configuring how validated data reaches downstream systems, controlling what data is visible in exports, and monitoring platform performance. This L1 category spans six modules: Organizations, Trading Parties, Data Export Templates, Destination Formats and APIs, Customize captured fields, and Usage Insights and Analytics. Together, these modules represent the operational backbone of a Docupath deployment — the configuration layer that connects the platform's AI capabilities to the real-world systems and workflows of the organisation.

How It Works

Organizations and Trading Parties

Before documents can be intelligently routed and processed, Docupath needs to understand the organisational structure and the business relationships involved. Organizations define the hierarchy — parent entities and sub-organisations representing departments, regions, or subsidiaries. Trading Parties represent the suppliers, buyers, or counterparties that appear on documents. Together, these two modules drive automated routing, rule scoping, and enrichment behaviour.

Data Export Templates and Destination Formats

Once a document is approved, structured data needs to leave Docupath in a format that downstream systems understand. Destination Formats define the target file structure (e.g., XML, JSON). Data Export Templates use mustache syntax to map Docupath's extracted fields to the exact schema expected by the receiving system — ERP, EDI gateway, data lake, or compliance tool — without requiring custom code.

Customize Captured Fields

Not every field extracted by Docupath is needed in every export. Customize captured fields allows organisations to suppress entire sections or individual fields at the output level, with scope-based control (Global, Country, Organization, or Trading Party). This supports data minimisation practices and keeps downstream payloads clean.

Usage Insights and Analytics

Usage Insights provides the operational dashboard for monitoring document throughput, accuracy rates, rejection patterns, and reviewer productivity. It is the primary tool for identifying bottlenecks, measuring SLA performance, and generating audit-ready reporting.

Supported Configurations and Options

Organizations

Setting

Options

Notes

Self-Service Access

Enabled / Disabled

Restricts document visibility to mapped users

Overriding Trading Party

One per sub-organization

Sets Primary Party for all routed documents

Urgent Flag

Enabled / Disabled

Marks all documents as high priority

Trading Parties

Setting

Options

Notes

Trading Relationships

Auto-created

Created when two parties interact

Manual Assignment

Available in Review screen

Override auto-detected party

Data Export Templates

Setting

Options

Notes

Variable syntax

Mustache ({variable_name})

Dynamic field mapping

Document type scope

Per document type

One template active at a time per type

Naming convention

Free text (recommended: Format-Type-Region-v1.0)

Versioning best practice

Destination Formats and APIs

Setting

Options

Notes

Output format

XML

XML standard; additional formats available

Credential scope

Tenant-level

Fine-grained field-level scoping not supported

Customize Captured Fields

Setting

Options

Notes

Scope

Global, Country, Organization, Trading Party

Higher scope overrides lower

Disable level

Section-level or field-level

Mandatory sections (primary/secondary party) cannot be disabled

Usage Insights

Metric

Description

Uploaded

Total documents ingested

Processed

Documents through AI extraction

Pending

Awaiting review

Approved / Rejected

Final disposition counts

Accuracy

AI extraction accuracy rate

Other Technical Specifications

Specification

Value

Max sub-organizations per parent

100

Max alternate names per trading party

20

Max API credential pairs

No published limit

Client Secret recovery

Not possible — must regenerate

Export format change scope

Future exports only (historical unchanged)

Max users per tenant

500

Notes

  • Only one data export template can be active per document type at a time; multiple simultaneous mappings require separate workflows

  • Changing the destination format applies to future exports only — historical exports are not retroactively converted

  • Client Secrets cannot be recovered; loss requires full credential regeneration and downstream reconfiguration

  • Self-Service Access creates document silos — if not planned carefully, users may be unable to see documents they need

  • Regions are filtering tools only; they do not enforce data residency or control document routing

  • Acknowledgement status requires the external system to call back to Docupath — systems without callback support remain permanently in "Sent" status

Did this answer your question?