--- title: "Directory \"Securities\" — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-cennyebumagi-tehnicheskoe-opisanie-en source: BuhGPT --- # Directory "Securities" — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name Securities Full Name Catalog.Securities Synonym Securities Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Hierarchy Not used (linear list) Owner No (independent catalog) Purpose. The catalog stores --- 1. Identification Parameter Value Object Type Catalog Name Securities Full Name Catalog.Securities Synonym Securities Configuration Accounting for Kazakhstan, ed. 3.0 (version 3.0.74.2) Hierarchy Not used (linear list) Owner No (independent catalog) Purpose. The catalog stores a list of securities used by the organization in accounting for financial investments. The elements of the catalog serve as analytics (subaccount/value of the attribute) when processing transactions for the acquisition, disposal, revaluation of stocks, bonds, promissory notes, and other financial instruments, as well as when generating reports on financial investments. The main users are accountants and financial specialists. Where to find in 1C. Section "Enterprise" → "Securities". Navigation link: e1cib/list/Catalog.Securities 2. Attributes and Table Parts 2.1 Header Attributes According to the metadata, the catalog does not contain user-defined attributes beyond the standard fields of the catalog. Only standard attributes are actually used: Name Type Mandatory Purpose Code String Yes Unique code of the element for identifying the security Name String Yes Full name of the security (e.g., "Ordinary Shares of JSC ...") Note. The absence of additional attributes means that the catalog is maintained in a simplified form: it acts as a classifier catalog (analytics), while quantitative-sum and date-specific characteristics of transactions (cost, nominal value, type of investment, term) are stored not in the element itself, but in related documents and registers that refer to the catalog element. 2.2 Table Parts Table parts in the catalog are absent. 3. Forms The catalog contains three forms: Form Purpose ListForm Main list form for viewing and navigating through the catalog elements (≈32 control elements). Opens via the navigation link e1cib/list/Catalog.Securities. SelectionForm Form for selecting an element from the list in selection mode — called from the fields of documents and other objects referring to the security (≈26 control elements). ElementForm Key form for creating and editing a single element: entering the code and name of the security (≈10 control elements). The main working form for the user is ElementForm. 4. Key Module Procedures In the catalog evidence, the module code (BSL) is not attached, so below are the typical handlers characteristic of a catalog of this type. Specific lines cannot be indicated — if necessary, exact implementations are verified in the configurator. Object Module (ObjectModule): - BeforeWriting(Refusal) — control of data correctness before writing (checking mandatory fields, uniqueness of the name). - FillingProcessing(FillingData, FillingText, StandardProcessing) — filling in attributes when creating based on data. - FillingCheck(Refusal, CheckedAttributes) — extended filling check. Manager Module (ManagerModule): - Functions for obtaining elements by code/name, handlers for selection forms. Form Module ElementForm: - OnCreateOnServer(Refusal, StandardProcessing) — form initialization, setting visibility/accessibility. - OnOpen(Refusal) — finalizing the interface upon opening. Form Module ListForm / SelectionForm: - OnCreateOnServer — setting filters, formatting the list. - Handlers for selecting/picking values. Requires verification (version-specific): the presence and exact signature of handlers depend on the specific build 3.0.74.2 and may differ in form modules. 5. Posting and Movements The catalog is not a document and does not generate movements — it is not posted by itself and does not create postings. A security as an element of the catalog serves as analytics (value of the attribute/subaccount) in documents and registers of financial investment accounting. Movements are generated by documents that use the catalog element. Below is the standard logic of postings according to the typical chart of accounts of the RK (numbers and rates — Kazakhstan 2026). Acquisition of a security (for cash): Debit Credit Content 1120 / 2040 (financial investments) 3310 Debt to the seller for the security has been recorded 3310 1030 Payment to the seller from the current account Disposal (realization) of a security: Debit Credit Content 1210 6010 Income from the realization of the security has been recognized 7010 1120 / 2040 Carrying (accounting) value of the disposed security has been written off 1030 1210 Receipt of payment from the buyer Feature regarding VAT. Transactions for the realization of securities (financial instruments) are classified as exempt from VAT, therefore the account 3130 "VAT payable" is not involved in typical operations with securities. For reference: the current VAT rate in the RK for 2026 is 16% (applied to taxable transactions, not to operations with securities). Electronic documents. Electronic invoices (ESF) and tax invoices for transactions with securities are generally not issued, as this is not a turnover from the sale of goods/taxable services. Specific accounts for accounting financial investments (1120/2040 — short-term/long-term) are selected in the document depending on the term and type of investment. 6. Related Objects and Input Based On - Documents for accounting financial investments — use the catalog element as analytics for acquisition/disposal/revaluation of securities. - Accounting registers — the element serves as a subaccount on financial investment accounts (1120/2040). - Selection forms (SelectionForm) — called from fields of type CatalogReference.Securities in related documents. The catalog does not typically have its own input based on: the element is created manually from the list/element form or selected in the document. Input based on is implemented on the side of documents where the security participates as an attribute. 7. Extension Points - Additional attributes and information — through the "Properties" mechanism (plans of types of characteristics AdditionalAttributes / AdditionalInformation) without changing the configuration: type of paper, issuer, nominal value, ISIN, currency of nominal value. - Configuration extensions — adding custom attributes, changing forms (ElementForm, ListForm), subscribing to events BeforeWriting / OnWriting. - Event subscriptions — control/autofill when writing the element. - Borrowing forms — overriding the behavior of SelectionForm/ElementForm in the extension for local accounting requirements. When making modifications, ensure compatibility with updates to the standard configuration: implement changes in the extension, not in the main configuration. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_