Step 1: Classify the exception
Identify the mismatch, amount, owner, due date, and permitted resolution path.
Reconcile invoice and purchase-order records, apply policy, and send only true exceptions for approval.
Give accounts payable one place to compare the invoice, purchase order, receipt, approval history, and vendor context. Routine mismatches move forward; material conflicts arrive with the evidence a reviewer needs. The result is a resolved exception or an evidence-complete escalation, ready for the accountable team to review and move forward. By keeping source-backed facts, open questions, and ownership together, the team can make the next decision without rebuilding context by hand.
Compare invoice, order, receipt, contract, and approval records side by side.
Resolve routine variance within policy and preserve separation of duties.
Give approvers the mismatch, rule, source records, and proposed next action.
Prepared output: Invoice 4817 · three-way match
Source state: Current approved records retained
Quantity and receipt match; a pricing variance requires procurement approval.
Identify the mismatch, amount, owner, due date, and permitted resolution path.
Compare invoice, order, receipt, contract, vendor, and payment state.
Determine whether the case is routine or needs additional authority.
Update approved fields or request the missing information.
Record the rule, source facts, approval, action, and final state.
Put this agent to work