A North American utility challenged a supplier-fee re-tiering on the Ariba Network, recovered three years of overcharges, and rewrote the document-count clause that triggered the increase.
All numbers are real and anonymised at the client’s request. Specific results can be verified through a confidentiality-protected reference call.
The utility serves twelve states across the northeastern and mid-Atlantic United States and operates a procurement function with roughly two thousand four hundred active suppliers transacting through the SAP Ariba Network. The original Ariba contract dated to a multi-year transformation programme and included a supplier-fee structure tied to document-volume tiers, with annual measurement and tier adjustments applied on the anniversary of the go-live date.
In the third quarter of the year before our engagement, internal finance noted a roughly thirty per cent year-on-year increase in network fees absorbed by the buyer side. The Ariba account team explained the increase as a tier reclassification triggered by document growth and offered to discuss a longer-term commitment that would “normalise” the position.
The client’s commercial team escalated. The procurement leadership engaged us to validate the measurement, audit three years of historical billing, and lead the recovery negotiation. The mandate explicitly excluded any new commitment as a precondition.
We obtained the full document log from Ariba covering the prior thirty-six months and reconstructed the tier calculation from first principles. The contract defined a chargeable document as a discrete purchase-order or invoice transmission, with specific carve-outs for change documents, technical acknowledgements, and integration-driven re-sends. The Ariba measurement had counted all three excluded categories as chargeable documents.
Across the three-year window, the inflated count was approximately sixty-one per cent higher than the contract-defined count. Re-running the tier calculation against the corrected count placed the utility two tiers below the position Ariba had been billing.
First, change-document re-sends were being counted as new documents each time an order was updated. Second, technical acknowledgements transmitted under the cXML protocol were charged as separate documents despite the explicit contract exclusion. Third, integration-driven re-sends from a middleware retry queue had inflated the count during two specific weeks in which the integration layer had been unstable.
We presented the reconstructed measurement to Ariba in a single written submission, with the document log, the contract clauses, and a line-by-line tier reconstruction. The Ariba commercial team conceded the position within fourteen business days.
The settlement returned four point two million dollars in credits applied against forward network fees. The supplier-fee tier was reset two levels below the prior billing position, producing a thirty-eight per cent reduction in the forward network access fee. The amendment locked the tier for a minimum of twenty-four months and added a re-measurement audit right for the client.
Two clauses were rewritten in the executed amendment. The document-count definition was tightened with explicit inclusions and exclusions matching the cXML specification. The annual tier-adjustment clause was modified to require a written measurement submission from Ariba thirty days in advance, with a buyer-side review window, before any tier change could take effect.
The utility was also able to extend the recovery logic to roughly six per cent of its supplier base that had been re-charging Ariba fees through their own pricing, producing a secondary recovery at the operational level for the twenty-four months following close.
They unwound three years of billing in fourteen weeks. The amendment we signed is the most defensible contract we have ever held on the Ariba side.
Settlement and remediation work. We model the commercial position, validate every measurement, and lead the negotiation through to executed amendment.
Read the brief →Pre-audit baseline of every measurement and entitlement in the estate. We map the contract to the configuration before SAP or Ariba can.
Read the brief →The four chargeable events, the network access fee, and the supplier-side charges most procurement teams never see.
From audit-rights to assignment, the clauses that buyer-side teams most often leave on the table at signature.
How a global CPG manufacturer recovered $2.1M in SAP Fieldglass services-procurement charges and capped forward usage.
If your Ariba, Fieldglass, or SuccessFactors fees have moved in the last twelve months, it is worth a conversation. The first call is at no cost and under privilege.
Contact Us →Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.