Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
A counterparty sent an act for 1,392,000 ₸, but in your database this same sale shows 1,508,800 ₸. Or you clearly remember posting a payment order for 850,000 ₸, but you open it today — and there it's 580,000 ₸ and a different account. Asking "who touched it?" is useless — everyone throws up their hands. This is exactly when you open "Analysis of Object Versions". The report shows the change history of documents and reference items: who created it, who edited it, what exactly they changed and when. Then you compare two versions line by line and see that a manager raised the amount retroactively but didn't recalculate the VAT.
1. Purpose
The report builds a summary of saved object versions (documents, reference items). It answers three questions: which objects were changed, who changed them and how many versions accumulated. From the report you drill down into a comparison of specific versions and see the changed attributes word for word. This is a control and investigation tool, not an accounting document — it makes no postings.
Important: the report works only for those objects for which versioning is enabled. If the mechanism is disabled, the report will be empty (see section 8).
2. Where to find it
The report belongs to the versioning subsystem (a standard platform mechanism), so it lives in administration:
- Administration → Change history → Reports (or the "Analysis of Object Versions" button);
- if you don't see it — Main → All functions → Reports → Analysis of Object Versions (the "All functions" item is enabled in "Service → Options → Show the 'All functions' command").
The exact position of the menu item drifts a little between releases — this is the only thing worth double-checking in your build.
The fastest way is a navigation link. Copy it, then in the 1C menu "Service" (or the main menu) → "Go to navigation link", paste it and click OK:
e1cib/list/Отчет.АнализВерсийОбъектов
2a. How to find out your release
The menu "Help" → "About" (or the "i" icon). In the window that opens: at the top — the platform version (for example, 8.3.24.xxxx), below — the configuration release ("Accounting for Kazakhstan, edition 3.0, version 3.0.74.2"). Compare this guide specifically against the configuration line.
3. How to fill in (set up the report)
The report is configured through the header and "Settings" (the "More → Change variant" button or "Settings"). Key fields:
| Field | Why it's needed and what happens if you get it wrong |
|---|---|
| Period (required) | Limits the version creation dates. Too narrow — you won't see the change you need; too wide on a large database — the report will take a long time to build. Set an interval that the edit definitely falls into. |
| Object type / Object | Filter by a specific kind (for example, "Sale of goods and services") or by a single document. If left empty — the report will list all objects in a row, and you'll drown in a heap of versions. For an investigation, always narrow it down to the needed document. |
| User (Version author) | Filter by who made the change. Useful when you suspect a specific employee. Get the user wrong — and you'll "lose" the real edits. |
| Report variant (must be selected) | Determines what you'll see: a list of versions, top objects by number of versions, or dynamics over dates. The wrong variant — correct data in an inconvenient breakdown. |
| Filter by attributes | In the advanced settings you can select versions where a specific field was changed (for example, "Document amount"). It helps you avoid scrolling through dozens of technical re-saves. |
Order of work: set the period → select the object type (or a specific document) → if necessary specify the user → "Generate". Then in the result, double-click to open the versions and press "Compare versions".
4. Worked example
Situation. The buyer LLP "Astana-Trade" sent a reconciliation act: for sale No. 125 dated 20.08.2026 they have an amount of 1,392,000 ₸. In your database — 1,508,800 ₸. Discrepancy of 116,800 ₸.
What you do:
- Open "Analysis of Object Versions", period — August 2026, object type — "Sale of goods and services", object — document No. 125.
- Generate. You see two versions:
| Version | Date/time | Author | Document amount |
|---|---|---|---|
| No. 1 (creation) | 20.08.2026 09:14 | Ivanov A. (manager) | 1,392,000 ₸ |
| No. 2 (change) | 03.09.2026 17:40 | Petrov S. | 1,508,800 ₸ |
- Select both rows → "Compare versions". The report highlights the changed fields: the quantity of goods increased, which recalculated income excluding VAT (was 1,200,000 → became 1,300,000) and VAT 16% (was 192,000 → became 208,000).
Verification by the figures of version No. 1 (the one the counterparty has):
- Income excluding VAT: 1,200,000 ₸
- VAT 16%: 1,200,000 × 16% = 192,000 ₸
- Total: 1,392,000 ₸ ✓ matches the buyer's act.
Postings of the sales document (for clarity — they are made by the sale itself, not by the report), version No. 2:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1,300,000 | Revenue from sales (excluding VAT) |
| 1210 | 3130 | 208,000 | VAT 16% payable |
| 7010 | 1330 | 900,000 | Cost of goods written off |
Conclusion from the report: the edit on 03.09 was made by Petrov, who raised the quantity retroactively. This is exactly why the act and the database diverged. Next you decide: either return the document to the amount of 1,392,000 ₸ (and reissue the ESF), or agree the new amount with the buyer. The report gave the main thing — the fact, the author and the content of the edit.
5. Operation types (report variants)
The report has no "operation types" like a document, but it has ready-made presentation variants — selected in the "Report variant" field:
- List of object versions — line by line: object, version, author, date, comment. The main mode for investigation.
- Number of versions by objects — top documents and reference items by number of edits. Shows the "hot" objects that get rewritten most often.
- Dynamics of version creation — by dates/periods: when and how many versions appeared. Convenient for catching spikes of mass re-postings.
- By change authors — a summary by users: who created how many versions.
Plus any variant can be reshaped via "Change variant" (groupings, filters, fields).
6. What is generated on building
The report posts nothing and creates nothing — no postings, no movements in accounting registers, no electronic documents. It does not issue ESF or SNT — this is done by the sale/purchase documents themselves, and the report only shows how they changed.
The report takes data from the service version storage — the information register "Object versions", where the versioning mechanism stores a copy of the object at each recorded change. Therefore, the depth of history depends on:
- enabled versioning for the needed object type;
- the version retention period (in the settings you can limit it, for example, "keep for the last N months");
- the fact that the versions were not cleared by the scheduled operation for deleting obsolete versions.
Everything is configured in Administration → Change history → Versioning settings: there, for each type of objects, a mode is set ("Version" / "Version on posting" / "Do not version").
7. Printed forms
The report has no separate form — the result itself is printed:
- Print (Ctrl+P) — output of the generated table to the printer;
- Save as… — export to Excel (.xlsx), .mxl, PDF, HTML;
- Send — as an email attachment;
- Version comparison can also be printed/saved — convenient to attach to a memo as proof of the edit.
8. Common mistakes
"No data to generate the report" / the report is empty. Cause No. 1 — versioning is disabled for this object. Go to Administration → Change history → Versioning settings and enable the mode for the needed type (for example, "Sale of goods and services"). Note: history will start accumulating only from the moment it is enabled — past edits will not be recovered.
Only one version is visible, although the document was definitely edited. The versions could have been deleted by the routine for clearing obsolete versions, or the "Version on posting" mode was set while the document was changed without re-posting. Check the storage settings.
The report builds very slowly / hangs. Too wide a period without a filter by object on a large database. Narrow the period and specify a specific object type.
"Insufficient rights" when opening. The report is from the administration subsystem. Rights to view the change history are required — ask the administrator to add the role or grant access to versioning.
In the version comparison it is visible that an attribute was changed, but the old value is empty/"<object deleted>". The reference attribute (counterparty, contract, item) in the old version pointed to an element that was then deleted. This is normal for old versions, not a report failure.
9. FAQ
Will the report restore a deleted or changed document back? The report itself — no, it only shows. But from the object's change history window you can go to a version and restore it — then the document will return to the selected state. The report only helps to find the needed version.
Why is the report empty, although the document was clearly edited? Most likely, versioning for this type of objects was disabled at the time of the edit. History is kept only after the mechanism is enabled — versions will not appear retroactively.
How does the report differ from the event log? The event log records the fact of the action itself (who, when, what they recorded), but does not store the content. "Analysis of Object Versions" stores full copies of the object and lets you compare which field changed and from which to which value.
Can you see who changed the amount specifically, rather than any field? Yes. Set a filter by attribute (for example, "Amount") in the advanced variant settings — the report will show only the versions where this field was changed.
Does enabling versioning affect the database's operating speed? A little — each object record is duplicated in the version storage, the database grows. Therefore enable versioning selectively (for critical documents) and limit the version retention period.
The report shows a VAT change — did it recalculate the tax? No. The report only records that the attribute with VAT in the document became different. The recalculation is done by the document itself when the amount/rate changes. In 2026 the VAT rate in the RK is 16%, and if an old version contains 12%, it means the document was entered under the previous norm — this is a reason to double-check and reissue the ESF.
How long are versions kept? As long as specified in the versioning settings (can be "indefinitely" or "for the last N months"). Obsolete versions are deleted by a scheduled job. Clarify the setting if the history is shorter than expected.
Can you limit whose changes are visible in the report? Visibility is determined by access rights, not by the report. A user with access to the change history sees the versions of all authors; the "User" filter only narrows the output but does not limit the rights.
Does the report account for changes made via exchange/import? Yes, if versioning is enabled. A version is created on any record of the object — whether manually, via data exchange or import from an external file. The author will show the user of the exchange session.
10. Related objects
- Object change history — called directly from any document/reference item (the "More → Change history" menu). This is the same mechanism, but for a single object; from it you open version comparison and restoration.
- Object versioning settings (Administration → Change history) — the data for the report appears "on the basis of" its enabled settings. Without it, the report is empty.
- Event log — supplements the report with information about actions without storing the content.
- The documents you are investigating (Sale of goods and services, Purchase, Payment order, etc.) — it's convenient to open their history directly from them, and based on the edits — reissue the related ESF and SNT.
How to find out your release
The menu "Help" → "About": the configuration line will show "Accounting for Kazakhstan, edition 3.0, version 3.0.74.2" and the platform version. If your release differs — the location of the menu item and the set of report variants may differ slightly, the operating logic is preserved.
The guide is prepared for 1C:Accounting for Kazakhstan, release 3.0.74.2 (edition 3.0). Figures and rates are per the norms of the RK for 2026.