Trigger: An invoice in SAP Ariba Invoice Management fails the three-way match (PO, receipt, invoice) or hits a validation rule.
Context Pulled: The agent retrieves the invoice header and line items, the related PO (including item descriptions, quantities, prices), goods receipt notes, and any prior correspondence with the supplier from the Ariba Network.
Agent Action:
- Classifies the exception type (price mismatch, quantity discrepancy, tax error, missing receipt).
- For quantity/price mismatches, it cross-references the PO amendment history and checks for approved price variances.
- For missing receipts, it queries the connected ERP (e.g., S/4HANA) for pending GRs or checks shipment tracking via carrier API.
- Drafts a resolution:
- Auto-correct: If variance is within a pre-defined tolerance (e.g., 2% on price), it logs the justification and updates the invoice line.
- Route for Approval: If variance exceeds tolerance, it generates a summary for the PO owner/approver with a recommendation to approve or reject.
- Supplier Query: If data is missing, it drafts a clarification request to the supplier via the Ariba Network.
System Update: Based on the agent's decision and any human approval, the agent calls the Ariba Invoice API to update the invoice status (APPROVED, ON_HOLD), adjust line items, or post a comment to the audit trail.
Human Review Point: All exceptions flagged for approval are sent to a designated workflow inbox in Ariba or Microsoft Teams, where an AP clerk can review the agent's summary and click "Approve" or "Reject."