SAP indirect-access settlement examples, annotated.

Settlements end where the contract, the measurement evidence, and the commercial pressure converge. In SAP indirect-access matters that convergence is unusually visible: the opening claim is almost always large, the contractual ambiguity is almost always real, and the eventual settlement is almost always a structural reshape rather than a haircut on the original number. The six anonymised examples that follow are drawn from settlements closed across the last twenty-four months. Each one is presented as the audit team described the position on the way in, the buyer-side defensive narrative that reduced it, and the structural remedy that became the contract.

Example one — the e-commerce reset

A consumer-goods manufacturer running pre-2018 SAP licensing received an audit position quoting eleven point two million dollars for indirect use through a Salesforce Commerce Cloud storefront and a customer-self-service portal. SAP’s methodology counted every storefront user who had created a registered account over the prior thirty-six months and applied a Professional User price to each.

The defensive argument worked on three fronts: the storefront created an SAP sales order document per transaction rather than a per-user posting; the registered-account population vastly exceeded the active-transacting population; and the Digital Access model, available as a conversion, priced the chargeable surface at document tier, not per-user. The settlement converted the matter to Digital Access for sales documents only, with capped tier pricing, a re-measurement protection clause, and a release for all prior indirect use. The final value was two point seven million dollars across a three-year term.

The pattern is documented further in our middleware risk article and in the indirect-access topic page.

Example two — the field-service claim

A facilities-services group running SAP ECC with a ServiceMax field-service application received an opening claim of six point four million dollars. The audit team had counted every named technician with a ServiceMax login as a Professional User equivalent because the application posted service-order completions into SAP. The buyer’s SAP user population was three hundred and fifty Professional Users; the implied add was a further nine hundred technician seats.

The defensive position rebuilt the work-order flow from the source. ServiceMax was creating one SAP service order per completed job, not per technician session, and the technicians did not have direct SAP login credentials. Under the Digital Access framing, only the service-document type applied, with a measured annual volume of forty-one thousand documents. The settlement structure was a Digital Access entitlement of fifty thousand service documents annually, a price floor of zero for non-service document types, and a $1.1M one-time settlement covering historical periods. The five-year present value was approximately eighty per cent below the opening claim.

Example three — the RPA question

A financial-services firm with extensive UiPath robotic process automation received an opening position of fourteen point eight million dollars for indirect access on the grounds that each robot constituted a non-human SAP user that, in SAP’s read, required a Professional User licence per robot or, alternatively, a per-bot indirect-use fee.

The defensive narrative was contractual rather than technical. The pre-2018 indirect-use clause references “users”, and the contractual definition the buyer relied on described a user as a natural person. The robots were not natural persons. The robots did, however, perform postings under a single technical user account that already held an SAP Professional User licence. The negotiation centred on the contractual definition rather than the document count. SAP’s position softened over three rounds, and the matter closed at three point one million dollars as a one-time settlement with a contractual amendment that recognised the technical-user posting model for the contract term. The methodology for handling RPA exposure is covered in the indirect-access white paper.

Example four — the EDI reduction

An automotive supplier running an extensive electronic-data-interchange topology with major OEM customers received an opening claim of eight point nine million dollars on the basis that every EDI partner generated SAP documents on the buyer’s side. The defensive position questioned both the document count and the contractual posture: under Digital Access the order documents were chargeable, but the acknowledgement and shipment-notification documents were intra-document-flow events that did not multiply the chargeable count under the buyer’s reading of the order form.

The settlement reshaped the engagement to Digital Access for order documents only, with a contractual exclusion for the secondary document types, a measured annual volume of one hundred and ninety thousand documents, and a graduated tier pricing schedule. Final settlement value was approximately three point four million dollars for the four-year term. The pattern echoes the global-retailer conversion case file.

Example five — the BI read-only defence

A pharmaceutical group with a large business-intelligence layer pulling data from SAP into Tableau and Power BI dashboards received an opening claim of nine point six million dollars for indirect use, on the grounds that several thousand non-SAP-licensed users were viewing SAP-originated data through the dashboards. SAP’s position cited the “benefit” language in the pre-2018 indirect-use clause.

The defensive position rested on the read-only argument and on the absence of a chargeable document under the Digital Access model. The BI flows did not create documents in SAP. The data movement was outbound only. The buyer’s contractual reading of the indirect-use clause was supported by external commentary and by the post-2018 model’s explicit silence on read-only flows. The settlement was a release for all read-only BI flows, a re-measurement protection clause covering the contract term, and a six hundred thousand dollar one-time concession. The result was effectively a contractual confirmation of the buyer-side read-only argument.

Example six — the portal conversion

A logistics group operating a bespoke customer-portal received an opening claim of twelve point one million dollars. The portal was authenticated, allowed customers to view shipment status, raise service requests, and update master-data records. SAP counted the registered customer population — just over four thousand — at indirect-use Professional pricing.

The defensive narrative reclassified each interaction type against the Digital Access document schedule. Status views were read-only and not chargeable. Service requests created one SAP service notification document each. Master-data updates were intra-system events that did not multiply documents. The settlement was a Digital Access entitlement of one hundred thousand service documents annually, a release for historical periods, and a price-lock clause for the contract term. The final value was three point six million dollars, a seventy per cent reduction from opening. The case file is on our case studies index.

What the settlements share

Across all six matters, the path from opening claim to settlement followed a similar structural arc. The opening position was anchored on a per-user reading of an integration whose chargeable surface was actually documents, not users. The defensive position rebuilt the integration topology, measured the document flow, and reclassified the chargeable surface under the Digital Access schedule. The remedy was usually a Digital Access conversion or a contractual amendment that fixed the buyer’s position for the contract term. The methodology for arriving at the rebuild is detailed in our license compliance pillar and in the audit response sequence article.

The negotiation arithmetic

Across the six matters, the unweighted average reduction from opening claim to settlement was seventy-one per cent, slightly above the firm-wide sixty-eight per cent average. The dispersion was modest: the smallest reduction was the EDI matter at sixty-two per cent, the largest the RPA matter at seventy-nine per cent. The reductions tracked with the strength of the contractual argument, not the size of the integration topology or the volume of documents in flow.

The implication for buyers running active indirect-access exposure is that the contractual reading is usually the controlling lever. The technical defence work — topology rebuild, document measurement, user-population correction — is necessary but not sufficient. The settlement is reached when the contractual reading is robust enough to anchor the negotiation. The SAP indirect-access advisory service covers the contractual work in detail, and the contract negotiation service covers the post-audit settlement architecture.

What the settlement usually does not include

Three things that buyers sometimes expect but that the settlements rarely deliver: a cash refund for prior overpayments, a contractual admission by SAP of error, and a public statement. Settlements are forward-looking. They close historical periods with releases, fix the chargeable surface for the contract term, and protect the buyer against re-opening of the matter. They do not, in our experience, reverse positions that the buyer paid for in prior years even where the buyer-side reading would have supported a refund.

If you are running an active indirect-access matter and the opening claim is in the range these examples describe, the first conversation should be about the contractual posture, not the document count. The numbers fall out of the contractual reading, not the other way round.

The economic case for the conversion

Across our $180M+ in client savings on SAP matters, indirect-access settlements account for the largest single share. The economic pattern is consistent: the conversion to Digital Access trades open-ended exposure under the pre-2018 indirect-use clause for measured, capped, and price-locked exposure under the document model. The conversion is rarely free, but the conversion economics on integration topologies of any meaningful scale tend to favour the buyer over a four-to-six year horizon. The indirect-to-digital migration article covers the conversion economics in detail.