Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You imported marked goods from a supplier in the EAEU — for example, a batch of shoes or tires from Russia. The identification codes (IC) on the packages were issued in a foreign national system (in the "Honest Sign"). Selling this product in Kazakhstan with "foreign" codes is not allowed: the marking system does not recognize them as yours. The non-resident provided you with the codes via an electronic document, and now these codes need to be entered into circulation in the Kazakhstan IS CEDM. This is the step for which you open "Report on the Transfer of IC from Non-resident of the RK IS CEDM". Until the report is sent and accepted by the system — the goods are legally "unmarked" for retail in the RK, and the cash register will return a refusal upon sale.
1. Purpose
The document records the receipt of identification codes for marked goods from a non-resident of the RK (a participant in circulation from the EAEU) and generates an electronic report in the marking and traceability information system (IS CEDM). After the report is accepted, the codes become "yours" and the goods can be put into circulation and sold in Kazakhstan.
2. Where to find
- Section "Marking" (in some builds — "Sales" → "Marking and Traceability") → group "Import from EAEU / Introduction into circulation" → "Reports on the Transfer of IC from Non-resident of the RK IS CEDM" → button "Create".
- The document can also be created by the button "Create based on" from the document of marked goods receipt.
- Open the list directly in 1C: "Service" → "Go to navigation link" and paste:
e1cib/list/Document.ReportOnTransferICFromNonResidentRKISCEDM
2a. How to find out your release
"Help" → "About the program" (or the ℹ️ icon in the upper right corner). It indicates the platform version (for example, 8.3.24) and the configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". If your release is lower, the set of fields and exchange rules with IS CEDM may differ — check after the update.
3. How to fill out
Fill from top to bottom — some fields pull substitutions for the lower ones.
| Field | Why and what will happen in case of error |
|---|---|
| Organization (mandatory) | Your participant in the goods circulation. The identifier of the participant (GLN/IIN-BIN) for exchange is taken from it. If it is not the correct organization — the report will go under a different participant and the system will reject it. |
| Date (mandatory) | Date of report generation. Affects the period and numbering. Enter the actual date of receipt of codes, not "backdated" after the sale. |
| Number | Assigned automatically. Do not touch manually, otherwise you will disrupt the sequential numbering. |
| Counterparty (mandatory) | The non-resident sender of the codes. Their card must have the non-resident flag and the country of registration (EAEU country). If the counterparty is marked as a resident of the RK — the document will not allow selecting the operation type "from a non-resident". |
| Contract | Contract with the non-resident (import/purchase). Needed for linking with receipt and mutual settlements. An empty contract will not link with the receipt of goods. |
| Document basis | Receipt of goods / Import declaration (EAEU import) / GTD, under which the goods arrived. Convenient for transferring the nomenclature and quantity. |
| Warehouse | Where the goods actually arrived. Checks the compliance of balances and codes. |
| Participant identifier | Your ID in IS CEDM. Usually pulled from the organization's exchange settings. Empty — the exchange will not start. |
| Exchange settings / IS CEDM account | Connection to the marking system (certificate, address). Without it, the document will be processed, but will not be sent. |
The table part "Identification Codes" (mandatory to fill):
| Column | Why |
|---|---|
| Identification code (IC) | The actual code from the package/label. Entered by a 2D scanner or uploaded from a file from the non-resident. Each IC is unique; the system will not accept duplicates. |
| Nomenclature / GTIN | The product to which the code relates. GTIN must match the one registered in the catalog. |
| Quantity / Unit | For aggregated packages — nesting. Discrepancy in quantity with receipt will be highlighted. |
| Status of the code | "Received", "Put into circulation", "Error" — filled after the system's response. |
It is more convenient not to enter codes manually, but to upload using the "Upload codes" button from a file (CSV/XML) sent by the non-resident, or to scan with a scanner in the input field.
4. Detailed example
Condition. LLP "AstanaTrade" (VAT payer, rate 16%) imports 50 pairs of marked shoes from Russia. The supplier is the non-resident LLC "Shoes-RF". The value of the batch according to the invoice is 2,000,000 ₸, VAT on import from the EAEU is charged separately (form 320.00). The supplier sent a file with 50 identification codes.
Steps:
- Issued "Import Declaration" and "Receipt of Goods" for 50 pairs, warehouse "Main".
- Based on the receipt, created "Report on the Transfer of IC from Non-resident of the RK IS CEDM", counterparty — LLC "Shoes-RF".
- By clicking the "Upload codes" button, entered 50 ICs, GTIN was pulled to the nomenclature "Men's Shoes".
- Processed and clicked "Send" — the report was sent to IS CEDM, returned status "Accepted", codes received status "Put into circulation".
Important: this report does not generate accounting entries — it makes movements in the registers of marking codes and sends the electronic document. The value of the goods and VAT on the accounts appear from the underlying documents. For completeness, the entries of the basic documents on these same figures:
| Document | Dr | Cr | Amount, ₸ |
|---|---|---|---|
| Receipt of goods | 1330 "Goods" | 3310 "Payables to suppliers" | 2,000,000 |
| VAT accrual on EAEU import (16%) | 1420 "VAT to be refunded" | 3130 "VAT payable" | 320,000 |
The result of the report's work — 50 codes in the status "Put into circulation" in the register of marking codes. After this, when selling (retail/ESF), the cash register and the marking system see the codes as belonging to LLP "AstanaTrade".
5. Types of operations
Depending on the build of the release, the document supports options for receiving/transferring codes:
- Transfer of IC from non-resident EAEU — the main scenario: codes issued in another country of the Union are introduced into the circulation of the RK.
- Introduction into circulation of imported IC — recording the introduction of received codes.
- Correction / clarification of transferred IC — resending or correcting a previously sent list.
The specific set of types of operations depends on the release and connected product groups — this is version-dependent, check by the operation type selection button in your build.
6. What is generated upon processing
This document does not create accounting entries. Upon processing, it generates:
- Movements in the registers of marking codes — codes are registered as received/put into circulation, linked to the organization, warehouse, nomenclature, and underlying document.
- Electronic document (report) for IS CEDM — sent to the marking system by clicking "Send"; a response comes back with the acceptance status and statuses for each IC.
- Exchange history records — log of submissions/receipts for control.
Related electronic documents involved in the chain: SNT (accompanying invoice for goods), ESF (upon subsequent sale), import declaration (form 328.00) — they are issued as separate documents but are linked to this batch of codes.
7. Printed forms
The document is oriented towards electronic exchange, so the set of prints is minimal:
- "Report on the Transfer of Identification Codes" — list of IC with GTIN and quantity (for internal control and reconciliation with the non-resident).
- "List of Identification Codes" — simple register of IC by rows.
- Print/view electronic document and exchange protocol (receipt from IS CEDM) through the "Electronic Documents" form.
There is no full "accounting" primary document (invoice, waybill) — it is taken from the receipt and ESF.
8. Common errors
- "Identification code not filled in line №…" — empty line in the table part. Delete it or enter/scan the IC.
- "Participant identifier not specified" — the organization's connection details to IS CEDM are not filled in. Open the organization's exchange settings and fill in the identifier.
- "Identification code already put into circulation" — this IC has already been accepted by another report. Check if the batch was sent again; remove duplicates.
- "Identification code not found among those received from the non-resident" — the IC did not match what the supplier actually provided. Check the non-resident's file, ensure there are no extra characters when scanning.
- "Counterparty is not a non-resident" — the counterparty's card has the non-resident flag removed or the EAEU country is not specified. Correct the card.
- "Connection error with IS CEDM / certificate not found" — issue with the exchange account or certificate. Check the exchange settings and the certificate's validity, repeat the submission.
- "Number of codes does not match the number in the underlying document" — discrepancy with the receipt. Upload the missing ICs or adjust the receipt.
9. FAQ
1. Does this document create accounting entries? No. It works with marking codes and electronic exchange. The value of the goods (Dr 1330 Cr 3310) and VAT (Dr 1420 Cr 3130, rate 16%) are reflected in the receipt and VAT accrual documents.
2. How is it different from a regular introduction into circulation? It specifically concerns codes received from a non-resident of the EAEU: they need to be transferred from a foreign system to the Kazakhstan IS CEDM, not issued anew.
3. Can codes be uploaded from a file instead of scanned? Yes, using the "Upload codes" button from a file sent by the supplier (CSV/XML). This is more reliable than manually entering 50–500 codes.
4. What to do if the system returned an error for some codes? The processed document is sent, but for the "bad" lines, a status "Error" will come. Correct these ICs and resend only them (as a correction), the others have already been accepted.
5. Is a separate VAT needed in this document? No. VAT on import from the EAEU is calculated at a rate of 16% in the import declaration and form 320.00/328.00, not in the report on codes.
6. Can it be entered based on the receipt? Yes, this is the recommended way: nomenclature, quantity, and counterparty will be pulled from the receipt, leaving only the codes to be uploaded.
7. The goods have already been sold, but the report has not been sent — what will happen? Selling marked goods without entered codes into circulation is a violation: the cash register/IS CEDM will refuse the code. First the report and receipt of codes, then the sale.
8. Where to see the statuses of codes after submission? In the "Code Status" column of the table part and in the "Electronic Documents" form (exchange protocol/receipt from IS CEDM).
9. What counterparty is suitable? Only a non-resident with a registration country from the EAEU and the resident flag of the RK removed; otherwise, the document will not allow selecting the operation "from a non-resident".
10. Is an SNT needed for this batch? SNT is issued as a separate document for traceable goods; it and the report on IC are different links in one import chain, both tied to the batch.
10. Related documents
Introduced based on:
- Receipt of goods (import from EAEU) — source of nomenclature and quantity.
- Import declaration (EAEU import, form 328.00) — basis for the import of the batch.
Based on this report / further in the chain:
- SNT — accompanying invoice for traceable/marked goods.
- Sale of goods and ESF (IS ESF) — sale of goods already put into circulation with VAT rate 16%.
- Reports on the turnover of IC / removal from circulation — during further movement or disposal of codes.
How to find out your release: "Help" → "About the program" — there you will find the platform version and configuration release.
The instruction is relevant for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. After the update, check the set of fields and exchange rules with IS CEDM.