SAP Fieldglass Licensing Guide: Complete Reference for Enterprise Buyers

What is SAP Fieldglass?

SAP Fieldglass is a cloud-based vendor management system (VMS) that enables large enterprises to manage their contingent and extended workforce — including contractors, temporary workers, freelancers, consultants, and gig workers — and to procure external services through Statement of Work (SOW) arrangements. It was founded in 1999 as a standalone VMS business and was acquired by SAP in 2014 for approximately $1 billion, becoming the cornerstone of SAP's external workforce management portfolio.

Today, Fieldglass is positioned within SAP's Intelligent Spend Management suite alongside SAP Ariba (indirect procurement) and SAP Concur (travel and expense). For large enterprises that manage hundreds or thousands of external workers alongside substantial professional services spend, Fieldglass provides a centralised platform for sourcing, onboarding, time management, invoicing, and offboarding of contingent labour — all integrated with the core SAP ERP environment.

Understanding Fieldglass licensing is important because the platform sits at the intersection of workforce management, financial systems, and procurement — creating multiple touchpoints where licensing obligations can inadvertently be exceeded, and where SAP's continuous usage monitoring creates real-time compliance exposure that does not exist with traditional on-premise software.

The SAP Fieldglass Licensing Model

Fieldglass is licensed as a cloud subscription service. Unlike SAP's traditional on-premise portfolio, which uses named user types and module licences measured in periodic snapshots, Fieldglass pricing is usage-based and tied to actual external workforce activity. There is no published SAP price list for Fieldglass — all pricing is determined through direct commercial negotiation.

The absence of a public price list means that pricing is highly variable across customers, and that enterprises without independent benchmarking data have very limited visibility into whether they are paying market rates. Enterprises that negotiate Fieldglass in isolation from the rest of their SAP relationship typically pay 20 to 30% more than those who negotiate it as part of a consolidated SAP Intelligent Spend Management deal.

The subscription term is typically annual or multi-year, and the licence fee is recalculated at renewal based on actual usage in the preceding term. This creates a built-in renewal mechanism that favours SAP: if your contractor volumes or SOW spend have grown during the term, SAP arrives at the renewal with data showing higher usage — and will price the renewal accordingly unless you have prepared a counter-position in advance.

SAP's annual support is embedded within the Fieldglass cloud subscription. Unlike on-premise SAP licences — where support is separately paid at approximately 22% of net licence value — Fieldglass support is bundled into the subscription fee. This means you cannot opt out of support to reduce costs, and the all-inclusive subscription model makes it harder to benchmark Fieldglass pricing against traditional SAP on-premise cost structures.

Contingent Workforce Management Module: How It Is Priced

The Contingent Workforce Management (CWM) module manages individual workers hired on a time-and-materials basis — contractors, temporary agency staff, and similar arrangements where the worker is paid by the hour, day, or week rather than by project outcome. The CWM module is the core Fieldglass module for most enterprises and represents the majority of Fieldglass implementation globally.

The Active Worker Count Metric

The primary pricing metric for the CWM module is the number of active contingent workers in the Fieldglass system at any point during the subscription term. Most contracts structure this metric in tiered bands — for example, up to 500 active workers, 501 to 1,500 active workers, 1,501 to 3,000 active workers, and so on. Moving from one tier to the next triggers a step-change increase in annual fees, not a pro-rata increase. This means that if you are licensed for up to 500 workers and your count reaches 501, you pay for the entire next tier for the full year, not just for the incremental one worker.

The precise definition of "active worker" in your contract determines how this metric is counted. Critical definitional elements include:

• Peak vs average counting: Does SAP measure your highest active worker count at any single point in the year (peak), or the average count across the year? Peak counting is SAP's default and is significantly more expensive for enterprises with seasonal workforce patterns.
• Active vs total profiles: Does "active" mean a worker currently engaged on an assignment, or any worker with an active profile in the system, including those between assignments? Workers who have completed one assignment and not yet been formally offboarded may count as active under some contract definitions.
• Short-term and part-time workers: Are day workers, event staff, or part-time contractors counted the same as full-time long-term contractors? In standard Fieldglass contracts, all active worker records count equally regardless of engagement duration.

