Agentic AI for Accounts Payable: What's Real, What's Hype, What's Audit-Ready

This is moving faster than the controls around it

Someone on your team is using ChatGPT to draft vendor emails. Someone else is using Claude to explain a freight variance. Your shared services lead just sent you a deck about “agentic AP.” Three of your vendors just changed their homepage to say the same thing.

The question is not whether AI belongs in your AP function. It is already there. The question is whether any of it is defensible: in front of your auditor, in front of your audit committee, in front of the next duplicate payment your team finds in the wrong quarter.

That is what this session is about.

Who you'll hear from

55 minutes, no fluff

Three things, in 55 minutes

1. A clear-eyed view of what agentic AI actually does in AP today. Where ChatGPT, Claude, and the new wave of “agentic” AP tools genuinely help. Where they quietly fail. The gap between “94% confident” and “the auditor will sign off on it.” Stop reading vendor websites and start reading your own AP process.
2. Three workflows that show the difference, live. Non-PO invoice coding. 3-way match exceptions. Vendor statement reconciliation. The three workflows that consume the most AP labor in every enterprise we have seen, run end-to-end through Claude, governed by Kognitos. With the audit log on screen.
3. A framework your CFO will actually defend. A simple way to evaluate any agentic AI claim in your AP stack: what to ask in the RFP, what to demand in the demo, what to verify in the audit trail. Plus the leakage math for your own function, sized to your volume and exception rate.

Three things keeping AP leaders up at night

• The audit question you don't want to answer. “Walk me through how this invoice was coded, approved, and paid.” If the answer involves “the AI was 94% confident,” you have a problem. Probabilistic AI does not produce an audit trail. It produces a confidence score.
• The money already leaking out. Duplicate payments. Missed early-pay discounts. Non-PO invoices coded to the wrong cost center for three quarters before anyone noticed. Most AP teams are running on a 70% automated, 30% on-fire model, and the 30% is where the money actually goes.
• The team you cannot keep. Senior AP analysts are leaving for FP&A roles. The exception queue is what burns them out. Every cycle that ends in a Friday-night manual reconciliation is a retention risk you are not measuring.

If any of these are true, this hour will earn its slot on your calendar

• You sign off on financial statements and have started getting AI questions from your audit committee.
• Your AP team is already using ChatGPT or Claude informally and you have no governance around it.
• You have an OCR or AP automation tool that handles clean invoices and leaves the rest to your team.
• You are building an AP RFP and three vendors just told you they are “agentic.”
• You found a duplicate payment last quarter that should not have happened.
• Your senior AP people are leaving because of exception fatigue.

Job titles we built this for: CFOs, VPs of Finance, Controllers, AP Directors, Heads of Procure-to-Pay, Heads of Shared Services. Companies: 500–5,000 employees. Industries: manufacturing, logistics, healthcare, banking, retail, technology, CPG.

Every registrant gets a personalized scorecard

Generated from the registration questions, showing exposure across four areas:

• Duplicate payment risk, sized to your invoice volume.
• Non-PO coverage gap, where probabilistic AI most often fails.
• Exception aging, the labor cost hiding in your AP queue.
• Audit trail completeness, the question your auditor will ask next.

Request this during the webinar on chat with the speakers.