The Payments Podcast

The episode touches on legitimate P2P topics (invoice cycle times, straight-through processing, cost-per-invoice metrics, AI applications) but much of the value is delivered through high-level frameworks and general principles rather than actionable specifics. KO repeats key metrics throughout without deeply exploring how to achieve them. The AI segment offers some practical examples (PO matching accuracy, GL account coding, support case deflection) but is diluted by broad statements about hype.

“invoice cycle time, how do I get from, say, thirty days, which is present in most manual processes down to a best in class that's sub five days”

“manual processes are oftentimes, let's call it 15 to 25 dollars in cost”

The core thesis - that payments should be integrated into P2P strategy from the start rather than treated as an end-step - is sound but not novel. The ADKAR change management framework is borrowed from Prosci and is standard organizational consulting. The AI discussion rehashes familiar copilot vs. autopilot progressions and the data-as-fuel narrative without introducing genuinely fresh perspectives or contrarian thinking.

“If payments aren't deliberately thought of from day one as part of your overall supply chain strategy, oftentimes less mature organizations, it simply looked at as well, it's something finance needs to take care of at the end of the process”

“Awareness, Knowledge, Desire, Ability, Reinforcement”

KO brings 30 years of experience and held roles across supply chain, procurement, and payments at scale (25 years at a major company, now CCO at PairSoft). This is a legitimate practitioner with domain depth. However, the role is also at a vendor with direct commercial interest in the outcomes discussed, which introduces potential bias. The seniority is genuine but the independence to challenge assumptions is compromised by affiliation.

“I've worked in just three companies”

“I spent the better part of twenty-five years at Jagger across 10 different roles”

KO provides some concrete numbers (cost per invoice $2-5 vs. $15-60, 70-90% accuracy on PO matching, 5-7 payment platforms per customer, 65% of searches with AI) but rarely ties these to named companies, customer examples, or deeper case data. Statements like 'I've seen customers deliver less than a day' and 'nine failed projects for every successful one' lack attribution or supporting detail. The episode leans heavily on generalities.

“manual processes are oftentimes, let's call it 15 to 25 dollars in cost. And I expect you, I've seen some as abysmally high as 50 to 60 dollars per invoice”

“I've seen nine failed projects for every successful project”

Paul asks competent open-ended questions (e.g., 'what's misunderstood about P2P,' 'where should finance leaders balance priorities'), but rarely follows up sharply or challenges KO's claims. The interview lacks productive tension; KO pivots smoothly without deep pushback. The setup is professional but the dialogue reads more like a structured vendor conversation than investigative inquiry. Paul accepts frameworks and claims at face value.

“From your perspective, what's still most misunderstood about P2P and finance organizations today?”

“I would love to get your point of view on payments and the need to be designed earlier in the pre procure to pay process”