1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ЗаявлениеНаПредоставлениеВычетовИПНПрисоединенныеФайлы |
| Full name | Справочник.ЗаявлениеНаПредоставлениеВычетовИПНПрисоединенныеФайлы |
| Synonym | — (not set; for service file catalogs the synonym is usually empty) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| File owner | Документ.ЗаявлениеНаПредоставлениеВычетовИПН |
| Mechanism subsystem | "File Management" (SSL, РаботаСФайлами) |
Purpose. A service catalog — a storage of files attached to the "Application for granting IIT deductions" documents. It implements the standard file-attachment mechanism: scans, PDFs, images and other documents confirming the right to an IIT tax deduction (application, supporting certificates, documents for standard and other deductions) are attached to the employee's application. The user does not work with the catalog directly — records are created and opened automatically from the owner document card via the commands "Attach file", "Open", "Save as", "Sign with digital signature". The target audience is the payroll accountant and HR officer who prepare primary documents for IIT reporting.
2026 context (RK). The owner document ensures the application of the basic IIT tax deduction of 30 MCI per month (no more than 360 MCI per year), where 1 MCI = 4,325 ₸. IIT is calculated at a rate of 10% up to an annual income of 8,500 MCI and 15% above it. Minimum wage = 85,000 ₸. The catalog itself performs no calculations — it merely stores the supporting files attached to the application.
Where to find. Direct list (service, usually hidden from the command interface):
e1cib/list/Справочник.ЗаявлениеНаПредоставлениеВычетовИПНПрисоединенныеФайлы
Standard access — from the "Application for granting IIT deductions" document form → panel/command "Attached files".
2. Header attributes and tabular sections
2.1 Attributes (from evidence + standard composition of the "File Management" subsystem)
| Name | Type | Requirement | Purpose |
|---|---|---|---|
| Автор | СправочникСсылка.Пользователи | Mandatory (ShowError) | User who originally uploaded the file. Filled in automatically upon creation. |
| ВладелецФайла | ДокументСсылка.ЗаявлениеНаПредоставлениеВычетовИПН | Optional | Reference to the owner document to which the file is attached. |
| ДатаМодификацииУниверсальная | Date (xs:dateTime, UTC) | Optional | Universal date/time of the last file modification. Synchronization and version control. |
| ДатаСоздания | Date (xs:dateTime, UTC) | Mandatory (ShowError) | Date/time the file record was created in the infobase. |
| Зашифрован | Boolean | Optional | Flag of an encrypted file (working with confidential data). |
| Изменил | СправочникСсылка.Пользователи | Optional | User who last modified the record/file. |
| ИндексКартинки | Number | Optional | Index of the file type icon in the interface image collection. |
| Описание | String | Optional | User comment on the file content. |
| ПодписанЭП | Boolean | Optional | Flag of the presence of a digital signature (legally significant document flow). |
| ПутьКФайлу | String | Optional | Path to the file on the volume (when stored "In volumes on disk"). |
| Размер | Number | Optional | File size in bytes. |
| Расширение | String | Optional | File extension (pdf, docx, jpg …). |
| Редактирует | СправочникСсылка.Пользователи | Optional | User currently editing the file (locking against conflicts). |
| СтатусИзвлеченияТекста | ПеречислениеСсылка.СтатусыИзвлеченияТекстаФайлов | Optional | Text extraction status for full-text search. |
| ТекстХранилище | Value storage | Optional | Extracted file text for the full-text index. (standard subsystem attribute) |
| ТипХранилищаФайла | Enumeration | Optional | Storage method: in the infobase / in volumes on disk. (standard subsystem attribute) |
| ТомХранения | СправочникСсылка.ТомаХраненияФайлов | Optional | Volume where the file is physically located (when stored on disk). (standard subsystem attribute) |
| Наименование (standard) | String | — | File name without extension; the displayed name of the catalog record. |
The attributes Автор, Изменил, Редактирует form the standard SSL triad of ownership control and version locking.
2.2 Tabular sections
Tabular sections are absent — this is typical for an attached-files catalog. The binary file data is stored not in a string attribute, but either in an attribute of the "Value storage" type (storage in the infobase), or in a volume on disk (attributes ТипХранилищаФайла/ТомХранения/ПутьКФайлу), or in a separate versions table (when versioning is enabled).
3. Forms
The catalog uses a minimal set of forms; all interactive work goes through the universal forms of the "File Management" subsystem.
| Form | Purpose |
|---|---|
Item form (ФормаЭлемента) |
File card: name, description, author, dates, size, "Signed with digital signature" / "Encrypted" flags. As a rule, the common SSL form is used. |
List form (ФормаСписка) |
List of files attached to a specific application. Usually replaced by the common form РаботаСФайламиКлиент / the attached files panel. |
Choice form (ФормаВыбора) |
Selecting a file from those already attached (when inserting a file reference into other objects). |
In practice, the forms for attachment, viewing and signing are provided by SSL (the common forms ПрисоединенныеФайлы, РаботаСФайлами), so the catalog's own forms may be unset or may override the appearance.
4. Key module procedures
The BSL code is not attached in the evidence, so below is the set of handlers typical for an attached-files catalog (implemented in the object module, the manager module, and via the common modules of the "File Management" subsystem).
Object module:
ПередЗаписью(Отказ)— recordsИзменилandДатаМодификацииУниверсальная, recalculatesРазмер, and, if necessary, resetsСтатусИзвлеченияТекстаto "ExtractionRequired".ПриКопировании(ОбъектКопирования)— clears the signature/encryption and ownership flags (ПодписанЭП,Зашифрован,Редактирует) so that the copy does not inherit locks.ОбработкаЗаполнения(ДанныеЗаполнения, …)— settingАвтор,ДатаСоздания,ВладелецФайлаwhen created from the document.
Manager module:
- Handlers for exporting/importing exchange data, registration in the file subsystem subscriptions.
Common subsystem modules (called instead of the object's own code):
РаботаСФайламиСлужебный.ДобавитьФайл(...)— creating a catalog record, placing binary data in the storage/volume.РаботаСФайлами.ОткрытьФайл(...)/.СохранитьФайлКак(...)— obtaining and opening the file data.ЭлектроннаяПодписьКлиент/Сервер— setting theПодписанЭПflag, adding signatures.ИзвлечениеТекстаСервер— background filling ofТекстХранилищеandСтатусИзвлеченияТекстаfor full-text search.
Requires verification (version-dependent): the specific composition of the overridden object module procedures in build 3.0.74.2 — determined via the Configurator, since SSL periodically moves logic from objects to common modules.
5. Posting and register records
The catalog is not posted and generates no register records — an object of the "Catalog" type has no posting mechanism. Accordingly:
- the object does not create accounting entries for RK accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010);
- it does not write to the IIT/tax deduction calculation registers;
- it does not generate electronic documents (ESF in the IS ESF, SNT) — these mechanisms are not related to attached files.
The only records the object produces are the catalog record itself and, optionally:
- a binary data record in the storage (in the infobase) or a file in the storage volume (the register/catalog
ТомаХраненияФайлов); - a file version record (if versioning is enabled for the owner);
- an update of the full-text search data.
The economic result (application of the 30 MCI/month deduction, but no more than 360 MCI/year, IIT calculation at 10%/15%, OPV withholding 10%, OPVR 3.5%, VOSMS 2%, OSMS 3%, SO contributions 5% and social tax 6%) is generated by the owner document "Application for granting IIT deductions" and the subsequent payroll calculation, not by this catalog. The attached file merely serves as documentary grounds.
6. Related objects and entry on the basis
| Relation | Object | Nature |
|---|---|---|
| File owner | Документ.ЗаявлениеНаПредоставлениеВычетовИПН |
Each catalog record belongs to one application (ВладелецФайла). |
| Users | Справочник.Пользователи |
The attributes Автор, Изменил, Редактирует. |
| Storage volumes | Справочник.ТомаХраненияФайлов |
Physical placement of the file when stored on disk. |
| Statuses | Перечисление.СтатусыИзвлеченияТекстаФайлов |
State of text indexing. |
| Digital signature | SSL digital signature/cryptography subsystem | The ПодписанЭП flag, storage of signatures. |
Entry on the basis. The classic "Entry on the basis" mechanism is not applied to the catalog. Records are created via the file attachment commands from the owner document form; there is no separate entry of other documents on the basis of a file.
7. Extension points
- Configuration extension (Adopt/Extend). Borrowing the item/list form to add custom display attributes or buttons. Changing the composition of stored file fields is not recommended — it will break compatibility with SSL.
- Additional attributes and information. Connecting the object to the "Properties" subsystem (
ПланВидовХарактеристик.ДополнительныеРеквизитыИСведения) for a label of the type of the basis document (for example, "Application", "Supporting certificate"). - Event subscriptions. The catalog's
ПередЗаписью/ПриЗаписи— for auditing file uploads/modifications and controlling the mandatory presence of a digital signature on legally significant scans. - Exchange rules (CD 2/3, EnterpriseData). Setting up the export of attached files together with the owner document in synchronization.
- Full-text search. Using
ТекстХранилище/СтатусИзвлеченияТекстаto search by the content of attached PDFs/scans. - Access restriction (RLS). Setting up file access by owner — relevant for employees' personal data in IIT applications.