How to Automate Without Mapping Every Step First
A new hire gets a short briefing, a mentor and a few days alongside a colleague. Most AI gets a commissioned process discovery project, months of log mining, a map, and a committee debating whether the map is accurate.
Binny Gill and Rushil Khurana make the case that process discovery solved a problem that no longer applies: automations that do not break on exceptions do not need it. Roughly half the session is live. The AI reads the connected ERP, drafts an accounts payable four-way match, asks a question only where a necessary detail is unresolved, and turns each resolved exception into a rule that runs on its own.
See how Kognitos works for you.
Speakers
More Webinars
Session FAQ
Wednesday, October 21, 2026, at 10 AM PT. The recording runs 56 minutes, and the full session is on this page.
The full session is embedded at the top of this page and is also published on the Kognitos YouTube channel. No registration is required.
Binny Gill, Founder and CEO of Kognitos, and Rushil Khurana, Head of Product at Kognitos.
An accounts payable four-way match for raw material supplier invoices, drafted from the connected ERP. The AI asks a question only where a necessary detail is unresolved. Exceptions then arrive, get resolved, and become rules that run on their own.
No. The approach starts with a defined goal, appropriate system access, and a person to ask. New rules are reviewed and approved by a human before reuse.
At 46:00 the test run completes a four-way match end to end and catches a real defect: an invoiced quantity of “120 PC” was split into a number and a unit, which SAP rejected with a 400 error. Watching a system find and fix that is more persuasive than a slide.
Automation CoE leads, controllers, AP managers, and anyone facing a process discovery project before their automation program can start.
00:00 Welcome; 03:00 We’re hiring AI the wrong way; 05:00 Why mapping takes months, and why the map is stale on arrival; 10:00 Why process discovery was needed: RPA breaks, early LLMs invent; 15:00 The minimum sufficient assignment; 20:00 Quill reads everything on day one. Compile once, execute many times.; 25:00 Live: building an AP four-way match blueprint; 30:00 Learning through exceptions; 35:00 Live: the exception queue, and asking the right question; 40:00 Live: turning a resolution into a rule; 46:00 Live: the full run, and a real bug caught in the process; 51:00 Stop mapping, start onboarding; 54:00 Questions.