Registry entry

Kazakhstan Limited Liability Partnership (ТОО) State Registration (Single Resident Founder)

Register a limited liability partnership (Товарищество с ограниченной ответственностью, ТОО — Kazakhstan's LLC-equivalent legal form) with the state registration service for legal entities, administered by the Ministry of Justice of the Republic of Kazakhstan. Modelled from Appendix 2 to the Rules for rendering the state service "State registration of legal entities, accounting registration of their branches and representative offices," an Order of the Acting Minister of Justice of the Republic of Kazakhstan (No. 66, 29 May 2020), published in full, unauthenticated, on the Ministry of Justice's own official legal-information system, ИПС «Әділет». The Appendix 2 application form covers the founding entity's organisational form and name variants, the appointed director's identity and appointment-decision particulars, founder and beneficial-owner disclosure, the registered address, principal economic-activity code, headcount, VAT-registration election, and an optional bundled bank-account-opening/mandatory-employee-accident-insurance request. This schema scopes to a single Kazakhstan-resident natural-person founder who is also the sole beneficial owner — the most common single-founder ТОО formation — and discloses rather than silently omits: non-resident founders, corporate (legal-entity) founders, multiple founders, a beneficial owner distinct from the founder, and the branch/representative-office variants of the same form. It does not submit anything or imply government endorsement.

Registry entry

kz/moj/state-registration-limited-liability-partnership

Jurisdiction
Kazakhstan · national
Version
1.0.0
Verification
draft

Authoritative source Приложение 2 к Правилам государственной услуги "Государственная регистрация юридических лиц, учетная регистрация их филиалов и представительств" (Order of the Acting Minister of Justice of the Republic of Kazakhstan No. 66, 29 May 2020, registered with the Ministry of Justice 29 May 2020 No. 20771)

Machine access

Registry catalog
registry/index.jsonone record per schema id

Field reference

56 fields, read from the published schema.json, with names, types, requiredness, and validation as the document states them. The live government form remains the authoritative source.

Fields

  • entityType enum required

    Which of the three organisational forms this application registers, per the Rules' own title (state registration of legal entities, accounting registration of their branches and representative offices). This schema scopes primarily to legal_entity (a newly-formed ТОО); the other two values are disclosed for completeness of the enum, not separately modelled below.

    enum: legal_entity | branch | representative_office
  • organizationalLegalForm string required

    The organisational-legal form of the entity being registered. This schema's own scope is the Товарищество с ограниченной ответственностью (ТОО, limited liability partnership); the source form itself presents this as a live directory dropdown with no published closed value list, so it is modelled as a free string rather than an invented enum.

    length: 1–100
  • companyNameKazakh string required

    The company's name in Kazakh, without the organisational-legal-form (ОПФ) suffix.

    length: 1–300
  • companyNameRussian string required

    The company's name in Russian, without the organisational-legal-form suffix.

    length: 1–300
  • companyNameEnglish string optional

    Optional English-language rendering of the company name, including the organisational-legal-form suffix (e.g. LLP).

    length: 0–300
  • companyShortNameKazakh string optional

    Optional abbreviated Kazakh-language name.

    length: 0–150
  • companyShortNameRussian string optional

    Optional abbreviated Russian-language name.

    length: 0–150
  • companyShortNameEnglish string optional

    Optional abbreviated English-language name, including the organisational-legal-form suffix.

    length: 0–150
  • directorFullName string required

    Full name (surname, first name, patronymic if any) of the person appointed as the entity's head/director (руководитель).

    length: 1–200classification: pii
  • directorCitizenship string required

    The director's country of citizenship.

    length: 1–100classification: pii
  • directorIdentityDocumentNumber string required

    The number (and series, if the document carries one) of the director's identity document.

    length: 1–50classification: sensitive-pii
  • directorIdentityDocumentIssuer string required

    The authority that issued the director's identity document.

    length: 1–200classification: sensitive-pii
  • directorIdentityDocumentValidUntil date required

    The expiry date of the director's identity document.

    classification: sensitive-pii
  • directorIin string required

    The director's 12-digit Individual Identification Number (ИИН), issued under Kazakhstan's State Population Register Law.

    patternclassification: sensitive-pii
  • directorAppointmentDecisionNumber string required

    The number of the founder's decision appointing the director.

    length: 1–50
  • directorAppointmentDecisionDate date required

    The date of the founder's decision appointing the director.

  • founderIin string required

    The 12-digit Individual Identification Number of the sole Kazakhstan-resident natural-person founder. Scoped to a single resident individual founder; non-resident, corporate, and multi-founder cases are out of scope (see the document's own VERIFICATION.md).

    patternclassification: sensitive-pii
  • founderFullName string required

    Full name of the sole founder.

    length: 1–200classification: pii
  • founderContributionAmountTenge number required

    The founder's contribution to the charter capital, in Kazakhstani tenge.

    range: 1–∞
  • founderOwnershipSharePercent number required

    The founder's percentage share of the charter capital. For a sole founder this is ordinarily 100.

    range: 0–100
  • usesModelCharter boolean required

    Whether the entity operates on the basis of the state's standard model charter (типовой устав) rather than an individually drafted charter.

  • beneficialOwnerFullName string required

    Full name of the beneficial owner, per the form's own definition (a natural person who directly or indirectly owns more than 25% of participation shares, or otherwise controls the entity). Modelled as a single beneficial owner, the sole founder in the ordinary single-founder case; a beneficial owner distinct from the founder is out of scope.

    length: 1–200classification: pii
  • beneficialOwnerCitizenship string required

    The beneficial owner's country of citizenship.

    length: 1–100classification: pii
  • beneficialOwnerIdentityDocumentData string required

    The beneficial owner's identity-document particulars (type, number, issuing authority).

    length: 1–300classification: sensitive-pii
  • beneficialOwnerIin string optional

    The beneficial owner's IIN, if they have one, or their foreign-national identification number in their country of residence otherwise. The source form itself marks this '(при наличии)' — 'if available'.

    patternclassification: sensitive-pii
  • beneficialOwnerDateOfBirth date required

    The beneficial owner's date of birth.

    classification: pii
  • beneficialOwnerResidentialAddress string required

    The beneficial owner's place of residence.

    length: 1–400classification: pii
  • beneficialOwnerOwnershipSharePercent number required

    The beneficial owner's percentage share of the charter capital or, for a joint-stock structure, of placed shares.

    range: 0–100
  • locationType enum required

    Whether the entity's registered location is property it owns or property it leases.

    enum: owned_property | leased_property
  • addressRegion string required

    The region (область) of the entity's registered address.

    length: 1–150
  • addressCity string required

    The city, district, or rural district of the entity's registered address.

    length: 1–150
  • addressSettlement string optional

    The village or settlement of the entity's registered address, when applicable.

    length: 0–150
  • addressStreet string required

    The street or avenue of the entity's registered address.

    length: 1–200
  • propertyType enum required

    Whether the registered address is a standalone premises (помещение) or a building (здание).

    enum: premises | building
  • houseNumber string required

    The house number of the entity's registered address.

    length: 1–20
  • buildingNumber string optional

    The building/corpus number, when the address includes one.

    length: 0–20
  • blockNumber string optional

    The block number, when the address includes one.

    length: 0–20
  • apartmentNumber string optional

    The apartment/office/suite number, when applicable.

    length: 0–20
  • postalCode string required

    The 6-digit postal code of the entity's registered address.

    pattern
  • contactPhoneNumber string required

    A contact telephone (or fax) number for the entity.

    length: 1–30
  • emailAddress string required

    The entity's contact email address.

    patternlength: 0–200
  • mainActivityCode string required

    The entity's principal economic-activity code, per Kazakhstan's General Classifier of Economic Activities (ОКЭД).

    length: 1–20
  • expectedEmployeeCount integer required

    The entity's expected (approximate) number of employees; the form itself requires at least 1.

    range: 1–∞
  • vatRegistration boolean required

    Whether the entity elects to register as a VAT (НДС) payer at the same time as incorporation.

  • openBankAccountAndInsurance boolean required

    Whether the applicant elects to bundle a bank-account-opening request and a mandatory employee-accident-insurance contract with this same registration submission. Gates items 15-18 and 20-22 below.

  • bankName string optional

    The bank at which the account is to be opened, selected from the e-government cabinet's own bank directory; modelled as a free string since no closed value list is published in the form text. Required when openBankAccountAndInsurance is true.

    length: 0–200
  • bankBranch string optional

    The branch of the selected bank at which the account is to be opened. Required when openBankAccountAndInsurance is true.

    length: 0–200
  • accountCurrency enum optional

    The currency of the bank account to be opened. Required when openBankAccountAndInsurance is true.

    enum: KZT | USD | EUR | RUB
  • bankContactPhoneNumber string optional

    A contact telephone number for the bank-account-opening/insurance request. Required when openBankAccountAndInsurance is true.

    length: 1–30
  • executiveBodyType enum required

    Whether the entity's executive body is sole (единоличный, the ordinary case for a single-founder ТОО whose director is that executive body) or collegial (коллегиальный, e.g. a management board).

    enum: sole | collegial
  • executiveBodyName string optional

    The name of the collegial executive body. Required when executiveBodyType is collegial.

    length: 0–200
  • insuranceCompany string optional

    The insurance company selected for the mandatory employee-accident-insurance contract, from the e-government cabinet's own directory; modelled as a free string since no closed value list is published in the form text. Required when openBankAccountAndInsurance is true.

    length: 0–200
  • annualPayrollFundTenge number optional

    The entity's annual payroll fund, in tenge, used to calculate the insurance premium. Required when openBankAccountAndInsurance is true.

    range: 0–∞
  • insurancePeriodStartDate date optional

    The start date of the insurance period. Required when openBankAccountAndInsurance is true.

  • insurancePeriodEndDate date optional

    The end date of the insurance period. Required when openBankAccountAndInsurance is true.

  • consentToUseProtectedInformation boolean required

    The applicant's consent to the registering body's use of information constituting legally protected secrets, held in the relevant information systems, for processing this application.

Verification record

This file is the source-review record for this document version, per the manual-source-review-v1 practice. It documents the provenance of the published fields and states the current verification claim honestly.

Current claim

  • status: draft
  • verification.method: manual-source-review-v1
  • verification.lastVerifiedAt: 2026-07-17

This is a GovSchema Standard Research cycle (GOV-3459, a backlog candidate scouted in parallel with Morocco during the GOV-3454 cycle and delegated as a child issue, authored this cycle). Kazakhstan opens as this registry's 72nd jurisdiction.

Why this candidate

The GOV-3454 cycle scouted three new-jurisdiction candidates in parallel: Morocco (authored that same cycle via ma/maec/evisa-application), Bahrain (confirmed a dead end — every vertical funnels through a unified SSO login or a WAF-gated e-visa), and Kazakhstan. Kazakhstan's own government legal-text publisher, adilet.zan.kz (part of the Ministry of Justice's ИПС «Әділет» system), was found to publish entire Rules-of-service annexes — including the actual application-form text, not just procedure/fee prose — unauthenticated and in full, with no CAPTCHA/WAF/login gate. This is the same class of source strength this registry has repeatedly favoured (e.g. tax.gov.kh for Cambodia, eta.gov.eg for Egypt).

Kazakhstan's other candidate verticals were screened the same cycle and found weak/gated (see GOV-3459's own backlog note, reconfirmed this cycle by re-fetching each cited domain before writing this record):

  • Visa (e-visa.gov.kz/vmp.gov.kz): the application flow loads Google reCAPTCHA. CAPTCHA-gated.
  • Taxes filing (kgd.gov.kz/salyk.kz): actual filing happens in the login+EDS-gated "Taxpayer's Cabinet" (cabinet.salyk.kz). A blank Individual Income Tax Declaration (Form 220.00) is separately published via the same adilet.zan.kz Ministry-of-Finance-order route and is a viable backlog candidate for a future cycle.
  • DMV, Passport, National ID (egov.kz): service pages describe the process in prose, but the actual wizards require portal login plus an EDS/SMS signature; no field structure is visible unauthenticated.

