Invoice Exception Management demo
Blocked invoices released before late fees and supplier holds, every fix checked twice. 1:30
What the demo shows
Agents resolve three-way-match failures, price and quantity variances and blocked invoices
Blocked invoices sit on a pinboard by root cause (price drift, short receipt, missing receipt, unit mismatch, closed PO), each a chip sized by the money falling due, with the PO line, receipt and invoice side by side and every figure pinned to its source. Agents trace each cause to the event behind it, a resolver proposes one fix for every invoice that shares it, and a separate checker re-runs the three-way match before anything moves. The outreach agent sends the buyer or receiver the change ready to post; anything over tolerance is signed by a named approver.
Transcript
- Invoice Exception Management. Agents that clear blocked invoices by fixing their cause.
- Most teams see 14 to 22% of invoices blocked.
- Here, 137 wait. The board groups them by root cause, every figure pinned to its source.
- Fourteen Halvorsen invoices share one cause.
- Each line is 3.2% over.
- The cause finder traced it to a contract price rise.
- the resolver proposes amending the order.
- Then the checker, a second agent, rematches on its own, 14 of 14.
- Six are overdue and Halvorsen stops deliveries on Monday, so a person decides.
- Priya, the AP lead, signs with a reason code.
- The buyer posts the change, the checker rematches, and all 14 are released.
- Every step is cited, signed, and logged for the auditor.
- $271,000 released before the supplier hold, and a late charge's stop.
- Built on Botminds: agents, data, screens, and governance on one platform.
Transcribed from the film’s narration. Captions are on the player.