Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You've decided that customers should receive messages: "order assembled", "pay your debt by Friday", "we have a coffee promotion". You set up a mailing — and the program asks you to specify a notification type. Empty list. You open this catalog to add your own message types: "Order Readiness", "Debt Reminder", "Marketing". This is exactly where order is established in why and to whom you write. Let's break it down.
Important right away: this is a classifier catalog, not a document. It doesn't "post" anything, doesn't generate ESF, SNT, or accounting entries. Its job is to give you a neat list of categories that mailings, templates, and communication reports later reference. That's why the sections on entries and electronic documents below are honestly marked: no movements.
1. Purpose
"Customer Notification Types" is a catalog where you store types (categories) of messages sent to buyers: about order status, debt, promotions, etc. The value from this catalog is inserted into mailing and notification settings, and then used for grouping and filtering in interaction reports.
2. Where to find it
The direct and reliable way is to open it via a navigation link:
- Menu "Service" → "Go to navigation link" (or the "star/link" icon in the top panel).
- Insert:
e1cib/list/Справочник.ВидыОповещенийКлиентам - Click "Go" — the list will open.
Through the interface, the catalog is located in the CRM/marketing settings block. Reference point: section "CRM and Marketing" (or "Sales") → group "Settings and Catalogs" → "Customer Notification Types". If the item isn't visible — enable the notification/mailing functional option in "Master Data and Administration" → "CRM and Marketing", otherwise the catalog won't show in the menu (though the object itself exists and is accessible via the navigation link).
2a. How to find out your release
"Help" → "About the Program" (in some interfaces — the "i" icon in the top right). In the window that opens:
- Platform version — for example, 8.3.24.xxxx;
- Configuration — "Trade Management for Kazakhstan", release 3.4.5.21, edition 3.4.
If your release is older or newer — the set of fields may differ by one or two, but the catalog logic is the same.
3. How to fill it in
Open the list and click "Create". There are few fields — it's a simple classifier.
| Field | Required | Why it's needed and what happens on error |
|---|---|---|
| Name | Yes | This is what you'll see in the selection list when setting up a mailing. Write it meaningfully: "Order Readiness", "Debt Reminder", "Promotions and Mailings". If you name it vaguely ("Type 1", "Test") — later in mailings and reports you won't be able to figure out what's what, and you'll send the wrong thing to the wrong people. |
| Code | Filled automatically | The program assigns it itself. Don't touch it manually without reason: a manual code can conflict with auto-numbering and interfere with sorting. |
| Parent / Group | No | Appears if the catalog is hierarchical. Allows you to group types: for example, folders "Service" and "Marketing". Useful when there are many types. An empty parent means the item is at the root, which is normal. |
| Comment / Note | No | Free text for yourself: when and to whom we send this type. Doesn't affect selection, but helps colleagues avoid re-asking. |
| Deletion mark | No | Not an input field, but an indicator. Set it if the type is no longer used but can't be deleted immediately (old mailings reference it). |
Filling practice:
- Create a separate type for each business purpose of the message. Don't lump "debts" and "promotions" into one type — they have different logic for customer mailing consent and different reporting.
- Keep the list short: 5–10 types for the whole business is usually enough. Nobody maintains a bloated classifier.
- Once filled — "Save and Close".
Note (version-dependent, requires verification in your release): in certain 3.4 builds, the item may have an attribute linking to a channel (SMS/e-mail) or a message template. If such fields aren't present in your card — the channel and text are set not here, but in the mailing setup itself.
4. Worked example
Task: an online store in Almaty wants three types of messages to buyers. We create three catalog items.
Item 1
- Name:
Order Ready for Pickup - Group:
Service - Comment:
Sent when the order is set to "Assembled" status
Item 2
- Name:
Debt Reminder - Group:
Service - Comment:
For customers with overdue payment on account 1210
Item 3
- Name:
Promotions and Special Offers - Group:
Marketing - Comment:
Only for customers who consented to advertising
What happens with money and accounting? Nothing. Creating a catalog item does not generate a single accounting entry. For clarity — here's how it looks against a real sales movement (which is done by the sales document, not this catalog): when shipping goods worth 116,000 ₸ (including VAT 16% = 16,000 ₸, price excluding VAT 100,000 ₸, cost 70,000 ₸), the sale generates:
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1210 | 6010 | 116,000 | Revenue accrued, buyer's receivable |
| 6010 | 3130 | 16,000 | VAT payable allocated (16%) |
| 7010 | 1330 | 70,000 | Cost of goods written off |
Our catalog is not involved in these entries — it only marks which notification type you'll use to notify this buyer (e.g., "Order Readiness"). That's its only role: categorizing communication, not accounting.
5. Operation types
The classifier catalog has no "operation types" — that's an attribute of documents, not catalogs. The only actions with an item are: Create, Edit (F2), Mark for Deletion, Copy (F9), and with hierarchy — Create Group. The catalog's "operational load" is to be a value selected in other objects (mailing settings, templates, reports).
6. What is generated upon posting
Nothing is posted. Catalogs in 1C are not posted and do not create movements. When an item is saved:
- no accounting entries;
- ESF (IS ESF) and SNT are not generated (this is a function of sales/transfer documents, not the classifier);
- no movements in accumulation/information registers (only a record in the catalog table itself).
All the catalog does is save a new item and make it available for selection. Sending messages is done by mailing mechanisms, which just reference the selected type.
7. Printed forms
The catalog item has no printed forms of its own — there's nothing and no reason to print a "notification type". The standard output of the list to print/file is available via "More" → "Output List" (to Excel/spreadsheet document) — handy for giving colleagues a list of the types created.
8. Common errors
"Field 'Name' is not filled in" 1C won't let you save an item without a name. Enter a meaningful name and repeat "Save".
"An item of the catalog 'Customer Notification Types' with this name already exists" (or duplicate by code) You're creating something that already exists. Don't multiply duplicates — find the existing type in the list and use it. Close the unnecessary draft without saving.
"Failed to delete '…': there are references to the object" The type is already specified in a mailing or report. Direct deletion is prohibited. Set a deletion mark, then run reference control via "Administration" → "Maintenance" → "Deletion of Marked Objects": the program will show where the type is used and offer to replace it with another before deletion.
Catalog not in the menu
The notification/mailing functionality isn't enabled. Go to "Master Data and Administration" → "CRM and Marketing" and enable the required option, or open the object directly via the link e1cib/list/Справочник.ВидыОповещенийКлиентам.
The needed type isn't inserted into the mailing Check whether the item has a deletion mark set — marked values usually don't appear in selection. Remove the mark.
9. FAQ
1. Does this catalog generate entries or ESF? No. It's a classifier. It creates no entries, no ESF, no SNT. Electronic documents are generated by sales and transfer documents, not by this catalog.
2. Does the notification type affect VAT or taxes? No. The catalog has nothing to do with VAT calculation (16% in 2026), individual income tax, mandatory pension contributions, or other taxes. It's about communications, not accounting.
3. Is it mandatory to fill it in to work in the program? No. As long as you're not setting up mailings and automatic notifications to customers, the catalog can remain empty. It's needed exactly when you enable notifications.
4. How many types should be created? Usually 5–10 — by the number of real scenarios: order readiness, debt reminder, promotions, quality survey, greetings. More becomes harder to maintain.
5. Can a type be renamed after creation? Yes. Open the item, change the name, save. All references to it will be preserved automatically — renaming doesn't break links.
6. How do I delete an unnecessary type? Mark it for deletion, then run "Deletion of Marked Objects" in the "Administration" → "Maintenance" section. If the type has references, the program will ask you to replace it before deletion.
7. Where is the message text and channel (SMS/e-mail) set? Usually — in the mailing setup itself or in the message template, not in this catalog. Only the category is stored here. In some 3.4 releases, the channel binding may also be in the card — check the field composition in yours.
8. Can types be grouped into folders? If the catalog is hierarchical — yes, via "Create Group" (for example, "Service" and "Marketing"). If there's no "Parent" field, hierarchy isn't provided in your release, and all types are in a single list.
9. Why isn't the new type in the selection list when setting up a mailing? Most often it has a deletion mark, or you're looking in the wrong section. Remove the mark and refresh the form.
10. How do I quickly export the entire list of types? Open the list, "More" → "Output List", select output to a spreadsheet document or Excel.
10. Related documents
The catalog is not entered based on documents and is not itself a basis for entering documents — it's master data (reference information). Its values are used by:
- Mailing / automatic customer notification settings (CRM) — insert the type as a message category;
- Message templates (if present in the release) — linked to the type;
- Interaction and communication reports — filter and group correspondence by notification type;
- Indirectly related to scenarios around customer orders, sales, and debt reminders (account 1210) — it's events on these documents that serve as the trigger to send a notification of the corresponding type.
How to find out your release: "Help" → "About the Program" — it shows the platform version and configuration release.
This guide was prepared for "Trade Management for Kazakhstan", release 3.4.5.21 (edition 3.4). When updating the configuration, check the field composition of the card.