Fieldglass is SAP's Vendor Management System for contingent workforce, services procurement and statement-of-work management. The licensing surface runs against the buyer's spend-under-management. The buyer-side question is whether the VMS commercial mechanic reads sensibly against the actual contingent-workforce profile.
Fieldglass is a Vendor Management System that runs the buyer's contingent workforce operations end-to-end. The platform manages the requisition of contingent workers, the supplier-of-record relationships (typically staffing agencies and consultancies), the time and expense capture, the invoicing and the analytical reporting against the consolidated contingent workforce population.
The platform sits adjacent to the buyer's permanent-workforce HCM (SuccessFactors, Workday, Oracle Cloud HCM). The integration is technical, but the commercial constructs differ; the HCM licenses the permanent population at a per-named-user rate, while Fieldglass licenses the contingent population at a spend-under-management rate.
The full reading on the SAP application catalogue sits in the SAP pillar; parallel reads in SuccessFactors licensing and Ariba and procurement licensing.
Fieldglass prices against the buyer's gross spend-under-management through the platform, structured as a percentage of the contingent workforce spend plus services procurement spend plus statement-of-work spend that flows through the system. The percentage rate scales with the committed spend volume and is typically tiered.
The buyer-side complication is that the spend-under-management mechanic creates a commercial alignment problem: as the buyer's contingent workforce grows, the Fieldglass fee grows proportionally, regardless of whether the platform's value to the buyer grows proportionally. The renewal negotiation is the moment to reset the percentage rate against the volume.
The Admodum methodology benchmarks the buyer's percentage rate against the published rate cards for comparable spend volumes, against the firm's benchmarking database, and against the alternative VMS providers (Beeline, SAP successor systems, and the established Beeline / VNDLY / Pixel Labs surfaces). Where the rate reads materially above market, the negotiation runs.
A growing portion of the Fieldglass commercial surface runs against statement-of-work (SOW) management rather than purely contingent-staffing management. The SOW surface licenses the buyer's services-procurement team and the suppliers delivering against scoped engagements (consulting, professional services, project-based work).
The SOW surface reads against the spend-under-management mechanic, so the larger the buyer's services-procurement spend through Fieldglass, the larger the Fieldglass fee. The buyer's strategic question is whether Fieldglass is the right surface for SOW or whether the SOW spend should run through Ariba Sourcing and Ariba Contracts instead.
The Ariba-versus-Fieldglass question for SOW is the renewal-cycle work. The decision depends on the buyer's procurement organisation, the supplier base and the integration footprint.
The supplier-of-record (SOR) on Fieldglass is typically a staffing agency or a consultancy that holds the direct commercial relationship with the contingent worker. The SOR pays the worker, invoices the buyer through Fieldglass and absorbs the regulatory and compliance burden.
The buyer's SOR economics affect the Fieldglass position. Where the buyer's contingent workforce is heavily concentrated with a small number of preferred SORs, the renewal can negotiate consolidated SOR-specific commercial terms inside the Fieldglass platform. Where the contingent workforce is widely distributed, the negotiation runs on different ground.
The full reading on the related procurement-cycle mechanics sits in The SAP renewal cycle.
Fieldglass renewal sits inside the SAP commercial relationship and the wider VMS market. The renewal posture depends on the spend-under-management read, the percentage-rate benchmark, the SOW versus contingent split, the SOR concentration profile and the alternative-VMS posture (where credible).
The methodology runs four independent reads against the publisher's renewal proposal: the spend-under-management reconciliation against the contracted percentage, the SOW versus contingent split against the platform value, the SOR concentration audit against the rate-card and the alternative-VMS BATNA read.
The renewal engagement runs under one of three Admodum frameworks: fixed fee, contingency / gainshare or annual retainer.
Five checks for the buyer running into a Fieldglass decision: benchmark the spend-under-management percentage against the comparable cohort. Read the SOW spend separately from the contingent-staffing spend. Audit the supplier-of-record concentration. Open the alternative-VMS BATNA before the renewal. Run the negotiation on the validated data, not on the publisher position.
For the wider SAP reading, return to the SAP pillar, visit the SAP knowledge hub, or open a private conversation with a senior Admodum SAP advisor through /contact/.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route directly to the Audit Defence programme.