Tail Spend vs Maverick Spend: The Difference, and Why the Overlap Is Where the Money Goes

Tail spend is defined by size: the long tail of small, fragmented purchases that make up roughly 80 percent of transactions and about 20 percent of total spend. Maverick spend is defined by process: any purchase made outside the agreed channel, at any value. A 90 dollar subscription bought through the approved catalog is tail spend and not maverick. A 400,000 dollar contract signed without procurement is maverick spend and not tail spend. Most of the money organizations actually lose sits in the overlap, and it is the hardest part to find because nothing in your purchasing system contains a record of a purchase nobody submitted.

These two terms get used as synonyms in vendor material, and the confusion is expensive. They call for different tools, produce different savings cases, and fail in different ways. A program aimed at the wrong one reports a clean result on a fraction of the money.

What is the difference between tail spend and maverick spend?

Tail spend measures the shape of your purchasing. Maverick spend measures compliance with your own rules. They are independent axes, which is why a purchase can be one, both, or neither.

There is no universal threshold for either. The 80/20 framing is a convention, and real organizations report anything from 70/30 to 90/10. The most workable definition of tail spend is any vendor procurement is not actively managing, because that is a population you can list. The most workable definition of maverick spend is any payment with no corresponding requisition, because that is a query you can run.

What is maverick spend in procurement?

Maverick spend is buying that bypasses the agreed process: no requisition, no approved supplier, no negotiated price, often no contract. It happens for mundane reasons rather than dishonest ones. The approved supplier could not deliver in time. The catalog did not have the item. The requester did not know a process existed. Somebody needed a tool for a client demo on Thursday and expensed it.

The reason it matters more than the dollar value suggests is that a maverick purchase carries none of the protections the process exists to provide. Nobody checked the supplier's insurance, nobody read the terms, nobody noticed that another department already has a contract with the same vendor at a better rate, and nobody recorded a renewal date. The purchase price is the smallest part of what it costs.

Why the overlap is the part that matters

Draw the two definitions as a grid and four quadrants appear. Three of them are manageable with tools you probably already have.

Large and compliant is your strategic spend, and it is already governed. Large and maverick is rare, alarming, and gets found quickly because a payment that size triggers questions. Small and compliant is the classic tail: visible in the purchasing system, sourced badly or not at all, and addressable through catalogs, consolidation, and competitive sourcing.

Small and maverick is the quadrant that defeats most programs. Each individual purchase is too small to trigger any review, and none of them appear in the purchasing system at all, so a spend analysis run on procurement data reports that this quadrant is empty. It is not empty. At a software heavy company it is frequently the largest of the four by supplier count and it grows every month, because a recurring charge that nobody approved also has nobody scheduled to cancel it.

What does small maverick spend actually look like?

It is almost always recurring, and that is what makes it durable. A one-time 300 dollar purchase is over. A 60 dollar monthly subscription bought on a card in 2023 is still running, has cost 2,160 dollars, and will keep going until someone reads the card statement line by line.

The pattern repeats across categories. Three teams paying separately for the same design tool because each signed up independently. A project management workspace still billing for 40 seats after the project ended with 6 people. An API plan bought for a prototype that shipped two years ago. A monitoring tool nobody has logged into since the engineer who set it up left. A cloud account opened for a proof of concept, still running two instances.

None of those pass a purchase order review because none of them ever reached one. They pass unnoticed through expense approval every month because a 60 dollar line is below every threshold anyone set.

How do you detect maverick spend?

Reconcile from the payment side, never the purchasing side. This is the single most important procedural point in this article: the purchasing system by construction does not contain the purchases you are looking for, so any analysis that starts there will conclude the problem is small.

The sequence that works:

1. Pull twelve months of accounts payable, corporate card, and bank transactions. Twelve months, because annual subscriptions renew once and a quarterly window misses them entirely.
2. Normalize supplier names. The same vendor will appear as several strings across payment processors, and unnormalized data understates supplier counts badly.
3. Join that list against your approved supplier list and your purchase order history. Everything with no match is a candidate.
4. Flag anything recurring. Same vendor, similar amount, regular interval. Recurring maverick spend is worth far more than one-off maverick spend because cancelling it saves every future period.
5. Attribute each line to a person and a cost center. Card transactions carry a cardholder. Software subscriptions carry a billing admin. Cloud accounts carry an owner.

Step five is the one teams skip and it is the one that produces action. A list of unmanaged vendors delivered to a CFO produces agreement that something should be done. The same list split by department, with each line named, produces cancellations within a week, because a department head now has to defend a specific charge rather than a total. Getting the split right is an allocation problem, and the same driver logic that applies to cost allocation software applies here: attribute from the record that created the charge rather than waiting for a tagging project nobody will finish.

Does tail spend include SaaS subscriptions?

At most technology companies it is the majority of the tail. Software fits every element of the definition: small individually, enormous in aggregate, spread across hundreds of suppliers, rarely competitively sourced, and usually bought by the team that will use it rather than by procurement.

It also has a property physical goods do not, which is that it renews itself. A stationery order stops when you stop ordering. A subscription continues until someone actively cancels it, and the cost of doing nothing is the entire contract value every year. That asymmetry is why software deserves separate treatment inside a tail spend program rather than being one category among many.

Which problem should you solve first?

Solve visibility first, regardless of which term describes your situation, because you cannot size either problem from the purchasing system alone. Run the payment side reconciliation above and you get both answers at once: the supplier count and value distribution tell you how big the tail is, and the unmatched lines tell you how much of it is maverick.

Then pick the intervention that matches what you found. If the tail is large but compliant, the answer is sourcing and consolidation, and the tail spend management providers that work at the requisition or at the supplier will reach it. If the tail is large and mostly maverick, controls and catalogs come first, because sourcing a category nobody buys through the approved channel just moves the paperwork. If the maverick portion is mostly software, a SaaS discovery layer finds it faster than any procurement project will be implemented.

One risk deserves naming separately. A long tail of one-off suppliers is also a long tail of vendors nobody vetted, which is why organizations that finally list their unmanaged suppliers usually discover the same gap on the compliance side and need a way to track certificates of insurance across hundreds of small vendors that were never onboarded properly. The purchasing gap and the compliance gap are the same list viewed from two angles.

How do you stop the tail from regrowing?

Every tail spend program produces a good first year and a disappointing second one, because the cleanup is a project and the regrowth is a process. Three controls do most of the work.

Make the compliant route faster than the maverick one. People bypass procurement because it is slow, not because they are hostile to it. A catalog that returns an approved answer in a minute beats a policy memo permanently.

Put a standing recurring-charge review in place. Monthly, automated, from payment data, with each new recurring vendor routed to a named owner for confirmation. New unapproved subscriptions then surface within one billing cycle instead of three years.

Publish the numbers by department. Showback is enough at first; departments argue with their own figures, correct the attribution, and cancel what they cannot defend. Move to chargeback only once the departments genuinely control the spending behind the number, and see showback vs chargeback for how that decision usually goes.

Costanalyst covers the software and cloud portion of this directly. It connects your cloud accounts and SaaS subscriptions read-only, surfaces the recurring charges nobody approved, and attributes them to teams and cost centers so the report arrives with a name attached. For the wider procurement tail, the guide to tail spend management providers and companies compares the ten options by where each one actually intercepts the spend, and SaaS spend management tools covers the software half in more depth.