How SAP Fieldglass Licensing Works: The Double-Fee Model

SAP Fieldglass is a cloud-based Vendor Management System (VMS) that manages the entire lifecycle of contingent workers — temporary staff sourced through agencies, independent contractors, and statement of work (SOW) services engagements. Unlike most enterprise software licences, Fieldglass does not charge a flat per-user or per-seat fee. Instead, it operates on a managed spend model: pricing is calculated as a percentage of the total contingent workforce spend processed through the platform.

What distinguishes Fieldglass from other VMS platforms is that SAP monetises both parties in every transaction. The enterprise (buyer) pays a platform fee typically set at 0.25–0.5% of total managed spend. Simultaneously, every staffing agency or supplier invoicing through Fieldglass pays a supplier network fee of 2–3% on each invoice submitted. Suppliers virtually always recover this cost by embedding it into their bill rates — meaning buyers absorb the supplier-side fee through inflated rates without ever seeing it on an invoice. For an enterprise managing £50M of contingent spend annually through Fieldglass, this double-fee structure generates £750,000–£1.75M in total platform costs, compared to the £125,000–£250,000 buyer-side fee SAP presents in commercial discussions. Review the SAP Contract Negotiation Fundamentals guide for the commercial frameworks used to renegotiate Fieldglass pricing in practice.

Understand Your True Fieldglass Cost

Redress Compliance builds total-cost-of-ownership models for SAP Fieldglass engagements, including the supplier fee pass-through that most enterprises never quantify. We have identified £500k+ in recoverable costs across Fieldglass renegotiations in the UK and US.

Talk to a SAP Fieldglass Specialist

Buyer-Side Fee Structure: What Enterprises Actually Pay

The buyer-side Fieldglass licence is structured around three variable components that make year-on-year cost comparisons difficult and give SAP flexibility to expand charges without appearing to raise the headline rate.

Managed Spend Percentage

The core fee is expressed as a basis point charge on total contingent spend processed through Fieldglass. SAP typically quotes 25–50 basis points (0.25–0.50%) at initial contract, but this rate can step up in subsequent years if managed spend decreases — SAP uses a minimum managed spend floor to protect revenue if an enterprise reduces its contingent workforce. Enterprises that do not negotiate a rate lock will see effective fee rates increase 8–15% at renewal simply because their contingent headcount fell below the prior year's baseline. Negotiate a fixed rate per transaction or a fixed annual fee capped at current managed spend volumes to remove this exposure.

Module Licensing

Fieldglass separates its functionality into distinct modules, each attracting an independent charge. The Contingent Staffing module (temporary and agency workers) is the core and covered by the managed spend fee. Analytics and Reporting, Supplier Diversity tracking, and the Job Posting Portal are add-ons that SAP prices separately — typically £15,000–£45,000 per module per year for a mid-market enterprise. Enterprises that implement Fieldglass without rationalising module requirements against those of their incumbent VMS routinely pay for capabilities they already have in Ariba, SuccessFactors, or their HRIS.

Integration and API Charges

Fieldglass integration with SAP's own products — SuccessFactors for worker records, S/4HANA for purchase orders and invoice processing, and Concur for expense management — is presented as native and included. In practice, enterprises find that complex integration scenarios (multi-entity, multi-currency, or involving non-SAP HRIS systems) trigger professional services charges and, in some configurations, API consumption fees billed against SAP BTP cloud credits. Map every integration point before contract signature and require SAP to confirm in writing which integrations are included in the base licence versus those subject to additional charges.

Supplier-Side Fees: The Hidden Cost Passed Back to You

The Fieldglass supplier network fee — charged to staffing agencies and independent contractors who submit invoices through the platform — is the most consistently misunderstood element of total Fieldglass cost. SAP charges suppliers 2–3% on each invoice value as a condition of participation in the Fieldglass supplier network. This fee is not visible to the buyer on any invoice, but is recovered by suppliers through one of three mechanisms: a direct uplift on the agreed bill rate, a reduction in the quality or seniority of workers provided at the same nominal rate, or a surcharge disclosed in supplier terms and conditions that buyers rarely scrutinise.

