Topic · SAP Fieldglass Subscription Audit

The VMS, as a percentage of spend.

Fieldglass is priced as a percentage of contingent-workforce spend under management. The spend definition is contractual. The annualised threshold is the reconciliation event. The category creep is the audit risk.

The Contingent WorkforceSpend under management — defined, reconciled, and the centre of the audit.

Section I · The Landscape

A platform priced against the programme.

SAP Fieldglass is the vendor management system for contingent workforce and services procurement. The pricing model is a percentage of spend under management — the total annual value of contingent labour, statements of work, and services procurement routed through the platform — with optional per-worker and per-SOW pricing on certain editions.

The spend definition is the central reconciliation metric and is contractual rather than standard. Whether managed services, master vendor fees, expense pass-through, and overtime premiums are included in the calculation sits in the drafted clause, and the answer determines the size of the next invoice.

The Fieldglass platform scales with the contingent-workforce programme. New regions onboard. New categories — IT services, marketing services, professional services — route through the platform. The annualised spend climbs, and the percentage applied against it follows.

The defensible Fieldglass posture combines a tight spend-under-management definition, a documented programme baseline, and a contractually negotiated reconciliation cap. We work the Fieldglass estate from the master agreement upward.

Section II · The Risk Surface

Eight spend triggers.

— I.

Spend Definition Drift

Pass-through expenses, overtime, and master-vendor fees often slip into the spend calculation without contractual basis.

— II.

Category Expansion

New services categories — marketing, professional services, IT — routed through Fieldglass multiply the spend baseline.

— III.

Geographic Rollout

Additional country deployments inflate the global spend under management above the contracted threshold.

— IV.

SOW Volume Growth

Statement-of-work modules carry per-SOW pricing on certain editions. Active-SOW counts drift upward with programme maturity.

— V.

Worker Profile Module Activation

Worker Profile Management activated outside the original subscription scope creates documented out-of-contract exposure.

— VI.

MSP Integration Fees

Managed-service-provider fees sometimes count toward spend, sometimes do not. The default treatment is the audit risk.

— VII.

Currency & Exchange Treatment

Multi-currency spend converted at variable rates can drift the reported baseline upward without operational change.

— VIII.

Renewal Threshold Lock-In

The annualised spend at renewal becomes the next floor. Without a cap, the trajectory is upward only across the term.

— Field Note · Fieldglass Reconciliation

The VMS programme that crossed the threshold.

A financial services group was issued a Fieldglass reconciliation for two point one million dollars at the fourth annual measurement, driven by category expansion into professional services, undefined treatment of MSP fees, and currency rebasing of European spend.

We rebuilt the spend-under-management baseline against the contractual definition. We separated the bona-fide programme growth from the categorisation drift. We negotiated a retrospective amendment with a capped reconciliation and rewrote the spend-definition clause for the remaining term.

Read the case file →

Reconciliation

$2.1M

Fieldglass year-four overage claim

Settled

$0.55M

capped retrospective amendment

Reduction

74%

below opening reconciliation

Renewal

-21%

negotiated against extended term

Questions, frequently.

How is SAP Fieldglass licensed?

On a percentage of spend under management, with optional per-worker and per-SOW pricing depending on the module mix. Contingent Workforce, Services Procurement, and Worker Profile Management are licensed independently against the contractually committed annualised spend.

What is spend under management?

The total contingent-workforce and services spend routed through Fieldglass in the contract year. It is the central reconciliation metric and is defined contractually rather than by platform default.

Why does Fieldglass create audit exposure?

Because contingent-workforce programmes scale upward across multi-year subscriptions. New regions, new categories, and new staffing partners drive spend above the contracted threshold, and the gap is reconciled at the annual measurement.

Are pass-through expenses included in spend?

Sometimes. Pass-through expenses, overtime premiums, and master-vendor fees can be included or excluded depending on the drafted clause. The default treatment usually inflates the spend basis.

How long is a typical Fieldglass subscription?

Three to five years is standard, often aligned with the broader SAP estate. The longer term attracts a better percentage rate but locks in the spend ratchet for the duration.