Tested on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The sales department head asks: "Split the deals up — separate retail requests, separate project deliveries, so the pipeline isn't a dumping ground." You open the first "Customer Deal" and 1C won't let you save it: the "Deal Type" field is highlighted red, and the selection list is empty. This is exactly the catalog you're about to fill in. What you configure in it determines how managers will run the deal, which stages they'll see, and what the sales reports will show.
Let's agree on the main point right away. "Customer Deal Types" is a classifier catalog, not a document. It doesn't post anything, doesn't generate an ESF, and doesn't create accounting entries. Entries and electronic documents are created later — in the sales documents you enter inside the deal. Below I'll show the whole chain so you can see exactly where the money and taxes appear.
1. Purpose
The catalog defines "kinds" of deals: standard sale, deal with manual stage transitions, other non-process interactions. The deal type determines which stages the manager's work will go through, whether pipeline control is enabled, and how the deal enters sales analytics.
2. Where to find it
- Section CRM and Marketing → in the navigation panel, group Settings and Catalogs → Customer Deal Types.
- Direct navigation link (Main menu → Tools → Go to navigation link, or Ctrl+show link):
e1cib/list/Справочник.ВидыСделокСКлиентами
If the menu item is missing — the functionality is disabled. Enable it: Master Data and Administration → CRM and Marketing → checkbox "Customer deals". Without it, neither the catalog nor the deals themselves will appear.
2a. How to find out your release
Main menu (≡ icon in the top left corner) → Help → About the program. In the window that opens you'll see two lines: the platform version (1C:Enterprise 8.3.x) and the configuration release — "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)". This guide is written for this version; on neighboring releases the field composition is the same, only labels may differ.
3. How to fill it in
Click Create. There aren't many fields, but each one affects deal behavior.
| Field | Required | Why, and what happens if it's wrong |
|---|---|---|
| Name | ✅ Yes | What the manager selects from the list. Write it meaningfully: "Standard wholesale sale", "Equipment project delivery". A vague "Deal 1" — and in a month no one will understand which type is for what. |
| Deal Type | ✅ Yes | The main field. Determines the mechanics (see section 5). Once at least one deal has been posted under this type, the type cannot be changed — choose deliberately. |
| Sales Process / Stages | Depends on type | Filled in for the "Deal with manual stage transition" type. Here you list your own stages ("Request → Invoice → Shipment → Payment"). If left empty, the manager will have nowhere to move the deal. |
| Main Sales Process | For standard sale | For the "Standard sale" type, a preconfigured end-to-end process with fixed pipeline stages is used. |
| Comment / Description | No | A hint for managers: when to apply this type. Small detail, but saves questions. |
Procedure:
- Enter the Name.
- Select the Deal Type — this is the fork in the road, everything else depends on it.
- If you selected a type with stages — describe the sales process stages in the correct order.
- Fill in the Comment if needed.
- Save and close.
Tip: don't multiply dozens of types. In practice 2–4 are enough: standard sale, project deal, other interactions. The fewer types, the cleaner the reports.
4. Worked example with figures and entries
A company sells coffee machines wholesale. You create a deal type:
- Name: "Standard wholesale sale"
- Deal Type: "Standard sale"
Next the chain works like this:
- The manager creates a Customer Deal "Astana Coffee LLP", and in the Deal Type field sets "Standard wholesale sale".
- Inside the deal, based on it, a Sale of Goods and Services is entered: 10 coffee machines × 100,000 ₸.
Calculation at Kazakhstan 2026 rates:
| Indicator | Amount, ₸ |
|---|---|
| Cost excluding VAT | 1,000,000 |
| VAT 16% | 160,000 |
| Total payable | 1,160,000 |
| Cost of goods (10 × 70,000) | 700,000 |
The entries are generated by the sales document (not the catalog and not the deal itself):
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Revenue from sale (excl. VAT) |
| 1210 | 3130 | 160,000 | VAT payable 16% |
| 7010 | 1330 | 700,000 | Cost of goods written off |
After the buyer pays:
| Dr | Cr | Amount, ₸ | Description |
|---|---|---|---|
| 1030 | 1210 | 1,160,000 | Receipt to current account |
Based on the sale, an ESF is issued in the ESF IS for 1,160,000 ₸ (incl. VAT 160,000 ₸), and for goods subject to the virtual warehouse — a SNT. The deal type "drives" all this work through the stages and pulls the result into pipeline reports: how many deals of this type were won, for what amount, and what conversion rate.
Bottom line: the deal type itself doesn't move money, but it's exactly what groups this sale in the "Standard wholesale sales" analytics and defines which stages the manager went through before shipment.
5. Operation types (deal types)
The Deal Type field is the set of modes provided by the catalog:
| Deal Type | What it does |
|---|---|
| Standard sale | End-to-end process with preconfigured pipeline stages (initial interest → proposal → approval → sale). Provides full analytics on efficiency and loss reasons. |
| Deal with manual stage transition | You describe the stages yourself for your business. The manager moves the deal through stages manually. Flexible when the standard pipeline doesn't fit. |
| Other non-process interactions | No stages, no pipeline. You simply record the fact of working with the customer (calls, meetings, one-off sales) when there's no need to track the process. |
6. What is generated on save
The catalog is not posted — the element has no accounting register movements and no entries of its own. When an element is saved:
- a catalog entry is created/updated, available for selection in the "Customer Deal" document;
- the deal type becomes an analytics dimension in CRM reports.
Everything "accounting-related" appears further down the chain, in documents entered inside the deal:
- Entries (Dr 1210 Cr 6010, Dr 1210 Cr 3130, Dr 7010 Cr 1330, etc.) — from the sales document.
- ESF — from the ESF IS based on the sale.
- SNT — for goods requiring a waybill.
- Movements in sales and mutual settlements registers — from the deal's documents, broken down by deal type for reporting.
7. Printed forms
The catalog element has no printed forms of its own — there's no need to print a "deal type". Analytics by deal type are gathered in reports in the CRM and Marketing section:
- Sales Pipeline — conversion by stage, broken down by deal type.
- Deal Efficiency — won/lost, amounts, average cycle.
- Deal Loss Reasons — why deals of this type fall through.
Printed forms (invoice, waybill, act, ESF, SNT) belong to the sales documents inside the deal, not to the catalog.
8. Common errors
"The 'Deal Type' field is not filled in" — when trying to save a "Customer Deal". → The list of types is empty. Create at least one type (section 3) and select it in the deal.
"The catalog element 'Customer Deal Types' cannot be deleted because it is referenced" — when deleting. → Deals have already been created for this type. It cannot be deleted. Mark it for deletion and/or use More → Check deletion possibility to see which deals reference it.
The deal type is locked (unavailable for editing). → A deal has already been posted for this type. Changing the type is prohibited to avoid breaking pipeline history. Create a new type with the needed type.
The "Customer Deal Types" item is missing from the menu. → The functionality is not enabled. Master Data and Administration → CRM and Marketing → "Customer deals" — check the box.
A manual-transition deal has no stages. → The process/stages are not filled in for the deal type. Open the type and describe the stages in the correct order.
9. FAQ
Does this catalog generate entries? No. It's a classifier. The entries (Dr 1210 Cr 6010, Dr 1210 Cr 3130, Dr 7010 Cr 1330) are made by the sales document entered inside the deal.
Is an ESF issued from the deal type? No. The ESF (in the ESF IS) and SNT are issued based on sales documents. The deal type only groups these sales in analytics.
What VAT rate applies in 2026? In Kazakhstan in 2026 the rate is 16%. In the example with a sale of 1,000,000 ₸, VAT is 160,000 ₸, total 1,160,000 ₸.
Can the deal type be changed after creation? As long as no deal has been made under this type — yes. Once at least one deal has been posted — no. Create a new type.
How many deal types should you set up? Usually 2–4: standard sale, project deal, other interactions. An excess of types blurs the reports.
How does "standard sale" differ from "deal with manual transition"? A standard sale follows a preconfigured end-to-end process with a ready-made pipeline. In a manual one, you set the stages yourself and move the deal between them manually.
How do I delete an unnecessary deal type? If it isn't referenced — mark it for deletion and run Administration → Delete marked objects. If there are references, deal with the deals first.
Why is the type list empty? The "Customer deals" functionality is enabled, but no one has created any types yet. Set up the first type yourself.
Does the deal type affect accounts? No. Accounts (1210, 1330, 6010, 3130, 7010) are substituted in sales documents based on accounting settings, not from the deal type.
Where can I see efficiency by deal type? Section CRM and Marketing → reports Sales Pipeline, Deal Efficiency, Deal Loss Reasons — filtered by type.
10. Related documents
- What it's filled in based on: the catalog is maintained manually; the functionality must first be enabled in Master Data and Administration → CRM and Marketing.
- Where it's used: the "Customer Deal" document (the "Deal Type" field) — the main consumer.
- What's entered next inside the deal: Commercial Proposal, Customer Order, Sale of Goods and Services, and based on them — ESF, SNT, payment documents.
- Related catalogs: "Sales Process Stages", "Partners", "Counterparties", "Customer Agreements".
How to find out your release: Main menu → Help → About the program — the platform version and configuration release are shown there.
This guide was prepared for "Trade Management for Kazakhstan", release 3.4.5.21 (edition 3.4). Rates and accounts are given per Kazakhstan 2026 standards: VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸.