Reference "Types of Price Nomenclature" — Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification

Purpose. The catalog stores customizable price types for goods and services: retail, wholesale, contractual, purchase, planned, etc. Each price type sets the rules for forming and storing the price — currency, indication of VAT/excise inclusion, rounding method. Price types are used in sales and purchase documents, in the price setting document for nomenclature, and in price reports. Sales managers, procurement specialists, and accountants work with the object when setting up pricing.

Where to find in 1C: section "Nomenclature and Warehouse" → "Price Types Catalog". Navigation link: e1cib/list/Catalog.PriceTypesCatalog.

2. Attributes and Table Parts

2.1 Header Attributes

Standard attributes of the catalog: Code, Name, DeletionMark, Predefined.

2.2 Table Parts

Table parts are absent. The catalog has a simple structure — all attributes are located in the header of the item.

About VAT rate. The price type itself only stores the indicator PriceIncludesVAT; the numerical rate is taken from the document/nomenclature. In the RK for 2026, the basic VAT rate is 16%. When PriceIncludesVAT = True, VAT is separated from the price using the formula Price × 16 / 116; when False — it is added on top Price × 16%.

3. Forms

The catalog contains three forms:

4. Key Module Procedures

In the attached evidence, the original BSL code of the modules is not provided, so below is a typical set of handlers for catalogs of this type (actual names/strings are specified according to the specific assembly 3.0.74.2).

Object Module (ObjectModule):

• BeforeWriting(Refusal) — control of filling PriceCurrency; upon the first recording of the item — enabling the functional option UsePriceTypesCatalog.
• OnCopying(CopyingObject) — transfer of rounding settings and VAT/excise indicators during copying.
• FillingProcessing(FillingData, FillingText, StandardProcessing) — setting default values (currency from accounting policy/constants, RoundingMethod).

Element Form Module (ElementForm):

• OnCreateOnServer(Refusal, StandardProcessing) — setting visibility/accessibility of fields (for example, blocking PriceIncludesExcise when there is no excise accounting).
• PriceIncludesVATOnChange(Element) / RoundingMethodOnChange(Element) — updating dependent availability of form elements.

Manager Module (ManagerModule):

• FormObtainingProcessing — selection of the form during programmatic opening.
• Export functions for obtaining predefined/main price types for use in documents.

“Requires verification” (version-specific): the exact composition of included functional options and the presence of an activation handler in the object module against the subscription to the event — depends on the subsystem of the specific assembly.

5. Posting and Movements

The catalog is not a document and is not posted — it does not generate its own movements in the registers. It is an element of regulatory and reference information (pricing).

The price type participates in the posting of documents that reference it. Below is the standard logic with specific accounts from the typical chart of accounts of the RK (for VAT, a rate of 16% is used).

Information Register "PricesNomenclature". The document "Setting Prices for Nomenclature" writes records in the context of PriceType (reference to this catalog), Nomenclature, Currency (from PriceCurrency). The indicator PriceIncludesVAT is recorded along with the price.

Posting of sales documents (price type — retail/wholesale):

Example. Retail price of the product = 11,600 ₸, price type with PriceIncludesVAT = True:

• VAT = 11,600 × 16 / 116 = 1,600 ₸ (Dr 1210 Cr 3130);
• income without VAT = 10,000 ₸ (Cr 6010).

Posting of purchase documents (price type — purchase):

Electronic Documents. When selling, electronic invoices (ESF) are generated (IS ESF) and, if necessary, SNF; the tax indicators of the document rely on the price and the indicator PriceIncludesVAT of the selected price type. The VAT rate in the ESF is 16%.

6. Related Objects and Input Based On

References to the catalog:

• Information register PricesNomenclature (dimension PriceType).
• Document SettingPricesNomenclature (attribute "Price Type").
• Sales documents (SalesOfGoodsServices, invoices, retail sales) — price selection by type.
• Purchase documents (ReceiptOfGoodsServices) — when using the purchase price type.
• Information register PriceTypesCatalogsCounterparties / settings of counterparties' contracts (default price type for the counterparty).
• Price reports (price lists, price analysis).

Input Based On. Direct input of documents "based on" the price type is not provided. The price type itself is used as a parameter for filling other objects (documents and contracts).

Dependencies of Attributes: PriceCurrency → catalog "Currencies"; RoundingMethod → enumeration "RoundingMethods".

7. Extension Points

• Event subscriptions BeforeWriting/OnWriting of the object — for additional validation (for example, prohibiting simultaneous inclusion of VAT and excise for certain categories or controlling the allowable currency).
• Configuration extension (Extensions): adding attributes (for example, "DefaultDiscount", "PriceCategory"), new forms, changing form handlers through borrowing.
• Additional attributes and information (subsystem "Properties") — without changing metadata, through PlanOfCharacteristicTypes.AdditionalAttributesAndInformation.
• Overridable pricing modules — mechanisms for automatic price calculation (markup from the base type, rounding) for programmatic price setting through the register PricesNomenclature.
• Functional option UsePriceTypesCatalog — managing the visibility of the object in the interface.

Version-specific (requires verification in 3.0.74.2): the presence of standard mechanics "price from the base type + percentage markup" and the composition of overridable pricing modules depend on the subsystem of the specific assembly.