Verified on release 3.4.5.21 of “Trade Management for Kazakhstan” (version 3.4).
A courier calls from the city: “The application won’t let me in; it says the version is outdated.” A warehouse worker complains that the mobile terminal stopped synchronizing after the database was updated. You open the administration section and are told: “Check the mobile application versions directory.” This is when you encounter this object for the first time. It is not about money or taxes—it is about which versions of mobile clients are compatible with your database, who can continue working, and who needs to update.
First, the main point, so that you do not waste time searching: this is a service (technical) directory. It does not generate accounting entries, issue E-invoices or SNTs, print source documents, or affect VAT, IIT, or contributions in any way. Therefore, Kazakhstan rates and accounts from the Kazakhstan Chart of Accounts simply do not apply to it—this is not an omission in the instructions but the nature of the object. Below, we explain what it actually does and how to work with it.
1. Purpose
The directory stores a list of versions of mobile applications (mobile workstations for warehouse workers, couriers, sales representatives, etc.) that connect to your infobase. Based on these entries, the system determines which mobile client version is current and which needs to be updated, and checks the compatibility of the mobile device with the current database release.
2. Where to Find It
The directory is a service directory, so it is not available in the regular work sections—it is opened from the administration area for data exchange with mobile devices.
- Menu path:
Master Data and Administration→Mobile Applications(orData Synchronization/Exchange with Mobile Devices, depending on which mobile functions are enabled) → the command that opens the list of versions. - Direct 1C navigation link:
e1cib/list/Справочник.ВерсииМобильныхПриложений
How to open it using the link: in the “Service” menu (the tools icon or main menu), select “Go to Navigation Link”, paste the string above, and click “Go.” The list will open even if the menu item is hidden.
2a. How to Find Your Release
Menu (the icon in the upper-right corner or “Main Menu”) → “Help” → “About”. In the window that opens:
- Platform version—for example,
1C:Enterprise 8.3.24.xxxx; - Configuration—
Trade Management for Kazakhstan, version3.4, release3.4.5.21.
Compare the configuration release with the heading of this guide: the set of service fields used by mobile mechanisms changes between releases.
3. How to Complete It
Entries are normally added to this directory automatically—when a mobile device connects and synchronizes, the database registers the client version itself. Manual creation is rarely required: for example, when you enter an allowed version in advance or clear out obsolete entries. To open a new record, click “Create” in the list.
| Field | Required | Purpose and consequences of an error |
|---|---|---|
| Description | Yes | A clear entry name that will help you find it in the list (for example, “Warehouse Worker Mobile Workstation 3.4.5”). If left blank, 1C will not allow the item to be saved. A duplicate or unclear name will make it harder to find the required version. |
| Code | Assigned automatically | A unique internal identifier. It does not need to be changed manually; manual editing may produce a duplicate code and cause a conflict when saving. |
| Version | Yes (in practical terms) | The actual mobile application version number (for example, 3.4.5.21). This is the key field used to check compatibility. If you enter the wrong number, the database will decide that the device is running another, incompatible version, and synchronization may be blocked. |
| Application / application type | Depends on the settings | Specifies which mobile client the version relates to (warehouse worker, courier, or sales representative). If the wrong type is selected, the version will be linked to the wrong application and the compatibility check will return an incorrect result. |
| Date / registration date | Completed by the system | Indicates when the version appeared in the database. It is useful for understanding the chronology of updates. |
| Current / in use (attribute) | No | Indicates whether work with this version is allowed. If you clear the attribute for a version that is currently in use, users running it may no longer be able to connect. |
| Comment | No | Your note for other users: what changed, why the version was disabled, etc. It does not affect database operation but saves time when investigating incidents. |
The exact set of service fields in this release branch may differ by one or two fields—this is the only point that requires verification in your specific 3.4.5.21 build. The essential fields (description, version, and application link) are always present.
Manual procedure:
- Open the list using the navigation link.
- Click “Create”.
- Complete Description and Version (required in practical terms).
- Specify the application type if the field is available.
- If necessary, clear/select the current-version attribute and add a comment.
- “Save and Close”.
4. Worked Example
Situation: You updated the database to release 3.4.5.21. Couriers use a mobile application, and after the update, some phones remained on the old build 3.4.4.10. You want the old version to stop connecting and the new one to be treated as current.
What you do:
- Open the directory and find the entry for version
3.4.4.10. - Clear its “Current” attribute (or mark it for deletion if it is no longer needed).
- Check that an entry for version
3.4.5.21exists and is marked as current. If it does not exist, create it: Description—“Courier Mobile Workstation 3.4.5.21,” Version—3.4.5.21, application type—“Courier,” with the “Current” attribute selected. - Save the entry.
Result: during the next synchronization, a phone running 3.4.4.10 will receive a message that an update is required, while devices running 3.4.5.21 will continue to work.
What about debit/credit entries? There are none and cannot be any here. The directory does not represent a business transaction: it does not move goods, money, or settlements. Therefore, Kazakhstan accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010), the VAT rate of 16 %, IIT, MPPС, and other 2026 indicators do not apply to this entry. If you need an object that generates entries, use sales/receipt/payment documents, not this directory.
5. Operation Types
The directory has no “operation types” in the sense that documents do (sale, receipt, payment, etc.). A directory item is simply a record card. The only actions you can perform with it are to create it, edit it, mark it as current/not current, or mark it for deletion.
6. What Is Generated When an Entry Is Saved
- Accounting entries—none are generated.
- Electronic documents (E-invoices in the E-Invoicing IS, SNTs)—none are generated. This object is unrelated to electronic document workflow in Kazakhstan.
- Register movements—there are no “document movements” as such: the directory stores the version record itself. Version data is used by service synchronization mechanisms when a mobile device connects in order to check compatibility.
Simply put, saving creates a row in the directory—and that is all. There are no financial consequences.
7. Print Forms
The directory has no print forms of its own. It is a technical record and is not printed as a source document. If necessary, the list can be output using standard platform tools: More → Output List (for printing or exporting to a table/file)—but this is a universal feature of any list, not a “print form” of the object.
8. Common Errors
- “The ‘Description’ field is not completed”—appears when you try to save a blank record. Enter a clear name (for example, including the version number) and save again.
- “An item with this code already exists”—appears if you manually specify a code that matches an existing one. Do not change the code; let it be assigned automatically.
- The courier/warehouse worker reports “version outdated” even though you entered the new version—a common cause is that the new entry is not marked as current or the number in the “Version” field contains a typo (an extra space or a different digit). Compare the number character by character with the version shown on the device.
- All devices stopped connecting after the directory was cleaned up—you marked the current version for deletion and deleted it. Restore the entry for the required version and remove the deletion mark, then synchronize.
- You are looking for the directory under “Sales” or “Finance” and cannot find it—by definition, it is not located there. Open it through mobile application administration or by using the navigation link in section 2.
9. FAQ
See also the faq JSON block—the questions there are the same.
10. Related Objects
- What it is populated from: entries are created by the mobile-device exchange mechanism when devices connect/synchronize. The directory has no “source document” in the accounting sense.
- What it is related to: settings for data synchronization / exchange with mobile applications (the warehouse worker’s mobile workstation, courier application, and sales representative application). These mechanisms read versions from the directory to check compatibility.
- What is entered “based on” this directory: nothing—the service directory is not a basis for documents.
How to Find Your Release
Menu → “Help” → “About”: the “1C:Enterprise” platform version and configuration release are shown there. Compare the configuration release with the heading of the guide.
This guide was prepared for release 3.4.5.21 of “Trade Management for Kazakhstan” (version 3.4). The set of service fields may differ in other releases.