RUKKENZH
Ask AI
Sections1C configuration objects
Directory "PurchaseOfGoodsAcceptedForStorage" Attached Files
Article language:🇷🇺 RU🇰🇿 KK🇬🇧 EN🇨🇳 ZH
Article version:📘 For accountants⚙️ For technical specialists

Directory "PurchaseOfGoodsAcceptedForStorage" Attached Files

Applies to: 1С:Управление торговлей для Казахстана, release 3.4.5.21 (9 July 2026) · by 1C-Sapa Group, 1C partner
СТ
Сапа Т.И. — 1C and accounting expert, practising trainer
Prepared by the BuhGPT editorial team

1. Identification

Parameter Value
Object type Catalog
Name ВыкупПринятыхНаХранениеТоваровПрисоединенныеФайлы
Full name Catalog.ВыкупПринятыхНаХранениеТоваровПрисоединенныеФайлы
Synonym Attached Files (Redemption of Goods from Storage)
Configuration Trade Management for Kazakhstan, ed. 3.4 (3.4.5.21)
Owner Document (owner object) "Redemption of Goods Accepted for Storage"
Subsystem "File Management" of the Standard Subsystems Library (SSL)
Purpose Storage of files (scans, contracts, invoices, acts, images, etc.) attached to a specific document for the redemption of goods previously accepted for custody

This is a service storage catalog, automatically generated by the "Attached Files" mechanism of the SSL. For each configuration object supporting attachments, a separate subordinate catalog of the form <ObjectName>AttachedFiles is created. Users do not work with it directly as a catalog — files are opened via the "Attached Files" command in the owner document's form.

Navigation link (section "Where to find"): e1cib/list/Catalog.ВыкупПринятыхНаХранениеТоваровПрисоединенныеФайлы

Direct opening of the list is mainly used for administration/debugging. The standard scenario is the "Attached Files" button on the redemption document's form.


2. Attributes and Tabular Sections

The catalog has no tabular sections. The set of attributes is standard for the SSL attached files mechanism.

Header Attributes

Attribute Type Purpose
Owner CatalogRef (redemption document) Object to which the file is attached. Defines the "document → files" link
Description String File name without extension (displayed to the user)
Extension String File extension without a dot (pdf, jpg, docx, xml…)
FileStorage ValueStorage Binary file data when stored in the infobase
Volume CatalogRef.FileStorageVolumes Disk storage volume when stored outside the infobase (in volumes)
PathToFileInVolume String Relative path to the file within the volume
Size Number File size in bytes
SignedByES Boolean Flag indicating the presence of an electronic signature on the file
EncryptedFile Boolean Flag indicating that the file is encrypted
TextExtraction ValueStorage / String Extracted text for full-text search
TextExtractionStatus Enumeration Text extraction status (Extracted / NotExtracted / ExtractionError)
Author CatalogRef.Users User who added the file
ChangedByUser CatalogRef.Users Who made the last change
CreationDate Date Moment the file was added
UniversalModificationDate Date Date of the last change (UTC)
BeingEditedBy CatalogRef.Users User who checked out the file for editing (lock)
LockedDate Date Date the editing lock was set
VersionDescription String Comment on the version/file
CurrentVersion CatalogRef (versions) Reference to the current file version (when versioning is enabled)
EditProhibitionInDatabase Boolean Prohibition on opening for editing directly in the infobase
DeletionMark Boolean Standard deletion mark flag

Depending on "File Management" settings, files are stored either in the FileStorage attribute (in the infobase) or in volumes (Volume + PathToFileInVolume). Only one option is used for a given file at a time.


3. Forms

Form Purpose
ItemForm Attached file card: name, author, size, date, "Open," "Edit," "Finish Editing," "Save as…" buttons, working with versions and ES
ListForm List of files attached to the owner; invoked by the "Attached Files" command from the document form
ChoiceForm File selection for programmatic use/substitution

The main user interface is implemented by managed forms of the common "File Management" subsystem (e.g., CommonForm.AttachedFiles), which are parameterized by the owner. The catalog's own forms remain standard and, in most scenarios, are not opened directly.


4. Key Module Procedures

No BSL code evidence has been attached for this object. Below are typical handlers and points characteristic of the SSL attached files catalog (object module / manager module).

Object module:

  • BeforeWrite(Cancel) — validation of attributes, updating UniversalModificationDate, recording the change author.
  • BeforeDelete(Cancel) — deletion of file data from the volume (if stored in volumes), cleanup of related versions.
  • OnCopy(CopiedObject) — resetting the editing lock and service flags.

Manager module:

  • FormGetProcessing(...) — substitution of forms with common file management forms.
  • PresentationFieldsGetProcessing / SearchFieldsGetProcessing — file presentation (name + extension).

