Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
You have updated the configuration to a new release, you open a regular sales document — and it is not processed. Or the balances in the report do not match those that were fine yesterday. A yellow banner hangs at the bottom of the window: "The program update is not complete, some data is being processed in the background." This is not a malfunction. After a major update, part of the work in 1C is done not immediately, but in batches in the background — so you can work while the old data is being recalculated. The report "Progress of Deferred Update" is exactly where you can see how much is left, what is stuck, and what has failed with an error.
1. Purpose
The report shows the status of deferred update handlers — background procedures that write and recalculate data after the release change. You see a list of handlers, their status (completed / in progress / error / paused) and the percentage of readiness. This is a service, technical report — it does not make accounting entries and does not generate electronic invoices (ESF)/SNT, it only diagnoses the progress of the update.
2. Where to find
Two ways:
- Through the menu: section "Administration" → "Maintenance" → block "Configuration Update / Program Update Results" → link "Progress of Deferred Update" (or "Not all update handlers have been completed" — if there are unfinished ones).
- Through the 1C navigation link: menu "Service and Settings" (gear icon at the top right) → "File" → "Open URL…", or "Main Menu" → "Go to Navigation Link", and paste:
e1cib/list/Report.ProgressDeferredUpdate
The link will open the report directly, even if the menu item is hidden.
The report is available to users with administrator rights. A regular accountant usually does not see it — if the banner about the unfinished update is hanging, call someone with the "Administrator" profile.
2a. How to know your release
"Main Menu" (icon at the top left) → "Help" → "About the Program". In the opened window:
- Platform version — for example, 8.3.24.xxxx (line "1C:Enterprise").
- Configuration release — line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)".
These numbers are what you should mention in support. The instructions below are described for release 3.0.74.2; in neighboring releases, the set of handlers and button labels may differ.
3. How to fill (what settings are there)
This is a report, not a document, so there is almost nothing to "fill" — but the control elements are important.
| Element | Purpose | What will happen if ignored |
|---|---|---|
| "Refresh" / "Generate" button | Re-reads the current state of the handlers. Progress in the background is ongoing constantly, while the screen image "freezes". | You will be looking at outdated numbers and will think that everything is stuck, while the handler has already reached 90%. |
| Status filter (checkbox "Show only unfinished") | Filters out hundreds of already completed handlers, leaving only what really requires attention. | You will drown in a long list and not notice the only handler with an error. |
| Grouping by subsystems/libraries | Shows which block the handler belongs to (VAT accounting, payroll, standard subsystems). | Harder to understand which area of accounting is still "not ready". |
| "Execute" link/button on the handler line | Launches a specific handler with priority, without waiting for the queue. | The handler will just wait its turn in the background for hours. |
| "Details" / "Reason" link for a handler with the status "Paused" or "Error" | Opens the text of the problem: what was missing, which handler blocked the queue. | You won't understand why the update has stalled and will be guessing. |
There are no separate mandatory input fields here — the report opens already filled with the current state of the database. Your task is to read the statuses and, where necessary, click "Execute".
4. Analyzed example
You updated from 3.0.73 to 3.0.74.2 in the evening. In the morning, the accountant complains that the month-end closing is not processed. You open the report, click "Refresh" and see:
| Handler | Subsystem | Status | Progress |
|---|---|---|---|
| Filling in the attributes of sales documents | VAT accounting | Completed | 100 % |
| Recalculation of the "VAT to be refunded" register | VAT accounting | Completed | 100 % |
| Updating ESF/SNT data | Electronic documents | In progress | 68 % |
| Recalculation of tax registers for individual income tax/social tax | Payroll and personnel | Paused | 0 % |
| Re-filling of account 1210 analytics | Mutual settlements | Error | 41 % |
Total: handlers — 47, completed — 44, in progress — 1, paused — 1, error — 1. Overall progress — 94 %.
What you do step by step:
- Handler "In progress" (68 %) you leave alone — it is running by itself, just give the background time to finish. After 10 minutes, you click "Refresh" — it has become 100 %.
- "Paused" — you open "Reason". It says: waiting for the completion of the handler "Re-filling of account 1210 analytics". So the queue is stuck because of the neighbor with an error.
- "Error" (41 %) — you open the details, see the error text (for example, "Documents with an unfilled counterparty detected"). You fix the cause (fill in the problematic documents), return to the report and click "Execute" on this line — the handler reaches 100 %.
- After that, the paused handler for individual income tax/social tax is automatically picked up by the queue. You click "Refresh" — progress is 100 %, the banner about the unfinished update disappears, and the month-end closing is processed normally.
This report does not make any debit/credit entries — it only showed that the re-accounting of analytics for account 1210 (short-term receivables from customers) was "stalled", and allowed you to fix it. The entries are generated by the documents themselves after the update is completed.
5. Types of operations (statuses of handlers)
There are no separate "types of operations" like in a document — there are handler statuses that you read:
- Not executed / Waiting — in the queue, not started yet.
- In progress — running right now, percentage visible.
- Completed — data recalculated, area ready.
- Paused — waiting due to dependency (waiting for another handler) or manual stop.
- Error — interrupted; you need to fix the cause and restart.
6. What is formed during work
Honestly: this report does not generate any accounting entries, tax movements, or electronic invoices (ESF)/SNT. It reads service data about the progress of the information base update and displays it on the screen.
The real consequences are given by the handlers themselves, the status of which you are monitoring: they write attributes into old documents, recalculate VAT registers, tax registers for individual income tax/social tax/OSMS/social tax, re-fill account analytics (1210, 3310, 1330, etc.). While the handler is not completed — the corresponding area may provide incomplete data, which is why 1C asks you to wait for 100 %.
The "Execute" button in the report is the only action that changes data: it forcibly brings a specific handler to completion.
7. Printed forms
There are no classic printed forms (like invoice or act) for this service report. The standard for reports is available:
- "Print" — outputs the status table to paper/PDF (convenient to attach in a support request).
- "Save as…" — export to Excel (
.xlsx), Word, spreadsheet document (.mxl), PDF. - Copying error text from the details window — to send to the developer or 1C partner.
8. Frequent errors
"Not all update handlers have been completed. Some data is being processed in the background." This is not an error, but a norm right after the update. Give the background time to finish; if the database is running on schedule/in a session without background tasks — open the report and click "Execute" manually.
"Update handler completed with an error." Open "Details", read the text. Most often, "dirty" data interfere (unfilled counterparty, contract, organization in old documents). Fix the violating document and click "Execute" again.
Progress has "frozen" and is not moving. The screen image is static — click "Refresh". If background tasks are really not running (file database, all sessions closed) — handlers will not start by themselves: keep the session open or run with priority using the "Execute" button.
"Execution of deferred handlers is blocked by another session." The update is already running under another user/in another session. Do not start it in parallel — wait until it is released, otherwise you risk a lock conflict.
Documents are not processed / month is not closed after the update. While the accounting area is not fully updated, processing may be blocked. Bring the handlers of this subsystem to 100 % and repeat the processing.
"Handler paused" and is not moving. It is waiting for a neighboring handler. Find the one with an error or "in progress", deal with it first — the queue will move on by itself.
9. FAQ
Does this report do anything for accounting? No. It does not make entries, does not calculate taxes, does not generate electronic invoices (ESF) or SNT. It is a diagnosis of the update process. The data is changed by the handlers, not the report itself.
Can I work while the update is not completed at 100 %? Yes, in most cases you can. This is exactly why the update was made to run in the background. But certain operations (processing part of the documents, some reports) may be blocked until the necessary handler reaches completion.
How long does a deferred update take? It depends on the size of the database: from minutes to several hours on large databases. Major recalculations (VAT, mutual settlements, payroll for many periods) are the longest. Check the percentage for a specific handler.
Handler stopped with an error — is the database broken? No. An error in one handler does not break the database, it only leaves its area un-updated. Fix the cause from the details and click "Execute" again.
What to do if the percentage does not change? First, click "Refresh" — the screen might be showing the old state. If background tasks are not running in your database (file mode, closed sessions), manually start the handler using the "Execute" button.
Can I speed up the update? Yes — execute the necessary handlers with priority using the "Execute" button, without waiting for the queue. Do this during non-working hours: priority execution loads the database and may interfere with users.
Who can open this report? A user with administrator rights. A regular accountant usually only sees the warning banner; administrative rights are needed to manage handlers.
Is the report related to the VAT rate of 16% or taxes for 2026? Directly — no. It is technical. But the handlers it controls may recalculate tax registers under the new rules (VAT 16%, individual income tax deduction of 30 MRP, social tax limits) after the release update — so it is important to bring them to 100 % before submitting reports.
Is it necessary to make a backup before running handlers? Before updating the configuration — definitely. The report itself does not require a backup, but if there is a lot of data in the database and handlers are massively recalculating registers, a fresh backup will not be superfluous.
The report showed 100 %, but the banner about the unfinished update remains. What to do? Click "Refresh", then reopen the window. If the warning hangs after that — restart the 1C session; the completion status is recorded at the next login.
10. Related documents and objects
The report "Progress of Deferred Update" is not introduced "on the basis of" and does not generate documents itself. It works in conjunction with the service mechanisms of the update:
- "Configuration Update / Program Update Results" (section "Administration" → "Maintenance") — the main center from where this report is opened.
- Deferred update handlers (subsystem "Information Base Update" of standard subsystems) — that whose progress you see.
- Log of registrations (section "Administration" → "Maintenance" → "Log of registrations") — there are also details of errors. ```