Process Hub · Business scenarios to work through
Business example: match a purchase order, receipt and invoice
Trace one supplier purchase through linked business document numbers and identify an unmatched invoice.
On this page
Before you start
- Use a training profile and synthetic data. NovaNest Living is a fictional home-goods business; names, records and amounts below are examples, not installed customer configuration.
- Ask your administrator to prepare the approved runtime connection and member roles. Use the linked build guide before this walkthrough; only authorised people should publish/deploy.
- Prepare deployed Purchase Order, Goods Receipt and Supplier Invoice demo processes/lookups with the business numbers and matching references below.
Known source values
On smaller screens, scroll the table sideways to see all columns.
| Document | Business number | Reference to preceding step |
|---|---|---|
| Purchase Order | PO-1001 | Anchor |
| Goods Receipt | GR-2001 | po_reference = PO-1001 |
| Supplier Invoice | INV-3001 | receipt_reference = GR-2001 |
Follow these steps
- Create a Document Chain named Supplier Document Check. Use Purchase Order as the anchor and configure its business number as identity.
- Add Goods Receipt and Supplier Invoice in order. Set their document-number fields and match PO number → receipt po_reference, then receipt number → invoice receipt_reference.
- Choose Suggest and confirm for a training review flow, or supported Automatic loading if a worker-backed exact-match flow is intended. Set required completion steps and review cardinality.
- Save, publish and deploy. Grant the reviewer the intended chain/source access. Create source records PO-1001, GR-2001 referencing PO-1001 and INV-3001 referencing GR-2001.
- Open/create the chain from anchor PO-1001. Review suggestions/matched values and confirm the correct documents according to the configured mode.
- Verify the required steps are satisfied and complete the chain using the permitted controls. Inspect the snapshot/history without changing source documents through the chain.
- Create a separate invoice with an incorrect receipt reference and run a second test. Confirm it remains unmatched; correct the source reference through its source process and use the supported refresh/review flow.
- Test an ambiguous duplicate business number and a changed source snapshot. Resolve the identity/source issue before confirming completion or using an authorised override with a reason.
Useful negative test
Change the invoice reference to GR-9999 in a separate training record. It should not match GR-2001 merely because the supplier/amount looks similar. This example proves relationship matching, not a financial three-way amount reconciliation.
What you should see
The reviewer can trace exact related documents and recognise missing, ambiguous or stale matches.
If something goes wrong
The invoice does not match although its own number is correct
Check the join reference to the preceding receipt, not only the invoice’s identity. Exact matching values must correspond.
A completed chain was expected to pay the invoice
The chain links evidence. It does not post accounting transactions, calculate payment allocations or pay a supplier.
Automatic matching is slow
Inspect worker status and source values; matching/suggestions may be asynchronous. Do not create duplicate source documents to force a result.