Service logic (SSL common modules):

  • FilesOperations, FilesOperationsInternal, FilesOperationsInternalServerCall — adding, updating, opening, editing, versioning and deleting files.
  • FilesOperationsServerCall.AddFile(...) — creation of a new catalog item from a selected file.
  • FilesOperationsInternal.LockFile / UnlockFile — management of the BeingEditedBy attribute.
  • Text extraction mechanism for full-text search (filling TextExtraction, TextExtractionStatus).

Specific procedure names and their signatures are version-dependent (depend on the built-in SSL version) — requires verification against the set of common modules in the specific 3.4.5.21 build.


5. Posting and Movements

The catalog is non-postable and does not generate movements in registers. It is a file storage, not an accounting document: it has no PostingProcessing procedure, it does not create postings, and it does not participate in accounting/tax accounting.

Accounting movements (accumulation registers for goods and settlements, mutual settlements, VAT/ESF registers) are generated by the owner document "Redemption of Goods Accepted for Storage," not by its attached files. For reference — under the standard Kazakhstan accounting methodology, the redemption document affects accounts of the Kazakhstan standard chart of accounts:

Operation Dr Cr
Capitalization of goods upon redemption 1330 "Goods" 3310 "AP to suppliers"
Input VAT (rate 16%) 1420 "VAT recoverable" 3310
Sale/transfer of goods 1210 "AR from customers" 6010 "Sales revenue"
VAT payable accrual (16%) 1210 3130 "VAT payable"
Cost of goods sold 7010 "Cost of sales" 1330
Payment/cash receipt 1030 "Cash at current accounts" 1210

Accompanying Kazakhstani electronic documents (ESF in the ESF IS, SNT) are also issued at the level of the owner document and its subordinate EDF objects, but not at the level of the attached files catalog.

Figures/rates are current for Kazakhstan as of 2026: VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸. These values relate to the configuration's accounting documents; the file catalog itself does not use them.


6. Related Objects and Input on Basis

  • Owner: Document "Redemption of Goods Accepted for Storage" — the only object whose records files in this catalog are linked to (Owner).
  • File storage volumes: Catalog.FileStorageVolumes — for external storage.
  • File versions: the SSL versioning mechanism (when version storage settings are enabled).
  • Users: Catalog.Users — Author, ChangedByUser, BeingEditedBy attributes.
  • Digital signatures / encryption: the SSL ES subsystem (SignedByES, EncryptedFile attributes).

Input on basis is not provided for this catalog and is practically meaningless: items are created exclusively through the command of attaching a file to the owner document (drag-and-drop, "Add → File from disk," "Create from template," from scanner, from email).


7. Extension Points

  • Storage settings: switching "in infobase / in volumes," restricting file size and types — in the "File Management" subsystem (without modifying the catalog).
  • Configuration extension: adding custom attributes/handlers via object extension; overriding form commands via extension of common file management forms.
  • SSL programming interfaces: FilesOperations, FilesOperationsServerCall, FilesOperationsInternalServerCall — for programmatically adding, reading, and updating files.
  • Versioning and ES: enabling/disabling version storage, mandatory signing — through the settings of the respective subsystems.
  • Full-text search: text extraction is configured globally; if necessary — customization of extraction handlers.

When customizing, accounting logic should not be duplicated in this catalog — it should remain in the owner document "Redemption of Goods Accepted for Storage."

Frequently asked questions

Does this catalog generate accounting entries or register movements?
No. This is a service file storage of the "Attached Files" BSP mechanism. It is non-posting, has no Posting Processing, and creates no movements. All accounting movements and entries (accounts 1330, 3310, 3130, 1210, 6010, 7010, etc.) are generated by the owner document "Redemption of Goods Accepted for Storage".
Where are the files themselves stored — in the database or on disk?
It depends on the settings of the "File Management" subsystem. When stored in the infobase, the binary data resides in the FileStorage attribute. When stored externally, the Volume (Catalog.FileStorageVolumes) and PathToFileInVolume attributes are used, and the data is placed on a disk volume.
How does the user add and open files?
Through the "Attached Files" command in the form of the "Redemption of Goods Accepted for Storage" document: adding from disk, by drag-and-drop, from a scanner or email; opening/editing — from the item form with locking (the IsEditing attribute) and, if the setting is enabled, version tracking.
Can an item of this catalog be entered "based on" something?
Normally no. Records are created only by attaching a file to the owner document. Direct opening of the list (e1cib/list/Catalog.RedemptionOfGoodsAcceptedForStorageAttachedFiles) is used mainly for administration and debugging.
Why does the description mention a VAT rate of 16% if this is a file catalog?
The 16% rate and other parameters of RK-2026 (MCI 4,325 ₸, MMW 85,000 ₸) are given as context for the accounting of the owner document. The attached files catalog itself does not use tax values.

Read also

Latest answers

Sources

Was this article helpful?
💼 Need help with 1C or accounting? Слава КВЦ — many years of 1C practice in Kazakhstan. Explore the annotated Tax Code of RK 2026 or ask in the BuhGPT chat — answers in seconds.