Extracts invoice fields, matches them against the purchase order, routes for approval by value, and releases payment. VisML VisML 2026-08-04T09:00:00Z Apache-2.0 3 enterprise finance approval

A GUARD, not a decision. If there is no PO number the node is SKIPPED — a terminal SUCCESSFUL state — and its control successors still run. A decision node would instead have to route somewhere.

Approval authority by amount. Cases in document order, first true wins — so the thresholds read top-down like the policy they encode. Reached only for a PO-matched invoice within 2% variance and under the manager threshold.

High-value invoices need a second pair of eyes and a longer window, because the approver is more likely to be travelling.

joinPolicy="any" — exactly one approval path is ever taken, so the barrier releases on the first and cancels nothing real. Not idempotent: posting the same invoice twice is a double entry. A runtime MUST NOT auto-retry, which is why no retry policy is declared here even though every other node has one.

Compensation for a posted entry when payment later fails. A reversal, not a delete — the original entry stays in the audit trail. Note that `pay` deliberately has NO outgoing error edge. An error edge would make the failure HANDLED (§5.8), the workflow would continue, and compensation would never run — so the rollback this node exists for would be silently skipped. Letting the failure propagate is what triggers unwinding.