Kazakhstan Judicial Cabinet Translated Document Upload Guide
A Kazakhstan Judicial Cabinet translated document upload can fail even when the translation itself is accurate. The practical problem is usually the electronic packet: the wrong case language, one oversized combined PDF, an attachment count that does not match the pleading, an unreadable scan, or a filename that describes something different from the document inside.
This guide explains how to prepare translated pleadings and evidence for Kazakhstan’s ordinary civil courts through Судебный кабинет, also called Сот кабинеті. It does not cover the separate AIFC Court system, arbitration, legal strategy, or the full process of starting a civil lawsuit.
Key Takeaways
- Use the language of the proceedings. Translate a foreign-language exhibit into the Russian or Kazakh language established for the case—not automatically into Russian.
- Upload identifiable document units. Current nationwide technical rules set a 20 MB limit per file and list PDF, DOC/DOCX, and XLS/XLSX formats.
- Make the attachment list control the packet. The uploaded documents must correspond to the listed attachments. Source records and translations need matching exhibit numbers and recognizable filenames.
- EDS does not certify translation accuracy. The filer’s electronic digital signature authenticates the electronic submission; it does not replace translator accountability or a required notarial act.
Who This Guide Is For
This Kazakhstan-wide guide is for foreign individuals, Kazakhstan-based lawyers, self-represented parties, litigation assistants, cross-border companies, and in-house legal teams preparing documents for an ordinary civil case. It is most useful in contract, debt, trade, property, corporate, employment, or damages disputes involving records that were not created in the case language.
Typical language combinations include English into Russian or Kazakh. Chinese, Turkish, German, French, and other source languages may also arise in cross-border cases, but there is no official national ranking of court translation language pairs. The required target language depends on the language of the proceedings.
A common packet includes a statement of claim or response, an attachment list, a state-fee receipt, a power of attorney, contracts and amendments, invoices, acceptance certificates, bank records, correspondence, corporate extracts, message screenshots, each foreign-language source, and its corresponding translation. This guide is especially relevant if you are unsure how to split those materials, name them, scan a notarized translation, or respond to a missing or rejected attachment.
Start With the Case Language, Not the Translator
Article 14 of Kazakhstan’s Civil Procedure Code provides that civil proceedings are conducted in Kazakh, with Russian also officially used, and that the court determines the language of a case based on the language in which the claim was filed. Documents submitted in another language must be accompanied by a translation into the language of the proceedings in the circumstances specified by the Code. The current text is available through Kazakhstan’s official Civil Procedure Code.
This creates an important distinction:
- A pleading should normally be drafted in the established case language.
- A foreign-language contract, invoice, corporate record, email, or other exhibit needs a corresponding version in that language.
- A Russian translation is not automatically correct for a case being conducted in Kazakh.
If the claim has not yet been filed, confirm the intended litigation language with the lawyer or authorized filer before ordering a large translation set. Changing the target language after dozens of exhibits have been translated is an expensive preparation error.
Kazakhstan Judicial Cabinet Translated Document Upload Rules
Kazakhstan’s technical requirements treat file preparation as part of a valid electronic submission. Under the official Technical Requirements for Electronic Documents and Their Circulation in the Court Information System, each separate document must be provided as a separate file and its filename must identify the document.
The current rules provide for:
- PDF for fixed-layout court documents and scans;
- DOC or DOCX for word-processing documents;
- XLS or XLSX for spreadsheets;
- a maximum of 20 MB per file;
- splitting a multi-page document when it exceeds 20 MB;
- files that can be opened, copied, and printed without embedded interactive scripts.
Older instructions and cached screenshots may still mention a 10 MB limit or JPEG attachments. Use the current 20 MB and current-format provisions when preparing a new filing, while also checking the portal’s live validation and any case-specific court direction before a deadline.
Scanning paper and notarized records
The technical rules call for paper records to be scanned at a 1:1 scale, normally in black-and-white or grayscale at 200–300 DPI, while preserving signatures, seals, stamps, and other authentic features. Use color where color itself matters—for example, when annotations, stamps, highlighting, or image content cannot be understood reliably in grayscale.
Compression must not make small text, seal details, handwritten notes, QR codes, or notarial endorsements unreadable. A file below 20 MB can still face a registration problem if court staff cannot read it.
Build the Attachment List Before Naming Files
The technical filing rules require the uploaded files to correspond to the documents identified in the attachment list. Registration may be refused when listed materials are missing, a document is unreadable, its contents do not match its filename, or it is submitted through the wrong section. These grounds appear in the nationwide Rules for Technical Use of Electronic Court Filing.
The safest working method is to prepare one control table before opening the portal:
| List number | Document | Source file | Translation file | Certification |
|---|---|---|---|---|
| 1 | Statement of claim | Not applicable | Claim-Russian.pdf | Signed by filer as required |
| 2 | Contract dated 12 March | Exhibit-02-Contract-English.pdf | Exhibit-02-Contract-Russian.pdf | Record the applicable certification |
| 3 | Invoice 448 | Exhibit-03-Invoice-English.pdf | Exhibit-03-Invoice-Russian.pdf | Record the applicable certification |
| 4 | Email chain | Exhibit-04-Emails-English.pdf | Exhibit-04-Emails-Russian.pdf | Keep dates and sender fields visible |
Whether the source and translation are counted as two attachment entries or described as paired components of one exhibit should be settled in the pleading’s attachment list. Do not list “Contract with translation” and then upload three ambiguously named files without showing how they relate.
Use mirrored exhibit labels
If the source is Exhibit 7, label the translated version “Translation of Exhibit 7.” Keep the same contract date, invoice number, message date range, or corporate-record title in both filenames. For long records, add corresponding page references inside the translation.
A practical filename pattern is:
Exhibit-07-Supply-Contract-English.pdfExhibit-07-Supply-Contract-Russian-Translation.pdf
Avoid filenames such as scan001.pdf, final-new-2.pdf, or translation.pdf. They do not tell a registry employee, judge, lawyer, or opposing party what the file contains.
Should the Source and Translation Be One PDF or Separate Files?
There is no single safe answer for every document because two principles intersect:
- The Judicial Cabinet rules require each separate document to be uploaded as a separate file.
- Kazakhstan’s notarial rules may make the source, translation, translator’s signature, notarial endorsement, numbering, and binding one legally connected document.
For an ordinary professional translation that is not physically or legally bound, the clearest electronic structure is generally a source file and a separately named translation file with matching exhibit numbers. List both clearly.
For a notarized translation that has been stitched, numbered, signed, and sealed with the source or its copy, scanning the complete bound unit as one PDF may better preserve the notarial relationship. Do not mechanically detach the certification page or scan only the translated text.
Kazakhstan’s current Rules for Notarial Acts explain that a notary who knows both languages may certify the correctness of a translation. If the notary does not know a relevant language, a translator prepares the translation and the notary verifies the translator’s identity and qualifications. The rules also address attaching, numbering, stitching, signing, and sealing a translation placed separately from the source.
Counterintuitive point: combining everything into one large PDF can conflict with the separate-document rule, but splitting a notarized bundle into unrelated fragments can obscure the certification that makes the translation usable. Ask the authorized filer or receiving court how the particular bound instrument should appear in the attachment list.
What “Certified Translation” Means in Kazakhstan Civil Cases
“Certified translation” is a useful English bridge term, but Kazakhstan’s more precise expressions are перевод на язык судопроизводства—translation into the language of proceedings—and надлежащим образом заверенный перевод—a properly certified translation. The latter wording appears in the Supreme Court’s normative resolution on the language of judicial proceedings.
A generic foreign translation-company certificate is not automatically equivalent to a Kazakhstan notarial act. A working translation used only for internal case review is also different from a translation actually filed as evidence. Anything intended for filing should follow the certification requirement applicable to that document and case.
Keep four questions separate:
- Is the translation complete and accurate?
- Does the filed document require a translator statement or Kazakhstan notarial certification?
- Does a foreign public document need apostille or legalization?
- How should the resulting legal unit be represented in the electronic attachment list?
For the broader terminology boundary, see CertOf’s guide to certified, notarized, and sworn translation for civil lawsuit documents. Kazakhstan’s own rules control the filing; U.S.-style certification wording should not be imported mechanically.
EDS Signing: What It Proves and What It Does Not
After the documents are uploaded, the authorized filer signs and sends the electronic submission using Kazakhstan’s electronic digital signature, commonly called EDS or ЭЦП/ЭЦҚ. The signature must belong to the person identified as signing the electronic document or to a properly authorized representative.
The official Judicial Cabinet user guide shows the sequence: complete the electronic form, add the claim and attachments, sign the application, send it, download the dispatch ticket, and monitor the filing under “My Cases.”
EDS establishes the filer’s electronic identity and protects the integrity of the submitted electronic document. It does not:
- prove that the translator is qualified;
- certify that the translation is accurate;
- authenticate the underlying contract or screenshot;
- replace apostille, legalization, or notarial certification;
- guarantee that the court will admit the evidence.
Never send an EDS private key or password to a translator, document preparer, or unverified intermediary. Obtain EDS software and services only through Kazakhstan’s official National Certification Authority and eGov channels. CertOf does not request or use a customer’s Kazakhstan EDS.
Submission Workflow: From Source Files to Dispatch Ticket
- Confirm the ordinary-court route. Make sure the matter belongs in Kazakhstan’s ordinary courts rather than the AIFC Court or an arbitral forum.
- Confirm the court and case language. Do this before translating a large record set.
- Create the attachment list. Assign one stable number and title to every pleading, exhibit, translation, certification, authorization document, and payment record.
- Translate complete visible content. Include headers, footers, stamps, signatures, handwriting, tables, attachments, and unreadable portions. Do not silently omit pages.
- Determine the certification route. Confirm whether the filed item needs a translator statement or Kazakhstan notarial handling.
- Scan and quality-check. Preserve the notarial chain, keep the file readable, and verify current format and size rules.
- Match filenames to the attachment list. Run a line-by-line count before uploading.
- Use the correct Judicial Cabinet section. A response, motion, appeal, and initial claim are not interchangeable portal categories.
- Sign with the authorized EDS. Confirm that the signer named in the document and the EDS holder are consistent.
- Save the dispatch ticket. Record its date, time, unique number, sender, and recipient details.
- Check “My Cases.” Sending, receipt, and registration are separate events. Review notices rather than assuming that clicking “Send” completed registration.
Common Upload-Preparation Errors
| Error | Why it matters | Practical correction |
|---|---|---|
| One PDF contains the claim and every exhibit | Separate documents become difficult to identify and may conflict with the separate-file rule | Split by legal document or exhibit while preserving notarized bundles |
| The list says 12 items but 14 unexplained files are uploaded | The registry cannot reconcile the packet | List source and translation components expressly and recount |
| The translation uses Russian in a Kazakh-language case | The translation may not serve the established case language | Confirm the case language before production |
| A public record is translated before an applicable apostille is added | The final authenticated chain may be incomplete | Confirm the authentication order before translating |
| A notarial page is separated from its document | The certification relationship becomes unclear | Preserve the bound unit or use an approved paired structure |
| Compression hides seals or handwriting | Unreadable attachments may be refused registration | Rescan and inspect every final page |
| The filename says “Invoice” but contains a bank statement | Filename-content mismatch is an identified registration problem | Open every final file and compare it with its name |
| The filer treats EDS as translator certification | The translation has no separate accountability trail | Use the required translator or notarial documentation |
Timing, Cost, and System Reality
There is no nationwide official promise that every translated-document submission will be registered within a fixed number of hours. Under the electronic-document rules, documents received after the court’s working day may be registered on the next working day. A dispatch ticket confirms transmission; it is not the same as substantive court acceptance.
Translation, notarization, apostille, state fees, and legal review are separate cost categories. Commercial price lists do not establish a national court fee or guarantee acceptance. Obtain a document-specific quotation based on the language, page condition, word count, certification route, and deadline.
Practitioner interviews published by Inbusiness.kz in April 2025 described daytime access problems and delayed work. BES.media’s April 2025 report separately documented a multi-day interruption and included an explanation from the Judicial Administration.
These dated reports are not a current uptime measure, but they support a practical precaution: prepare the packet early, test EDS access before the deadline, and retain the dispatch ticket and any dated error evidence. Do not assume that an error screenshot automatically extends a legal deadline.
Operational Numbers That Affect the Packet
| Operational fact | Why it matters |
|---|---|
| 20 MB per file | Long contracts, notarized bundles, image-heavy exhibits, and chat records may need controlled splitting |
| 200–300 DPI scanning | Balances readability and file size while preserving signatures and seals |
| One identifiable file per separate document | Makes the attachment list and electronic record auditable |
| Kazakh or Russian case language | The correct target language depends on the proceedings |
| Support closes for a midday break | A filer facing a late-day problem may not receive immediate assistance |
Commercial Translation and Notarial-Coordination Options
The following are limited examples of Kazakhstan-based providers with publicly stated local operations and document or notarial-translation services. They are included for comparison, not as recommendations, court-approved providers, or acceptance guarantees. Confirm the language pair, legal-document experience, BIN, invoice, revision policy, notarial arrangement, and ability to supply an organized electronic packet.
| Provider | Public presence signal | Questions to ask |
|---|---|---|
| APEK Translation Service | Publishes an Almaty office, contact details, and document and notarized-translation services | Can it mirror exhibit numbers and deliver a complete court-oriented PDF set? |
| NT Proffi | Publishes Astana and Almaty operations and written, legal, and notarial-translation services | Which notary handles the required language, and how is the bound unit scanned? |
| KazTranslate | Publishes offices in several Kazakhstan cities | Which office handles litigation documents and post-delivery corrections? |
A commercial bureau is not the court and does not decide whether evidence is admissible. Treat claims such as “guaranteed court acceptance” or “Supreme Court certified translator” cautiously unless the provider identifies a verifiable legal basis.
Official and Public Support Resources
| Resource | Use it for | Do not use it for |
|---|---|---|
| Judicial Cabinet technical support | Login, portal behavior, upload, signature, and system errors | Legal advice or an appeal against a court decision |
| Receiving court registry | Filing status and procedural instructions within its authority | Translation production or legal representation |
| National Certification Authority and eGov | EDS infrastructure and official digital-government services | Translator certification |
| Regional notarial chamber or licensed notary | Notarial authority and translation-notarization procedure | Guaranteeing evidentiary admission |
The official Judicial Cabinet support page lists 1401 as free from landlines, +7 (7172) 71-00-00, +7 (7172) 71-03-73, and [email protected]. Published support hours are Monday–Friday, 09:00–13:00 and 14:30–18:30. Technical support does not provide legal advice.
Fraud and Complaint Boundaries
- Use the official Judicial Cabinet domain and official Kazakhstan EDS channels. Do not install signing software sent by an unverified intermediary.
- Do not share an EDS key, password, or signing access with a translation bureau.
- Treat guaranteed-acceptance and unsupported official-translator claims cautiously.
- Direct portal malfunctions to Judicial Cabinet technical support. A disagreement with a registry action or judicial ruling requires the applicable procedural route, not a technical-support complaint.
- For notarial questions, verify the notary through Kazakhstan’s Ministry of Justice or the appropriate notarial chamber.
Related CertOf Resources
For the broader Astana litigation setting, use the guide to foreign-evidence translation in an Astana civil lawsuit. For file-delivery differences, see electronic certified translation in PDF, Word, and paper formats. If the evidence consists of chats, the guide to certified translation of WhatsApp messages for court explains timestamps, participants, sequence, and screenshot context.
Frequently Asked Questions
Does every Judicial Cabinet attachment need a separate file?
Each separate document should be provided as a separate identifiable file. A multi-page document remains one document unless it must be split because it exceeds the file limit. Preserve a notarized source-and-translation bundle as a coherent legal unit unless the authorized filer or court directs otherwise.
What is the current Judicial Cabinet file-size limit?
The current nationwide technical rule sets a 20 MB maximum per file. Older sources may still display the previous 10 MB limit.
Can I upload JPEG scans?
The updated rule lists PDF, DOC/DOCX, and XLS/XLSX. Convert image scans into a readable PDF instead of relying on older JPEG guidance, while preserving the required resolution and document features.
Should a Kazakhstan court translation be in Russian or Kazakh?
Translate into the language established for the proceedings. The language used to file the claim is central to that determination, so confirm it before ordering translations.
Must the number of files match the attachment list?
The uploaded documents must correspond to those identified in the attachment list. If one exhibit has a source, translation, and certification component, describe and name those components clearly so the registry can reconcile them.
Does EDS certify a translation?
No. EDS authenticates the filer and electronic submission. Translation accuracy and any required notarial certification are separate matters.
Can a missing translation be added later?
Judicial Cabinet provides functions for additional case documents in relevant workflows, but do not assume that a later upload cures an incomplete filing or preserves the original deadline. Ask the authorized filer or receiving court about the procedural consequence.
How do I prove that the submission was sent?
Download and retain the dispatch ticket showing the transmission details and unique number, then monitor the filing under “My Cases.” If no receipt or registration notice appears, contact technical support promptly.
Does this guide apply to the AIFC Court?
No. The AIFC Court has a separate institutional and procedural system. This guide concerns Kazakhstan’s ordinary court Judicial Cabinet.
Prepare a Traceable Translation Packet
CertOf can translate foreign-language contracts, invoices, bank records, corporate documents, correspondence, and message evidence; preserve relevant layout; apply consistent exhibit labels; and prepare organized digital files for review. You can upload your documents securely and provide the intended Russian or Kazakh target language plus the draft attachment list.
Before ordering, review who signs a CertOf translation certificate and CertOf’s published translation quality metrics. If Kazakhstan notarial certification is required, a local authorized notary must complete or approve that stage. CertOf does not obtain EDS credentials, file lawsuits, select the court, provide Kazakhstan legal representation, or guarantee registration or evidentiary admission.
Disclaimer: This guide provides general document-preparation information, not legal advice. Kazakhstan’s current legislation, the receiving court’s directions, and case-specific orders control. Consult a qualified Kazakhstan lawyer or the receiving court before relying on a filing format near a procedural deadline.