1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Document.UnusedFilesVolume) |
| Name | UnusedFilesVolume |
| Synonym | — (not specified) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Accounting Currency | Tenge (₸) |
| Purpose | Service (technical) object for analyzing disk space occupied by unnecessary files in the information database. Generates a detailed list of files with their volume to make an informed decision about cleanup before starting deletion procedures. Used by administrators and those responsible for maintenance before scheduled maintenance work or when disk space is insufficient. |
Important Note (classification discrepancy). According to the navigation link and metadata, the object is registered as a Document (e1cib/list/Document.UnusedFilesVolume). However, the reference evidence describes it as a service report in the data composition system (DCS): without user attributes, without tabular parts, with an automatically generated form and result formation through data composition. The practical conclusion for the developer: this is not an accounting document — it does not participate in posting, does not generate entries and movements in registers, and serves as a tool for technical maintenance of the database. If a specific delivery requires the exact role of the object (document vs. report), this is the only point that should be verified against the metadata of your version.
Where to find in 1C: section "Administration" → "Unused Files Volume". Navigation link: e1cib/list/Document.UnusedFilesVolume.
2. Header Attributes and Tabular Parts
2.1 Header Attributes
User attributes in the metadata are absent. Behavior and output parameters are controlled by the built-in mechanisms of the data composition system (DCS) and standard parameters.
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| (attributes absent) | — | — | Only built-in DCS mechanisms are used |
2.2 Tabular Parts
Tabular parts in the metadata are absent. The result (list of files and their volume) is built dynamically — in the form of a value table through the data composition procedure, and is not stored in the object's attributes.
2.3 Forms
The object does not contain a separate application form (document form, list form with manual layout). All work is done through the standard data composition form, which provides:
- building the result based on the DCS scheme;
- user customization of the structure (groupings/fields/selections);
- output of the file volume column and totals for assessing released space.
4. Key Procedures of Modules
Application BSL code (evidence on modules) is not attached. Below are typical handlers for an object of this kind (DCS report/service object without accounting logic). They should be considered as a guideline, not as a guaranteed code composition of a specific version.
| Handler / Procedure | Where it is placed | What it does (typical logic) |
|---|---|---|
OnResultComposition(DocumentResult, DataDecoding, StandardProcessing) |
Report form module | Connection point to the composition process: preparation/complementing data, programmatic result formation |
| Initialization of the composition scheme and settings | Object/form module | Obtaining the main DCS scheme, applying default settings, setting selection parameters |
| Function for collecting data about files | Common/server module | Scanning stored files (volume/database), calculating size, selecting "unnecessary" by auto-cleaning criteria, returning a value table to the DCS source |
Handlers typical for an accounting document (ProcessingPosting, ProcessingDeletionPosting, OnRecord, ProcessingFilling) are not applied to this object, as it does not generate movements and does not participate in accounting.
5. Posting and Movements
The object is not posted and does not generate accounting entries or movements in registers (accumulations, information, accounting). This is a service tool for analyzing disk space.
Therefore, for "UnusedFilesVolume" the following are not applicable:
- entries according to the standard chart of accounts of the RK (for example, 1210 "Short-term receivables from customers", 1030, 1330, 3310, 6010, 7010);
- calculation and reflection of VAT in the VAT calculation register and account 3130 "VAT payable";
- tax parameters of the RK for 2026 (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, deduction for sole proprietors 30 MRP/month, PIT 10%/15%, OPE 10%, OPEA 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%);
- issuance of electronic documents ESF (IS ESF) and CNT.
The listed norms and accounts are the context of the "Accounting for Kazakhstan" configuration as a whole; they have no relation to this technical object. The only "result" of its operation is the generated list of files with volume, used for making a decision about cleanup.
6. Related Objects and Input Based On
- Input based on: not provided (neither as a basis nor as a result). Accounting documents based on this object are not entered.
- Related objects: file management subsystem of the platform (repositories/volumes of files) and mechanisms for scheduled automatic cleanup — as a source of data on volume and candidates for deletion.
- Registers: does not have its own movement registers; reads data from the file subsystem, not from the configuration registers.
7. Extension Points
- Data composition scheme: modification of the composition of fields, resources (volume sum), groupings, calculated fields; addition of user settings and report options.
- Selection of candidates for cleanup: expansion of "unnecessariness" criteria (by date, type, owner, size) in the data collection function.
OnResultComposition: programmatic addition/post-processing of the result, highlighting large files, adding total indicators of released space.- Configuration extensions: addition of a custom managed form or commands (for example, "Go to cleanup") without removing the configuration from support.
- Rights and visibility: restriction of access to the object by administration/maintenance roles.
The only truly version-specific point that requires verification in your delivery 3.0.74.2 is the actual type of the object in the metadata (Document or Report) and the exact composition of its module, as the evidence describes the behavior of the DCS report when registered via the link as a document.