--- title: "Reference \"RemoveExternalProcesses\" (Accounting for Kazakhstan 3.0.74.2)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-udalitvneshnieobrabotki-buhgalteriya-dlya-kaz-en source: BuhGPT --- # Reference "RemoveExternalProcesses" (Accounting for Kazakhstan 3.0.74.2) > **TL;DR:** 1. Identification of the Object Parameter Value Object Type Catalog Name RemoveExternalProcesses Full Identifier Catalog.RemoveExternalProcesses / Catalogs.RemoveExternalProcesses Synonym — (marked as “(Do not use)” in the configuration) Configuration Accounting for Kazakhstan --- 1. Identification of the Object Parameter Value Object Type Catalog Name RemoveExternalProcesses Full Identifier Catalog.RemoveExternalProcesses / Catalogs.RemoveExternalProcesses Synonym — (marked as “(Do not use)” in the configuration) Configuration Accounting for Kazakhstan, edition 3.0 (3.0.74.2) Status Legacy, marked with the prefix Remove Navigation Link e1cib/list/Catalog.RemoveExternalProcesses Purpose. The catalog is a legacy object, as indicated by the prefix “Remove” in the name and the note “(Do not use)” in the synonym. Historically, it was intended for storing external processes and reports (*.epf, *.erf) that were connected to the configuration to extend functionality without changing the core code. The catalog stored both the binary data of the files (as value storage) and metadata: type of processing, places of use, and links to metadata objects. In current versions of the configuration, this functionality has been transferred to the built-in subsystem “Additional Reports and Processes” (BSP). The object remains in the metadata solely for compatibility and correct updating of information bases where the old mechanism was previously used. This catalog should not be used for new tasks. Where to find in 1C: section “Universal Mechanisms” → “(Do not use) External Processes”. In the standard delivery, it is usually hidden in the command interface. 2. Attributes of the Header and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose ExternalProcessStorage ValueStorage Not checked (DontCheck) Stores the binary data of the external process file (*.epf) or report (*.erf) as a value storage. The main attribute for saving the executable code itself. ProcessingType Enumeration.RemoveTypesOfAdditionalExternalProcesses Not checked (DontCheck) Defines the type of external processing: additional report, processing, print form, object filling, etc. The context of application depends on the value. Comment String Not checked (DontCheck) Arbitrary text comment describing the purpose of the processing, notes from the administrator. SourceFileComment String Not checked (DontCheck) Comment on the source file of the processing (version, author, change history). TemplateName String Not checked (DontCheck) Name of the template if the processing is used as a template/layout for other configuration objects. UseExternalObject Boolean Not checked (DontCheck) Activity flag: whether the processing is used in the system or temporarily disabled. In addition to the listed attributes, the catalog has standard attributes: Code, Name, DeletionMark, Predefined, Reference. 2.2 Table Parts Affiliation Purpose. Stores links of the external processing with metadata objects of the configuration (documents, catalogs, reports) to which it is “attached” for calling from the command interface or forms. Name Type Purpose ObjectRepresentation String Text representation of the metadata object (e.g., “Document Sale of Goods and Services”) for user perception convenience. ObjectReference Arbitrary type Reference to the metadata or data object to which the processing is linked (catalog, document, etc.). TablePartName String Name of the table part of the object if the processing is related to a specific table part (e.g., for processing product lines). TablePartRepresentation String Representation of the table part for display to the user. BuilderSettingsForSelection ValueStorage Storage of data composition settings (SKD) for selections if the processing uses the selection mechanism. ExternalProcessStorage ValueStorage Duplicates the storage of the processing file at the table part row level (for processing options for different objects). 3. Forms As for the legacy service catalog, the set of forms is minimal and follows the standard set for catalogs: Form Purpose Element Form (ElementForm) View/edit the card of the external processing: upload the file to ExternalProcessStorage, select the type of processing, fill in the table part “Affiliation”, manage the usage flag. List Form (ListForm) View the list of registered external processes, search, set the deletion mark. Selection Form (SelectionForm) Select an element of the catalog when choosing processing from other places in the configuration. There are no specialized forms for scheduling or regulatory tasks for this object — this functionality is implemented in the current subsystem of additional processes, not here. 4. Key Procedures of Modules The attached evidence does not provide the source code of the modules (BSL), so below are typical handlers characteristic of a catalog of this type. Specific lines should be clarified in the configurator of the target version. Object Module (ProcessingConducting is absent — catalog): - FillProcessing(DataFilling, StandardProcessing) — initialization of fields of a new element (e.g., setting UseExternalObject = True by default). - BeforeWriting(Refusal) — service checks before writing; for a legacy object, they are usually minimal. - CheckFillingProcessing(Refusal, CheckedAttributes) — all attributes are marked DontCheck, so mandatory checks are essentially absent. Element Form Module: - OnCreateOnServer(Refusal, StandardProcessing) — restoring the state of the form, reading auxiliary data from value storages. - Commands for uploading/downloading the processing file (UploadExternalProcessFile, DownloadFile) — place/extract binary data from the ExternalProcessStorage attribute. - Commands for connecting the processing to the context (filling the table part “Affiliation”). Requires verification (version-specific): the presence and exact composition of export procedures of the manager module involved in the migration of data from this catalog to the subsystem “Additional Reports and Processes”. 5. Conducting and Movements The catalog is not a document and does not generate accounting entries and movements in registers. Objects of the type “Catalog” do not have a conducting mechanism (Conducting = Prohibit is inapplicable; there are no movements by definition). Changes to the element only affect its own data (attributes and table parts), but not the registers of accounting, accumulation, or information. Accordingly, for this object, the standard accounts of the chart of accounts of the RK are not applicable (1210, 1030, 1330, 3310, 3130, 6010, 7010), tax calculations, and electronic documents (ESF/IS ESF, SCT). External processes that were stored in this catalog could, when launched, generate any data — but this is the logic of the processes themselves, not the catalog. For the context of current tax parameters of the RK for 2026 (used by documents, not by this catalog): VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for PIT 30 MRP/month (no more than 360 MRP per year), PIT 10% (up to 8,500 MRP of annual income) / 15% above, OPE 10% (base ceiling 50 MSP), OPEP 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%. The accounting currency is tenge (₸). These norms do not relate to the catalog itself. 6. Related Objects and Input on the Basis - Enumeration.RemoveTypesOfAdditionalExternalProcesses — source of values for the ProcessingType attribute; the same legacy object. - Subsystem “Additional Reports and Processes” (BSP) — the current successor: catalog AdditionalReportsAndProcesses, information registers with command and schedule settings. This is where the functionality migrates. - Metadata objects specified in the table part “Affiliation” — documents, catalogs, and reports to which the external processing was linked. Input on the basis is not provided for this catalog: it is neither a basis nor a recipient of input on the basis. 7. Extension Points - Do not extend or use in new modifications. Any integration of external processes should be implemented through the built-in subsystem “Additional Reports and Processes”. - If there are elements of this catalog left in the database — transfer them to the current mechanism and set the deletion mark on legacy elements. - When writing configuration extensions, do not add handlers to the forms/modules of this object: this will create a dependency on the removed functionality and complicate future updates. - When updating the configuration, ensure that the migration of data from RemoveExternalProcesses has been carried out correctly (binary data of processes and their links are preserved in the new subsystem). --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_