State Contracts" Directory (Trade Management for Kazakhstan 3.4)

1. Identification of the object

Purpose. The catalog stores a list of government (budget) contracts under which the organization acts as a supplier of goods, works, or services to customers from the public sector. The catalog entry is used as an analytical dimension in sales, payment, and electronic document flow documents (e-invoice/waybill), allowing separation of government procurement operations, separate accounting of contract obligation fulfillment, and generation of reporting on government contracts (including for the government procurement web portal and accounting requirements broken down by budget funding sources).

The catalog is a reference and regulatory data item (master data). It does not generate movements itself — movements are generated by documents that reference it.

2. Header attributes and tabular sections

2.1. Attributes (header)

2.2. Tabular sections (typical for tracking execution)

The exact composition of tabular sections is version-specific: verify against the configurator for build 3.4.5.21 (requires verification for the specific build).

3. Forms

4. Key module procedures

No separate applied BSL evidence for this catalog has been provided. Below is the typical set of handlers for catalogs in Trade Management for Kazakhstan.

Object module (МодульОбъекта):

• ОбработкаПроверкиЗаполнения(Отказ, ПроверяемыеРеквизиты) — control of mandatory fields (Number, Date, Customer, Organization, ContractAmount); blocking the recording of an incomplete contract.
• ПередЗаписью(Отказ) — data normalization before writing: recalculation of total amounts, setting default values (currency = tenge, VAT rate = 16%).
• ПриКопировании(ОбъектКопирования) — clearing registration fields (Number, status) when creating a copy.

Item form module (ФормаЭлемента.Модуль):

• ПриСозданииНаСервере(Отказ, СтандартнаяОбработка) — form initialization, setting field availability based on status.
• ОрганизацияПриИзменении / КонтрагентПриИзменении — substitution of agreement and settlement currency.
• СтавкаНДСПриИзменении — recalculation of VAT amounts in the specification.

Manager (МодульМенеджера):

• Procedures for generating printed forms and selection handlers for the electronic document flow subsystem.

Specific paths path:string are not provided due to lack of BSL evidence; when developing further, look for handlers in the catalog's object module and item form module.

5. Posting and movements

The catalog is not posted and does not directly generate movements in registers. It serves as an analytical dimension in documents that reference it. The standard accounting chain for a contract (standard chart of accounts of the Republic of Kazakhstan) looks as follows:

Sale of goods/services under a government contract:

Payment from the customer (receipt to current account):

Settlements with suppliers under the contract (procurement): Dr 1330 / Cr 3310, input VAT accounted for separately.

VAT calculation example. Delivery price excluding VAT = 1,000,000 ₸. VAT 16% = 160,000 ₸. Total payable by the customer = 1,160,000 ₸. Entries: Dr 1210 Cr 6010 — 1,000,000 ₸; Dr 1210 Cr 3130 — 160,000 ₸.

Registers where the contract appears as an analytic dimension (through documents): "Sales," "Customer Settlements," "VAT," registers of the electronic document subsystem (e-invoice/waybill). The catalog entry is specified in the e-invoice and waybill attributes for transmission to the e-invoice information system.

6. Related objects and entry based on

Reference the catalog (used as a dimension):

• Sales documents: "Sale of Goods and Services," "Customer Invoice."
• Payment documents: "Receipt of Non-Cash Funds."
• Electronic documents: e-invoice (electronic invoice, e-invoice information system) and waybill (goods accompanying waybill).
• Counterparty agreements, Counterparties (Customer).

Entry based on (typical scenario):

• Based on the contract → "Sale of Goods and Services" / "Customer Invoice" with completion of the specification and "Government Contract" dimension.
• From the sale → e-invoice and waybill with transfer of the contract reference.

7. Extension points

• Configuration extensions (Extensions): adding attributes (e.g., procurement identification code, funding source, budget program code) without removing support.
• Event subscriptions (ПодпискиНаСобытия) on ПередЗаписью/ПриЗаписи for integration with the government procurement portal.
• Additional attributes and information (properties mechanism) — for storing lot attributes without changing metadata.
• Overridable common modules of Trade Management for Kazakhstan — for embedding custom logic for filling in e-invoice/waybill broken down by contract.
• Handler ОбработкаПроверкиЗаполнения — extension of business control (checking contract limits, deadlines, presence of procurement identification code).