Concur Renewal Negotiation: What Buyers Should Know
Expense platforms are priced against headcount or transaction volume, and both are usually estimated once and then inherited.
I spent years on the vendor side of enterprise software, and expense and travel platforms like Concur carry a specific characteristic at renewal: the commercial model tends to be tied to headcount, transaction volume, or report volume, and the numbers in the contract were often estimated at the original purchase and rolled forward at every renewal since.
Contracted volume against processed volume
Set at first purchase, rolled forward at every renewal since.
Where actual volume sits well inside the band, resetting it is a correction rather than a concession.
What typically shapes a renewal like this
Volume or headcount-based pricing where the contracted band rarely matches the real figure, modules for travel, invoice, and expense sold separately, and implementation depth that makes switching feel unrealistic, which reduces the pressure on the vendor to move on price.
Questions worth asking before your renewal
- What is our actual annual volume of expense reports or transactions, against the contracted band we are billed on
- How many employees actually submit expenses, versus total headcount we may be licensed against
- Which modules are contracted, and is each one being used by the function it was bought for
- Have travel patterns changed since the band was last set, and does the contract reflect that
- What happens commercially if our volume falls below the contracted minimum
Common levers buyers use
The strongest position usually comes from real volume data. Where actual usage sits well inside the contracted band, a reset to the correct band is a factual correction rather than a negotiation, and it is easier for an account team to approve than an unstructured discount.