Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
Important, read before starting. "Key Operations" is a service (technical) reference from the "Performance Evaluation" subsystem, not an accounting document. It does not create accounting entries, does not generate electronic invoices (ESF), does not calculate VAT, and does not affect amounts in reporting. It is needed to measure how quickly your actions in the database are performed (conduct a sale, open a journal, close a month). Therefore, this material does not include accounts 1210/3130 and VAT rate of 16% — there is simply nothing to apply them to here. If you were looking for an accounting object — this is not it.
The situation in which you find yourself here: the end of the month, the database is "lagging," processing an invoice takes 8–10 seconds, and you (or your administrator) need to prove with numbers that it is slow and understand what exactly is causing it. This is where "Key Operations" comes into play: you specify which actions to consider important and how many seconds they should take, and the platform starts measuring and calculating the APDEX index.
1. Purpose
The reference stores a list of user actions whose speed you want to control (process a document, open a list, generate a report). For each action, a target time is set — a standard in seconds. Based on the measurements, the APDEX index (0…1) is calculated — an integral assessment of the "comfort" of work. This is a tool for administrators and implementers, not an accounting register.
2. Where to find
Path in the menu:
- "Administration" → "Maintenance" → "Performance Evaluation" — first, enable the "Performance Evaluation" checkbox (without it, the subsystem is inactive and the list of measurements is not maintained).
- After enabling, a link to the list of key operations and the performance evaluation report will appear there.
You can open the reference directly via the navigation link: in the "Functions" / "Service" menu, select "Go to navigation link" and paste:
e1cib/list/Reference.KeyOperations
If the "Performance Evaluation" item is not visible, it means that the corresponding functional option is not enabled in your database or the user does not have administrative rights. The exact location of the item in the "Maintenance" submenu may vary slightly between releases — this is the only place that should be double-checked in your version.
2a. How to know your release
"Help" → "About the program" (or the "i" icon in the upper right corner). In the opened window, you will see two lines: platform version (for example, 8.3.24.xxxx) and configuration release — "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". It is the second line that should match the one indicated at the beginning of this instruction.
3. How to fill
Open the list, click "Create", and fill out the card. There are few fields, but each has meaning.
| Field | Required | Purpose and consequences of error |
|---|---|---|
| Name | Yes | A human-readable name for the action: "Processing Sale", "Opening Purchases List", "Closing Month". You will search for the operation in the report by this name. If left empty, you will not be able to save; if unclear, you won’t understand what was measured later. |
| Target time (sec) | Yes | The standard time within which the action should be completed (threshold T in the APDEX formula). If set too high — APDEX will always be "green," and you won’t see the problem. If too low — everything will appear "red." Realistic values: opening a list ~1 sec, processing a document ~2–5 sec, report ~5–15 sec. |
| Minimum duration of included times | No | Filters out "noise" — very quick measurements (fractions of a second) are not included in the calculation. Usually left at 0. |
| Priority | No | A number for sorting in the report: important operations are higher. Does not affect the APDEX calculation. |
| Comment | No | Your notes: on what hardware the measurements were taken, what the database volume is. Helps to recall the context after six months. |
| Group (folder) | No | The reference is hierarchical. Group by sections: "Sales", "Purchases", "Regulatory". More convenient in large lists. |
Many key operations are created automatically — upon the first measurement of the action for which measurement is provided by the developer. You only need to set the target time for them.
4. Analyzed example
You are monitoring the action "Processing Goods Sale". The target time is set to T = 3 seconds. Over the working day, the platform collected 100 measurements. Let's break them down by APDEX zones:
| Zone | Condition | Measurements |
|---|---|---|
| Satisfied (comfortable) | time ≤ T (≤ 3 sec) | 70 |
| Tolerating (tolerable) | T < time ≤ 4T (3–12 sec) | 20 |
| Frustrated (frustrating) | time > 4T (> 12 sec) | 10 |
Formula:
APDEX = (Satisfied + Tolerating/2) / Total
APDEX = (70 + 20/2) / 100 = (70 + 10) / 100 = 0.80
Result: APDEX = 0.80. On the commonly accepted scale, this is "good, but there is room for improvement":
| APDEX | Rating |
|---|---|
| 1.00 – 0.94 | Excellent |
| 0.93 – 0.85 | Good |
| 0.84 – 0.70 | Acceptable |
| 0.69 – 0.50 | Poor |
| < 0.50 | Unacceptable |
Conclusion from the example: 10% of processes take longer than 12 seconds — this is a reason to show it to the administrator. No debit/credit entries arise here — the reference stores standards, not economic operations.
5. "Types of Operations"
A regular reference does not have "types of operations" like a document. However, key operations are divided by the method of appearance:
- Automatic — created by the standard configuration, measured by built-in commands (processing main documents, opening key lists).
- User-defined (manual) — you create the card yourself and measure the action using the built-in stopwatch (time measurement command in the performance evaluation subsystem).
- Group (folders) — serve only for structuring the list, do not have measurements.
6. What is formed when using
The reference is not processed, therefore:
- No accounting entries. Movements in accounts (1030, 1210, 3310, 6010, etc.) are not created.
- No electronic documents (ESF, SNT). The subsystem has no relation to the ESF IS.
- Movements in registers: each measurement goes into a service register of information with time measurements ("Time Measurements" / technological measurements), where the connection "key operation → duration → user → date" is stored. This is where the report takes data for APDEX.
7. Printed forms
The card of the reference does not have its own printed form. Results are output in a report:
- "Performance Evaluation" (APDEX report) — a summary table for all key operations: target time, number of measurements, average duration, APDEX value, rating. There is a dynamics chart.
- The report can be exported to Excel/PDF/file and sent to technical support or the developer as objective evidence of "slowness."
8. Common errors
"Performance evaluation is disabled" (or empty report). → The checkbox in "Administration → Maintenance → Performance Evaluation" is not enabled. Enable it — and measurements will start to be collected. Data for the past will not appear: only what happens after enabling is measured.
"The field 'Name' is not filled" / "The field 'Target time' is not filled." → Both fields are mandatory. Fill in the name and standard in seconds, then "Save and close."
"APDEX is always 1" — while the database is clearly lagging. → The target time is set too high. Reduce T to a realistic value (2–5 sec for processing) — the picture will become honest.
"All operations are red, although it works fine." → The opposite situation: the target time is set too low. Raise T to match users' real expectations.
"Not enough rights to view." → The reference is administrative. An administrator profile or rights to the maintenance subsystem are required.
9. FAQ
Does the "Key Operations" reference affect accounting, taxes, or amounts in declarations? No. This is purely a technical tool for measuring work speed. It does not create entries, does not calculate VAT (in the RK from 2026 — 16%), does not generate ESF, and does not participate in month-end closing in terms of accounting.
What is "target time"? A standard in seconds within which the action should be completed. This is the threshold T in the APDEX formula: measurements faster than T are considered comfortable, up to 4T — tolerable, longer than 4T — frustrating.
How to enable measurement collection? "Administration" → "Maintenance" → "Performance Evaluation" → check the "Performance Evaluation" checkbox. After that, the platform will start recording the duration of key actions.
How is APDEX calculated? APDEX = (number of comfortable + number of tolerating / 2) / total number of measurements. Value ranges from 0 to 1. Example: (70 + 20/2)/100 = 0.80.
Why is the list of key operations empty? Either the subsystem has just been enabled and there have been no measurements yet, or no automatic operations are registered in the database. Many cards are created automatically upon the first measurement of the corresponding action.
Can key operations be deleted? Yes, through marking for deletion and processing "Delete marked objects." But if the operation is created automatically, it will reappear at the next measurement. It is easier to set a large target time for it or move it to a separate group.
Does a regular accountant need this? Typically, no. This is a tool for administrators/implementers. It is useful for an accountant only in one situation — when the database is lagging and it is necessary to objectively (in numbers) show this to a specialist.
Where to see the results of measurements? In the "Performance Evaluation" report in the same subsystem. There is a table of operations with APDEX and a dynamics chart; the report can be exported and sent to support.
Are measurements collected "retroactively"? No. Only what happens after the subsystem is enabled is measured. The history before enabling cannot be restored.
Does the measurement collection itself slow down work? The overhead is minimal — only the duration and service data are recorded. For regular operation, this is safe.
10. Related objects
- Subsystem "Performance Evaluation" (section "Maintenance") — the parent mechanism: enabling collection, configuration, report.
- Information register with time measurements — this is where the measurement results are written, linked to the key operation; APDEX is built from it.
- Report "Performance Evaluation" (APDEX) — consumer of the reference data.
- Technological journal / APDEX measurements of the platform — external to the configuration tool of the same purpose (for in-depth analysis by the administrator).
How to know your release
Menu "Help" → "About the program": the top line is the version of the 1C:Enterprise platform, the bottom line is the configuration release. The instruction is relevant for the line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". In neighboring releases, the names of fields and the logic of APDEX do not change; only the exact location of the menu item may differ.
This material was prepared for the configuration "Accounting for Kazakhstan", version 3.0, release 3.0.74.2.