Each of these definitional choices has a direct impact on your licence cost. Negotiating precise, enterprise-favourable definitions at contract stage — rather than accepting SAP's standard language — is one of the highest-value actions available in Fieldglass negotiations.

Worker Classification and Onboarding Workflows

Fieldglass supports multiple worker classification types — W-2 employees placed by staffing agencies, 1099 independent contractors, SOW workers, and international workers operating under local employment frameworks. The classification of a worker in Fieldglass affects both the workflow through which they are managed and, in some configurations, whether they count against your CWM metric or your SOW metric.

Misclassification of workers — either accidentally or as a result of poor system configuration — can generate unexpected licence exposure. Workers managed as contingent CWM workers when they should be managed as SOW resources (or vice versa) create module cross-contamination that SAP's compliance reviews will identify. Establishing clear worker classification governance at implementation stage, with periodic audits, is an essential element of Fieldglass licensing management.

SOW / Services Procurement Module: How It Is Priced

The SOW module manages project-based engagements where work is contracted through a Statement of Work specifying deliverables, timelines, and outcomes rather than time inputs. Professional services engagements, consultancy projects, outsourced IT development, and managed service contracts are typical examples of SOW-managed spend.

The SOW module is licensed separately from the CWM module. Having a CWM licence does not entitle you to use the SOW module, and vice versa. This distinction is the most common source of unexpected Fieldglass compliance exposure — enterprises that begin with CWM and gradually start processing professional services SOWs through the same platform find that they are using a module they have not licensed.

SOW Pricing Metrics

The SOW module is typically priced using one of two metrics, or a combination of both:

• Total SOW spend processed: The total value of SOW contracts managed through Fieldglass during the term. This metric tiers in the same way as the CWM worker count — bands of spend volume with step-change fees at each tier boundary.
• Number of active SOW projects: Some contracts price by the number of concurrent active SOW engagements in the system rather than by spend value. This approach is more predictable for enterprises with a stable project portfolio but variable project values.

The spend-based metric creates a specific risk for enterprises using the supplier-funded MSP model: SAP may measure SOW spend at the gross invoice value (before the MSP fee is deducted) rather than the net spend value. If your SOW engagements are large, even a 2 to 3% MSP fee deducted from the measurement can create a meaningful difference in spend-tier calculations. Negotiate explicitly which spend figure — gross or net — is used as the SOW licensing base.

MSP Funding Models and Their Licensing Implications

Most large enterprise Fieldglass programmes operate through a Managed Service Provider (MSP) — a specialist third party that manages the day-to-day operation of the contingent workforce programme, supplier relationships, rate management, and compliance activities. The MSP earns a fee, and how that fee is funded within Fieldglass has direct implications for licensing cost and compliance.

Buyer-Funded MSP Model

In the buyer-funded model, the enterprise pays the MSP fee explicitly and separately. Within Fieldglass, the MSP fee is configured as an add-on to the supplier bill rate, and the buyer sees exactly what is paid to the supplier and what is paid to the MSP. The licensing implication is straightforward: your active worker count and SOW spend are measured at actual values, and there is no ambiguity about gross versus net figures.

Supplier-Funded MSP Model

In the supplier-funded model, the MSP fee is deducted from the invoice amount before the supplier receives payment. The supplier invoices at a gross rate; the MSP holds back its percentage and remits the remainder to the supplier. This model appears cost-neutral from the buyer's perspective — the total amount leaving the buyer is unchanged — but it creates accounting complexity and a potential SAP licensing wrinkle.

