What Is the SAP Intelligent Spend Group?
The Intelligent Spend Group (ISG) is SAP's umbrella brand for four cloud-based spend management applications it acquired over the course of a decade: SAP Ariba (indirect and direct procurement, sourcing, contract management), SAP Concur (travel, expense, and invoice management), SAP Fieldglass (contingent workforce and services procurement), and the SAP Business Network (the transaction network that connects buyers and suppliers). SAP began marketing these four applications as a unified suite around 2020, introducing per-employee-per-month bundle pricing as an alternative to individual module subscriptions.
The commercial logic is straightforward: SAP wants to expand wallet share by bundling all spend categories into a single enterprise agreement. For buyers, the promise is simplicity — one contract, one renewal date, one integrated data model. The reality is more complicated. Each pillar retains its own pricing architecture, its own professional services ecosystem, and its own contract mechanics. Signing an ISG enterprise agreement does not automatically entitle you to everything; it entitles you to what you negotiate, and SAP's default ISG contract skews heavily toward SAP's interests.
Understanding how each module is priced individually is the prerequisite for evaluating whether the bundle genuinely saves money — or merely consolidates spend under SAP's control while reducing your ability to walk away.
Module-by-Module Pricing: What SAP Actually Charges
SAP Ariba
Ariba pricing is a labyrinth of per-user subscription fees layered on top of transaction-based network fees. Core procurement modules (guided buying, purchase orders, receipts) run approximately $40–$65 per user per month for active-user licensing. Sourcing modules — used by procurement professionals, not all employees — run $50–$85 per user per month. Contract management is typically licensed separately at $25–$45 per user per month, with supplier lifecycle and performance management (SLP) adding another $20–$35 PUPM.
On top of subscription fees, the Ariba Network charges transaction fees when purchase orders and invoices flow through the network. Buying-side transaction fees are typically 0.155% of transacted value, capped at approximately $40,000 per year for standard enterprise agreements. Selling-side (supplier) fees are separate and borne by your suppliers — though buyers need to understand this cost because it affects supplier adoption rates and can surface as an indirect procurement cost.
Key benchmark: A 5,000-employee organisation licensing Ariba procurement, sourcing, and contract management for 200 active buyers typically pays $1.2M–$1.8M annually before Ariba Network transaction fees — before any ISG bundle discount is applied.
SAP Concur
Concur pricing is the simplest of the three major modules and is typically per-active-user per month for the functions used. Concur Travel (booking tool integration plus travel policy management) runs $14–$24 PUPM. Concur Expense (automated expense reports, receipt matching, ERP integration) runs $6–$10 PUPM. Concur Invoice (AP automation, three-way matching) adds $5–$8 PUPM. Most organisations pay for all three, yielding a blended Concur cost of $20–$38 PUPM for finance and travel users.
Concur has historically been licensed on a named-user or active-user model — a distinction that matters enormously for organisations with seasonal travel patterns or large populations of employees who file expense reports infrequently. Negotiating an active-user model, with a realistic cap on expected active users, is usually more cost-effective than a named-user count based on total headcount.
SAP Fieldglass
Fieldglass pricing is the most opaque of the three modules and is often based on a percentage of contingent spend managed through the platform, rather than a per-user fee. For enterprise agreements, this typically runs 0.5–1.0% of total contingent workforce spend flowing through the system. For a large organisation with $50M in annual contingent spend, this equates to $250,000–$500,000 per year in Fieldglass subscription fees before implementation.
Alternative pricing models — particularly for organisations with lower contingent spend — use a per-worker-per-month structure. In this model, each active contingent worker tracked in Fieldglass costs approximately $10–$25 per month. For organisations with large but intermittent contractor populations, negotiating a hybrid model with both a base fee and a per-worker fee (with annual true-up) can reduce costs by 20–30% compared to a pure percentage-of-spend model.
The Bundle Discount: ISG Economics vs Individual Licensing
SAP's ISG bundle offer converts all three modules to a per-employee-per-month (PEPM) pricing model based on total headcount. Typical ISG bundle pricing ranges from $6–$12 PEPM for a standard enterprise tier, with pricing declining as headcount increases. For a 10,000-employee organisation, this equates to roughly $720,000–$1,440,000 per year.
| Module | Individual Licensing (est.) | ISG Bundle Equivalent | Effective Saving |
|---|---|---|---|
| SAP Ariba (200 active buyers) | $1.2M–$1.8M/yr | Included in PEPM | Varies by usage |
| SAP Concur (2,000 users) | $480K–$912K/yr | Included in PEPM | Usually favourable |
| SAP Fieldglass ($30M contingent) | $150K–$300K/yr | Included in PEPM | Often unfavourable |
| Total 10,000-employee org | $1.83M–$3.0M/yr | $720K–$1.44M/yr | Potentially 20–50% |
The bundle trap: The savings analysis above assumes you are fully utilising all three modules across your entire workforce. If you use Fieldglass lightly, or only need Concur for 20% of employees, the PEPM model forces you to pay for hypothetical consumption across all employees — often making the bundle more expensive than targeted individual licenses.
The genuinely favourable ISG bundle scenario is one where all three modules are already in use, the organisation has substantial active user populations in all pillars, and the ISG PEPM rate has been negotiated down from SAP's opening position. In that scenario, discounts of 15–30% below individual list pricing are achievable. The unfavourable scenario is signing the ISG bundle before confirming usage breadth, because the PEPM model provides no credit for under-utilisation.
Negotiation Tactics for the Intelligent Spend Group
Regardless of whether you are evaluating ISG for the first time or renewing an existing agreement, the negotiation principles are the same: build leverage before SAP's quarter-end pressure mounts, demonstrate credible alternatives, and ensure the final contract matches your actual usage pattern.
The single most effective tactic is competitive pricing from alternative vendors. For Ariba, that means obtaining quotes from Coupa, Ivalua, or Jaggaer. For Concur, that means a quote from Navan (formerly TripActions), SAP Concur's most credible challenger. For Fieldglass, that means pricing from Beeline or Workday Contingent Workforce. SAP's account team will dismiss these comparisons as "not apples to apples" — but your procurement team does not need to be convinced, only SAP's deal desk does. A credible competitive quote shifts the deal from a price justification exercise to a competitive negotiation.
Timing matters significantly. SAP quarter-end discounts are real: Q4 (October–December) is consistently the most aggressive discounting period, followed by Q2 (April–June). If your renewal falls outside these windows, negotiating a contract start-date shift of 60–90 days to align with SAP's fiscal pressure is a legitimate and frequently used tactic. Organisations that renew in January or July typically leave 8–12% on the table compared to those who time their signature for the last two weeks of SAP's quarter.
For multi-year deals, always negotiate annual price cap provisions. SAP's standard ISG agreement permits CPI-linked uplift or a fixed escalator (often 3–5% annually). Capping this at 3% or tying it to a benchmarked index, rather than accepting SAP's default, is worth £200,000+ over a five-year deal for mid-market enterprises. Larger organisations can often negotiate a flat multi-year price with no annual escalation in exchange for a five-year term.
Frequently missed: The ISG bundle does not automatically include implementation, configuration, or integration services. These are sold separately by SAP and its SI partners, typically at $1.5–$2.5 for every $1 of software in year one. Scope these costs before committing to a bundle contract, and consider phasing the ISG rollout to control implementation spend.
ISG vs Best-of-Breed: When the Bundle Is Not the Answer
The ISG bundle is the right commercial structure only if your organisation genuinely needs all three pillars at enterprise scale. There are common scenarios where best-of-breed delivers better value at lower total cost of ownership.
If your travel and expense programme is managed with Navan, Expensify, or Brex and your employees are satisfied, replacing it with Concur as part of an ISG bundle adds migration cost, change management friction, and often a worse user experience. The Concur component of the ISG PEPM price is typically $2–$4 PEPM — which sounds small but represents $240,000–$480,000 per year for a 10,000-employee organisation paying for a tool they did not want.
Similarly, if your contingent workforce programme is handled through a small VMS or managed manually, adding Fieldglass via the ISG bundle introduces complexity that does not match the value. Fieldglass implementations for organisations with fewer than 500 active contingent workers rarely generate positive ROI within the contract term. The per-employee PEPM model makes this problem invisible — the cost of Fieldglass is embedded in the bundle rate, not visible as a line item.
The cleaner negotiation approach is to separate the modules: negotiate Ariba independently if that is your primary requirement, and add Concur and Fieldglass only if you have a genuine business case with defined success metrics. SAP will push back on this approach because disaggregated deals reduce SAP's commercial leverage, but organisations with credible alternative sourcing options can hold this position.
See also our guides on SAP Ariba licensing and negotiation and SAP Concur pricing and renewal tactics for module-specific deep dives. For organisations evaluating the broader SAP cloud portfolio, our RISE with SAP guide explains how ISG licensing may interact with RISE contracts.