Business Formation — authored this cycle, via the LLC/ТОО state-registration application, Appendix 2 to the Rules for the state service "State registration of legal entities, accounting registration of their branches and representative offices."

Sources examined

Primary source
  • Authority: Министерство юстиции Республики Казахстан (Ministry of Justice of the Republic of Kazakhstan) — official site confirmed at https://www.gov.kz/memleket/entities/adilet.
  • Document — Order of the Acting Minister of Justice of the Republic of Kazakhstan No. 66, 29 May 2020 ("Об утверждении правил оказания государственных услуг в сфере государственной регистрации юридических лиц и учетной регистрации филиалов и представительств"), registered with the Ministry of Justice 29 May 2020 No. 20771.
    • URL (directly retrieved, HTTP 200): https://adilet.zan.kz/rus/docs/V2000020771
    • Access note: the server's TLS certificate chain is missing an intermediate (openssl verify returns code 21, unauthorized certificate); curl -k or any browser that tolerates the chain loads the page fine at HTTP 200. This is a server misconfiguration, not a real access gate — re-confirmed this cycle with a fresh fetch.
    • File identity: full consolidated-legislation HTML page, 682,112 bytes, sha256:f0ccd41a3df5dffef92a96ed0c682c807e4ce728dc1106642e90ea638d03fa27.
    • Structure confirmed: the page publishes numbered Appendices for several distinct state services and process variants sharing the same Rules. Appendix 1 is an output Extract (Выписка) from the National Register of Business Identification Numbers — a produced document, not an input form. Appendix 2 — "Заявление о государственной регистрации субъектов малого и среднего предпринимательства, также на открытие банковского счета и обязательным страхованием работника от несчастных случаев..." — is the genuine 23-item numbered application form this schema models. Appendices 3 and onward cover other registration/branch/representative-office/reorganisation/liquidation variants not modelled here.
    • Extraction method: raw HTML fetched directly (curl -k), decoded as UTF-8, <br>/tag-stripped to plain text, and read in full in Russian. Every one of the form's 23 numbered items was mapped to this schema's fields in item order; no OCR or PDF-rendering step was needed since the source is native text-layer HTML.
