Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The manager asks for a sales plan for Q1 2026 — broken down by month and product group, to later compare with actuals. You go into the planning section, click "Create sales plan" — and the first field of the card requires you to specify the plan type, and the list is empty. Until you describe the rules here (what we are planning, at what frequency, and in what breakdown), you cannot create a single planning document. That's why working with planning doesn't start with the plan itself, but with the "Plan Types" reference book.
1. Purpose
"Plan Types" is a reference-setting book. One element sets a "template" for planning documents: what we are planning (sales, procurement, assembly), at what frequency, and in what breakdowns (by nomenclature, warehouses, partners). The reference book itself calculates nothing and posts nothing — it defines the data structure that is later filled in by the "Sales Plan," "Procurement Plan," "Assembly Plan" documents.
2. Where to find it
Three working ways:
- Via the planning section: "Master Data and Administration" → "Planning" → "Plan Types" block (or the "Planning" section → "Settings and reference books" → "Plan Types," if the section is placed on the panel).
- From the plan document: when creating a "Sales Plan," in the "Plan Type" field click "+" and create a new one right there.
- Direct 1C navigation link: copy and open via "Service" → "Go to navigation link" (or Ctrl+F11):
e1cib/list/Справочник.ВидыПланов
If there is no "Planning" section in the interface — it is disabled. Enable it: "Master Data and Administration" → "Section Settings" → "Planning" → check "Sales and procurement planning."
2a. How to find out your release
"Help" → "About the program" (or the "i" icon in the top right corner). In the window that opens, you will see the platform version (e.g., 8.3.24) and the configuration release — a line like "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)." It's the second part that matters: the instructions below apply to release 3.4.5.21. On adjacent releases, field names match, but the set of available breakdowns may differ.
3. How to fill it in
Open "Create." Let's go through each field — why it's needed and what happens if you make a mistake.
| Field | Required | Why it's needed / what happens if you make a mistake |
|---|---|---|
| Name | Yes | The name by which you select the type in documents. Write it meaningfully: "Sales by month by groups." A vague "Type 1" — and in a month you won't remember what breakdown you were planning in. |
| Frequency | Yes | The plan's step: Day / Week / Decade / Month / Quarter / Half-year / Year. Determines how many period rows the plan will be split into. Set "Year" instead of "Month" — you won't see seasonality and won't be able to compare with actuals by month. You won't be able to change the frequency after entering plans. |
| Planned data (quantity / amount) | Yes | What you enter into the plan: only amounts (₸), only quantity, or both. Make a mistake — you'll have to create the type anew: the system won't let you switch on an existing type that already has entered plans. |
| Nomenclature detail level | Yes | Breakdown: Nomenclature / Nomenclature types / Price groups / Categories. This determines the granularity of the plan. Choose "Nomenclature" for 20,000 items — the plan will become unmanageable; for a top-level plan, take "Nomenclature types" or "Categories." |
| Warehouse detail level | No | Whether to plan by warehouses or without them. Needed if warehouses are managed separately. |
| Partner / manager detail level | No | Breakdown by clients and persons in charge. Enable if you later distribute the plan to managers under personal responsibility. |
| Organization / department | No | Restricts the scope of the plan to one organization or department. Empty — the plan is general. |
| Filling method (source) | No | Auto-fill rule: "Based on last period's sales data," "Based on customer orders," "Manually." Sets where the document pulls figures from when you click "Fill." Leave it as "Manually" — you'll have to enter everything by hand. |
| Planning currency | No (default ₸) | Currency of plan amounts. For Kazakhstan — tenge (₸). |
After filling it in — "Save and close." The element is immediately available in documents.
4. Worked example with numbers
Task. Plan sales for Q1 2026 by month, in amounts, by product group, and compare with actuals.
Step 1. Plan type. Create an element:
- Name:
Sales 2026, monthly by groups - Frequency: Month
- Planned data: Amount
- Nomenclature detail level: Nomenclature types
- Currency: ₸
Step 2. "Sales Plan" document with this type. Enter the plan (amounts excluding VAT):
| Period | Planned revenue, ₸ |
|---|---|
| January 2026 | 5,000,000 |
| February 2026 | 6,000,000 |
| March 2026 | 7,000,000 |
| Quarter total | 18,000,000 |
The plan itself is a benchmark. It creates no postings: a plan is never "posted" in the accounting sense, it only writes figures to the planning register for the "Plan-actual analysis" report.
Step 3. Actuals. In March, you sold goods for exactly the planned 7,000,000 ₸ (excluding VAT). Postings are not generated by the plan type — they are generated by the sales document. At the Kazakhstan VAT rate of 16% and a cost of goods of 60% (4,200,000 ₸), the sale will record:
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1210 | 6010 | 7,000,000 | Revenue from sales |
| 1210 | 3130 | 1,120,000 | VAT 16% (7,000,000 × 16%) |
| 7010 | 1330 | 4,200,000 | Cost of goods sold written off |
Total receivable from the buyer: 7,000,000 + 1,120,000 = 8,120,000 ₸. Funds to the account: Dr 1030 Cr 1210 — 8,120,000 ₸.
Step 4. Comparison. The "Sales plan-actual analysis" report will show: March plan 7,000,000, actual 7,000,000, deviation 0. It is precisely for this reconciliation that the plan type was created — without it there is nothing for the report to compare against.
5. Operation types (what the reference book provides)
One reference book element defines the type of planning. Possible variants for which you create types:
- Sales plan — by nomenclature, types, price groups, or categories.
- Procurement plan — need for goods under the sales plan or under orders.
- Assembly (disassembly) plan — if you handle kitting.
- Assortment plan — assortment matrix management by store formats.
- Internal consumption plan — materials consumed for own needs.
The set of available types depends on the planning functional options enabled in "Master Data and Administration."
6. What is generated
The reference book is a setting, so it's important to clearly understand the boundary here:
- The reference book creates no Dr/Cr postings. The element is not posted. Accounting entries (1210, 6010, 3130, 7010, 1330, etc.) are generated only by sales/receipt documents, not by the plan.
- No electronic documents (ESF, SNT) are generated. ESF in the ESF IS and SNT are issued from actual shipments and transfers; the plan has no relation to electronic document flow.
- Register movements: selecting the plan type fills in the planning registers (planned sales/procurement). These are what "Plan-actual analysis" reads.
7. Printed forms
The reference book element has no printed forms of its own — there's no need to print a "plan type." Printing and reports exist at the level of documents and reporting:
- Report "Sales (procurement) plan-actual analysis" — plan against actual.
- Report "Sales plan fulfillment."
- Printed form of the "Sales Plan" document itself (tabular export by period).
8. Common errors
"The 'Name' field is not filled in" — you tried to save without a name. Enter a meaningful name and repeat the save.
"Changing frequency is unavailable: planned data has already been entered for this plan type" — you're trying to switch month/quarter for a type that already has documents. Create a new type with the needed frequency, mark the old one for deletion.
"Could not select plan type: it is marked for deletion" — the element cannot be selected in a document. Remove the mark (right-click → "Mark for deletion / Remove mark") or select another type.
"Detail level in the sales plan does not match the plan type" — you changed the breakdown (e.g., from "Nomenclature types" to "Nomenclature") after already entering rows. Restore the original detail level or create a separate type for the new breakdown.
There is no "Planning" section in the menu — the functional option is disabled. "Master Data and Administration" → "Section Settings" → "Planning" → enable.
9. FAQ
See the question block below — the same answers are given separately.
10. Related documents
- What is a plan type created on the basis of: nothing — it is a primary setting. You create it before the planning documents.
- What uses the plan type: the documents "Sales Plan," "Procurement Plan," "Assembly (Disassembly) Plan," "Assortment Plan" — in the "Plan Type" attribute.
- What reconciles the plan with actuals: sales and receipt documents (they provide the actuals and postings/ESF), and the "Plan-actual analysis" reports match them against the plan.
- Related reference books: "Nomenclature," "Nomenclature Types," "Price Groups," "Warehouses," "Partners" — define the detail-level breakdowns.
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," edition 3.4, release 3.4.5.21.