Across Redress Compliance client engagements, the effective supplier fee pass-through adds 1.5–2.5% to the blended bill rate across the contingent workforce portfolio. For an enterprise with 500 agency workers at an average bill rate of £35/hour, working 1,750 hours per year, this represents an annual hidden cost of approximately £460,000–£765,000 sitting invisibly within workforce costs. Enterprises negotiating Fieldglass contracts should demand a supplier fee cap (1.5% maximum), require SAP to publish a public supplier fee schedule, and build fee transparency obligations into supplier contracts. See the SAP Intelligent Spend Group licensing guide for how Fieldglass supplier fees interact with Ariba and Concur supplier network charges.

SOW Module Pricing and Services Procurement

SAP Fieldglass offers a separate Statement of Work (SOW) module for managing project-based services engagements — consultancies, outsourced projects, and managed service providers — where deliverables rather than time-and-materials are the basis of payment. The SOW module is priced separately from the contingent staffing module and carries a distinct managed spend percentage, typically at a slightly lower rate (0.15–0.30%) but applied to a broader spend base that often includes contracts three to five times larger than individual worker engagements.

Enterprises frequently underestimate SOW managed spend at contract signature. If a company processes its IT outsourcing contracts, facilities management agreements, or professional services retainers through Fieldglass SOW, the resulting managed spend can easily reach £100M+ annually — generating SOW module fees of £150,000–£300,000 on top of contingent staffing fees. SAP sales teams deliberately encourage broad SOW adoption at initial contracting to lock in high managed spend volumes; the renewal conversation then anchors to those volumes. Before signing, define precisely which spend categories will be in scope for the SOW module and negotiate a managed spend exclusion for legacy contracts already in procurement systems that will not genuinely be managed through Fieldglass. Consult the SAP Ariba licensing guide for how SOW scope in Fieldglass overlaps with Ariba Contracts and creates double-charging risk.

SAP Fieldglass Assessment Tool

Use the Redress SAP Assessment Tools to model your true Fieldglass total cost of ownership — including managed spend projections, supplier fee pass-through estimates, and module cost breakdowns — before entering any renewal or renegotiation discussion with SAP.

Run Your Fieldglass Assessment

Negotiating Fieldglass as Part of SAP Intelligent Spend Group

SAP bundles Fieldglass with Ariba (direct and indirect procurement) and Concur (travel and expense) under the Intelligent Spend Group (ISG) umbrella. The ISG bundle is priced on a per-employee basis rather than per-module managed spend, which for large enterprises typically results in a blended cost 15–25% lower than purchasing each product individually at list price. SAP uses ISG to consolidate renewal leverage: if you hold individual contracts for Ariba, Fieldglass, and Concur at different renewal dates, SAP will actively propose consolidating them into a single ISG agreement at next renewal — which simplifies SAP's position but reduces your negotiating flexibility.

For enterprises already in RISE with SAP, Fieldglass is not included in the core SAP RISE subscription — it must be licensed separately. SAP will propose attaching Fieldglass to the RISE renewal at a bundled ISG rate, presenting this as a commercial benefit. However, the ISG per-employee pricing model removes the managed spend cap that individual Fieldglass contracts contain, replacing it with headcount growth risk. Enterprises that plan to grow headcount significantly in the RISE contract period will face steeper Fieldglass cost escalation under ISG pricing than under a standalone managed spend model. Model both scenarios against your 3-year workforce plan before accepting any RISE-attached ISG proposal from SAP.

Key negotiating levers in any Fieldglass or ISG negotiation include: a supplier fee cap written into the MSA (not just the order form), a fixed managed spend rate with no step-up provisions for volume decreases, an explicit list of modules in scope versus those excluded, a 30-day termination-for-convenience clause in year 3 to preserve optionality, and a price lock on API and integration charges for the contract term. Redress Compliance has structured Fieldglass contracts that delivered 22–28% total cost reduction compared to SAP's initial renewal proposal, primarily through supplier fee transparency and managed spend rate negotiations. Review our SAP Named User Optimisation guide for complementary licence efficiency strategies that reduce the overall SAP commercial footprint.