---
title: "Report \"Duration of Deferred Update\" in 1C:Accounting for Kazakhstan 3.0"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/otchet-dlitelnost-otlozhennogo-obnovleniya-v-1s-buhgalter-en
source: BuhGPT
---

# Report "Duration of Deferred Update" in 1C:Accounting for Kazakhstan 3.0

> **TL;DR:** Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0). You have updated the configuration to the new release. Two days have passed, and the yellow message still hangs in the header of the database: "Data update in progress, working with some data is temporarily

---

Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).

You have updated the configuration to the new release. Two days have passed, and the yellow message still hangs in the header of the database: "Data update in progress, working with some data is temporarily unavailable." Users are complaining: some reports are generated strangely, and certain documents do not open. You want to understand a simple thing — how long this has been going on, which handler is currently running, and whether it has "hung" forever. This is exactly why the report "Duration of Deferred Update" is opened.

First, an important warning so that you do not look for what is not here. This is a service (technical) report of the version update mechanism of the information base. It is not about accounting: it has no entries, it does not generate electronic invoices (ESF) or tax returns (SNT), does not make movements in accounting registers, and is not related to VAT rates, MRP, individual income tax (IIT), or the chart of accounts. The rates and tax parameters of Kazakhstan for 2026 (VAT 16%, MRP 4,325 ₸, minimum wage 85,000 ₸, accounts 1210/3310/3130, etc.) have no relation to this object. The report answers exactly one question: how long and with what result the deferred update handlers have been processed.

1. Purpose

The report shows a list of deferred data update handlers and their execution time: when each started, how long it ran, and what status it finished with. It is needed by the administrator and the chief accountant of the database to diagnose why the update is taking so long and to find a specific "heavy" or faulty handler.

2. Where to find

Path through the interface:

Reference Information and Administration → Maintenance → Data Update of the Information Base → follow the link about the progress of deferred processing → command/hyperlink "Duration of Deferred Update".

If the section is not visible, the report can be opened directly through "Main Menu → All Functions → Reports" (the "All Functions" item must be enabled in Service → Options → Show the "All Functions" command).

The fastest way is through the navigation link. Copy it and open it via "Service → Go to Navigation Link" (or Ctrl+click in some forms):

e1cib/list/Report.DurationOfDeferredUpdate

Administrator rights (or a role in the information base update subsystem) are required for access. A regular user with only accounting rights will not be able to open the report.

2a. How to know your release

Main Menu (☰ icon or "Help") → About the Program. In the opened window, you will see:

- Platform version — for example, 8.3.24.xxxx (the number of "1C:Enterprise");

- Configuration / release — "Accounting for Kazakhstan", version 3.0, version (release) 3.0.74.2.

It is the release of the configuration that determines the composition of deferred handlers, which is why this instruction is tied to 3.0.74.2. If you have a different release, the set of rows in the report will differ.

3. How to fill

This is a report, so "filling" means setting parameters and clicking "Generate". There are no separate mandatory attributes for input; the report itself takes data from the update execution log. The following settings control the output:

- Period (key). Sets the interval for which the launches of handlers are shown. If you set too narrow dates, you will see an empty table, even though the update was in progress. Set the period with a margin: from the date of the release update to the current moment.

- Status filter. Allows you to keep only the necessary rows: "Completed", "In Progress", "Error", "Not Executed". If you are looking for a "hung" handler, filter for "In Progress" and "Error".

- Grouping / sorting by duration. Enable sorting in descending order of duration — you will immediately see the heaviest handlers at the top of the list.

- Detailing by queues. In some releases, handlers are divided into queues (execution order). Grouping by queue shows at which stage the update got stuck.

This report does not write anything to the database: incorrectly selected period or filter only spoils the view on the screen, not the data. Therefore, "incorrectly filling" here is safe — just reformat with different settings.

4. Analyzed Example

Situation. On September 3, 2026, you updated the database to release 3.0.74.2. Today is September 6, and the message about data updating still hangs. You open the report, period — from 03.09.2026 to 06.09.2026, sorting by duration in descending order. You get a table like this:

Handler
Start
End
Duration
Status

Recalculation of batches and cost
03.09.2026 22:10
05.09.2026 04:37
1 d 06:27
Completed

Filling new attributes of electronic invoice (ESF)
05.09.2026 04:37
05.09.2026 09:12
04:35
Completed

Updating the mutual settlements register
05.09.2026 09:12
—
(in progress) 22:48
In Progress

Indexing the counterparty directory
—
—
—
Not Executed

How to read this:

- The longest handler is the recalculation of batches, more than a day. This is normal for a large database: the update is "hanging" because of it.

- Currently, "Updating the mutual settlements register" is running — almost a day. As long as it is in the status "In Progress" without errors — there is no need to panic, wait for completion.

- The next handler is still "Not Executed" — it will start after the current one.

Since this is a technical report, it does not generate debit/credit entries — neither on these lines nor on any others. Showing accounting entries here would be incorrect: update handlers restructure internal registers and attributes, rather than reflect business transactions. If you were looking for sales entries (Debit 1210 Credit 6010, Debit 3310 Credit 3130, etc.), they should be viewed in accounting documents, not in this report.

