The Treasury Update Podcast

The episode delivers concrete regulatory requirements and implementation guidance that a treasury practitioner would genuinely need, such as company ID specifications, risk assessment components, and the proportionality principle. However, it relies heavily on explanation of compliance mechanics rather than novel insights into *why* these rules matter or how to operationalize them effectively, and includes filler moments ('this is a good topic', throat-clearing transitions).

“You have to monitor your ACH activity for unauthorized returns and authorized under false pretenses items”

“Your fraud risk assessment has to be specific to your organization. It has to identify where the ACH fraud risk is most likely to happen, by payment type”

The content faithfully explains published regulatory requirements but offers minimal original thinking or contrarian perspective. Craig does articulate the proportionality principle clearly, but the overall framing - compliance rules, checklists, risk frameworks - follows standard regulatory podcast templates without fresh angles or unexpected insights.

“Just like card had PCI DSS about 20 years ago to protect card information, uh, that expanded to Swift messaging with Swift csp”

“the treasurer is the superintendent of payments, not doing everything, but making sure everything happens”

Craig Jeffrey is identified as managing partner of Strategic Treasurer, suggesting operational and advisory experience in treasury compliance. He speaks with authority about implementation and demonstrates practical knowledge of how rules apply across organization sizes and payment types. However, the transcript provides limited evidence of his direct operational experience running a treasury function at scale.

“I'm Craig Jeffrey, our managing partner”

“If someone has extremely low volume, uh, maybe has limits set on things, while their, their elements of risk management might be a little bit more manual, a little simpler, uh, someone who's doing, let's say an insurance company is doing 10, uh, million ach is a month, they're going to have a lot more automation”

The episode names specific rules (company ID, risk-based fraud monitoring), references a concrete deadline (June 22nd), and provides threshold guidance (6 million ACH transactions annually). However, it lacks named company examples, actual penalty amounts, detailed case studies, or quantified impacts of non-compliance. The guidance is prescriptive but largely abstract in application.

“June 22nd where you have to have the, your risk based framework”

“sending things without that, you're not in compliance. There's, you know, the potential for all the penalties”

Lee asks clarifying follow-up questions ('Who do these rules apply to and why is that important?', 'can you talk a little bit about the principle of appropriate to risk') and invites Craig to explain practical implications. However, questions tend to be surface-level invitations to explain rather than challenging or probing deeper; there is no productive disagreement or pressure testing of claims, and some transitions feel scripted.

“Okay, a little bit more specifics. Who do these rules apply to and why is that important?”

“can you talk a little bit about the principle of appropriate to risk and what does that mean?”