Coordinate extraction, matching, supplier communication, compliance, approval, and ERP posting across hours or days with the same run state and actor lineage.
An invoice exception is not one task. It is a chain of them, spread across a document store, an ERP, a supplier mailbox, and at least one approver with waits in between that are measured in hours or days, not seconds.
The hard part is not reading the invoice. It is holding the run together across those waits: knowing what was already matched, which supplier reply belongs to which exception, who approved what, and under whose authority the ERP was finally written to.
Orchestrate runs the whole exception as a single durable workflow. Extraction and matching agents do the reading and reconciliation, deterministic rules decide what counts as an exception and what may be auto-cleared, and the run pauses for a supplier reply or an approver without losing its place.
Every hop carries the delegated identity of the person the work is being done for, downscoped to what that step needs. The ERP posting happens under a traceable actor, not a shared service account.
Run state is durable, so a workflow waiting three days on a supplier is the same run when it resumes — not a new one stitched to the old by a ticket number.
Actor, action, decision, and execution lineage are retained end to end: which agent read which document, which rule fired, who approved, and what was written to the ERP.
A posted invoice, or a documented rejection, with a complete record of every extraction, rule, message, and approval that produced it — reviewable long after the run has closed.
.svg)