Summary: Version 3.4.5.21 of the "1C: Trade Management for Kazakhstan" configuration was released on 09.07.2026 and includes four key changes: spelling of "tenge" in printed forms in accordance with the Constitution of the Republic of Kazakhstan, a new tool for monitoring NKT codes in ESF and SNT, accounting of NKT in retail cash register receipts, as well as refinement of form 328.00 and an update to the KATO classifier. It is recommended to install the update without delay — some of the changes affect mandatory requirements for electronic document flow.
Essence of the changes in version 3.4.5.21
1. Currency: "tenge" → "teñge"
In accordance with paragraph 6 of Article 2 of the Constitution of the Republic of Kazakhstan, adopted at the national referendum on March 15, 2026, in all printed forms the currency name has been changed from "tenge" to "teñge" (with a lower loop).
Important: the system now uses a fixed value of "teñge" when generating printed forms in the currency of regulated accounting — regardless of what is written in the currency reference book. For foreign currencies, the behavior has not changed.
2. ESF: monitoring the relevance of NKT codes
- A mechanism for monitoring the relevance of product codes in origin sources has been added when filling in the "Product code" field in the ESF document.
- In section G of the ESF document, a new command "Replace duplicate codes" has appeared — it refills the "Product code" field with the current value across all erroneous rows at once, in a single action.
Current NKT code formats: - NTIN (permanent) — starts with "02" - XTIN (temporary) — starts with "004", length 13 digits
3. SNT: accounting for deactivated NKT codes
- A mechanism has been implemented for filling in the product code when generating SNT, taking into account the "Product code deactivated" flag in the origin source.
- The SNT document also has the "Replace duplicate codes" command added for section G.
4. Retail trade: NKT in KKM receipts
- KKM receipts now include accounting of items broken down by NKT codes — aggregation of line items now takes into account the matched codes.
- The "Retail Sales Report" is now generated broken down by NKT; the codes are displayed in the "Goods" table section.
5. National Catalog of Goods (NKT)
In the "Check deactivated NKT codes" processing, the ability to manually run the algorithm for setting the relevance flag for product codes in origin sources has been added. Previously, the run was only automatic.
6. Form 328.00 and contract reference book
- In the "Declaration on the import of goods (form 328.00)", filling in of the "Currency contract registration number" and "Date of assignment of the currency contract registration number" fields has been implemented when generating the export file.
- In the "Contracts with counterparties" reference book → "Currency control" section, a new attribute "Date of assignment" has been added — used specifically for exporting form 328.00.
7. KATO classifier
Updated as of 18.06.2026 — the update is applied automatically.
What exactly the accountant should do after installation
✅ Step 1. Create a backup copy BEFORE installation
Administration → Maintenance → Backup. Do not update the working database without a backup copy.
✅ Step 2. Check printed forms with the amount in words
Open any document (invoice, waybill, act) and generate a printed form. Make sure the amount in words contains "teñge", not "tenge". If you use manually modified templates — bring them into compliance.
✅ Step 3. Run the check for deactivated NKT codes
Go to the "Check deactivated NKT codes" processing (usually: Warehouse and delivery → Service). Run the algorithm manually — it will flag origin sources with outdated product codes. Do this before issuing the next ESF and SNT.
⚠️ The mandatory use of the product code from NKT in ESF has been in effect since 01.01.2026. A deactivated or duplicate code is grounds for the IS ESF portal to refuse to accept the document.
✅ Step 4. Check ESF with NKT codes
- Open Sales → Electronic invoices.
- Open an ESF document that contains items with NKT codes.
- In the table section of section G, make sure the "Replace duplicate codes" button has appeared.
- If the system issues a warning about outdated codes — use this command for batch replacement across all erroneous rows.
✅ Step 5. Check SNT
Similar to ESF — open Sales → Electronic SNT, section G, make sure the "Replace duplicate codes" command is present, and run the replacement if necessary.
✅ Step 6. Check NKT accounting in retail sales (if you conduct retail)
- Open an unclosed cash shift, add a test item — make sure aggregation in the receipt takes into account the NKT codes.
- After closing the shift, open the "Retail Sales Report" → "Goods" tab — check for the presence of a column with NKT codes.
✅ Step 7. Fill in the "Date of assignment" attribute in contracts with currency control
- Master data → Contracts with counterparties → "Currency control" section.
- Find contracts with a currency contract registration number.
- Fill in the new "Date of assignment" attribute — without it, the fields in the form 328.00 export file will remain empty.
✅ Step 8. Check the export of form 328.00
Generate the export file for the "Declaration on the import of goods". Make sure the "Currency contract registration number" and "Date of assignment of the currency contract registration number" fields are filled in correctly.
✅ Step 9. Check the VAT rate in the settings
The current VAT rate in 2026 is 16%. Open the tax settings and make sure that this exact rate is specified in document templates, item cards, and contracts. This is critical: understating the tax in the declaration entails fines — from 20% (small business) to 80% (large business) of the additionally assessed amount.
Deadlines and what to pay attention to
| Change | When it applies | Priority |
|---|---|---|
| Spelling of "teñge" in printed forms | Since 15.03.2026 (Constitution of the Republic of Kazakhstan) | 🔴 High |
| Mandatory NKT codes in ESF/SNT | Since 01.01.2026 (already in effect) | 🔴 High — risk of IS ESF refusal |
| NKT accounting in retail receipts | From the moment the update is installed | 🟡 Medium — for retail |
| "Date of assignment" attribute in contracts | Before the next submission of 328.00 | 🟡 Medium |
| KATO update to 18.06.2026 | Applied automatically | 🟢 Low |
Additionally: - A detailed description of the changes for each block is located in the AddDoc folder in the update template installation directory. - After updating, it is recommended to conduct a "test day": create all standard documents (receipt, sale, ESF, return) and make sure the calculations are correct before starting real work. - If you use 1C:Accounting for Kazakhstan or 1C:Payroll and HR together with Trade Management — after updating, check synchronization: the exchange rules may require a separate update.
Frequently asked questions
❓ Do I need to manually change "tenge" to "teñge" in the currency reference book?
No. After installing the update, the program automatically uses the fixed value "teñge" when generating printed forms in the currency of regulated accounting — regardless of what is written in the reference book. No additional settings are required.
❓ What happens if deactivated NKT codes remain in the ESF — will the document not be sent?
Yes, the IS ESF portal may reject a document with an outdated or duplicate code. Use the new "Replace duplicate codes" command in section G — it will refill the "Product code" field with the current value across all problematic rows at once. First run the "Check deactivated NKT codes" processing manually.
❓ Is it mandatory to fill in the "Date of assignment" attribute in contracts?
Only if you export form 328.00 ("Declaration on the import of goods and payment of indirect taxes"). For other contracts, the attribute is not mandatory. If you do submit form 328.00 — fill in the attribute in the contract card before the next export, otherwise the corresponding fields in the file will remain empty.