Knowledge base

How a Kazakhstan company buys software

How a Kazakhstan company buys software — selection, terms and a business quote in Kazakhstan.

From task to specification

Start with employee roles and required functions, then select product, edition, term and quantity. “Office” or “Adobe” alone is insufficient for procurement. Match product name, SKU, organization and usage period in the specification.

Request and quote

Provide BIN, an administrator contact and delivery requirements. Ask for separate license, engineering and support items. For starting prices, clarify minimum scope, VAT treatment and validity date. The supplier confirms availability and timing; a catalogue page does not prove stock availability.

Documents before payment

Agree the contract or supply terms, invoice and license-evidence method. Closing documents and e-invoices depend on the transaction and accounting requirements: discuss them beforehand. IT Technology’s catalogue states VAT exempt based on customer-provided information; the status is confirmed before contracting.

Entitlement versus a key

An activation code alone does not describe a company’s right to use software. Program, organization, quantity and restrictions matter. Retain rights-confirmation emails or documents alongside the contract. Do not send account passwords through a website form or to a procurement employee.

After delivery

Verify seat assignments and required functions, then record renewal dates. Set implementation acceptance criteria: user login, data access, mail delivery or backup recovery. Tender requirements and authorization letters are checked separately; participation or permissions are not claimed in advance.

A procurement control check

Compare the request, commercial quote and invoice. Names, quantities, periods and organization should match. If an edition changes, request an updated specification instead of relying on an explanation in correspondence. For multiple products, ensure a total price does not hide different terms and renewal conditions.

Assign the electronic-rights recipient and contract owner. Retain delivery evidence in the company archive rather than only an employee’s personal mailbox. If accounting requires a particular acceptance or e-invoice format, establish feasibility before payment. An audit needs documents linked to installations: where the product is used and which entitlement covers it.

Before deciding

This guide helps prepare questions; it does not replace the supplier’s current specification. Plan contents and program rules can change. Confirm the exact edition and entitlement at the order date, and verify implementation against agreed criteria.

Microsoft 365 · Licensing · Implementation and support

Rights holder terms

IT TECHNOLOGY · ALMATY

Find a solution

Tell us your task — we’ll send a quote within one business day. Send an email ↗