Checked on release 3.0.74.2 "Accounting for Kazakhstan" (edition 3.0).
You are organizing the database. You open the list of reference books through "All Functions" or see an unfamiliar name in the data volume report — DeleteAdditionalInformationStorage. Inside are some old records. There is no synonym, it cannot be found in the regular menu, and the prefix "Delete" is alarming: should you delete it or leave it alone? Below is what this object is, where it came from, whether it is safe to clean it, and where your data has moved.
First and foremost: this is a service (technical) reference book "legacy". The prefix "Delete" in the name is not your command to the program, but a label from the developers of 1C. This marks objects that have been decommissioned but left in the configuration to avoid losing historical data during updates. New records should not be added here.
1. Purpose
"DeleteAdditionalInformationStorage" is an outdated storage for additional information on database objects (reference books, documents). Previously, arbitrary information was "attached" to objects through it. Now this role is performed by the standard subsystem "Additional Attributes and Information". The reference book is left only for compatibility and storage of old data — manual work with it is not intended.
2. Where to find
In the standard interface, there is no menu item for it — the object is intentionally hidden. It can be opened in three ways.
| Method | Path |
|---|---|
| Through the navigation link | Menu Service → Go to navigation link (in the client — the "star/globe" icon) and paste the line below |
| Through "All Functions" | Main menu (☰) → All Functions → Reference Books → find by name |
| Through the data report | Administration → Maintenance → Performance Assessment / Data Volume — if the object "weighs", it will be visible in the list |
1C navigation link:
e1cib/list/ReferenceBook.DeleteAdditionalInformationStorage
Copy it, open Go to navigation link and paste — the list of records of this reference book will open directly.
If the "All Functions" item is not displayed, enable it: Main menu → Service → Settings → Show "All Functions" command.
2a. How to know your release
The instruction is tied to the version of the configuration, so check yours: Help → About the program (or the "i" icon in the upper right corner). In the opened window, the platform version is indicated (for example, 8.3.24) and the configuration release — a line like "Accounting for Kazakhstan, edition 3.0 (3.0.74.2)". The number after the name is your release.
3. How to fill
The correct answer for a working database is not to fill it at all. This is not a working tool, but a container for inherited data. Manually creating elements here will not affect anything useful and will only confuse during the next update.
However, if you opened the card of an existing record, here is what it usually consists of. The exact set of attributes depends on the history of your configuration (this is the only place in the text that requires verification in your specific release — open one card and check):
- Code — a service identifier for the record. You do not need to change it manually: the object is linked to the original data by the code, and editing the code will "detach" the record from what it was related to.
- Name — usually technical, not human-readable. This is not the name of a document for printing, but a label for the program.
- Owner / source object — a reference to the element of the reference book or document to which the additional information was related. If cleared, the link will be lost, and the record will turn into a "dangling" one.
- Stored value / type of information — the actual value that was once placed in the storage.
Conclusion for this section: there are no mandatory fields for filling here because you should not fill it. If there is a need to add arbitrary information to a counterparty, nomenclature, or document — use the current mechanism (see section 10), not this reference book.
4. Analyzed example
This object does not create entries (see section 6), so an "example with Dr/Cr" here would be fictional. Let's analyze a real scenario for which this reference book is usually opened — checking before cleaning the database.
Situation. LLP "Astana-Trade" has been updated from 3.0.6x to 3.0.74.2. After the update, the accountant sees that the reference book "DeleteAdditionalInformationStorage" contains 128 records and "weighs" several megabytes. The question: delete?
Verification steps.
- Opened the list via the navigation link. We see 128 items, some have "Owner" filled (links to counterparties), some have an empty owner.
- Opened Administration → Maintenance → Search and delete marked / Check reference integrity, but for control, we first marked 1-2 test records for deletion and ran Search for links to the object (right-click on the record → "More → Related documents" / "Find links").
- For records with a filled "Owner", the program showed that the data has already been transferred to the "Additional Information" subsystem — that is, duplicates. For "empty" records, there are no links to anything.
Conclusion. Marked all 128 records for deletion, performed Administration → Maintenance → Deletion of marked objects. No links were "broken", the database size decreased. No amounts in tenge, VAT 16% or RK accounts (1210, 3310, 6010) are affected — the reference book has no relation to accounting and taxes.
Rule: before mass deletion, always make a dump / backup of the database (Administration → Maintenance → Backup), and on the 1C:Fresh cloud — a request for an archive. Marked objects are deleted using the standard mechanism with link control — there is no need to clean anything manually from the configurator.
5. Types of operations
The reference book (unlike a document) does not have "types of operations" in the accounting sense — it does not select the scenario for entries. Practically, three actions are possible with it:
| Action | When applicable |
|---|---|
| View | To understand what historical data lies inside |
| Mark for deletion / deletion | Cleaning after confirming that the data is duplicates or garbage |
| Leave as is | If it does not interfere and you are not sure — it is safe, the object is passive |
6. What is formed when conducting
Nothing. The reference book is not conducted, therefore:
- there are no accounting entries (Dr/Cr) — it does not move through the RK chart of accounts;
- does not form tax registers (individual income tax, 10% social tax, 3.5% pension fund, 2% health insurance, 3% social health insurance, 5% social tax, 6% VAT);
- does not issue electronic documents (ESF in the ESF IS, SCT);
- does not create movements in information/accumulation registers in current work — the data inside is static and only stored.
If you need something that actually generates entries and ESF (sales, receipts) — this is done by the documents "Sales", "Receipt", etc., not this reference book.
7. Printed forms
The object does not have its own printed forms. Neither "Act", nor "Invoice", nor "ESF" can be printed from here. This is another sign that you are dealing with a service entity, not a working document.
8. Common errors
"Failed to delete the object: it is referenced by other objects". Someone or some old register is still referencing the record. Do not force deletion. Run Search and delete marked objects — it will show the chain of links. First, remove/reprocess what is referencing, then delete the record.
"Object not found" / "Reference to a non-existent object" in the report or processing. This appears if the record was deleted in the configurator "brutally", bypassing marked deletion. It is fixed by checking reference integrity (Administration → Maintenance → Testing and correction / Check data integrity).
"For some reason, I created a new element here". Mark it for deletion and delete it. New records in "Delete..." are useless — they do not participate in current mechanisms.
After the update, the object "swelled". This is normal: when transferring to a new subsystem, old data are temporarily duplicated. Ensure that the transfer is complete (records are in "Additional Information") and clean up the legacy.
9. FAQ
1. Can I delete the entire reference book "DeleteAdditionalInformationStorage"? Records — yes, through marking and standard "Deletion of marked objects", after making a backup and checking links. The metadata object should not be deleted from the configurator in a standard supported database — it will be removed with the next update.
2. Does the prefix "Delete" mean the program suggests deleting or is that the name of the object? That is the name of the object. 1C developers mark entities that have been decommissioned with the name "Delete..." so you understand: you should not work with them, they are living out their time until complete cleaning.
3. Will deletion affect entries, VAT, or reporting? No. The object does not create entries, does not affect VAT 16%, individual income tax, social tax, and does not participate in declarations. Accounting data is stored in other objects.
4. Where should I now enter additional information for a counterparty or nomenclature? In the subsystem "Additional Attributes and Information": Administration → General settings → check the box, then in the object card — the command "Additional Information" / "More → Edit the composition of additional information".
5. Why does the reference book have no synonym and is not visible in the menu? The synonym is intentionally removed/empty, and the object is excluded from the command interface — so that the user does not accidentally stumble upon it. It can only be opened through "All Functions" or the navigation link.
6. I found important data inside — should I transfer them manually? As a rule, the transfer is performed automatically during the release update. If the data did not appear in the current mechanism, contact the configuration update/1C partner — manual copying from the service reference book is not provided.
7. Is it safe to just leave it as is? Yes. The object is passive, does not consume resources in operation, does not affect speed and accounting. Cleaning is a matter of order, not necessity.
8. How to open it the fastest?
Copy e1cib/list/ReferenceBook.DeleteAdditionalInformationStorage, call Service → Go to navigation link, paste — the list will open.
9. Can this reference book be the cause of an error when closing the month or submitting a tax return form? Directly — no. It does not participate in regulatory operations and tax calculations. Look for month-end closing errors in accounting documents and registers, not here.
10. Related documents
This reference book does not "create based on" anything and nothing is created on its basis — it is outside the chain of primary documents. Functionally, it is replaced by:
- Additional Attributes and Information — the current mechanism for arbitrary properties of objects (enabled in the "Administration" section).
- Database maintenance: "Search and delete marked objects", "Deletion of marked objects", "Check reference integrity", "Backup" — tools you work with this reference book.
Conclusion
"DeleteAdditionalInformationStorage" is not a working document, but a service legacy storage. Do not fill it, do not look for entries and printed forms in it. If it interferes with volume — check links, make a backup, and delete records using the standard mechanism. For new arbitrary information, use the subsystem "Additional Attributes and Information".
How to know your release: "Help" → "About the program" — there you will find the platform and configuration release.
This material was prepared for "Accounting for Kazakhstan", edition 3.0, release 3.0.74.2. In other releases, the set of attributes of the service reference book may differ — check through "Help → About the program".