Document "RemoveAdjustmentOfCostOfGoodsWriteOff" (Accounting for Kazakhstan 3.0)

1. Identification of the Object

Purpose. Historically, the document was intended for adjusting the cost of written-off (sold) inventory in accounting and tax reporting at the end of the accounting period. It worked in conjunction with the calculation of the cost of inventory and allowed for the adjustment of the cost of already written-off goods when clarifying their actual cost (for example, after registering all incoming operations of the closing month).

In the current version of the configuration, the functionality has been replaced by standard mechanisms for closing the period and adjusting costs (regulatory operations “Adjustment of inventory write-off cost” / “Month closing”). The object is preserved solely for compatibility with data from previous periods. Creating new documents of this type in operational mode is not recommended — when attempting to create, the form displays the error “Adding new documents is prohibited!”.

Where to find in 1C: section “Operations” → “(Not used) Cost adjustments of goods write-off”. Navigation link: e1cib/list/Document.DeleteCostAdjustmentOfGoodsWriteOff

2. Attributes of the Header and Table Parts

2.1 Header Attributes

Mandatory attributes are Organization and RegistrationPeriod. If the field is not filled, 1C will not allow the document to be processed and will display the error “Field … is not filled”.

2.2 Table Parts

The document stores a line-by-line breakdown of the adjustment by nomenclature and accounting accounts. The typical composition of the table part (cost calculation data):

The specific composition of the columns is formed at the stage of processing from the cost calculation table (see section 4). In the interface, some columns may be hidden, as the document is marked as unused.

3. Forms

4. Key Procedures of Modules

Below are the handlers for the evidence of the configuration (release 3.0.68.1) and the standard logic for this type of object.

4.1 Form Module (Form.DocumentForm)

• OnCreateOnServer — blocks the addition of new documents. When the condition Parameters.Key.Empty() is met (i.e., opening a new, not yet recorded document), the message is displayed:

  Adding new documents is prohibited!

  and creation is canceled (Refusal = True). This is a key indicator of a deprecated object.

4.2 Object Module — Processing

The processing procedure implements the following logic:

1. From the processing parameters, the cost calculation table is obtained.
2. If ManualAdjustment = False, an automatic adjustment calculation is performed through standard modules CostCalculation and AccountingProcedures.
3. Records are formed in the information register InformationOnCostAdjustmentsOfProductsAndGoods.
4. Movements in the accounting registers Tax and Standard are created through the procedures of the standard processing of the configuration (considering the flag ConsiderCIT).

The paths path:string in the provided evidence are absent; the names of procedures and logic are taken from the facets processing/attributes and the standard architecture of documents of this type. Exact line numbers are version-specific and require verification with the specific cf-file of release 3.0.74.2.

5. Processing and Movements

When processed, the document generates movements in the following registers.

5.1 Registers

5.2 Entries (register “Standard”, chart of accounts of the RK)

The logic of adjusting the cost of already written-off (sold) goods:

In the automatic calculation, the amounts are taken from the cost calculation table (the difference between preliminary and actual cost of the period). In tax accounting (register “Tax”), the similar amount is reflected only when ConsiderCIT = True.

For reference (RK accounts involved in related operations of sales/payments): 1210 — short-term receivables from customers, 1030 — cash in current accounts, 3310 — payables to suppliers, 3130 — VAT payable, 6010 — revenue from sales. The adjustment document does not generate movements in revenue and VAT — it only affects the link “goods ↔ cost”.

5.3 Numeric Environment of the RK (Kazakhstan, 2026)

The document does not calculate taxes but operates in the current tax environment of the configuration:

• VAT rate — 16 % (register 3130 for sales operations);
• MPR = 4,325 ₸, MZP = 85,000 ₸;
• Individual income tax: basic deduction 30 MPR per month (not more than 360 MPR per year), rate 10 % up to 8,500 MPR of annual income and 15 % above;
• Contributions/deductions: OPV 10 % (base ceiling 50 MZP), OPVR 3.5 %, VOSMS 2 %, OSMS 3 %, CO 5 %, social tax 6 %.

Electronic documents of the sales contour (electronic invoice (ESF) in the ESF IS and STS) are generated by specialized objects of the configuration, not by this document.

6. Related Objects and Input Based On

• Cost Calculation of Inventory / Month Closing — the source of the cost calculation table, on the basis of which adjustments were built. In the current contour, these regulatory operations replace the document.
• Register InventorySales — links the adjustment with primary sales documents (write-off operations for inventory).
• Information register InformationOnCostAdjustmentsOfProductsAndGoods — used by reports for cost analysis.
• Input based on — is not supported in standard mode for the deprecated object. Copying the document (see scenario 3.5) is theoretically possible but not recommended and is blocked by the logic of the form when creating a new item.

Typical Work Scenarios (read-only/service):

Typical Errors

The texts are quoted verbatim from the configuration code (release 3.0.68.1).

7. Extension Points

• Configuration extension (without removal from support): you can override the handler OnCreateOnServer of the document form to, for example, allow access to historical data without blocking, or add service export commands.
• Event subscriptions: for migration/service tasks, it is permissible to subscribe to Processing/ProcessingDeletion through event subscription without modifying the object module.
• Reports and SCD: new analytical reports are built on top of the information register InformationOnCostAdjustmentsOfProductsAndGoods and register InventorySales — this is a safe point for reading historical data.
• Additional processing (BSP): service processing for mass unprocessing/duplicate analysis is connected as external, without interfering with the object's metadata.

Since the object is marked as unused, any modifications should be strictly service-oriented (reading, migration, unprocessing). It is not advisable to build business logic on it — new cost adjustment tasks are solved by standard regulatory operations for closing the period.