SAP Intelligent Spend Group bundles Ariba, Concur, and Fieldglass, but each runs on a different metric. Read them separately to see where the cost really sits before the next renewal.
SAP Intelligent Spend Group bundles Ariba, Concur, and Fieldglass under one marketing umbrella, but each product is licensed on a different metric. Treating them as one contract is the first mistake. This guide decodes the three metrics and the levers that cut each renewal.
SAP markets spend management as one connected story. The licensing reality is three different engines with three different cost drivers.
The buyer side job is to read each metric on its own terms, then decide whether to negotiate them together or apart.
The group is SAP's source to pay and travel portfolio. Three products carry most of the spend and most of the license cost.
Ariba covers sourcing, procurement, and the supplier network. It is the largest line in most Intelligent Spend contracts and the one most tied to transaction volume.
Concur covers travel, expense, and invoice. It is usually the most user driven product in the group and the easiest to over license through drift.
Fieldglass covers contingent labor and services procurement. It scales with external workforce spend, which can grow quickly in services heavy organizations.
Ariba pricing is built around the value of spend flowing through the platform, not the number of internal users.
The core fee scales with the procurement spend transacted through SAP Ariba. As spend grows, so does the fee, unless a tier or cap is negotiated.
The Ariba Network adds supplier side fees and buyer transaction fees. These can surprise buyers who modeled only the subscription line.
Intelligent Spend Group metrics at a glance
| Product | Primary metric | Scales with | Main lever |
|---|---|---|---|
| Ariba | Percentage of spend | Procurement volume | Negotiated cap or tier |
| Concur | Transactions or users | Reports or active users | User cleanup, module fit |
| Fieldglass | Percentage of spend | External workforce spend | Scope and cap |
Sourcing, contracts, and procurement modules are priced separately. Buy the modules you use, not the full suite, unless the bundle genuinely earns its price.
Concur and Fieldglass sit at opposite ends of the metric spectrum, users versus spend.
Concur is priced on expense transactions or active users, depending on the module. The SAP Concur contract often carries inflated user counts from years of drift.
Fieldglass charges a percentage of the external workforce and services spend managed through SAP Fieldglass. The fee follows contingent labor volume, not headcount.
The common advice is to buy the Intelligent Spend bundle because the integrated suite is simpler and the bundle discount looks attractive. We disagree. In most of the renewals we have run, the bundle handed SAP a single lever and hid spend based fees that grew faster than the value delivered. The buyer side move is to license each product on its own metric, cap the percentage of spend lines, clean Concur users to real usage, and decide bundle versus separate on measured cost, not on the simplicity story. A tidy suite is not the same as a cheap one.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The bundle is sold as simplicity. At renewal it becomes a single lever in SAP's hands. Keep the metrics separate and keep your leverage.
Five levers move the cost across the three products.
Negotiate a cap or a declining rate on Ariba and Fieldglass spend tiers so volume growth does not reprice the deal.
Remove dormant and duplicate accounts before renewal. Right size active users to real activity.
License only the modules in use. A suite discount on capability you never deploy is not a saving.
Include Ariba Network supplier and transaction fees in the total cost view, not just the subscription.
Align renewal dates with the wider SAP estate only when timing strengthens your hand, not when it forces an early renewal.
Approach it product by product, then decide on bundling with the full picture in hand.
Pull spend, transactions, and active users for each product. The metric data is your negotiation position.
Compare your percentage of spend and per user rates against current market levels before you accept a renewal quote.
White Paper · SAP
The SAP contract. The buyer side fundamentals
Nine buyer side fundamentals for an SAP contract: discount baselines, indirect access caps, price protection, audit clauses, and clean exit terms. Read it free.
The SAP Intelligent Spend Group is SAP's spend management portfolio, built mainly from Ariba, Concur, and Fieldglass. It covers procurement, travel and expense, and external workforce management. Each product is licensed on its own metric, so the group is not a single contract.
SAP Ariba is licensed mainly on a percentage of spend transacted through the platform, plus the Ariba Network supplier fees. Procurement modules can also be priced per user or per supplier relationship, so the metric depends on the specific Ariba product.
SAP Concur is licensed primarily on transaction volume, usually expense reports processed, or on a per active user basis. Modules such as Travel, Expense, and Invoice are priced separately, and bundling them is a common negotiation lever.
SAP Fieldglass is licensed on a percentage of the contingent workforce and services spend managed through the platform. The fee scales with the volume of external labor and services transactions, not with the number of internal users.
Yes. Ariba, Concur, and Fieldglass are sold and licensed independently. SAP offers bundles, but there is no requirement to buy the full suite, and buying piecemeal can be cheaper if only one capability is needed.
Spend based metrics that scale faster than value. As transaction volume grows, percentage of spend fees can rise sharply without a matching increase in benefit, so uncapped spend tiers are the main trap.
Right size active users to real usage, remove dormant accounts, and benchmark the per transaction or per user rate against current market levels. Concur renewals often carry inflated user counts that have drifted over years.
Often yes. Aligning Ariba, Concur, and Fieldglass renewal dates with the wider SAP agreement creates a larger negotiation and more room to trade, though it is only worth doing if the timing does not force an early, weak renewal.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next SAP renewal cycle.
Intelligent Spend is three engines, not one. Read each metric on its own terms and the bundle stops being a black box.
