SAP License Audits Contact Us
Home · Case Studies · Case File FG-009 · Fieldglass Contingent Worker

A $5.4M Fieldglass demand, reset to $1.7M.

A financial services firm disputed a Fieldglass true-up demand by reclassifying worker categories, retiring duplicated SOW records, and renegotiating the per-worker measurement basis.

Financial services trading floor
Industry
Financial Services
Geography
USA · UK · APAC
SAP Estate
Fieldglass VMS + integration
In Scope
11,800 contingent workers
— Case File FG-009 · Fieldglass Contingent Worker

The headline numbers, on the record.

Every result on this site is anonymised at the client's request. Specific figures are real and verifiable through a confidentiality-protected reference call arranged on request.

Opening demand
$5.4M
Fieldglass true-up
Settled value
$1.7M
after reclassification
Reduction
69%
below opening claim
Duration
13wk
letter to settlement
Chapter I · The Brief

The true-up demand

The firm operates a global contingent workforce programme spanning approximately eleven thousand eight hundred workers across staff augmentation, statement-of-work engagements, and a small independent contractor population. Fieldglass had been deployed in 2019 as the vendor management system of record, with a contracted per-worker subscription fee plus a service-fee line for SOW engagements.

The annual measurement cycle produced a worker count of eleven thousand eight hundred against a contracted ceiling of seven thousand five hundred. SAP Fieldglass issued a true-up demand of five point four million dollars covering the cumulative excess and the prospective adjustment for the current year.

The firm's Contingent Workforce Programme Office had been preparing an internal true-up and had estimated the exposure at roughly two million dollars. The CFO required a defended position before any payment was authorised.

Chapter II · The Opening Claim

The measurement position

Fieldglass had counted every active worker record on the VMS during the measurement window. The composite came to eleven thousand eight hundred. The contracted ceiling of seven thousand five hundred had been set at deployment and had not been adjusted for the firm's growth or for the worker-category mix.

On a line-by-line review the count included approximately two thousand three hundred SOW workers who were billed under the service-fee line rather than the per-worker line, and a further seven hundred workers who were active for less than thirty days in the measurement window and were therefore below the contract's minimum-duration threshold.

Fieldglass's account team initially declined the reclassification arguments. The framing was that the per-worker count was reported as transmitted by the platform and would be true-up at the contracted unit price.

Chapter III · The Defence

The four tactics

We worked four tactics in parallel against the true-up demand. Each one was grounded in the contract definitions and supported by evidence drawn from the firm's VMS and the underlying engagement records.

SOW worker reclassification

The SOW worker population is licensed under the service-fee line, not the per-worker line, when the engagement is delivered under a statement of work with deliverables-based pricing. We documented the contractual basis of two thousand two hundred and eighty workers and presented the reclassification as a contract-definition correction rather than a usage projection.

Minimum-duration threshold

The contract excludes workers active for less than thirty days from the per-worker count. We extracted the engagement start- and end-dates for the measurement window and identified six hundred and ninety workers below the threshold. The exclusion was supported by VMS records and accepted by SAP's reconciliation team.

Duplicate record purge

A vendor consolidation during the measurement period had produced duplicate worker records as engagements were re-keyed from the absorbed vendor's system. We reconstructed the underlying engagement trail and identified two hundred and forty duplicate records. The deduplication was accepted with a single-source attestation from the Contingent Workforce PMO.

Forward measurement protocol

The settlement included a forward measurement protocol documenting the worker-category definitions, the minimum-duration threshold, and the vendor-consolidation event handling. The protocol applies for the remainder of the contract term and is reviewed annually.

Chapter IV · The Settlement

The settled position

The true-up closed at one point seven million dollars against an opening demand of five point four, a sixty-nine per cent reduction. The settlement covered a true-up of approximately eight hundred per-worker seats and a small adjustment to the SOW service-fee line. No additional licences were purchased outside the reclassification.

Contractually, the worker-category definitions were written into a measurement addendum, with the minimum-duration threshold confirmed in writing and the vendor-consolidation protocol documented as a recurring exclusion right. The firm's Contingent Workforce Programme Office now runs a quarterly reconciliation aligned to the measurement protocol.

Total elapsed time from the true-up notification to signed settlement was thirteen weeks. The matter closed inside the same quarter and the contingent liability was removed from the interim disclosures.

Chapter V · Lessons Applicable

The lessons

First, Fieldglass measurements anchor on the VMS active-worker count, which includes workers that the contract excludes when the category is correctly applied. SOW engagements, short-duration workers, and duplicate records all distort the count without producing contract value.

Second, the SOW versus per-worker distinction is the single largest line in most Fieldglass true-up disputes. The contract definition rests on the engagement structure, not the worker's presence on the platform.

Third, minimum-duration thresholds are routinely overlooked and are routinely available as contractual exclusions. Fourth, vendor consolidations produce duplicate record artefacts that must be unwound before any measurement closes. Fifth, every Fieldglass deployment needs a quarterly reconciliation cycle aligned to the worker-category definitions, not an annual true-up surprise.

The true-up was anchored on a count that didn't match our contract. Once the worker categories were rebuilt, two thirds of the demand came off the table.

Head of Contingent WorkforceGlobal Financial Services Firm · Q2 2026
Continue with the firm

The two services this matter drew on.

I.

License Compliance Assessment

A reconciliation of the Fieldglass worker mix against contractual category definitions. Run before the annual true-up cycle, not after the demand letter arrives.

Read the brief →
II.

SAP Contract Negotiation

Reset the commercial structure after a Fieldglass true-up demand. Worker-category definitions written into addenda. Minimum-duration thresholds confirmed in writing.

Read the brief →
Related reading

From the research desk.

— Topic Page

SAP Fieldglass

The topic page sets out the licensing structure, the audit triggers, and the negotiation levers across this SAP product line.

Topic guide · Updated 2026
— White Paper

Fieldglass Contingent Worker Compliance

A 3,500-word analyst paper covering the methodology behind the defence, with five numbered recommendations and the field evidence.

Research paper · Gated
— Pillar Article

The SAP Fieldglass licensing pillar

The pillar article in this cluster covers the licensing structure, the audit triggers, and the defence sequence applicable to estates like this one.

Pillar · 2026
Other case files

Adjacent defences.

— Fieldglass Recovery

CPG group recovers Fieldglass overage

A multinational CPG group disputed a $3.8M Fieldglass overage and settled at $1.1M after a worker-category reclassification.

Case file
— License Reclamation

Financial services license reclamation

A North American financial services firm reclaimed 2,400 dormant SAP seats and reduced its renewal by 18%.

Case file
— All Case Files

The full case-file index

One hundred-plus anonymised case files across audit defence, license compliance, contract negotiation, and S/4HANA conversion.

Index · Updated weekly

Speak with a specialist.

Every engagement opens with a confidential, no-obligation conversation. We listen, test the position, and tell you whether there is a defendable case before any commercial discussion begins.

Contact Us →
— Subscribe

SAP Audit Alerts · The weekly briefing

Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.