When a CFO asks IT to "deploy AI for payables automation," the request lands in a department that is structurally not configured to deliver it. This is not an IT failure. It is a category error in how the work was assigned.
Four structural mismatches:
- IT teams measure uptime; AI deployments require judgment. IT is graded on whether systems are available. AI is graded on whether the system's outputs match the operational reality of the business. The first is a network problem; the second is a finance problem. They share almost no skills and no metrics.
- IT teams own infrastructure; AI deployments require business specification. Wiring a language model into an ERP is the easy half. The hard half is deciding which exceptions auto-resolve below $500, which payors route to which approval chain, what the confidence threshold should be for a sales tax classification. None of that is IT's domain. None of it can be done without finance, operations, and compliance writing the specification.
- IT teams ship in code releases; AI deployments require operational handover. A new ERP module ships when it passes UAT. An AI deployment ships when finance, audit, and operations have all signed off on the confidence framework, the exception flow, and the audit trail. Those signoffs are not in IT's mandate. They are not even in IT's vocabulary.
- IT teams maintain stable systems; AI deployments require ongoing recalibration. Every quarter, the confidence threshold drifts, the operations rules evolve, and new edge cases surface. The system needs a cross-functional review that IT cannot run alone.
In one engagement, a long-standing monthly relationship ended because the client had routed all AI scope through their internal IT director. Nine months in, IT had built three integrations, none of which the finance team could sign off on, because nobody had translated the operational logic into a specification. The work was technically excellent and operationally useless.
The fix is not to take the work away from IT. IT has an essential role — the infrastructure layer, the security review, the production deployment, the change management process. The fix is to add the missing roles: the translator from operations, the framework owner from finance, the auditor-aware compliance review.
If your CFO is asking IT to ship AI without those other roles named, the deployment is being scoped to fail. The right next conversation is not "how is IT going to build it." It is "who owns each of the four roles, and is the translator inside or outside the company."
Filed under
