Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You opened the list of external processing to run an old report that you used a couple of years ago and stumbled upon a directory with a frightening name "DeleteExternalProcesses". Or you received a .epf file and are looking for where to "put" it, and the configuration search threw out this object. Calm down. This is a service directory-"retiree". The word "Delete" in its name is not a command to you and not an error, but a label from the 1C developer: the object is left in the configuration only for compatibility and data accumulated in old databases, and you need to work somewhere else. Below is what’s inside, how to transfer it, and why you shouldn’t load new files there.
1. Purpose
The directory stores external processes and reports (files .epf / .erf) that were loaded into the database in old versions of the configuration. This is an archival mechanism: it is left so that nothing is lost when updating from old releases. The current tool is the subsystem "Additional reports and processes" (BSP). Connect new files there, not here.
2. Where to find
This directory does not have a direct menu item — it is intentionally hidden because it is marked for deletion. You can open it in two ways:
- Through the navigation link. Menu "Service and settings" (icon ≡ in the upper right corner) → "File" → "Open by link..." (or
Ctrl+F11in the thick client), paste:e1cib/list/Directory.DeleteExternalProcesses - The current equivalent (where you probably need to go): "Administration" → "Print forms, reports, and processes" → "Additional reports and processes". This is where everything new lives.
If a blank list form opened via the link, it means that this directory has never been filled in your database, and you do not need to deal with it.
2a. How to know your release
"Help" → "About the program" (or icon ≡ → "About the program"). In the opened window, there are two key lines: platform version (for example, 8.3.24.xxxx) and configuration version — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". The instructions are written for release 3.0.74.2; the behavior is the same in neighboring releases, field for field.
3. How to fill
First, a disclaimer: you do not need to fill this directory. Creating new items in it is a dead-end path; they will not be picked up by the current connection mechanism. But to help you understand what you see in the already existing cards, let’s break down the fields.
| Field | What it is for and what will happen if filled incorrectly |
|---|---|
| Name (mandatory) | This is how the process is named in the list. If left empty, 1C will not allow you to save the item ("The field 'Name' is not filled"). It does not affect the operation of the file itself; it is just a label for searching. |
| Code | A service number, automatically assigned by 1C. Do not touch it manually: manual input may result in a duplicate code and conflict when saving. |
| Processing storage | This is where the binary data of the file .epf/.erf is stored — that is, the process is "embedded" inside the database. If the field is empty, there is a name in the card, but there is nothing to run: the execution button will not open anything. You can overwrite the file only through the built-in file upload (if it is available in your form); nothing is written manually into this field. |
| Comment | An arbitrary note: who uploaded it, for what purpose. It does not affect anything but helps avoid guessing during the inventory of external processes. |
The only mandatory field here is Name. Everything else is either service or optional. The key point: even a correctly filled card in modern 1C will not provide an automatic button in the journals of documents and directories — this is exactly what the directory was replaced for.
4. Analyzed example
This object does not have any accounting entries — it is not accounting but service, so there cannot be a classic example of "Dr/Cr in numbers" (and anyone who shows you them for this directory is fantasizing). A practical example is how to "move" correctly.
Situation. After updating from release 3.0.5x, the external process "Bank statement upload" remained in the database, stored in DeleteExternalProcesses. It runs, but you need it to be visible to the accountant by a button in the payment documents list.
Steps to take:
- Open the directory via the link
e1cib/list/Directory.DeleteExternalProcesses, find the item "Bank statement upload". - Export the file: the command "More" → "Save process to file" (if the command is available) or request the original
.epffrom the person who created it. - Go to "Administration" → "Print forms, reports, and processes" → "Additional reports and processes", enable the flag "Additional reports and processes" if it is off.
- Click the "Add from file..." button, select
.epf. 1C will read the embedded description of the process and offer "Placement" — that is, in which sections and for which documents to show the button. - Check the placement box for payment documents, save.
- Return to the old directory and mark for deletion the transferred item (
Delor "More" → "Mark for deletion") to avoid confusion.
Result: the process is now connected as standard, updates along with the placement description, and will survive the next configuration update. No accounting movements are generated by these actions — only the composition of service data changes.
5. Types of operations
The directory is not a document; it does not have "types of operations" in the accounting sense. Available actions with the element:
- Open / execute the stored process (if the file is in the "Processing storage" field and the form allows it).
- Mark for deletion / unmark.
- View attributes (name, comment).
- Enter based on — not provided.
6. What is formed when posting
Nothing. The directory is not posted. It does not generate:
- accounting entries (Dr/Cr) — accounting is not affected at all;
- tax movements and declarations;
- electronic documents — the ESF in the ESF IS and STN does not issue this object (for ESF/STN there are their own documents for sales and transfers);
- movements in accumulation registers and information — except for the service record about the element of the directory itself.
If you were looking for "where the ESF is formed" or "why the entries for VAT 16% do not appear," — you need not this directory but the sales document (RK accounting accounts: Dr 1210 / Cr 6010 for revenue, Cr 3130 for VAT, Dr 7010 / Cr 1330 for cost). This has nothing to do with "DeleteExternalProcesses".
7. Print forms
The directory does not have its own print forms —. Print forms may be contained within a specific stored process (for example, an old act form), but this is the capability of the file itself, not the directory card. You will not see a "Print" button on the element form.
8. Common errors
- "The field 'Name' is not filled" — when trying to save an empty item. Fill in the name or, more correctly, do not create new items here at all.
- "External process not connected / button does not appear in documents". Expected: this directory cannot place buttons in forms. Connect the file through "Additional reports and processes".
- "Error calling context method... the process cannot be executed". Usually, the old
.epfis incompatible with the current platform/release. Get the current version of the process from the developer and reconnect it. - The process "disappeared" after the update. The file was only stored in this directory and was not transferred. Restore from the database backup (export via "Save to file") or request the source file.
- Duplicate code when manually entering. Do not fill in "Code" manually — leave it for auto-numbering.
9. FAQ
Why is the directory called "DeleteExternalProcesses"? The prefix "Delete" is placed by the 1C developer on objects that are being prepared for exclusion from the configuration. It is left for compatibility with old databases. This does not mean that you need to delete anything right now.
Can it be deleted at all? The directory itself cannot be deleted from the configuration — it is metadata. You can and should mark for deletion the elements inside that you have already transferred, and then clear them with the standard "Delete marked objects".
Where should external processes and reports be uploaded now? In "Administration" → "Print forms, reports, and processes" → "Additional reports and processes", click the "Add from file" button.
Will my processes in this directory stop working? As long as they are there and compatible with the platform — they will run. But they will not have updates and convenient buttons in documents. Transfer them to the current subsystem.
Does this directory generate ESF or STN? No. Electronic invoices (IS ESF) and STN are issued from sales/transfer documents, not from here.
Does it provide entries or affect VAT? No. The directory does not have accounting and tax movements. VAT at the rate of 16% and entries (1210/6010/3130/7010/1330, etc.) are generated by accounting documents, not this object.
I do not see the directory in the menu — is this normal?
Yes. It is hidden as outdated. Open it via the link e1cib/list/Directory.DeleteExternalProcesses.
How to retrieve the processing file back from the directory?
Open the element and, if the command is available, "More" → "Save process to file". If the command is not there — request the original .epf from the author or restore from the archive copy of the database.
Do I need to do anything with it during the regular work of the accountant? No. If you are not transferring old processes, just ignore this directory.
Does it affect month-end closing or reporting? Not at all. It does not participate in calculations of individual income tax, mandatory pension contributions, social contributions, social tax, and in regulatory operations.
10. Related documents
- Based on what it is entered: based on nothing — elements were placed here through manual file uploads in old releases.
- What is entered based on: nothing.
- Current replacement: directory "Additional reports and processes" (BSP subsystem) — this is where all work with external
.epf/.erfis moving. - Related area: "Delete marked objects" ("Administration" → "Maintenance") — to finally remove marked elements.
How to know your release
"Help" → "About the program" (or ≡ → "About the program"). The line "Configuration" will show "Accounting for Kazakhstan, version 3.0" and the release number, the line "Platform" — version 8.3.
This material was prepared for release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). In other releases, the appearance of forms may differ slightly.