Process Hub · Build by process type
Build a Document Chain process
Match business document numbers across ordered record steps without editing the source documents.
On this page
Before you start
- Deploy the source processes/lookups. Identify unique business document-number fields and matching keys. Agree one anchor step and who may resolve incomplete/ambiguous links.
Example structure
On smaller screens, scroll the table sideways to see all columns.
| Setting | How to use it |
|---|---|
| Purchase Order (anchor) | Business number PO-1001; supplier order. |
| Goods Receipt | Business number GR-2001; its po_reference equals the earlier purchase-order number. |
| Supplier Invoice | Business number INV-3001; its receipt_reference equals the goods-receipt number. |
Follow these steps
- Open Builder → New process → Document Chain. Configure Chain identity and its prefix, then add the ordered Record steps.
- Choose one anchor step. For each step select its supported source: a deployed Process, deployed Lookup or Manual entry. Select its Document-number identity field.
- Choose loading mode per step: Manual, Suggest and confirm or Automatic. Configure manual fields only in a mode that supports user confirmation/manual entry.
- Connect adjacent ordered steps with the required equality matches, using an earlier step’s field and the next step’s corresponding key. Review exclusive/shared cardinality rules.
- Set which steps are required for completion and any authorised override/reason or archive-after-match behaviour. Keep shared invoice/payment relationships distinct from financial allocation logic.
- Save, validate, publish and deploy. Grant access to the chain and its permitted source records. Create a chain from a known anchor business number and test exact matching.
- Test no match, several matches, a shared relationship and a changed source. Review suggestions/refresh and stale evidence before confirming completion; allow time for asynchronous matching workers.
Try a complete business example
What you should see
The chain presents auditable linked document snapshots using the intended business identities and matching rules.
If something goes wrong
The source GUID gives no match
Use the configured business document number, not an internal record/source GUID.
A match did not appear instantly
Automatic matching/suggestions can run asynchronously. Inspect source values, worker state and supported refresh/reconciliation; do not assume all historical records are scanned on deployment.
The chain was expected to update invoices or allocate balances
Document Chain is non-owning and read-only over source documents. Shared links do not calculate account/payment allocations.