1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Full name | Catalogs.ВерсииМобильныхПриложений |
| Navigation link | e1cib/list/Справочник.ВерсииМобильныхПриложений |
| Synonym | “Mobile application versions” |
| Configuration | Trade Management for Kazakhstan, ed. 3.4 (version 3.4.5.21) |
| Purpose | A list of mobile application versions used for data exchange between a mobile device (PDA / data collection terminal) and a trading enterprise’s infobase. It serves as a reference classifier for matching the client application version with the exchange rules and format. |
This is a service (technical) catalog. It is not involved in inventory, cash, or tax accounting, is not a source of accounting entries, and is not reflected in statutory reporting. Its records are metadata of the mobile exchange subsystem.
2. Header attributes and tabular sections
The evidence provided only describes the purpose of the catalog; the attributes below are listed as typical for a service catalog of exchange versions of this class. The specific list of fields should be verified in the configurator for version 3.4.5.21 (version-specific).
Standard attributes (predefined by the platform)
| Attribute | Type | Purpose |
|---|---|---|
Код |
String/Number | Internal version identifier in the catalog |
Наименование |
String | Displayed name of the mobile application version (for example, “Mobile Client 3.4.5”) |
ПометкаУдаления |
Boolean | Deletion mark indicator |
Предопределённый |
Boolean | Predefined item indicator (if versions are created by the configuration) |
Typical application-specific header attributes
| Attribute | Type | Purpose |
|---|---|---|
НомерВерсии / Версия |
String | String-form version number of the client application used for matching during exchange |
Комментарий |
String (multiline) | Free-form description and purpose of the version |
Актуальность / Используется |
Boolean | Indicator of an active (supported) version |
Tabular sections: as a rule, service catalogs of versions do not have any. The list is a flat classifier. The presence of a tabular section (for example, a list of supported formats/rules) must be verified for the specific build.
3. Forms
| Form | Purpose |
|---|---|
List form (ФормаСписка) |
Main form for viewing and selecting versions; opened via the link e1cib/list/Справочник.ВерсииМобильныхПриложений |
Item form (ФормаЭлемента) |
Viewing and editing a single version (name, number, comment) |
Selection form (ФормаВыбора) |
Selecting a version from fields of other objects in the mobile exchange subsystem |
For service catalogs of this class, custom (overridden) forms are often not created; forms generated automatically by the platform are used instead. The presence of managed forms in the metadata tree must be verified for build 3.4.5.21.
4. Key module procedures
The attached evidence does not contain any BSL procedures (only the purpose facet was provided). The following is a typical set of handlers for a catalog of this kind; see the configuration’s object/form modules for the specific procedure bodies.
Object module (МодульОбъекта):
ПередЗаписью(Отказ)— standard validation before saving (checking that the name/version number is completed and preventing duplicates).ОбработкаПроверкиЗаполнения(Отказ, ПроверяемыеРеквизиты)— validation of required attributes.
Manager module (МодульМенеджера):
- May contain functions for retrieving a version by number and matching the client version with exchange rules (used by the mobile exchange subsystem).
Form modules:
ПриСозданииНаСервере— initial setup of the list/item form.- Standard selection handlers.
Because this is a service object, its modules contain no posting or calculation business logic. The catalog is primarily used as a reference attribute value in objects of the mobile device exchange subsystem.
5. Posting and register movements
The catalog is not posted and does not generate register movements. Posting is a property of documents; catalogs do not have it. This object:
- does not create records in accumulation registers (goods, settlements, cash);
- does not generate accounting entries;
- does not affect tax calculation or electronic documents (electronic invoices in the Electronic Invoice Information System, accompanying notes for goods).
For reference, movements and account entries are generated by documents in the accounting area of Trade Management for Kazakhstan, not by this catalog. The standard chart of accounts of the Republic of Kazakhstan used by those documents includes:
| Account | Purpose |
|---|---|
| 1210 | Short-term trade receivables |
| 1030 | Cash in current bank accounts |
| 1330 | Goods |
| 3310 | Short-term trade payables |
| 3130 | VAT payable |
| 6010 | Revenue from the sale of goods and services |
| 7010 | Cost of goods and services sold |
Parameters applicable in the Republic of Kazakhstan in 2026 and used by accounting documents (not by this catalog): VAT rate of 16%; MCI = 4 325 ₸, MMW = 85 000 ₸; the basic PIT deduction is 30 MCI/month (but no more than 360 MCI per year); PIT is 10% up to 8 500 MCI of annual income and 15% above that amount; MPC 10% (assessment base capped at 50 MMW), EMPC 3,5%, employee CSHI contributions 2%, employer CSHI contributions 3%, SC 5%, social tax 6%. The accounting currency is the tenge (₸).
6. Related objects and creation based on
- Mobile device exchange subsystem (PDA/data collection terminal). Data exchange objects use the catalog to identify the client application version and select a compatible upload/download format and rules.
- Reference usage. Catalog values are used as reference attributes in the settings/registers of the mobile exchange subsystem.
- Creation based on. Not applicable—the service classifier is not a basis for creating documents and is not itself created based on accounting objects.
7. Extension points
- Configuration extension (Extension): adding custom attributes (for example, a supported protocol indicator or the date when a version is decommissioned) and overriding forms without removing the configuration from support.
- Object module handlers:
ПередЗаписью,ОбработкаПроверкиЗаполнения— for additional validation of version number uniqueness and naming rules. - Manager module: placing functions that match the client version with exchange rules and are used by external/background synchronization logic.
- Event subscriptions (
ПодпискиНаСобытия) for catalog recording—to log changes to the set of supported versions. - Additional attributes/information through the common properties mechanism (if enabled in the configuration).
When customizing the object, remember that it is a service object. Accounting logic (movements, taxes, electronic invoices/accompanying notes for goods) should not be attached to it—such logic belongs in accounting documents.