1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | БонусныеПрограммыЛояльности |
| Full name | Справочник.БонусныеПрограммыЛояльности / Catalogs.БонусныеПрограммыЛояльности |
| Synonym | “Loyalty Bonus Programs” |
| Configuration | Trade Management for Kazakhstan, edition 3.4, version 3.4.5.21 |
| Where to find it in 1C | “Service Subsystems” section → “Loyalty Bonus Programs” |
| Navigation link | e1cib/list/Справочник.БонусныеПрограммыЛояльности |
Purpose. The catalog stores settings for the rules governing the accrual and redemption of bonus points under loyalty programs. A catalog item determines which points and under what conditions are awarded to a customer upon a sale, how points are converted into a monetary equivalent, how long they remain valid, and the extent to which they can be used to pay for subsequent purchases. The catalog is part of the master data and is used by retail and wholesale sales documents when applying program settings and recording bonus-point transactions.
2. Attributes and tabular sections
2.1. Header attributes
| Attribute | Type | Purpose |
|---|---|---|
| Код | String | Unique item code, a standard catalog attribute. |
| Наименование | String | Name of the loyalty program, for example, “Gold Card” or “5% Cashback.” |
| Наименование полное / НаименованиеПолное | String | Full name used to display the program in forms and documents. |
| Родитель | CatalogRef | Catalog group when a hierarchy is used. |
| ПометкаУдаления | Boolean | Standard flag marking an item for deletion. |
| Организация | CatalogRef.Организации | Organization on whose behalf the program is applied. |
| ВидБонуснойПрограммы / ТипНачисления | Enumeration | Accrual method: a percentage of the sale amount, a fixed number of points, or accrual based on specified conditions. |
| ПравилоНачисления | CatalogRef / Enumeration | Reference to a rule or condition for accruing points. |
| КурсБалла / СтоимостьБалла | Number | Monetary equivalent of one point in tenge upon redemption. |
| ПроцентНачисления | Number | Percentage of points accrued on the purchase amount. |
| МаксПроцентОплатыБаллами | Number | Maximum share of the receipt amount that may be paid with points. |
| СрокДействияБаллов / ПериодСгорания | Number and period unit | Validity period of accrued points before they expire. |
| Валюта | CatalogRef.Валюты | Currency used to calculate the monetary equivalent of a point. |
| ДатаНачала / ДатаОкончания | Date | Program validity period. |
| Действует / Активна | Boolean | Program activity flag. |
| Комментарий | String | Free-form description of the program and the specifics of its application. |
2.2. Tabular sections
| Tabular section | Key fields | Purpose |
|---|---|---|
| УсловияНачисления | Сегмент, ЦеноваяГруппа, Номенклатура, Процент, ДатаНачала, ДатаОкончания | Differentiated accrual rules for individual customer segments, price groups, or products. |
| ПериодыАкций / Расписание | ДатаС, ДатаПо, КоэффициентНачисления | Accrual multipliers applied during specified promotion periods. |
| Ограничения | ВидОграничения, Значение | Conditions relating to the minimum receipt amount, product categories, or sales channels. |
The set of attributes, their names, and the availability of tabular sections are determined by the metadata of version 3.4.5.21. The actual object structure can be viewed in the Configurator: “Common” → “Catalogs” → “БонусныеПрограммыЛояльности” → “Data.”
3. Forms
| Form | Purpose |
|---|---|
| ФормаСписка (ListForm) | List of loyalty programs with available filters. It opens via the e1cib/list/Справочник.БонусныеПрограммыЛояльности link. |
| ФормаЭлемента (ItemForm) | Main form for entering and editing program attributes, accrual conditions, the point exchange rate, and the validity period. |
| ФормаВыбора (ChoiceForm) | Selection of a program in objects that contain a reference to a loyalty bonus program. |
| ФормаГруппы (FolderForm) | Editing a group when a catalog hierarchy is used. |
4. Key module procedures
The set of handlers is determined by the metadata and program code of version 3.4.5.21. When analyzing the object, primary attention is given to form events, validation before writing, and the program interfaces through which the program settings are used in sales.
Item form module:
- ПриСозданииНаСервере — initial form setup, population of specified values, and management of element visibility.
- Bonus program type change handler — manages the availability of fields related to the selected accrual method.
- Accrual percentage and point exchange rate change handlers — validate entered numeric values against the configuration rules.
Object module:
- ОбработкаПроверкиЗаполнения — validates required attributes and the logical sequence of the program validity dates.
- ПередЗаписью — performs the configuration-defined validation of the program parameters being written.
Manager module:
- The manager's program interfaces may be used by application objects to obtain the loyalty program settings as of the transaction date.
The actual procedure names should be taken from the catalog modules and related common modules in version 3.4.5.21. This prevents customizations from being tied to hypothetical handler names that do not exist in the production infobase.
5. Posting and register movements
The catalog is used as master data. Transactions involving the accrual and redemption of points are recorded by sales documents and other application objects that access the settings of the selected loyalty program.
Data related to the use of the program:
- Information on bonus-point balances and turnover by customer or card.
- Data on sales, payments, discounts, and settlements with the customer recorded by the relevant documents.
- Program parameters applicable as of the transaction date.
Example of recording a sale with 16% VAT:
The sale price is 116 000 ₸, including VAT of 16 000 ₸. The price excluding VAT is 100 000 ₸.
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 100 000 | Revenue from the sale to the customer recognized |
| 1210 | 3130 | 16 000 | VAT on the sale recognized at the rate of 16% |
| 7010 | 1330 | According to accounting records | Cost of goods sold written off |
| 1030 | 1210 | 116 000 | Payment received in the bank account |
If bonus points are applied to a sale, the document must reflect the amount payable and the terms of the reward granted to the customer in accordance with the program settings. The procedure for recognizing the discount, revenue, VAT, and liabilities for accrued points is established in the organization's accounting policy and the implemented bonus program scheme.
Accrued points are accounted for under the rules adopted by the organization for the loyalty program. The selected method of recording the customer reward must be applied consistently in the production database, and the data must be checked for compliance with the source documents.
Electronic documents of the Republic of Kazakhstan. When processing a sale, the accountant applies the procedure prescribed for issuing electronic documents for the transaction. If an electronic invoice reflects taxable turnover for 2026 at the standard rate, VAT of 16% is specified. Whether a goods accompanying note must be issued is determined by the type of goods and the conditions of the specific transaction.
6. Related objects and creation based on
The following may be related to the catalog:
- Sales documents, cash register receipts, and retail sales reports in which the conditions for accruing or redeeming points are applied.
- Discount cards, partner and counterparty data, and customer segments, if such a relationship is provided for by the program settings.
- Information and accumulation registers used by the application logic to store program conditions and bonus-point data.
Use in transactions: the program is selected in the loyalty card, sales document, and discount setting attributes provided by the configuration. The available population options depend on the functionality enabled in the infobase.
7. Extension points
- Configuration extension: adding attributes and form elements, for example, to integrate with an external bonus processing system, without modifying the main configuration.
- Event subscriptions: handling the ПередЗаписью and ПриЗаписи events for additional data validation and synchronization with external loyalty systems.
- Additional attributes and information: storing additional program characteristics using the standard tools of the relevant subsystem.
- Program interface: connecting additional logic to discount and bonus calculations through the common modules and call points provided by the configuration.
The customization method is selected with regard to the infobase support mode. To preserve the ability to update, configuration extensions, event subscriptions, and standard additional attributes are preferable.
8. Questions and answers
Where can I view the actual set of catalog attributes?
Open the metadata of the БонусныеПрограммыЛояльности catalog in the Configurator for version 3.4.5.21 and go to the “Data” section. It displays the object's attributes, tabular sections, forms, and modules.
Why is the loyalty program not applied in the sales document?
Check the program's validity period and activity status, the organization, the customer and product selection conditions, the availability of the bonus card, and the document date. The values in the document must meet the conditions specified for the program.
How can I check the accrual and redemption of bonuses?
Compare the program settings with the sales document data, and then analyze the bonus-point information for the customer or card. Separately check the transaction date, the accrual percentage or rule, the point exchange rate, and the established limit on payment with points.
Can integration with an external bonus system be added?
Yes. A configuration extension and the provided write or sales-processing events are used for this purpose. The composition of the transmitted data, resubmission rules, and exchange controls are established in the integration regulations.