Docupath provides trading party enrichment as two features: Primary party data enrichment and Secondary party data enrichment. Each is enabled for a tenant independently of the other.
The two behave identically. What separates them is which party on the document they act on, which follows from the document itself rather than from the heading above the block on screen.
How It Works
Matching and Enrichment
Every processed document is matched against the trading party master records held under its organization. Trading Parties covers how that match is made.
Where a record matches, that party's enrichment writes the record's master data onto the document. It fills a field the page left blank, replaces a printed value that disagrees with the record, and clears a field the record leaves empty. A field the record confirms is badged Verified on the review screen.
Which Party Is Primary
Primary and secondary are not fixed labels. On a document that passes between two sides, the primary party is the one the document is addressed to and the secondary party is the one it comes from.
An invoice is addressed to its Buyer and comes from its Seller, so the Buyer is the primary party. A purchase order runs the other way: it is addressed to the Seller, so the Seller is the primary party. The same reading gives the pair on other trade documents, whatever the two sides are called on them.
Not every document type works this way. An agreement between two equal sides has no sender and no recipient, and a form or report that records information rather than passing it between two parties names its own pair. Some document types name no parties at all.
Each feature gates a party, not a heading. Turning off Primary party data enrichment therefore changes the Seller block on a purchase order and the Buyer block on an invoice, so read which side a document is addressed to before expecting a particular block to change.
What a Party Without Enrichment Looks Like
The feature is checked every time a document is read, not when the document is processed. Turning it off takes effect on the next view of any document, however old, and turning it back on restores it. Nothing is reprocessed and no data is lost.
Where a party's enrichment is not enabled, on the review screen:
The Trading party matched / Trading party not matched selector disappears, along with its Add button, so no trading party can be attached there.
Every field the record had vouched for drops its Verified badge and shows where the value actually came from: usually Printed, sometimes AI Derived or Normalized by AI.
A value the record had overwritten reverts to what the document printed, and a value the record had cleared comes back.
The exported destination file follows the same rule, so the screen and the export always agree.
The other party on the same document is untouched. The screenshot at the top of this article shows a purchase order with only Secondary party data enrichment turned off: the Buyer has lost its selector while the Seller keeps everything.
What Turning a Feature Off Does Not Touch
A value a reviewer edited by hand keeps the reviewer's value and stays badged Edited.
A value produced by a transformation rule keeps the rule's value.
Supported Configurations and Options
Option | What it does | Values |
Primary party data enrichment | Enriches the document's primary party | Enabled or not enabled |
Secondary party data enrichment | Enriches the document's secondary party | Enabled or not enabled |
Other Technical Specifications
Each feature applies to the whole tenant. Neither can be narrowed to one organization or one document type.
Matching and enrichment still run when a document is processed, whatever the tenant has enabled. The check is made at the point the document is read, which is why switching a feature back on restores the values with nothing to reprocess and nothing to backfill.
The review screen and the destination output read the same answer, so the two cannot disagree about a document.
Notes
Turning a feature off hides that party's enriched values. It does not delete them, and it does not unassign a trading party already held against the document.
Neither feature depends on the other. A tenant can hold one, both or neither, and a document can show an enriched primary party beside a secondary party that is not enriched.
Known Limitations and Edge Cases
The feature does not reach the document list, the search bar or the Regions filter. All three match the values stored when the document was processed, so a document can still be listed and found by an enriched party name while the review screen and the export show the printed value.
A reviewer cannot attach a trading party where enrichment is not enabled. The selector is not shown, so the feature has to be enabled first.
A document type that names no parties is unaffected by either feature.