US organisations facing an SAP licence measurement are tested on two fronts at once: the LAW/USMM named-user and engine count, and indirect/digital access where non-SAP systems touch SAP data — the issue at the centre of the landmark Diageo and AB InBev disputes. This page covers the SAP climate in the US, the local legal context, and the firms that defend the pair, listed alphabetically with pros and cons, not ranked.
Last reviewed: 5 June 2026
The United States is SAP’s largest market outside Germany, with a vast installed base across manufacturing, consumer goods, energy, retail and financial services. Globally roughly 62–63% of organisations report a software audit within any twelve-month period and around 52% now bring outside defense help; large US SAP estates, many mid-way through S/4HANA programmes, carry concentrated named-user and digital-access exposure.
The two dominant findings are named-user over-classification and indirect/digital access. Indirect access drew global attention through US-linked litigation and SAP’s response — the digital-access document model — which recast how third-party system access to SAP data is licensed. An S/4HANA conversion is the moment both usually surface, and US buyers typically have the negotiating scale to reshape the commercial terms when they prepare early.
The LAW, named-user and indirect-access mechanics that decide the number, the same worldwide but enforced locally.
SAP prices users by type (Professional, Limited Professional, Employee); assigning richer types than needed is the most common over-spend.
Third-party systems touching SAP data can create licence demand; the digital-access document model changes the count and was central to US-linked disputes.
SAP’s measurement tools aggregate the estate; their output depends on the classification discipline the customer maintains.
Package and engine licences scale by business volume (orders, payroll records, revenue) and drift past entitlement as the business grows.
RISE with SAP and S/4HANA conversions force re-measurement and a digital-access decision — the pivotal exposure and negotiation moment.
Findings convert into a true-up or an expanded deal; an independent licence position resets that conversation.
The United States is a common-law system in which software licences are governed by contract under the law of the chosen state (frequently New York, California or Delaware), with the Uniform Commercial Code informing commercial dealings. Limitation periods for written-contract claims are set state by state and commonly run four to six years, subject to the SAP agreement’s terms and choice-of-law and choice-of-forum clauses. US disputes are more likely than in many markets to involve litigation posture, which itself shapes settlement leverage.
There is no single federal data-protection statute equivalent to the GDPR, but state privacy laws — led by the California Consumer Privacy Act as amended by the CPRA, and a growing set of comparable state laws — govern how employee and personal data is handled during a measurement. Where measurement data touches personal information, those regimes and the company’s own data-handling commitments shape what may be shared with an auditor and on what terms.
This page is general information about the United States legal and procurement environment and SAP’s licensing practices, not legal advice for your situation. SAP’s program is described factually; figures are labelled indicative.
Listed alphabetically with balanced pros and cons — a directory, not a ranking.
Vendor- and tool-agnostic licensing boutique working across Microsoft, Oracle, SAP, Salesforce and IBM. Engagements run buyer-side, from compliance position through negotiation and ongoing optimization.
Vendor-agnostic licensing boutique founded by ex-vendor auditors. Does not resell, implement or conduct audits, focusing solely on buyer-side Oracle, SAP, IBM and Microsoft defense and negotiation.
Independent multi-vendor licensing practice covering IBM, Microsoft, Oracle, SAP and Tier-2 publishers, with a stated 100% impartial, buyer-side model.
Buyer-side independent licensing advisory with one of the broadest multi-vendor footprints, covering Oracle, Microsoft, SAP, IBM, Broadcom, Salesforce, ServiceNow and Workday.
Independent IT sourcing and negotiation advisor with no vendor ties, focused on large-enterprise deals across SAP, Microsoft, Oracle, Salesforce, ServiceNow and Workday.
DEMO — listings are compiled from public information and labelled demo until the verified registry is live. Firms are listed alphabetically, never ranked. Independence is shown as a pro; a reseller, Big-Four or vendor-side audit relationship is shown as a con — each a factual trade-off for you to weigh.
SAP matters in the US typically resolve through negotiated settlement — often converted into an S/4HANA or RISE commitment — rather than litigation, though a credible litigation posture can strengthen the buyer’s hand. What moves the number is a clean independent re-measurement: user types reclassified to actual need, indirect/digital access scoped and, where advantageous, moved to the document model, engine metrics reconciled, and timing aligned to SAP’s quarter and fiscal year end.
Indicative outcomes vary widely by estate and are not scored here: independent firms report meaningful reductions where user classification is corrected or an indirect-access assertion is reframed, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the SAP hub and the United States hub, across to sibling markets and services.
Both US-linked disputes turned on whether third-party systems accessing SAP data created additional licence demand. They pushed SAP to introduce the digital-access document model, which licenses certain third-party access by document type rather than by user. It remains the most contested area of SAP licensing. This is information, not legal advice.
SAP uses LAW and USMM to aggregate named-user classifications and engine metrics across the estate. Because the output reflects the customer’s classification hygiene, an independent re-measurement before SAP’s read lands is central to any defense, especially ahead of an S/4HANA or RISE conversion.
Limitation periods for written-contract claims are set state by state and commonly run four to six years, but the audited period and back-charges depend on your SAP agreement and its choice-of-law clause. Confirm the position for your specific contract with qualified US counsel.
No. This is a directory, not a ranking. Firms are listed in neutral alphabetical order with balanced pros and cons. Independence is shown as a pro; a reseller or vendor-side tie as a con — each a factual trade-off for you to weigh.
Yes. The directory and the matching service are free for buyers. We publish no prices or fees and take no money from software publishers.
Tell us your situation and we route your brief to firms covering SAP in the US. The directory and matching are free for buyers, no vendor ever sees your brief, and no firm is recommended over another.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.