Procurement said yes. Why did finance say no?

Quick answer: Finance says no because procurement usually arrives with a technology pitch, not a budget case. Finance needs three things before it releases money: a named owner for the outcome, a before-and-after it can independently verify, and a payback period measured in months, not years. Without those three, the deal does not die. It just stops moving.

On this page: Two different conversations · What finance actually needs to see · Why procurement cannot supply it alone · FAQ

Two different conversations

Procurement gets excited about a data-quality or classification project for reasons that make sense to procurement. The spend cube finally reconciles. Category management stops being guesswork. The team stops losing a day a month to a spreadsheet nobody else understands. All of that is real, and none of it moves finance.

This is not a new problem. Forrester's State of Business Buying research puts a number on it: 86% of B2B purchases stall somewhere in the cycle, and the leading cause is not the vendor or the price. It is the buyer's own internal structure. The average purchase now touches 13 people across two or more departments, and Gartner puts the typical buying group for a complex purchase at 6 to 10 stakeholders, rising to 11 to 20 for larger deals. Somewhere in that group sits someone whose job is to say no by default, and that person was not in the room when procurement got excited.

Finance is not blocking the deal because the data problem is not real. Finance is blocking it because nobody has answered the finance question yet, and procurement has been busy answering a different one.

What finance actually needs to see

Three things, roughly in this order.

A named owner for the outcome. Finance does not fund "better data" as an abstraction. It funds a specific person being accountable for a specific number moving. If nobody in the room can say who owns the outcome after the project ends, finance has no one to hold to it, and no reason to release money against it. This is the practical version of a stance worth stating plainly: most organisations do not have a data quality problem so much as an ownership problem. Data degrades quietly because it belongs to everyone and therefore to no one, and a business case that cannot name an owner is really asking finance to fund the same gap that caused the mess in the first place.

A before-and-after finance can check itself. Not a vendor's case study from a different industry. A baseline pulled from the buyer's own spend or asset data, and a projection of what changes if that baseline is cleaned and classified, stated in terms finance already tracks, not in terms of rows processed or records deduplicated. A payback period under twelve months is generally an easy approval. Under six months is a strong one. Above eighteen, most finance teams will ask the requester to come back next quarter, which in practice means the deal is dead.

A cost of doing nothing that finance recognises. Procurement's version of "doing nothing" is continued frustration. Finance's version is a number: spend that cannot be classified cannot be forecast, cannot be benchmarked against contract terms, and cannot be defended in an audit or a board pack. That gap does not show up as a line item, which is exactly why it survives budget cycles untouched. Naming it in finance's own language is what turns "nice to have" into "line item."

None of this is a cost-savings pitch, and it should not be dressed up as one. Finance has heard the savings pitch from every vendor this year. What finance has not been given, in most of these conversations, is a reason to trust the number it is currently working from. That is the actual ask: not "this will save you money" but "this is why the number in front of you might already be wrong."

Why procurement cannot supply it alone

This is not a criticism of procurement. Procurement is usually the one that lives closest to the pain and therefore the first to see the value. But procurement rarely has the standing, on its own, to certify a before-and-after to finance, or to name an owner who spans procurement, IT, and operations. That requires someone who can speak in both directions: the practical detail of the data problem, and the financial framing finance runs on.

This is exactly the gap outbound sales conversations run into. A procurement manager or data analyst gets genuinely convinced, becomes the internal champion, and then has to carry the case to a decision-maker who was never in the original conversation and has no reason yet to trust the number being presented. Multi-threaded deals close at roughly six times the rate of single-threaded ones, and the reason is not that more people means more pressure. It is that the champion alone usually cannot answer the questions the next person in the chain is going to ask.

The fix is not a better slide. It is arriving with the three things above already assembled, so the champion is not asking finance to trust their word. They are handing finance something finance can check on its own terms.

In four to six weeks, Pearstop turns a company's own unclassified spend data into a categorised, audit-ready before-and-after, for procurement champions in hard FM, construction, and manufacturing who need something finance can check rather than a claim to repeat on their behalf.

Frequently asked questions

Why does finance reject a procurement project that procurement already approved?

Finance is not rejecting the problem. It is rejecting the case as presented, usually because there is no named owner for the outcome, no independently checkable before-and-after, and no payback period stated in finance's own terms. Procurement approval reflects operational value; finance approval requires a financial case built separately from it.

What financial information does a CFO need to approve a data quality project?

A CFO typically needs a baseline drawn from the company's own data, a quantified before-and-after stated in terms finance already tracks such as spend visibility or forecast accuracy, and a payback period. Under twelve months is generally approvable, under six months is considered strong, and anything measured in years usually gets deferred rather than declined outright.

How long should a data quality business case take to pay back?

There is no fixed rule, but the pattern across software and data initiatives is consistent: a payback period under twelve months is usually straightforward to approve, and under six months is considered a strong case. Business cases that only show payback in years tend not to get an outright no, they simply stop being prioritised against faster-paying alternatives.

Who should own a data quality initiative inside a company?

Ownership should sit with a named individual accountable for the outcome after the project ends, not with a department. Most data quality failures happen because the data sits between procurement, finance, IT, and operations, with no single person accountable for it end to end, which is also why business cases that cannot name an owner struggle to get funded.

How does Pearstop help procurement teams get finance sign-off?

Pearstop builds a categorised, audit-ready before-and-after directly from a company's own procurement and asset data inside a scoped pilot, giving an internal champion a checkable baseline to bring to finance rather than a vendor claim to repeat on their behalf. This is aimed at hard FM, construction, manufacturing, and infrastructure teams carrying the case internally.

Why do B2B purchases stall even when the internal champion is convinced?

Research from Forrester finds 86% of B2B purchases stall at some point, most often because of the buyer's own internal structure rather than vendor performance or price. With an average of 13 people involved across two or more departments, a convinced champion is rarely enough on its own. The case has to survive contact with stakeholders who were never part of the original conversation.

Neharika Kishore

Content & Visibility, Pearstop

Neha works on content and visibility at Pearstop. She writes articles on procurement data quality for facilities management, construction and infrastructure teams, and supports The Data Edge podcast. She also runs outreach to procurement and finance leaders, which keeps her writing close to the problems those teams are actually raising.

LinkedIn →