Document "Change in Fixed Asset Status" (Documents.ChangeInFixedAssetStatus)

1. Identification

Purpose. The document registers changes in the status, characteristics, and tax parameters of the organization's fixed assets: changes in the depreciation calculation method, registration/deregistration of fixed assets for property, transport, or land tax purposes, reclassification of fixed assets. It is used by accountants for fixed asset accounting.

Important regarding the nature of the document. “Change of Asset Status” is a document for registering status, not for economic transactions of sale/purchase. It does not generate accounting entries in accounts (such as 1210 / 1030 / 6010 / 7010), but manages information registers for fixed asset and tax object accounting. Therefore, the accounts of the standard chart of accounts of the RK and tax rates (VAT 16%, PIT/Social Tax, etc.) are not directly involved in its movements — they are applied in other documents (sales, depreciation calculation, tax calculations) with which this document is logically connected.

2. Header Attributes and Table Parts

Header Attributes

The set of flags “Change…” in the header determines which specific registers will have movements generated from the rows of the table part.

Table Part “Assets”

If mandatory fields (Organization, FixedAsset) are not filled, the platform will not allow the document to be processed and will display an error “Field … is not filled”.

3. Forms

Forms support scenarios: creation based on the fixed asset card, mass change of status for a group of fixed assets, group editing of attributes from the list.

4. Key Module Procedures

No separate BSL text is attached in evidence; below are typical handlers for fixed asset accounting documents in the configuration.

Object Module (ProcessingProcedure)

• ProcessingProcedure(Refusal, ProcessingMode) — generates movements in information registers based on the rows of the table part “Assets” and the change flags in the header. Entries are generated through the module ProcessingParameters using temporary query tables; for each register, the slice of the latest values is taken as of the document date. Movements are not generated if the flag ManualAdjustment is set.
• FillingProcedure(FillingBasis, ...) — filling during input based on the “Fixed Assets” directory (substitution of organization, fixed asset, current status).
• FillingCheckProcedure(Refusal, CheckedAttributes) — control of mandatory fields Organization and FixedAsset.

Form Module

• OnCreationOnServer — initialization of group visibility depending on the set change flags.
• Handlers OnChange of depreciation/tax status change flags — management of the availability of corresponding columns in the table part.

Requires verification (version-wise): the exact composition of the ProcessingParameters procedures may differ between releases 3.0.7x.

5. Processing and Movements

The document generates movements in information registers (not in the accounting register). When processing, based on the rows of the table part “Assets” and considering the header flags, the following are recorded:

Features of movement generation:

• Movements are not generated when the flag ManualAdjustment is set.
• For each register, the slice of the latest values as of the document date is used.
• Data is taken from the table part “Assets” considering the established change flags in the header.
• Entries are generated through ProcessingParameters using temporary query tables.

What the document does NOT do: it does not generate accounting entries in the RK chart of accounts and does not calculate taxes. The consequences of changing the status (for example, a modified depreciation method) are reflected later — during the scheduled depreciation calculation and in tax calculations, where the current norms for RK 2026 are applied (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, etc.). There is no direct use of these numbers in the movements of the document itself.

6. Related Objects and Input Based On

Input based on / source of filling:

• Directory FixedAssets — the main source (creation from the fixed asset card; scenario 3.1).

Logically related objects:

• Documents AcceptanceOfFixedAssets, InputOfInitialBalances (set the initial status of fixed assets).
• Scheduled operation “Depreciation Calculation” — consumer of the register DepreciationCalculationForAccounting.
• Tax calculations for property, land, and transport taxes — consumers of the registers TaxObjects….
• Reports on fixed assets and tax objects that use status slices.

Application scenarios:

1. Creation based on the fixed asset directory (change of tax/depreciation status).
2. Mass change of status for a group of fixed assets (for example, deregistration of several objects from property tax).
3. Change of date for an already created document with clarification of data.
4. Manual adjustment without automatic movements (flag ManualAdjustment).
5. Viewing and group editing from the list (responsible, department).

7. Extension Points

• Event subscriptions for processing (ProcessingProcedure) to add custom movements or control.
• Configuration extension: adding header/column attributes to the table part “Assets”, custom change flags; overriding form handlers (OnCreationOnServer, OnChange).
• Common processing modules (ProcessingParameters) — inserting code before/after the generation of temporary tables.
• FillingCheckProcedure — adding additional control rules before processing.
• Additional reports and processing (external) for group filling of the table part and batch processing.

Requires verification (version-wise): the availability of specific methods for interception depends on the compatibility mode and the presence of extensibility annotations in release 3.0.74.2.