SAP exposure in Austria turns on the same global levers — named-user classification, the annual LAW measurement, indirect/digital access and the S/4HANA conversion — applied under Austrian contract and data law. This page covers the SAP climate in Austria, the contract context, and the firms that defend the pair — listed alphabetically with pros and cons, not ranked.
Published 7 May 2026 · Last reviewed 12 May 2026
SAP measures its customers annually rather than launching surprise audits: the License Administration Workbench (LAW) and the System Measurement Program produce a yearly self-declaration that SAP reviews. In Austria — a strong SAP market, with the publisher’s DACH heartland next door and a dense base of manufacturing, industrial and public-sector users — the recurring exposure is named-user classification (Professional versus Limited Professional versus Employee), engine and package metrics, and above all indirect (now “digital”) access, where third-party systems or bots touch SAP data and trigger licensing under the document-based Digital Access model.
The dominant pressure is the migration from ECC to S/4HANA, which forces a re-licensing conversion (contract conversion versus product conversion) and re-opens classification and digital-access questions at the same time. The traps are over-classified named users, indirect access that was never licensed or quantified, engines measured on the wrong metric, and treating the annual LAW submission as a clerical task rather than a position that can be reviewed and corrected before it is filed.
The named-user, indirect-access and S/4HANA mechanics that decide the number, the same worldwide but enforced under the Austrian contract.
SAP users are classified (Professional, Limited Professional, Employee); over-classification is the most common cost.
Third-party systems or bots touching SAP data trigger licensing under the document-based Digital Access model.
The License Administration Workbench self-declaration is reviewed yearly; it can be corrected before filing.
Engine and package metrics (by document, order, spend or records) sit alongside named users.
Migration forces a re-licensing conversion and re-opens classification and digital-access questions.
Users assigned Professional licences when a cheaper type fits are a recurring, avoidable cost.
Austria is a civil-law jurisdiction, and an SAP measurement is governed by the contract — the SAP software licence agreement and its order forms and price list — rather than by any statutory software-audit regime. The agreement sets out the measurement obligation, the named-user definitions and the engine metrics, and frames how indirect or digital access is treated. Under the Austrian Civil Code (ABGB), limitation periods vary by claim type, with a general long period of thirty years and a shorter three-year period applying to many ordinary claims, so the contract terms and the facts determine reach; local advice on time bars should be taken.
The General Data Protection Regulation, together with Austria’s Datenschutzgesetz (DSG) and the supervision of the Datenschutzbehörde, governs how personal and employee-linked data is processed, so collecting user and usage data for a measurement calls for data minimisation and a clear purpose, with works-council (Betriebsrat) consultation often relevant where employee monitoring is involved. Because an SAP measurement centres on user classification and system data, the privacy footprint is usually limited, but the rules still apply to employee records. This is information, not legal advice.
This page is general information about the Austria legal and procurement environment and SAP’s audit 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.
German independent licensing boutique covering Microsoft, Oracle, SAP, IBM and VMware across the DACH region, fluent in German contract and works-council practice.
German vendor-neutral consultancy with a SAM and audit-defense practice across the DACH region, fluent in German contract and works-council practice.
Central- and Eastern-European SAM and audit-support boutique with its own SAM tooling, covering Adobe, IBM, Microsoft, Oracle, SAP and VMware.
Independent SAP-licensing specialist covering audit defense, indirect/digital access, S/4HANA conversion and renewal negotiation, with decades of SAP experience.
Buyer-side independent licensing advisory with one of the broadest multi-vendor footprints, covering Oracle, Microsoft, SAP, IBM, Broadcom, Salesforce, ServiceNow and Workday.
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 Austria resolve through the annual measurement and the S/4HANA conversion, not in court: a finding is corrected in the LAW submission, re-classified, or folded into the next contract or conversion. What moves the number is reclassifying over-assigned named users to the right type, quantifying and containing indirect / digital access before SAP prices it, checking engine and package metrics against actual consumption, and treating an S/4HANA move as a negotiation rather than a forced conversion. Timing against SAP’s quarter and fiscal year-end is part of the leverage.
Indicative outcomes vary widely by estate and are not scored here: independent advisers report materially smaller measurement and conversion bills where classification and digital access are reconciled in advance, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the SAP hub and the Austria hub, across to sibling markets and services.
SAP measures rather than raids: an annual LAW self-declaration is reviewed each year, and the contract reserves a formal audit right. In Austria the recurring exposure is named-user classification, engine metrics and indirect / digital access. The position can be corrected before filing. This is information, not legal advice.
Mainly by named user (Professional, Limited Professional, Employee and others) plus engine and package metrics measured by documents, orders, spend or records. Indirect or digital access by third-party systems is licensed under the document-based Digital Access model.
It is when non-SAP systems, bots or interfaces create or read SAP data without a named user logging in. SAP’s Digital Access model licenses this by document type, and unquantified indirect access is one of the largest sources of unexpected SAP exposure.
The contract — the SAP licence agreement, order forms and price list — rather than any statutory audit regime. The ABGB sets limitation periods, and the GDPR with the DSG governs employee data, with works-council consultation often relevant. This is information, not legal advice.
No. Every firm covering SAP in Austria is listed in neutral alphabetical order with balanced pros and cons. Independence is shown as a pro and a reseller or vendor-side relationship as a con, never a ranking or a recommendation.
Tell us your situation and we route your brief to firms covering SAP in Austria. 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.