Verified on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
You receive an email from your cloud service provider: "Your application is approaching its subscription limit, uploading new documents will soon be blocked." Or you simply notice that the database has become slower to open, and there's almost no free space left under your plan. The first question is — "when did this start and what grew so much?" This report gives the answer: it shows how the data volume of your application changed day by day. You open it, look at the growth curve, and understand — whether it's a gradual accumulation over the years or a sharp spike after a specific operation (mass upload, exchange, attached files).
Right away, an important and honest warning, so you don't look for anything extra: this is a service (technical) report, not an accounting document. It doesn't post anything, doesn't make entries, doesn't generate ESF or SNT, and doesn't move accounting registers. It only reads and displays volume statistics. Therefore, the section on "standard entries" is physically inapplicable here — and I won't make them up.
1. Purpose
The "Application Size History" report shows the dynamics of the data volume of your information base (application) over time. It's needed to monitor database growth, forecast approaching the cloud subscription limit (1C:Fresh / rented application), and find the moment when the volume grew sharply.
2. Where to find it
The report is a service one, so it's not in the usual accounting sections ("Sales", "Purchases", "Bank and Cash Desk"). You can open it as follows:
Via "All Functions": main menu (button with a drop-down list in the upper left corner) → Functions for technical specialist / All Functions → Reports section → Application Size History. If the "All Functions" item is not visible, enable it: Service and Settings → Settings → Parameters → checkbox Display the "All Functions" command.
Directly via a 1C navigation link — the fastest way. Main menu → Service → Follow navigation link, paste:
e1cib/list/Отчет.ИсторияРазмераПриложенияIn the cloud (1C:Fresh, 1cfresh.kz) the report is also available from the personal account/service manager in the application volume control block. The full picture is seen by a user with application administrator rights.
If you work on your own server (not in the cloud), the report will still show the data volume dynamics, but the "subscription limit" does not apply to you — you're only interested in the database growth itself.
2a. How to find out your release
Main menu → Help → About the program. In the window that opens, you'll see the platform version (for example, 8.3.24.xxxx) and the configuration release — a line like "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". It's release 3.0.74.2 that this instruction refers to. If you have a different release, the location of menu items may differ slightly, but the report logic is the same.
3. How to generate (report settings)
The report has no "document fields" in the usual sense — you don't enter data, you set selection parameters. Let's break down each control element: why it's needed and what happens if set incorrectly.
| Element | Why it's needed | If set incorrectly |
|---|---|---|
| Period (REQUIRED) | Sets the interval over which the size history is built. Set a sufficiently wide period (six months to a year) to see the trend, not a single point. | Too narrow a period — you'll see a "flat" line and won't understand that growth happened earlier. An empty period — the report will take the default value and the picture will be incomplete. |
| Generate | Builds the report according to the specified parameters. Press after any change of settings. | Forgot to press — the screen shows old data, conclusions will be based on yesterday's picture. |
| Show settings / Settings | Opens the detailing panel: output by dates, grouping, filter. | Left an extra filter from last time — some of the data "disappears", the size will appear smaller than real. |
| Detailing (by days/months) | Determines the chart step. By months — the general trend, by days — the exact moment of the spike. | Too large a step will hide a one-time surge in a single day. |
| Output: chart / table | How to show the result — as a diagram (trend is more visual) or a table (exact numbers by dates). | Nothing terrible, this is only the form of display. |
The procedure is simple:
- Open the report (via the navigation link or through "All Functions").
- Set the Period — for example, from 01.09.2025 to 06.09.2026.
- If necessary, open Settings and select detailing by months.
- Press Generate.
- Look at the growth curve and the current size as of the latest date.
4. Worked example
Inputs (conditional figures for clarity):
- The cloud subscription plan gives an application limit of 5 GB (5,120 MB).
- You generate the report for the period 01.09.2025 – 06.09.2026, detailing by months.
The report shows the following dynamics:
| Date | Application size, MB | Growth per month, MB |
|---|---|---|
| 01.09.2025 | 2,800 | — |
| 01.12.2025 | 3,050 | ~83/month |
| 01.03.2026 | 3,300 | ~83/month |
| 01.06.2026 | 3,900 | ~200/month |
| 05.09.2026 | 4,950 | ~350/month |
What you read from this:
- Until March 2026 the database grew steadily by ~80 MB per month — normal accumulation of documents.
- From June the pace tripled, and from September — almost 4-fold. This means a new cause appeared: mass upload, an enabled exchange with a large volume, or attached files (scans) in documents.
- The current size is 4,950 MB out of 5,120 MB — ~170 MB remain until the limit, and at a pace of ~350 MB/month that's less than two weeks. Time to act.
What to do based on the results (this is already beyond the report itself, but the very reason you opened it):
- check and clear attached files (scans), which most often "bloat" the database;
- perform a rollup/archiving of old periods, if permissible;
- increase the subscription plan, if you need all the data in full.
This report generates no Dr/Cr accounting entries — I'll repeat it deliberately, because the structure of an "accounting" document implies them, whereas here they are not and cannot be: the object measures megabytes, not tenge.
5. Types of operation
The report has no separate "types of operation" like documents do (for example, "Receipt / Return / Adjustment"). Only the presentation of the result varies:
- History by dates — size dynamics over the period (main mode).
- Current size as of a date — how much is occupied at a specific moment.
- Comparison with the limit — the current volume relative to the subscription quota (in the cloud version).
6. What is generated upon generation
Honestly and point by point:
- Entries — not generated. This is a report, not a document.
- Electronic documents (ESF in the IS ESF, SNT) — not generated and have nothing to do with the object.
- Movements in accounting registers — not generated. The report only reads service data about the size, but itself records nothing in accounting registers.
- Result — an on-screen form (chart and/or table) that can be saved and printed.
7. Printed forms
A service report has no printed form of its own (like an act or an invoice). But the result is fully exported using the standard means of a 1C spreadsheet document:
- Print the report result (chart/table) — the "Print" button in the command panel.
- Save as — to Excel (.xlsx), PDF, HTML, spreadsheet document .mxl.
- Send by email — attach the export to a letter (convenient for forwarding to the service provider or manager).
8. Common mistakes
"Report not found" / no item in the menu.
The reason — the "All Functions" command is not enabled or the user has no rights. Solution: Service and Settings → Settings → Parameters → Display the "All Functions" command; or open via the navigation link e1cib/list/Отчет.ИсторияРазмераПриложения; if it doesn't open either — request application administrator rights.
"No data to generate the report" / empty chart. Usually a too narrow or future period is set, or the database hasn't yet accumulated a measurement history. Solution: expand the Period, start from an earlier date, press Generate again.
"Insufficient rights to perform the operation on the database". The report is invoked under a limited role. Solution: log in as a user with administrator rights or contact the service administrator.
The size in the report is smaller than "it feels". Often a filter from the previous run remained in the settings, and part of the data is filtered out. Solution: open Settings, remove extra filters, generate again.
"Application limit exceeded" — but you just went in to look. Simply opening the report does not consume the limit; the message refers to the subscription itself. The report is exactly what's needed to understand the cause and plan a cleanup or plan upgrade.
9. FAQ
Q: Does the "Application Size History" report make accounting entries? A: No. This is a service report. It's not posted, doesn't generate entries, doesn't move accounting registers, and doesn't affect VAT, IIT, or month-end closing.
Q: Does it generate ESF or SNT? A: No. Electronic documents (ESF in the IS ESF, SNT) have nothing to do with this object — it measures data volume, not sales.
Q: In what units is the size shown? A: In megabytes (MB) / gigabytes (GB). 1 GB = 1,024 MB.
Q: Is the report only in the cloud? A: The mechanism is most in demand in the cloud (1C:Fresh / rented application), where subscription limits apply. On your own server it will also show volume dynamics, but the "subscription limit" doesn't apply to you.
Q: How do I find out how much is left until the limit? A: Compare the current size as of the latest date with your plan's quota. The exact limit value depends on your subscription — check it with the service provider (this is the only parameter worth verifying specifically for your plan).
Q: What most often "bloats" the database? A: Attached files (document scans), bulky data exchanges, and mass uploads. The chart in the report helps catch the month when the spike started.
Q: Can I reduce the size by looking at this report? A: The report itself doesn't reduce the size — it diagnoses. The volume is reduced by other means: deleting/clearing attached files, rolling up old periods, archiving.
Q: Can the result be exported for a manager? A: Yes. Save the result to Excel or PDF or send it by email directly from the report's command panel.
Q: Why does the report show old figures after changing the period? A: You need to press Generate after each change of settings — otherwise the previous result stays on the screen.
Q: Does frequently opening the report affect database performance? A: Practically no. This is a light read of service statistics, not a recalculation of accounting data.
10. Related documents and mechanisms
A service report has no classic "entered on the basis of / enters on the basis of" link. By meaning it sits alongside the mechanisms of application maintenance and control:
- Subscription / plan management in the cloud service (that's where the limit itself is set, against which you compare the size).
- Working with attached files — the main candidate for cleanup if the report showed a spike.
- Information base rollup / archiving of periods — a way to reduce the volume after the report confirmed that the database is growing.
- Backup — before any cleanup prompted by the report's conclusions.
How to find out your release
Main menu → Help → About the program. There the 1C:Enterprise platform version and the configuration release are indicated. This guide is written for release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0). On adjacent releases the logic is the same, only minor details of command locations may differ.
Prepared for "Accounting for Kazakhstan", edition 3.0, release 3.0.74.2.