Document "Asset Completion" (Asset Completion)

1. Identification

Purpose. The document registers the composition of fixed assets (FA) included in the parent fixed asset. It is used by accountants and specialists in fixed asset accounting to record the current state of the completion: which FAs are included in the parent asset and what their status is (in use, retired, disposed of, etc.).

Typical application scenarios:

• commissioning of complex FA (for example, a computer with components) and recording the initial composition;
• modernization, replacement of components, addition or removal of FA from the parent asset;
• inventory of the set and registration of the related event.

Important. This is a document for accounting the composition of FA (managerial-register type). It does not generate accounting entries according to the chart of accounts and does not affect VAT, income, or cost of goods sold — movements are recorded only in information registers (see section 5). Therefore, the tax parameters of the RK (VAT rate 16%, MRP 4,325 ₸, individual income tax, pension contributions, etc.) do not apply directly to this document: value operations with FA are documented by other documents in the "Fixed Assets" block.

Where to find in 1C: section "Fixed Assets" → "Asset Completion". Navigation link: e1cib/list/Document.AssetCompletion.

2. Header Attributes and Table Parts

Header Attributes

Table Part "FA"

Attributes Organization, ParentFixedAsset, as well as columns FixedAsset and StatusInFAComposition — are mandatory. If a field is not filled, the platform will not process the document and will issue an error "Field ... is not filled".

3. Forms

Additionally, standard platform mechanisms are applicable: bulk modification of attributes (for mass editing of Responsible/FAEvent for several documents — scenario 3.3) and manual adjustment of registers through the "More → Edit Registers" mode (scenario 3.4).

4. Key Module Procedures

The source code (BSL) of the modules is not attached, so below are standard handlers for documents of this type. Specific signatures and lines should be clarified according to the configurator version 3.0.74.2.

Object Module:

• ProcessingPosting(Refusal, PostingMode) — generates sets of records in the information registers FAComposition and FAEventsOrganizations based on the header and table part data.
• ProcessingFilling(FillingData, ...) — filling when entering based on (transfers organization and parent FA from the source object).
• CheckFilling(Refusal, CheckedAttributes) — control of mandatory fields (Organization, Parent FA, rows of the table part).

Document Form Module:

• OnCreateOnServer — initial setup of organization, responsible, visibility of fields.
• Table part "FA" event handlers (OnChangeStatus…, FAOnChange) — control of duplicates and correctness of statuses.

Requires verification (version-specific): presence of subscription/additional logic in the common modules of the FA accounting subsystem, affecting the composition of movements in 3.0.74.2.

5. Posting and Movements

The document does not generate accounting entries. When posted, records are created in two information registers (according to evidence).

Information Register "FAComposition"

• Type: record of the latest snapshot (information register).
• Dimensions: ParentFA (from the header), FixedAsset (from the table part row).
• Resources: StatusInFAComposition (from the table part row).
• Logic: for each row of the table part, the current status of the FA in the composition of the parent asset is recorded on the document date. A document with a later date displaces previous records by the latest snapshot mechanism, forming the current composition of the set.

Information Register "FAEventsOrganizations"

• Type: record of the latest snapshot.
• Dimensions: Organization, ParentFA.
• Resources: FAEvent (if filled in the header).
• Logic: records an event related to the completion (for example, "Inventory of the set 01.12.2024"). If the event in the header is not filled — a record in this register is not created.

Value consequences of completion (change in initial cost, VAT at a rate of 16%, depreciation) are reflected in accompanying documents of the FA block and do not arise here.

6. Related Objects and Entry Based On

Entry Based On. Typical scenario — creating a completion based on the document of acceptance of FA for accounting (Organization and Parent FA are transferred). The list of bases in a specific version is determined by the entry based on commands of the FA subsystem — clarified according to the configurator.

7. Extension Points

• Object module handlers (ProcessingPosting, ProcessingFilling, BeforeWriting) — for adding custom logic to control the composition of the set.
• Event subscriptions (ProcessingPosting, OnWriting) — for additional movements in external registers without modifying the object module.
• Configuration extensions — adding header/table part attributes and form columns (for example, inventory sign, location) without removing from support.
• Additional reports and processes (BSP) — printed forms of the composition of the set, bulk processing of completion documents.
• Exchange rules / RIB — inclusion of the document and its registers in the exchange composition when using a distributed information base.

For RK implementations, remember: any value and tax operations (income 6010, cost of goods sold 7010, VAT 3130 at a rate of 16%) are documented by specialized FA and sales documents, not by "Asset Completion".