Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
To be honest, without embellishments. You opened this guide not because "the counterparty sent an act, and the amount does not match." That's not how it works. Most likely, you were looking for an object in the configurator, stumbled upon it through "All Functions," or saw it in the metadata list during data transfer — and you want to understand what it is and whether you will break something if you delete the records. Let's get to the point.
It is important to understand from the first line: DeleteTaskQueue is NOT an accounting document. There are no entries, no electronic invoices (ESF), no printed forms, and no operation type "Sales." This is a service directory of platform-technical purpose. The prefix Delete in the name is not an action verb, but a label from the 1C developer: this marks objects that are left in the configuration only for compatibility and will be removed in one of the future releases. Therefore, the entire standard methodology "field → entry → print" does not apply to it, and I will not invent fictitious VAT amounts and account correspondences for an object that has none. Below is what is really important to know about it.
1. Purpose
DeleteTaskQueue is an outdated service directory that stored records of the internal queue of deferred tasks (background processing tasks). The mechanism has been replaced by standard regulatory and background tasks of the platform. In current operation, the object is not used; the records in it are a historical "tail" from previous versions or from data exchange.
2. Where to find
Through the enterprise interface, it is not displayed in sections — the service object has no command in the navigation panel of the sections "Sales," "Purchases," "Bank and Cash," etc. You can open the list in two ways:
- Main Menu → "All Functions" → "Directories" → "DeleteTaskQueue" (the "All Functions" item must be enabled: "Service" → "Parameters" → checkbox "Show the 'All Functions' command").
- Directly via the 1C navigation link. Copy the line below, then in 1C: "Service" (or window menu) → "Go to navigation link" and paste:
e1cib/list/Directory.DeleteTaskQueue
If the item is not in "All Functions," and the link opens an empty list — this is normal: for most users, the directory is empty.
2a. How to know your release
"Help" → "About the program" (or the ℹ️ icon in the upper right corner). There are two lines you need:
- Platform version — for example,
1C:Enterprise 8.3.24.xxxx; - Configuration —
Accounting for Kazakhstan, version 3.0 (3.0.74.2).
It is the second line that determines which version this instruction refers to. If your release is newer — the service directory may no longer exist: it has been removed.
3. How to "fill"
I emphasize separately: there is no need to manually create records in this directory. You will most likely not find the "Create" button active at all, and if you do find it — do not use it. Records got here programmatically, through the old queue mechanism. The fields of such a technical object are minimal and service-oriented:
| Field | Purpose | What will happen if you touch it incorrectly |
|---|---|---|
| Code | Internal identifier of the queue record. | If you change it manually — you risk violating referential integrity if there is a reference to the record somewhere. |
| Name | Technical name/description of the task. | It has no value for accounting; editing is meaningless. |
| Attributes of the status/task parameters (if present) | Stored the status and parameters of the deferred task. | Changing it does not affect anything in the current logic — the mechanism no longer reads this data. |
There are no mandatory fields for you here — because filling the object manually is not intended. The only meaningful action for the user is to delete unnecessary records if needed (see section 8).
4. "Analyzed example"
Since there are no amounts and entries in the object, I will show a real-life scenario for which it is usually opened.
Situation. You transferred the "Accounting for Kazakhstan" database to a new server, launched the update to release 3.0.74.2. The registration journal shows a warning about the old task queue, and in "All Functions," you see the directory DeleteTaskQueue with 3 records.
What to do:
- Open the list via the link
e1cib/list/Directory.DeleteTaskQueue. - You see records — they do not affect accounting: neither on 1210, nor on 3130, nor on 6010, nor on month-end closing.
- Check for references: select the record → RMB → "Find by references" (or the link search button on the form).
- If there are no references — mark for deletion and run "Administration" → "Maintenance" → "Delete marked objects".
The "entries" of this operation — there are none. This is not a business operation, but a cleanup of service data. No figure in the trial balance, in the VAT declaration (16% rate in 2026) or on individual income tax (IIT) will budge. This is the essence: the object is neutral for accounting.
5. Types of operation
The directory has no types of operation. Types of operation are attributes of documents (for example, for "Receipts" — "Goods," "Services"). They do not exist here because this is a directory, not a document.
6. What is formed when posting
Nothing. The directory is not posted. Therefore:
- No entries (Dr/Cr);
- No electronic documents (ESF in the ESF IS, SNT) — they are formed by sales/movement documents, not this object;
- It does not create movements in accounting registers (accumulation, information, accounting).
If you were looking for an object that makes entries Dr 1210 Cr 6010 and Dr 3130, as well as issues ESF — you need the documents "Sales of goods and services" / "Invoice (ESF)," not this service queue.
7. Printed forms
There are no printed forms. The service directory is not printed. Neither "Act," nor "Invoice," nor ESF can be generated from here.
8. Common errors
"Failed to delete the object: there are references to it." The platform, when deleting marked objects, reports that the queue record is used somewhere. Solution: "Administration" → "Maintenance" → "Delete marked objects" → in the report on the inability to delete, click on the line and see who is referencing it. Remove the reference (usually it is another service record) and repeat the deletion.
"Object not found" / the list is empty. This is not an error. For most databases, the directory is empty — the mechanism has not been writing to it for a long time. Nothing needs to be created.
You are trying to enter a record manually — the form does not open for the record/fields are unavailable. This is intentional: interactive creation for the service object is closed. Do not bypass this through the configurator in the working database.
You deleted records "just in case" — worried about accounting. Calm down: the deletion of these records does not affect accounting results, VAT, and taxes. If something is wrong after cleaning in month-end closing — the reason lies in another object, not this one.
9. FAQ
What is DeleteTaskQueue in simple terms?
It is an old service directory for the internal queue of deferred tasks. It is not used now, left for compatibility, and will be removed in future releases.
Can I delete records from it? Yes, if there are no references to them. Mark for deletion and run "Delete marked objects." This does not affect accounting.
Why is "Delete" written in the name? This is a label from the 1C developer for outdated objects that are temporarily left and are subject to exclusion from the configuration. This is not a command and not the status of your record.
Does it affect VAT, IIT, or month-end closing? No. It does not create entries or movements in tax registers. It does not affect the VAT declaration (2026, 16% rate) or the calculation of payroll taxes.
Does it generate ESF or SNT? No. Electronic invoices and SNT are generated by sales and movement documents, not this directory.
I don't have it in "All Functions" — is this a problem? No. Either the display of the "All Functions" command is not enabled, or in your release, the object has already been removed. Both options are normal.
Do I need to enter anything into it before submitting reports? No. It does not participate in the preparation of tax return forms, declarations, and regulatory reports.
Why do I have records in it, but my colleague does not? Records remain from old versions or from data transfers. In a clean new database, they usually do not exist.
Is it safe to clean it before database compression? Yes. It is logical to delete such service "tails" before compression, after checking for the absence of references.
Where has its functionality "moved"? To the standard regulatory and background tasks of the 1C:Enterprise platform ("Administration" → "Maintenance" → "Regulatory operations").
10. Related objects
- Based on what it appears: records were created programmatically by the old task queue mechanism and during data exchange/transfers between databases. Users do not enter them.
- What is entered based on it: nothing — the service object is not a basis for documents.
- What it is replaced by: standard regulatory and background tasks of the platform (Administration → Maintenance → Regulatory operations).
- Where to look for real accounting: documents "Sales of goods and services", "Invoice (ESF)", "Delivery Note (SNT)" — these create entries (Dr 1210 Cr 6010, Dr 3130), generate ESF, and can be printed.
How to know your release
"Help" → "About the program": the top line is the platform version, below is the release of the configuration Accounting for Kazakhstan, version 3.0. Compare with the version in the signature below to understand if the instruction is relevant for your database.
This material was prepared for "Accounting for Kazakhstan," version 3.0, release 3.0.74.2. In newer releases, the service directory may be absent.