Under the supplier-funded model, the "invoice value" flowing through Fieldglass is the gross amount inclusive of the MSP fee. SAP may treat the gross value as the relevant SOW spend figure for licensing purposes, even though the effective procurement spend is lower. In large programmes with high SOW volume, this can push your spend measurement into a higher tier than your actual procurement activity warrants. Ensure your contract explicitly states that SOW spend is measured at net-to-supplier value.

Integration with SAP S/4HANA and SuccessFactors

SAP Fieldglass integrates with SAP S/4HANA for financial approvals and with SAP SuccessFactors for workforce data. These integrations are productised and included within the standard Fieldglass subscription — they do not require separate licence fees. However, the integration architecture has practical and compliance implications that deserve attention.

Fieldglass to S/4HANA Integration

The standard Fieldglass–S/4HANA integration connects the two platforms for purchase order creation, service entry sheet processing, and invoice management. In S/4HANA, the Data Replication Framework extracts master data — cost centres, company codes, purchase organisations — and makes it available in Fieldglass for assignment to worker records and SOW projects. In return, Fieldglass sends approved time sheets, expense reports, and SOW milestone completions back to S/4HANA, where they trigger the financial approval and payment workflows.

This integration is the primary touchpoint through which Fieldglass interacts with the core SAP financial system. If your enterprise is mid-migration from SAP ECC to S/4HANA, verify that your Fieldglass integration configuration is compatible with the target S/4HANA release. Some older Fieldglass integration configurations are not compatible with S/4HANA 2022 and later without reconfiguration, which may have implementation cost implications.

Fieldglass to SuccessFactors Integration

The Fieldglass–SuccessFactors integration synchronises worker data, enabling enterprises to manage their total workforce — employees and contractors — through a unified data model. Contractor records created in Fieldglass can be linked to SuccessFactors for access management, onboarding workflow, and workforce planning reporting. This integration is increasingly important as enterprises adopt total workforce management approaches that treat employees and contingent workers as part of a single planning and governance framework.

If you use both Fieldglass and SuccessFactors, ensure that worker records are not duplicated across both systems in a way that inflates your SuccessFactors seat count or your Fieldglass active worker count. Poor data governance between the two platforms — particularly during initial integration implementation — can create licence exposure in both systems simultaneously.

Indirect Access and the DDLC Metric

The Digital Document Lifecycle Count (DDLC) is SAP's primary metric for measuring and pricing indirect access — the use of SAP system capabilities by non-SAP users or non-SAP applications. DDLC counts the number of documents created or substantially modified through SAP interfaces by non-SAP-licenced users or by third-party systems that interact with SAP without their own SAP licence.

Fieldglass sits at the boundary of the SAP licensing perimeter in a way that creates indirect access exposure for some enterprises. Consider the following scenarios:

• Non-SAP HR or finance systems feeding Fieldglass: If your organisation uses Workday, Oracle HCM, or another non-SAP HR system that feeds worker data into Fieldglass, and Fieldglass then creates SAP purchase orders or service entry sheets in S/4HANA, SAP may argue that the originating non-SAP system is driving document creation in SAP and that the DDLC metric is triggered.
• Third-party analytics and reporting tools accessing Fieldglass data: If external BI tools or workforce analytics platforms query Fieldglass data and that data feeds back into SAP financial systems, the integration pathway may generate DDLC exposure depending on how SAP defines "document creation" in your contract.
• Supplier portal interactions: When suppliers interact with Fieldglass through supplier portals to submit time sheets or invoices, those interactions result in SAP documents being created or updated. SAP's position on whether supplier portal interactions generate DDLC exposure varies by contract and by the specific integration architecture used.

The DDLC-based indirect access risk associated with Fieldglass is manageable but must be assessed explicitly. Map all integration points between Fieldglass and non-SAP systems, and between Fieldglass and the SAP ERP core, before entering any Fieldglass contract renewal or renegotiation. Obtain a clear contractual statement from SAP specifying that normal Fieldglass usage within the licensed scope does not generate additional DDLC exposure. This clause is negotiable and should be included as a standard protective provision in any enterprise Fieldglass agreement.

