Organisations in Kazakhstan dealing with SAP are tested on two things at once: how every user is classified — Professional, Limited Professional or Employee, each priced differently — and whether non-SAP systems reading or writing SAP data have triggered indirect or digital-access demand. This page covers the SAP climate in Kazakhstan, the local legal and data context, and the firms that cover the pair, listed alphabetically with pros and cons, not ranked.
Published 20 March 2026 · Last reviewed 15 April 2026
SAP is deployed across Kazakhstan’s oil, gas and mining sector, banking and financial services, telecommunications, utilities, and the public sector. With roughly 62–63% of organisations reporting a software review within any twelve-month window globally and around 52% now bringing outside help, Kazakh SAP estates — some mid-conversion to S/4HANA — are within scope, with global independents and regional advisers covering the market. These global figures are indicative and not specific to Kazakhstan.
Kazakh SAP reviews turn on the same traps as elsewhere: named-user over-classification is the most common cost leak; indirect or digital access from non-SAP systems can recast licence demand under the document-based model; SAP’s LAW and USMM tools report only as well as classification hygiene allows; and an S/4HANA conversion forces a re-measurement and a digital-access decision at once — the pivotal exposure and negotiation moment.
The named-user, indirect-access and S/4HANA mechanics that decide the number — the same worldwide, 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.
Kazakhstan is a civil-law jurisdiction. Contract and limitation are governed by the Civil Code, under which the general limitation period is three years — subject always to the SAP agreement’s terms and its choice-of-law and dispute-resolution clauses, which for global vendors are frequently foreign. Software is protected under the Law on Copyright and Related Rights. The audited period and any back-charges depend on the specific contract; confirm the position with qualified Kazakh counsel.
Data handling is governed by the Law on Personal Data and its Protection, which includes a requirement to store the personal data of Kazakh citizens on servers located in Kazakhstan, overseen by the authorised data-protection body under the Ministry of Digital Development. The data-localization requirement and cross-border transfer rules for deployment or employee-linked measurement data are points a well-advised buyer can use to shape review scope, timing and where measurement data is processed. This is general information about the Kazakh environment, not legal advice.
This page is general information about the Kazakhstan 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.
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.
SAP matters in Kazakhstan typically resolve through negotiated settlement rather than litigation, with SAP preferring to convert findings into a true-up, an S/4HANA conversion or an expanded agreement. What moves the number is a clean independent named-user re-classification, a precise indirect/digital-access position, evidence from a properly maintained LAW/USMM baseline, sequencing the S/4HANA decision deliberately, and timing the conversation against SAP’s quarter and 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 right-sized, but any figure a firm cites is self-reported and indicative until independently verified.
Up to the SAP hub and the Kazakhstan hub, across to sibling markets and services.
It is licence demand triggered when non-SAP systems read or write SAP data — for example a portal or third-party application touching SAP records. SAP’s document-based digital-access model recasts how this is counted, and scoping it precisely is central to controlling exposure. This is information, not legal advice.
It forces a re-measurement of the estate and a digital-access decision at the same time, which makes it the pivotal negotiation and exposure moment. Sequencing the conversion deliberately, with an independent licence position in hand, changes the conversation.
The Civil Code sets a general three-year limitation period, but SAP’s reach is shaped primarily by the contract, which for global vendors is often governed by foreign law. Confirm the position for your specific agreement with qualified Kazakh counsel.
Under the Law on Personal Data and its Protection, which requires the personal data of Kazakh citizens to be stored on servers in Kazakhstan. Cross-border transfer of deployment or employee-linked measurement data raises lawful-basis and localization questions a buyer can use to shape review scope and where data is processed.
No. Every firm covering SAP in Kazakhstan is listed in neutral alphabetical order with balanced pros and cons, never a ranking or a recommendation.
Tell us your situation and we route your brief to firms covering SAP in Kazakhstan. The directory and matching are free for buyers, no vendor ever sees your brief, and no firm is favoured over another.
Our weekly dispatch on vendor audit programs, regional developments and one buyer move. Subscribe to The Licensing Radar.