External reference
  • IIN (Individual Identification Number) format: confirmed as a 12-digit personal identifier under Kazakhstan's State Population Register Law — a well-documented national convention, not assumed from the form's own underscore-ruled blanks (which carry no digit-count indicator). Modelled as ^[0-9]{12}$ for directorIin, founderIin, and beneficialOwnerIin.

Scope and disclosed boundaries

This schema is deliberately scoped to a single Kazakhstan-resident natural-person founder who is also the sole beneficial owner — the most common single-founder ТОО formation, and the same scoping convention this registry's am/moj/state-registration-limited-liability-company (GOV-3351) schema already established for Armenia's equivalent single-founder LLC form. Explicitly out of scope, and disclosed rather than silently omitted:

  • Multiple founders — item 6 of the source form describes a repeating table of resident founders; only one is modelled.
  • Non-resident founders (item 6.1) and corporate (legal-entity) founders, both resident and non-resident — the source form's own branching for these is not modelled.
  • A beneficial owner distinct from the founder — item 8 is modelled as a single block that, in the ordinary single-founder case, describes the same natural person as the founder.
  • The branch (филиал) and representative-office (представительство) variants of the same form — entityType's own enum discloses these as named values without this schema modelling their (likely different) downstream field requirements.
  • Items 1 (Форма организации) and 2 (Организационно-правовая форма): both are live e-government-cabinet dropdown selections with no published closed value list in the form text itself. entityType is modelled as a disclosed judgment-call enum limited to the three values implied by the Rules' own title; organizationalLegalForm is modelled as a free string, with this schema's own scope (ТОО) documented in its description rather than invented as a closed enum.
  • Items 15/16/20 (bank, bank branch, insurance company selection): each is printed as a "выбор из справочника" (selection from a directory) internal to the live cabinet, with no enumerated list published in the form text; modelled as free strings.
  • Item 10 (Регистрирующий орган): the form's own text states this is auto-derived from the address given in item 9, not an applicant-entered value — disclosed, not modelled as a field.

