Who Should Own SaaS Procurement — IT or Finance?

SaaS procurement ownership is contested in most organisations. IT wants control for security and governance reasons. Finance wants visibility for budget management. Business units want autonomy to adopt tools without lengthy approval processes. The tension between these interests is the root cause of most shadow IT problems.

The Case for IT Ownership

IT understands the technical and security implications of every new tool. They can assess data handling practices, evaluate integration requirements, and ensure tools meet compliance standards before contracts are signed. Without IT in the loop, organisations routinely adopt tools that fail security reviews, can't integrate with existing systems, or create data residency problems.

The Case for Finance Ownership

Finance has the budget visibility to prevent duplicate purchasing, the commercial expertise to negotiate better terms, and the authority to enforce spend thresholds. Procurement teams in finance-led organisations tend to negotiate more aggressively and maintain better contract records.

The Right Model

The highest-performing organisations use a joint model: Finance owns the commercial process (budgeting, contract management, vendor negotiation) while IT owns the technical approval process (security review, integration assessment, compliance check). Requests flow through a single intake point — often a software request form — that routes to both teams simultaneously, reducing total approval time.

What Joint Ownership Requires

Joint ownership is more than an organisational decision — it requires shared infrastructure. Both teams need access to the same software inventory, the same utilisation data, and the same renewal calendar. When IT and Finance are working from different data sources, they can't have productive shared conversations about optimisation. A single SaaS management platform that both teams use as their system of record is the enabling technology for joint ownership.

Regular shared reviews are equally important. A monthly 30-minute meeting between the IT lead and Finance lead to review the renewal pipeline, discuss utilisation outliers, and align on upcoming decisions keeps the joint ownership functional rather than theoretical. The most common failure mode is the joint model existing on paper but not in practice — where each team does their own thing and the handoff only happens at procurement time.

The Role of Business Units

IT and Finance's joint ownership of the SaaS portfolio doesn't mean business units have no role. Business units are the primary source of software demand, and their engagement is essential for adoption reviews, renewal recommendations, and identifying consolidation opportunities. The right model gives business units a clear voice in the software decision process without giving them unilateral authority to purchase and contract without IT and Finance review.

Formalise business unit involvement through tool ownership: every software application has a named business owner who is accountable for usage and renewal decisions. IT and Finance are governance partners who provide data, analysis, and commercial expertise. The business owner makes the final call on whether to renew, downgrade, or cancel — but they make it with IT and Finance's input, not without it.

Shadow IT as a Governance Failure Indicator

High volumes of shadow IT are almost always a symptom of a broken IT-Finance relationship. When the official procurement process is slow, opaque, or dominated by a single function's agenda, employees find alternatives. When IT and Finance collaborate effectively and the process is fast and transparent, the motivation to go around it largely disappears. Use shadow IT volume as a lagging indicator of procurement process health — a rising shadow IT discovery rate is a signal to review the governance model, not just tighten the controls.