Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
Friday, end of the month, everyone is closing periods. Accountants call and say the same thing: "the database is hanging," "the transaction takes a minute," "reports won't open." The director asks: "How bad is it in numbers?" — and you have nothing to show except feelings. This is where the report "Performance Assessment" comes in. It turns complaints of "slowness" into a specific number: the APDEX index from 0 to 1 and an assessment of "excellent / good / poor" for each key operation. With this, you can go to the administrator or the 1C franchisee and speak concretely.
First and foremost: this is a service (technical) report, not an accounting document. It does not create journal entries, does not generate electronic invoices (ESF) or tax returns, does not affect accounting, and does not change any amounts. It only measures how many seconds operations take in your database. Therefore, there will be no sections about account 1210, VAT 16%, or tax entries here — they are physically absent, and it would be misleading to invent them.
1. Purpose
The report shows the actual time taken to perform key operations (document processing, form opening, report generation) and consolidates it into the APDEX index — a single measure of "satisfaction" with speed. It is needed to objectively assess the performance of the database, find the slowest operations, and track whether it has become faster or slower after modifications, updates, or migration to a new server.
2. Where to find
The report belongs to the "Performance Assessment" subsystem within the Library of Standard Subsystems.
Menu path:
Administration → Maintenance → block "Performance Assessment" → command "Performance Assessment Report" (or "Performance Assessment").
Quick way — 1C navigation link. Menu Service (or the "star" icon/More) → "Go to navigation link" → insert:
e1cib/list/Report.PerformanceAssessment
The link opens the report directly, even if the command is hidden in the interface.
The exact location of the block in the "Maintenance" section may vary slightly between releases — this is the only place in the instructions that should be checked against your version. Everything else works the same.
2a. How to know your release
Help → About the program (or the ℹ️ icon in the upper right corner). In the opened window:
- Platform version (e.g., 8.3.24.xxxx) — the "1C:Enterprise";
- Configuration — "Accounting for Kazakhstan," release 3.0.74.2.
If your release is older — some settings may be named differently. The instructions are written for 3.0.74.2.
3. How to enable measurements and configure the report
The key point: the report will show data only if measurements are enabled in advance. The database itself does not store time — it needs to start collecting it.
Step 1. Enable measurements (MANDATORY)
Administration → Maintenance → Performance Assessment → check the box "Perform performance measurements" (in some releases — "Performance assessment is enabled").
What happens if you don't enable it: the report will open empty and say that there is no data. People often "assess performance" retroactively and are surprised by the empty table — that’s not how it works. Enable it → work in the database for a week → check the report.
Step 2. Check the scheduled task
Enabling measurements activates the background (scheduled) task "Processing performance measurements". It periodically transfers accumulated data to the database. In the file version, it works only when the database is open; in the client-server version — according to the schedule on the server. If the task is disabled, data will not be aggregated.
Step 3. Set key operations and target time
In the performance assessment settings, there is a list of key operations and for each — target time (T, in seconds). This is the standard: how long the operation should take for the user to be satisfied.
- Key operation — what we are measuring (e.g., "Processing document Sale of goods and services").
- Target time (T) — threshold. If it fits within T — "good". Up to 4×T — "tolerable". More than 4×T — "poor".
What happens with incorrect settings: if you set the target time to 0.1 seconds where it actually needs to be 2 seconds, the APDEX will always be low and the report will become a panic generator. If you set it to 30 seconds — the report will always be "green," and you won't see real slowdowns. The target time is set based on common sense and typical values (processing a simple document — about 1 second).
Step 4. Configure the report parameters
When opening the report, set:
- Period (MANDATORY) — for which interval we take measurements. A period that is too short — too little data, unreliable statistics; too wide — mixes "before" and "after" modifications.
- Key operation — can select one or all.
- User / priority — if necessary, leave only the needed ones.
- Report variant — summary, dynamics, detail (see section 5).
Click "Generate".
4. Analyzed example with numbers
You enabled measurements last week. You configured the key operation "Processing document Sale of goods and services", target time T = 1 second. During the reporting period, 100 measurements were accumulated.
The report laid them out as follows:
- 70 transactions fit within 1 second (user is satisfied — satisfied);
- 20 took from 1 to 4 seconds (tolerable — tolerating, zone T…4×T, i.e., 1–4 seconds);
- 10 took more than 4 seconds (frustrating — frustrated).
The APDEX index is calculated using the formula:
APDEX = (N satisfied + N tolerating / 2) / N total
APDEX = (70 + 20/2) / 100 = (70 + 10) / 100 = 0.80
The report will output the row:
| Key operation | Target time, s | Measurements | Avg. time, s | APDEX | Assessment |
|---|---|---|---|---|---|
| Processing sale of goods and services | 1.0 | 100 | 1.6 | 0.80 | Satisfactory |
How to read the APDEX assessment (standard scale):
| APDEX index | Assessment |
|---|---|
| 0.94 – 1.00 | Excellent |
| 0.85 – 0.93 | Good |
| 0.70 – 0.84 | Satisfactory |
| 0.50 – 0.69 | Poor |
| 0.00 – 0.49 | Unacceptable |
Conclusion from the example: 0.80 — "satisfactory," but 10% of transactions are slowing down for more than 4 seconds. There is room for improvement: we look at which hours and which users experience long measurements, check for locks and document volume.
Once again, I emphasize: this operation does not create any debit/credit entries. The only "movements" are the recording of the time measurements in the internal register (see section 6).
5. Types of operations (report variants)
The report can show the same measurements in different perspectives — switch the report variant:
- Summary assessment — APDEX and assessment for each key operation over the period (as in the example).
- Dynamics (by days/weeks) — how APDEX changed over time. The main variant to prove "it became faster/slower after the update."
- By users — who has slower operations (often this is the workplace or communication channel, not the database).
- Detail of measurements — a list of individual measurements with exact times; helps catch specific "spikes."
- Priority operations — only those marked as critical.
6. What is formed during work
Here it is honest and brief, because this is a report, not a document:
- No journal entries. The report does not create and cannot create any accounting movements in accounts (1210, 1030, 3310, 3130, 6010, 7010, etc.).
- No electronic documents. This report does not issue either electronic invoices (ESF) or tax returns — it has no relation to sales and VAT.
- Movements in registers: the time measurements themselves are written to the service information register of the subsystem (measurements of key operations' time). The report only reads this register and aggregates data — the database does not change when the report is generated.
- Result of work — a table/chart on the screen that can be saved or printed.
7. Print forms
There is no separate "print form" like an invoice here — this is a report. But the result can be output and transmitted:
- Print the report result (
Print/ Ctrl+P) — the APDEX table goes to the printer. - Save to a file via
More→Save as…: Excel (.xlsx), PDF, spreadsheet (.mxl), HTML. - Email the generated report (if the email account is configured).
It is usually PDF/Excel that is attached to the request to the 1C franchisee as proof of slowdowns.
8. Frequent errors
"No data for the report" / report is empty. Reason: measurements were not enabled at the time for which you are viewing the report, or the period selected is before the enabling. Correction: enable "Perform performance measurements," work in the database for a few days, then generate the report for the already past period.
APDEX equals 0 or 1 for all operations. Reason: incorrect target time. Setting T too small — everything is "unacceptable"; too large — everything is "excellent." Correction: set a realistic target time for each key operation.
"Scheduled task 'Processing performance measurements' was not executed."
Reason: in the file database, it has not been opened for a long time, or in the client-server version, the scheduled task is disabled. Correction: enable the task in Administration → Maintenance → Scheduled and background tasks, check the schedule.
Measurements are suspiciously few (single digits) during active work. Reason: only what is marked as a key operation is measured, and the required operation was not added to the list. Correction: add the operation of interest to the performance assessment settings.
Data has accumulated but takes up a lot of space. Reason: measurements have been stored for a long time and are not cleaned. Correction: set a retention period / periodic cleaning of old measurements to avoid bloating the database.
9. FAQ
Does this report create journal entries or affect accounting? No. This is a service technical report. It does not create journal entries, does not touch accounts and amounts, does not generate electronic invoices (ESF) or tax returns. It only measures the time taken for operations.
Why is the report empty, although the database is clearly slow? Because measurements were not enabled in advance. The report only shows already accumulated data. Enable "Perform performance measurements" and return to the report after a few days of work.
What is APDEX in simple terms? It is an index from 0 to 1, showing the proportion of operations performed quickly enough. 1 — all fast and users are satisfied, 0 — all slow. It is calculated based on the target time: if it fits within T — plus a point, up to 4×T — half a point, longer — zero.
What target time should be set? As long as the operation should take for the user not to be irritated. For processing a regular document, it is about 1 second, for a heavy report — more. The value is tailored to the specific operation.
Will enabling measurements slow down the database itself? The impact is minimal — only the start and end times of key operations are recorded. Against the backdrop of normal work, this is unnoticeable, but you get an objective picture.
The report shows low APDEX only for one user — is the database slow? Probably not. If the problem is with one person, it is usually their workplace or communication channel (thin client over slow internet). Check the "By users" variant to separate the database problem from the workplace issue.
Can performance before and after the update be compared? Yes. Use the "Dynamics" variant and build a report for a period covering both dates. A drop or increase in APDEX will be visible on the graph.
How to transmit the result to the 1C franchisee or administrator?
Generate the report and save it via More → Save as… in Excel or PDF, attach it to the request. This is objective proof of slowdowns instead of saying "everything is hanging."
Does this report change accounting data?