SAP exposure in Ukraine turns on the same global levers — named-user classification, the annual LAW measurement, indirect/digital access and the S/4HANA conversion — applied under Ukrainian contract law and its data-protection regime. This page covers the SAP climate in Ukraine, the contract context, and the firms that defend the pair — listed alphabetically with pros and cons, not ranked.
Published 25 November 2025 · Last reviewed 19 February 2026
SAP is established across Ukraine in agriculture and agribusiness, metals and mining, energy, manufacturing, retail and banking. It measures customers annually rather than launching surprise raids: the License Administration Workbench (LAW) and the System Measurement Program produce a yearly self-declaration that SAP, often through a regional or CEE partner, reviews. 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 touch SAP data and trigger licensing under the document-based Digital Access model.
Many Ukrainian estates are operating under disruption and changed footprints, which makes an accurate, current entitlement position more valuable, not less — user counts, decommissioned systems and relocated operations all change the measurement. The dominant strategic pressure remains the ECC-to-S/4HANA migration, which forces a re-licensing conversion and re-opens classification and digital-access questions. The traps are over-classified named users, unquantified indirect access, engines on the wrong metric, and treating the annual LAW submission as clerical rather than a position that can be reviewed and corrected before filing.
The named-user, indirect-access and S/4HANA mechanics that decide the number — the same worldwide, enforced here under the Ukrainian 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.
Reviews are often run via a regional SAP partner; data-residency and PDPL expectations shape data handling.
Ukraine is a civil-law jurisdiction whose contract framework rests on the Civil and Commercial Codes; disputes are heard before the commercial courts or, where agreed, in international arbitration. An SAP measurement is governed by the contract — the SAP software licence agreement, its order forms and price list — rather than by any statutory software-audit regime; the agreement sets the measurement obligation, the named-user definitions and engine metrics, and frames indirect or digital access. SAP agreements for the region are commonly governed by foreign law (often Irish, German or English) and routed through a regional entity, so practical leverage is commercial and contractual.
The Law of Ukraine on Personal Data Protection governs how personal and employee-linked data is processed, and as an EU candidate state Ukraine is progressively aligning its data-protection framework with the GDPR — both bear on collecting user and usage data for a measurement. A well-advised buyer aligns data collection with the applicable rules and uses the contract terms and measurement calendar to keep a partner-led review proportionate, taking account of any operational changes to the estate. This is information, not legal advice.
This page is general information about the Ukraine 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.
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.
Central- and Eastern-European SAM and audit-support boutique with its own SAM tooling, covering Adobe, IBM, Microsoft, Oracle, SAP and VMware.
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.
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.
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.
Indicative SAP matters in Ukraine 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, often via the regional partner that ran the review. What moves the number is reclassifying over-assigned named users, removing decommissioned or relocated systems from the count, quantifying and containing indirect / digital access before SAP prices it, and treating an S/4HANA move as a negotiation. Outcomes vary widely by estate; any figure a firm cites is self-reported and indicative until independently verified.
Up to the SAP hub and the Ukraine hub, across to sibling markets and services.
SAP measures rather than raids: an annual LAW self-declaration is reviewed each year, often via a regional or CEE SAP partner, and the contract reserves a formal audit right. 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 can. The Law of Ukraine on Personal Data Protection — progressively aligning with the GDPR as part of EU accession — governs how personal and employee-linked data is processed, which bears on collecting user data for a measurement. This is information, not legal advice.
It can materially. Decommissioned systems, reduced user counts and relocated operations all change a LAW measurement, so an accurate current entitlement position is worth establishing before filing. The firms here advise on the licensing position, not on local law.
No. Every firm covering SAP in Ukraine is listed in neutral alphabetical order with balanced pros and cons. Independence is shown as a pro and a reseller or vendor-partner relationship as a con, never a ranking or a recommendation.
Tell us your situation and we route your brief to firms covering SAP in Ukraine. 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.