Danish organisations facing an SAP licence measurement are tested on two things at once: the LAW/USMM named-user and engine count, and indirect/digital access where non-SAP systems touch SAP data. This page covers the SAP climate in Denmark, the local legal and data context, and the firms that defend the pair, listed alphabetically with pros and cons, not ranked.
Last reviewed: 5 June 2026
SAP runs an established licence-measurement programme in Denmark, where a deep installed base across manufacturing, shipping and logistics, pharmaceuticals and life sciences, the public sector and a strong mid-market creates broad exposure to named-user classification and engine metrics. Globally roughly 62–63% of organisations report a software audit within any twelve-month period and around 52% now bring outside defense help; Danish SAP estates moving toward S/4HANA sit squarely in scope as conversion forces a re-measurement.
The two findings that dominate are named-user over-classification — users assigned Professional licences who only need a lighter type — and indirect or digital access, where orders, data or documents flow into SAP from non-SAP systems. SAP’s shift to the digital-access document model changes how that exposure is counted, and an S/4HANA conversion is the moment it usually surfaces.
The LAW, named-user and indirect-access mechanics that decide the number, the same worldwide but enforced locally.
SAP classifies every user (Professional, Limited Professional, Employee) with different prices; over-classification is the most common cost leak.
Non-SAP systems reading or writing SAP data can trigger licence demand; the digital-access document model recasts how this is counted.
SAP’s License Administration Workbench and USMM tools aggregate the estate; what they report depends on classification hygiene maintained by the customer.
Package and engine licences (payroll records, orders, revenue) scale by business metric and are easy to exceed as volumes grow.
Moving to S/4HANA forces a re-measurement and a digital-access decision; it is the pivotal negotiation and exposure moment.
Findings convert into a true-up or an expanded agreement; an independent licence position changes that conversation.
Denmark is a civil-law jurisdiction. Contract is governed by the Danish Contracts Act (Aftaleloven), and the general limitation period under the Limitation Act (Forældelsesloven) is three years, with a longer ten-year long-stop — shorter at the front end than many markets, which can constrain how far back SAP reaches, subject always to the SAP agreement and its choice-of-law clause. Danish commercial culture favours negotiated, proportionate settlement over litigation.
Data handover is governed by the GDPR together with the Danish Data Protection Act (Databeskyttelsesloven) and supervised by Datatilsynet, the Danish Data Protection Agency. Where measurement data touches employee information, transferring it to a non-EU reviewer raises lawful-basis and transfer questions a well-advised buyer can use to shape scope and timing, and Danish organisations commonly insist on EU processing. Public-sector buyers procure heavily through SKI framework agreements, which sets expectations of orderly, documented process.
This page is general information about the Denmark 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.
Independent multi-vendor licensing practice covering IBM, Microsoft, Oracle, SAP and Tier-2 publishers, with a stated 100% impartial, buyer-side model.
Independent SAP-licensing specialist covering audit defense, indirect/digital access, S/4HANA conversion and renewal negotiation, with decades of SAP experience.
Independent multi-vendor SAM managed-service provider with an audit-readiness focus, serving large multinationals from a London base since 2010.
Buyer-side independent licensing advisory with one of the broadest multi-vendor footprints, covering Oracle, Microsoft, SAP, IBM, Broadcom, Salesforce, ServiceNow and Workday.
Independent SAP advisory focused on the licensing roadmap, audit defense and negotiation, including indirect/digital access and S/4HANA conversion.
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 Denmark typically resolve through negotiated settlement, usually folded into an S/4HANA conversion or a renewed agreement rather than litigation, in keeping with a consensus-driven commercial culture. 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 Denmark hub, across to sibling markets and services.
SAP uses the License Administration Workbench (LAW) and USMM to aggregate named-user classifications and engine metrics across the estate. The report reflects the classification hygiene the customer maintains, which is why an independent re-measurement before SAP’s read lands is the core of any defense. This is information, not legal advice.
It is licence demand arising when non-SAP systems read or write SAP data — for example an e-commerce front end creating SAP orders. SAP’s digital-access model counts this by document type rather than by user. It is the most contested area of SAP licensing and usually surfaces during an S/4HANA conversion.
The general limitation period under the Danish Limitation Act (Forældelsesloven) is three years with a ten-year long-stop, but SAP’s reach is also shaped by the agreement terms and the audited period depends on its choice-of-law clause. Confirm the position for your specific contract with qualified Danish counsel.
Only within the GDPR and the Danish Data Protection Act (Databeskyttelsesloven), supervised by Datatilsynet. Transferring measurement or employee-linked data outside the EU raises lawful-basis and transfer questions, and Danish organisations commonly insist on EU processing — a procedural lever over scope and timing.
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.
Tell us your situation and we route your brief to firms covering SAP in Denmark. 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.