The practical conclusion from the example: the update has not "hung", but is honestly processing a heavy handler. To speed it up — run the update in exclusive mode (see section 8).

5. Types of Operations

The service report does not have "types of operations" in the accounting sense. There are viewing modes that it provides:

- All handlers for the period — a complete list.

- Only running — what is currently in progress.

- Only with errors — handlers that have completed with errors.

- By duration — ranking of the longest.

- By queues/stages — order of execution.

6. What is formed when conducting

The report is not conducted — it has no "Conduct" button because it is not a document. Accordingly:

- there are no entries — movements in the chart of accounts are not created;

- electronic documents are not generated — neither electronic invoices (ESF) nor tax returns (SNT) are issued here;

- there are no movements in accounting registers — the report only reads service data about the progress of the update, it does not write anything to them.

The result of the work is a tabular document on the screen (a generated table with rows of handlers). It can be saved or printed.

7. Printed Forms

The report does not have separate forms (like an invoice or act) — the printed form is the generated tabular document itself. Standard actions of "1C:Enterprise" are available with it:

- Print the generated table (Ctrl+P);

- Save as... — to a file (.mxl, Excel .xlsx, PDF);

- Email directly from the report.

These files are convenient to attach in a request to the consultation line or a 1C partner when the update is taking unusually long.

8. Frequent Errors

"Insufficient rights to perform the operation on Report.DurationOfDeferredUpdate".
The user does not have administrator rights / a role in the update subsystem. Log in as a user with full rights or ask the administrator to add the role.

The report is generated empty.
Two reasons. The first — the deferred update has already been completed and the data has been cleared (then the message about the update in the header also disappeared — everything is fine). The second — the period is incorrectly set: expand it from the date of the release installation to today.

The message "Data update in progress..." hangs for days, but a normal cost calculation/month-end closing is needed.
While the deferred update is in progress, some data may be considered incorrect. Speed up the process: finish user sessions and run the database in exclusive mode — then the handlers process much faster than in the background. You can manage the launch in Reference Information and Administration → Maintenance → Data Update of the Information Base.

The handler line is in the status "Error".
The update cannot be completed until the handler has successfully processed. Open the handler card from the data update section, check the error message, and repeat the launch (the "Run Again" button). If it does not help — save the report and contact the 1C consultation line.

The scheduled task "Deferred Update" is disabled.
In a client-server database, background updates occur through a scheduled task. If it is turned off, the handlers do not start, and the message hangs indefinitely. Check: Reference Information and Administration → Maintenance → Scheduled and Background Tasks.

9. FAQ

What is this report and why does an accountant need it?
A service report of the update mechanism. It shows how long deferred handlers have been running after the release change. The accountant needs it to understand why the database is "updating" slowly and when it will finish.

Does it affect accounting, entries, and taxes?
No. It does not create entries, does not touch amounts and rates (VAT, IIT, MRP). It is diagnostics, not an accounting document.

Does it generate electronic invoices (ESF) or tax returns (SNT)?
No. This report does not issue electronic documents at all.

Why is the report empty?
Either the deferred update has already been fully completed (data cleared), or you have set too narrow a period. Expand the period and reformat.

How long should the deferred update take?
It depends on the volume of the database and the composition of the release handlers: from minutes to several days on large databases. As long as the handlers are in the status "In Progress" without errors — this is normal.

Can I work in the database while the deferred update is in progress?
Yes. The update runs in the background, only the part of the data currently being restructured by the handler is unavailable. However, month-end closing and cost calculations are better done after completion.

How to speed up the update?
Finish user sessions and run the database in exclusive mode — in the "Data Update of the Information Base" section, handlers can be processed forcibly and faster than in the background.

Where to see the reason for the handler error?
In the line with the status "Error" — from the "Data Update of the Information Base" section, the handler card opens with the error message and the restart button.

Are special rights needed to open the report?
Yes, administrator rights (role in the update subsystem). The report is not available to a regular user.

The report does not open via the navigation link — what is wrong?
Either you do not have rights, or in your release, the object is called differently. Open it through "All Functions → Reports" or from the data update section of the information base.

10. Related Documents

This report is not "entered based on" and does not generate other documents. It works in conjunction with the version update mechanisms of the information base:

- Data Update of the Information Base (form in the Reference Information and Administration → Maintenance section) — the main entry point, from where the progress of the update is visible and this report is launched.

- Results of the program update — what is new in the release and completion status.

- Scheduled task "Deferred Update" — background execution of handlers (Maintenance → Scheduled and Background Tasks).

- Registration log — detailed technical messages and errors if the report showed a faulty handler.

How to know your release

Main Menu (☰) → Help → About the Program. There, the version of the "1C:Enterprise" platform and the release of the configuration are indicated. If the release differs from the one specified below — the composition of deferred handlers in your report will be different.

Material prepared for "Accounting for Kazakhstan", version 3.0, release 3.0.74.2.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_