Exception routing: how invoices find the wrong person
Exception routing is the process of assigning a stalled invoice to the person or system that can actually resolve it, based on what caused the mismatch rather than which department happens to own the invoice. Most ERP and procure-to-pay systems route by rule: department, cost center, dollar threshold. None of those rules ask who holds the missing fact, which is why an invoice can bounce through two or three inboxes before it lands with someone who can act on it.
Static routing rules ignore who holds the missing fact
A rule that sends every invoice over $5,000 to a senior approver assumes the senior approver can resolve it. Often they can't. A price variance needs someone who can see the signed pricing agreement. A quantity mismatch needs someone near the receiving dock. Dollar-threshold and department-based rules were built for approval workflows. Exception resolution was never the design target, and AP teams inherited them anyway because building a second routing layer was never worth the effort by hand.
A price variance and a missing receipt need different people
Treat these as the same problem and the routing rule sends both to whoever is next in the queue. The buyer who negotiated the contract can confirm a price variance in minutes but has no visibility into whether goods arrived. The warehouse team can confirm receipt in minutes but has never seen the contract. Route either exception to the wrong side and the invoice sits until someone forwards it, which is the moment "days to resolve" starts climbing.
Each hop adds delay without adding an answer
Every forward is a wait: for the next person to open their inbox, understand why the invoice landed there, and decide whether they're the right owner. None of that time resolves anything. A stalled invoice that hops through three people before reaching the right one has spent most of its cycle time waiting to be forwarded. The eventual fix might take five minutes once it arrives at the right desk.
Route by the fact that's missing
The fix is to route on what's actually missing: a price question goes to whoever can see the contract, a quantity question goes to whoever can see the receiving log, a coding question goes to whoever owns that cost center. An agent that already has access to the ERP, the contract repository, and the receiving system can identify which fact is missing and route accordingly, or in many cases retrieve the fact itself and skip the routing step entirely. That's the difference between autonomous exception resolution and a smarter ticketing system.
Fragment's agents read across a company's ERP, supplier portals, and inboxes to identify what an exception actually needs before it ever reaches a person, cutting out the hops that add delay without adding an answer. Explore Fragment's workflows or book a demo to see routing and resolution in one step.