SAP's Compliance Monitoring Approach

Because Fieldglass is a cloud platform, SAP has continuous real-time visibility into usage data. This is fundamentally different from on-premise SAP licences, where SAP must conduct a formal measurement audit using the SAP License Administration Workbench (LAW) to establish usage. For Fieldglass, SAP can see your active worker counts, SOW spend values, and module usage at any time without any formal audit process.

SAP increasingly uses this data advantage proactively. In the six to twelve months before a Fieldglass contract renewal, SAP account teams routinely initiate what they describe as "licence position reviews" — essentially a pre-renewal compliance check that uses SAP's own platform data to identify any usage overage. By the time this review is presented to the customer, SAP already knows the result. The customer, unless they have run their own equivalent analysis, is operating with significantly less information.

Preparing for a Fieldglass renewal therefore requires conducting your own usage analysis using Fieldglass reporting tools before SAP initiates its review. The key metrics to establish independently are: peak active worker count by month for the past 12 months, total SOW spend by module for the past 12 months, number of active SOW projects at peak, inactive vs active worker profiles in the system, and any cross-module usage (CWM workers managed as SOW or vice versa). Presenting your own analysis at the start of a renewal negotiation — before SAP tables its position — changes the dynamic of the conversation materially.

Common Licensing Traps in SAP Fieldglass

Over 40+ Fieldglass contract reviews, Redress Compliance has identified the following as the most frequently encountered and most costly licensing traps:

• Peak counting without seasonal adjustment: Paying for the maximum worker count at any point in the year, regardless of how briefly that peak was reached, inflates annual fees substantially for industries with seasonal workforce patterns.
• SOW expansion without licence expansion: Gradually using the Fieldglass SOW module for professional services contracts without having licensed it. SAP's monitoring will identify this, typically at renewal when it has maximum commercial leverage.
• Discount loss at renewal: Initial Fieldglass contracts often include significant discounts not explicitly carried forward in the renewal language. At renewal, SAP quotes at standard pricing and the customer must re-negotiate the discount from scratch, typically with less leverage than at initial deal stage.
• Gross SOW spend measurement: As discussed, measuring SOW licensing tiers on gross invoice values that include MSP fees rather than net procurement spend can inflate the applicable tier by 2 to 5%.
• Inactive profiles counted as active: Poor offboarding governance leaves contractor profiles in an active state in Fieldglass after their engagement ends, inflating the active worker count metric unnecessarily.
• Module upgrades bundled with renewals: SAP sometimes bundles Fieldglass capability upgrades or new module additions into renewal conversations. These should be evaluated on standalone value and priced separately, not accepted as part of a package that implicitly raises the baseline renewal cost.

Negotiation Strategy for SAP Fieldglass

Effective Fieldglass negotiation requires preparation, market intelligence, and the right timing. The following strategy framework applies to both initial deals and renewals.

Bundle with the Broader SAP Relationship

Fieldglass negotiated as a standalone contract rarely achieves the same commercial outcome as Fieldglass negotiated as part of a broader SAP Intelligent Spend Management or enterprise-wide SAP deal. If your organisation also uses SAP Ariba, SAP Concur, SAP SuccessFactors, or is in active RISE with SAP discussions, include Fieldglass in that negotiation. Total relationship values above €5 million annually across SAP cloud applications typically support Fieldglass discounts of 40 to 50% off standard pricing. Below that threshold, discounts are typically in the 25 to 35% range.

Define Every Metric Before Signing

Ambiguity in metric definitions is the primary source of post-signature Fieldglass cost surprises. Before signing, ensure the following are explicitly defined in the contract: how "active worker" is counted (peak, average, year-end snapshot), the specific date or period on which the active worker count is measured, whether inactive profiles count as active, how SOW spend is measured (gross or net), and the specific module(s) licensed and explicitly excluded from the licence scope.

