NTIN on receipts: prepare your products and verify the integration
What to check in your product catalog, online fiscal register and receipt when working with NTIN in Kazakhstan, with official sources and a Paloma365 checklist.
Kazakhstan’s National Catalog of Goods links a product name to its identifier. Businesses need to check both the product record and the data transferred from their accounting system to the connected fiscal register and receipt.
Where to check the current requirements
Check official guidance applicable to your business for product registration, transitional codes and fiscal documents. Publications from different dates may describe different stages of implementation. This guide covers technical preparation and does not replace checking the requirements that apply to you.
Read the <a href="https://www.gov.kz/memleket/entities/minfin/press/news/details/1051066?lang=ru" target="_blank" rel="noopener noreferrer">Kazakhstan Ministry of Finance explanation of the National Catalog of Goods</a>. Current catalog information and support channels are available on the <a href="https://nct.gov.kz/" target="_blank" rel="noopener noreferrer">official catalog website</a>.
Prepare your product records
- Check names, manufacturers, packaging and units of measure: similar items are not always the same product.
- Find the corresponding catalog record and match it to the item in your accounting system.
- Follow the catalog operator’s procedure for missing or incorrect records. Do not enter an arbitrary code.
- Check products with different packaging and products sold by weight separately.
Verify the Paloma365 integration
Tell the specialist which fiscal register and hardware you use before configuration starts. Transmission of specific fields depends on the integration version and register settings. Catalog support in an accounting system alone does not establish that every receipt is correct.
- Check the product-to-code mapping in your records.
- Agree the integration verification method and testing procedure with support.
- Check the result in the fiscal register and fiscal data operator’s system: fields, product, quantity and amount.
- Repeat the check for returns and other operations your location uses.
Resolve a mismatch
Keep the operation description, register model and integration version. Send examples to support without unnecessary customer personal data. First identify whether the discrepancy comes from the product record, data exchange or register configuration, then repeat the check.
Next step
<a href="/kontakty">Contact Paloma365</a> to discuss your register and product range. Configuration scope and connection terms are agreed after reviewing your setup; a general promise of no errors or fines is not a substitute for this check.