Directory "BankExchangeMessageAttachedFiles" (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog is intended for storing files attached to СообщениеОбменСБанками documents within the framework of electronic interaction with the banking systems of Kazakhstan (exchange of payment orders, bank statements, registers, and other Direct Bank / "Client-Bank" documents). Records are created programmatically when a file is loaded or attached through the standard "Attached Files" mechanism of the Standard Subsystems Library (SSL). Both the files themselves (in the information base or in a volume on disk) and their metadata are stored: size, author, dates, versions, and encryption and electronic signature flags.

The catalog is a technical part of the file management subsystem and is not intended for direct manual maintenance by users through the main menu — it works "behind the scenes" of the owner document's form.

Where to find it in 1C:

• Service access (list): e1cib/list/Справочник.СообщениеОбменСБанкамиПрисоединенныеФайлы
• Functionally: the "Electronic interaction" → working with the "Bank exchange message" document section, the "Attached Files" command/hyperlink on the document form.

Each type of document that supports attached files has its own storage catalog of the form <DocumentName>ПрисоединенныеФайлы. This catalog serves exclusively the СообщениеОбменСБанками document.

2. Header attributes and tabular sections

2.1 Header attributes (from evidence)

2.2 Other standard attributes of the SSL "Attached Files" subsystem

Catalogs of attached files in SSL are additionally characterized by the following (even if not included in the evidence slice):

The "Наименование" attribute (standard). Used as the file name without the extension (full file name = Наименование + Расширение).

2.3 Tabular sections

The catalog does not contain its own applied tabular sections. The file body is stored either in a value storage attribute (when stored in the information base) or in a volume on disk (attributes ПутьКФайлу, ХранениеФайлаВБазеДанных). File versions are stored in a separate subordinate versions catalog, and the binary data itself — in the associated information register of the binary data storage.

3. Forms

Catalogs of attached files, as a rule, do not have their own applied editing forms: interaction goes through the universal forms of the SSL "File management" subsystem, opened from the owner document's form.

If in a specific distribution the catalog's own item/list forms are not set, the platform generates them automatically, but the standard scenario is working through the common SSL forms.

4. Key module procedures

The catalog's applied code is minimal; the main logic is placed in the common modules of the SSL "File management" subsystem. The module code (BSL) is not included in the evidence, so below is the standard set of handlers for objects of this type.

Object module (ОбработкаЗаполнения, ПередЗаписью, ПередУдалением):

• ОбработкаЗаполнения — upon programmatic creation, fills in Автор, ДатаСоздания, ДатаМодификацииУниверсальная, ВладелецФайла.
• ПередЗаписью — records Изменил, updates ДатаМодификацииУниверсальная, recalculates ИндексКартинки based on Расширение/state; control of the editing prohibition for a signed file.
• ПередУдалением — cleanup of related data: the file body in the binary data storage, versions, electronic signature records.

SSL common modules implementing the business logic (called instead of object code):

• РаботаСФайлами / РаботаСФайламиСлужебный — adding, updating, retrieving the file and its binary data.
• РаботаСФайламиСлужебныйКлиент / …Сервер — form commands: open, save, edit, lock/release.
• УправлениеЭлектроннойПодписью — signing with an electronic signature, signature verification, encryption/decryption (attributes ПодписанЭП, Зашифрован).
• ВерсионированиеФайлов — creating and storing versions, assigning the relevant version.

Requires verification (version-specific): the exact names of the common modules and their methods depend on the version of the built-in SSL in build 3.0.74.2.

5. Posting and movements

The catalog is not a document and is not posted — it does not generate accounting entries or movements in accumulation/accounting registers. It is a file storage.

Only service information registers of the "File management" subsystem are associated with files (binary data storage, extracted text for full-text search, electronic signature data). No applied accounting movements are made.

Accounting consequences arise not for the file, but for the owner document and the accounting documents associated with it. For reference — the standard RK accounts and the amounts under the current legislation of Kazakhstan (2026), applied in the accounting documents to which the bank exchange leads:

• Receipt of money from a buyer per statement: Dr 1030 "Money in current accounts" / Cr 1210 "Short-term receivables of buyers".
• Payment to a supplier: Dr 3310 "Payables to suppliers" / Cr 1030.
• Sale of goods: Dr 1210 / Cr 6010 "Income from sales" and Dr 7010 "Cost of sales" / Cr 1330 "Goods".
• VAT on sale: charged to account 3130 "VAT payable" at the rate of 16% (the RK VAT rate from 2026; the value of 12% is outdated).
• Electronic sales documents are accompanied by ESF (IS ESF) and, if necessary, SNT.

Current RK indicators for 2026 (for settlement documents, not for this catalog): MCI = 4,325 ₸, minimum wage = 85,000 ₸; the basic tax deduction for IIT — 30 MCI/month (no more than 360 MCI/year); IIT 10% up to 8,500 MCI of annual income and 15% above; mandatory pension contributions (OPV) 10% (base ceiling 50 minimum wages), employer's mandatory pension contributions (OPVR) 3.5%, contributions to compulsory social health insurance (VOSMS) 2%, compulsory social health insurance (OSMS) 3%, social contributions (SO) 5%, social tax 6%. Currency — tenge (₸).

6. Related objects and entry based on

Entry based on. Not applicable. Records are created programmatically by the file attachment mechanism, not through "Create based on". The user adds files with the commands of the owner document's attached files form (from disk, from the clipboard, from a scanner).

7. Extension points

• Configuration extensions (without removing from support): subscription to the catalog object's ПередЗаписью/ПередУдалением events for additional validation (for example, checking the file extension against the bank's formats — .xml, .txt, .sig).
• Additional attributes and information: through the properties subsystem (ПланыВидовХарактеристик.ДополнительныеРеквизитыИСведения) — file marking (bank document type, processing status).
• SSL common modules: overridable procedures of the "File management" subsystem for customizing the rules of storage, versioning, and text extraction.
• Data exchange / DIB: the ДатаМодификацииУниверсальная attribute (UTC) — a reference point for correct synchronization of files between nodes; take into account when configuring exchange rules.
• Storage: switching between storage in the information base and in volumes on disk (ХранениеФайлаВБазеДанных, storage volumes) — a scaling point for large volumes of banking attachments.

Requires verification: the availability of specific override points depends on the version of the SSL built into build 3.0.74.2.