Secure Seasonal Flexibility

If your contractor count fluctuates seasonally, negotiate a flexibility clause allowing your active worker count to exceed the contracted tier by a defined percentage (typically 10 to 20%) during specified peak periods, without triggering a tier upgrade. SAP will resist this clause but it is achievable in large-enterprise negotiations. Alternatively, negotiate a measurement methodology that uses annual average count rather than peak count — this is less common but has been achieved in deals where the customer has strong commercial leverage.

Lock In Renewal Pricing

Always include explicit contractual language governing how the discount is carried forward at renewal. The minimum standard is a clause specifying that the renewal pricing applies the same discount percentage as the original term to the then-current Fieldglass list price, with any price escalation capped at a defined rate — typically Consumer Price Index or a fixed 3 to 5% maximum annual increase. Without this clause, SAP can price the renewal at full list and you must renegotiate the discount from scratch.

Negotiate Both Modules at Inception

If there is any possibility that your Fieldglass use will expand from contingent workforce management into SOW services procurement — even if SOW use is not planned in the near term — negotiate SOW module coverage at the initial deal stage. Buying SOW coverage during a mid-term compliance review or at renewal, when SAP already knows your SOW usage pattern, is significantly more expensive than including it in the initial commercial discussion before any usage has been established.

Time the Negotiation Strategically

SAP's fiscal year ends December 31. The highest-pressure window for SAP's account teams is Q4, particularly November and December, when annual sales targets must be closed. Initiating Fieldglass renewal conversations in October — so that the commercial negotiation can conclude in November or December — gives SAP teams strong incentive to make concessions that would not be on the table in Q1 or Q2.

Ongoing Fieldglass Licensing Governance

Fieldglass licensing is not a one-time exercise — it requires ongoing governance throughout the subscription term to avoid the compliance exposures that accumulate between deals. Key governance activities include:

• Monthly active worker count reviews: Monitor your active worker count against your contracted tier monthly, not just at renewal. Identifying a potential tier breach six months before renewal gives you time to manage the exposure commercially rather than being forced into a true-up.
• Quarterly SOW spend tracking: Track cumulative SOW spend against your contracted tier quarterly. If you are approaching the spend tier threshold, address it with SAP before they raise it — proactive disclosure typically results in better commercial terms than a SAP-initiated true-up.
• Worker offboarding hygiene: Establish a formal process for offboarding contractors from Fieldglass promptly when their engagements end. Inactive profiles left in the system inflate the active worker count and create unnecessary licensing cost.
• Module usage audits: Conduct an annual audit of which Fieldglass modules are in active use and ensure they match your licence scope. Any new module usage identified during the audit should be addressed either by retiring the usage or by formalising it through a contract amendment before SAP identifies it independently.
• Integration change management: Any changes to the Fieldglass integration landscape — new connections to non-SAP systems, changes to the S/4HANA or SuccessFactors integration configuration — should be assessed for licensing implications before go-live, not after.

Conclusion

SAP Fieldglass is a strategically important platform for enterprises managing significant contingent and project-based workforce spend. Its licensing model — usage-based, cloud-monitored, and structurally opaque without public pricing benchmarks — creates a different category of commercial risk to traditional SAP on-premise licensing. Enterprises that understand the module structure, negotiate metric definitions precisely, maintain active usage governance, and approach renewals with independent data are consistently able to manage Fieldglass costs effectively. Those that treat Fieldglass as a set-and-forget SaaS subscription consistently discover expensive surprises at renewal time.

Redress Compliance specialises in independent SAP Fieldglass contract reviews, usage position assessments, and renewal negotiation support. We have reviewed over 40 Fieldglass contracts across all industry sectors. If you have a renewal approaching or want to understand your current licensing exposure, contact our team.