Conformance fixtures

10 fixtures are committed under conformance/kz/moj/state-registration-limited-liability-partnership/1.0.0/: 2 valid submissions (0 errors each — one minimal, required-fields-only submission with the bank/insurance bundle declined; one fuller submission with every optional field populated and the bank/insurance bundle accepted, exercising every requiredWhen branch) and 8 mutation-control fixtures (each expected to raise exactly 1 error): a missing required companyNameRussian, an invalid directorIin pattern (wrong digit count), an invalid postalCode pattern, an invalid emailAddress pattern, an invalid entityType enum value, a missing bankName when openBankAccountAndInsurance is true, a missing executiveBodyName when executiveBodyType is collegial, and a founderOwnershipSharePercent above the valid 0-100 range. All 10 were checked with a from-scratch, throwaway Node mock validator implementing this schema's own required/requiredWhen/validation rules (not committed, per this registry's established per-cycle practice). Both tools/validate.mjs and tools/validate-ajv.mjs pass at 527/527 across the full registry with this schema added.

Known gaps

  • Kazakhstan's remaining verticals — DMV, Passport, Visa, Taxes, and National ID — are open backlog. Visa is confirmed CAPTCHA-gated and DMV/Passport/National ID are confirmed login+EDS-gated this cycle (see "Why this candidate" above); Taxes has a disclosed, ready-to-scope adilet.zan.kz-sourced backup candidate (Form 220.00).
  • The multi-founder, non-resident-founder, and corporate-founder paths are a disclosed, open backlog candidate for a future minor-version cycle — see "Scope and disclosed boundaries" above.
  • The branch and representative-office variants of the same Rules (also filed via this same web page's other appendices) are a disclosed, open backlog candidate.

Verification method assessment

manual-source-review-v1 — a human/agent read the primary source directly and transcribed its fields. No automated re-verification tooling exists yet for this schema; nextReviewBy is set 6 months out per the practice's default cadence.

View the raw record (VERIFICATION.md)

Version history

  • 1.0.0 draft latest this page has verification record schema.json

Independent and non-affiliated

GovSchema is an independent, open-source project. This reference is not produced, reviewed, or endorsed by Министерство юстиции Республики Казахстан (Ministry of Justice of the Republic of Kazakhstan) or any government. The authoritative source is always the live government form and its official instructions.