Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
A counterparty sent an invoice, but your database shows a different price for the same item. Or a manager complains: "I'm selling below purchase price in wholesale." Or an accountant sees an amount without VAT in a sale, when it should include VAT. Almost always the root cause is the same — an incorrectly configured price type. This is the very "price list column" that all prices in sales, purchasing, and inventory reports stem from. Let's figure out how to set it up correctly once and stop running into discrepancies.
1. Purpose
"Price Types" is a catalog where you describe the columns of your price list: purchase, retail, wholesale, dealer, etc. For each column you set the currency, whether VAT is included in the price, how the price is calculated (manually, markup, formula), and how it's rounded. These price types are then used in "Item Price Setup," in orders and sales.
2. Where to find it
Section CRM and Marketing → block Prices → Price Types. The second path is Master Data and Administration → Items → Price Types (depending on enabled functions).
To open the list directly: Main Menu → Tools → Navigate by Reference Link and paste:
e1cib/list/Справочник.ВидыЦен
If the "Prices" section isn't visible — enable the functional option Master Data and Administration → CRM and Marketing → Multiple Price Types (with a single price type, the catalog is hidden).
2a. How to check your release
Main Menu (☰ icon top left) → Help → About. In the window that opens: the "Configuration" line shows the release (e.g., "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)"), the "Platform" line shows the 1C:Enterprise version. If your release is different — field placement may shift slightly, but the logic is the same.
3. How to fill it in
Click Create. The form is compact, but each field affects the final amount in documents.
| Field | Why it matters and what happens if it's wrong |
|---|---|
| Name (required) | The column's name: "Wholesale," "Retail," "Purchase." Seen by managers when selecting a price. Won't save if empty. Name it meaningfully, not "Price Type 1" — otherwise you won't make sense of the reports later. |
| Formula identifier | A short code (Latin/Cyrillic, no spaces) that other formulas use to reference this price type. If you plan "Wholesale = Purchase × 1.3" — the formula won't build without the base price's identifier. |
| Price includes VAT (key flag) | If checked — the entered price already contains 16% VAT, and the program will extract it by calculation. If unchecked — the price is "net," and VAT will be added on top. Mix this up and the sale will go out with an amount off by 16%. For retail it's usually checked, for wholesale it's up to you, but keep it consistent throughout the chain. |
| Currency (required) | The currency you store the price in: tenge (₸). If you set dollars but sell in tenge — the price will be recalculated by exchange rate, and amounts will "float." For Kazakhstan it's almost always KZT. |
| Price setting method (determines all behavior) | Options below. This is the main switch: do you calculate the price manually, or does the program do it for you. |
| Use in sales / base only | "Base only" — the price type is visible in formulas but unavailable to the manager in an order. This is how you hide the purchase price from sales. Forget to uncheck it, and the purchase price will "leak" into sales documents. |
| Rounding | Precision (to 1 ₸, to 10 ₸) and rule: "by arithmetic rules" or "round up." For retail it's convenient to use "round up to 5/10 ₸" to avoid price tags like 1,347 ₸. |
Price setting methods
- Assigned manually — you enter the price yourself in "Item Price Setup." Full control, but all the manual work falls on you.
- Markup on another price type — "Wholesale = Purchase + 30%." You specify the base price type and percentage. The most common choice.
- Markup on receipt — the price is calculated from the last receipt price of the item. When the purchase price changes, the selling price is automatically pulled up.
- Custom formula (based on database data) — complex schemes via the formula constructor (max/min of several prices, different markups by group).
For markup methods, the fields Base price type and % markup/discount appear — both are required, otherwise the price won't calculate.
4. Worked example with figures
Let's set up two columns for a trading company in Almaty.
Step 1. Price type "Purchase" — method "Assigned manually," currency KZT, "Price includes VAT" flag unchecked, "base only." Through the Item Price Setup document, we set for the "Coffee Machine" item: purchase price 100,000 ₸ (without VAT).
Step 2. Price type "Wholesale" — method "Markup on another price type," base price type "Purchase," markup 30%, "Price includes VAT" flag checked, rounding to 10 ₸ upward, identifier Opt.
The program calculates the wholesale price with VAT:
- base without VAT: 100,000 × 1.30 = 130,000 ₸;
- VAT 16%: 130,000 × 16% = 20,800 ₸;
- price with VAT: 150,800 ₸ → after rounding to 10 ₸ = 150,800 ₸.
Step 3. Sale of 1 unit at the wholesale price. The sale shows an amount of 150,800 ₸ (incl. VAT 20,800 ₸), cost 100,000 ₸. Entries per the standard chart of accounts for Kazakhstan:
| Dr | Cr | Amount, ₸ | Transaction |
|---|---|---|---|
| 1210 | 6010 | 130,000 | Revenue without VAT |
| 1210 | 3130 | 20,800 | VAT payable (16%) |
| 7010 | 1330 | 100,000 | Item cost written off |
Gross profit on the deal: 130,000 − 100,000 = 30,000 ₸ — exactly your markup. If you had mistakenly unchecked the "Price includes VAT" flag for the wholesale type, the program would have charged 16% on top of 150,800, and the buyer would have received an invoice for 174,928 ₸ instead of 150,800 — that's where "different amount on the delivery note" comes from.
5. Operation types (what the catalog provides)
The catalog itself does not create posting operations. It defines the pricing model used by:
- manual assignment — prices only through "Price Setup";
- markup/discount on a base price type — auto-recalculation from another column;
- markup on receipt price — tied to purchasing;
- custom formula based on database data — calculation via the query designer.
6. What is generated upon recording and use
When recording a catalog item, there are no accounting entries or e-invoices/waybills — this is reference/master data. The record fixes the price type setup and makes it available in documents.
The prices themselves are stored separately — in the information register "Item Prices," written by the Item Price Setup document (where you also select your price type).
Postings, e-invoices, and waybills appear in sales/purchase documents where the price of this type has been applied: a sale generates movements on accounts 1210 / 6010 / 3130 / 7010 (see example) and issues an e-invoice in the e-Invoice system, and for traceable/imported goods — a waybill (SNT). In other words, a correctly configured price type guarantees that the e-invoice will carry the correct amount and the correct 16% VAT.
7. Printed forms
The catalog itself has no printed form from the item card. Price types participate in printing through other objects:
- Price List (CRM and Marketing → Prices → Print Price List) — the price list columns are your price types;
- Item Price Setup — printing the document with a column for the selected price type;
- Invoice for Payment / Customer Order / Sale — printed forms where the price is taken from the assigned price type.
8. Common errors
"Base price type not filled in" — you chose "Markup on another price type" but didn't specify which one. Open the price type, fill in the Base price type and % markup fields.
"Circular reference in price calculation formula" — "Wholesale" refers to "Dealer," and "Dealer" refers back to "Wholesale." Break the loop: the markup should be based on an independent base type (usually "Purchase" with manual assignment).
Price in the sale is 16% higher/lower than expected — a mismatch of the "Price includes VAT" flag between the price type and the price setting in the document. Bring the flag to a consistent value across the entire "purchase → wholesale → retail" chain.
"Currency field is not filled in" — you're saving a price type without a currency. Set it to KZT.
The manager sees the purchase price in the order — the base price type isn't set to "base only." Open "Purchase," uncheck "Use in sales" / check "Base only."
9. FAQ
1. How does a price type differ from the price itself? A price type is a rule and a column (how to calculate, in what currency, with or without VAT). The specific number is stored by the "Item Price Setup" document in the "Item Prices" register.
2. How many price types can you set up? As many as you like. Typical set: Purchase, Retail, Wholesale, Small Wholesale, Dealer. The key requirement is enabling the "Multiple Price Types" option.
3. How do I set "wholesale = purchase + 30%"? Method "Markup on another price type," base — "Purchase," percentage 30. Change the purchase price, and wholesale will recalculate automatically at the next price setup.
4. Should I check the "Price includes VAT" flag? Decide based on your task, but keep it consistent across the entire chain. For retail it's usually checked (price tag with VAT). VAT in Kazakhstan for 2026 is 16%, and the program will extract it by calculation.
5. Why isn't the price being applied in the sale? Either no "Price Setup" has been created for this price type as of the document date, or the price type is marked "base only" and unavailable for sales, or it wasn't selected in the agreement/contract with the customer.
6. Can I store the price in a foreign currency but sell in tenge? Yes, specify the price type's currency (e.g., USD) — when applied in a document in tenge, the program will recalculate at the rate on that date. But for stable prices, it's more reliable to keep everything in KZT directly.
7. How do I set price rounding to 10 tenge? In the price type, set rounding precision to 10 and the rule "round up." A price of 150,803 ₸ will become 150,810 ₸.
8. Why can't I delete a price type? It's already used in documents (price setups, sales, agreements). Mark it for deletion and run "Delete Marked Objects" — the program will show where it's being used.
9. Does the price type affect the e-invoice? Not directly, but through it, the price and VAT amount that go into the e-invoice are determined in the sale. An incorrect VAT flag → incorrect tax amount on the electronic invoice.
10. How can I sell the same item at different prices to different customers? Set up several price types and link the appropriate one to the sales terms agreement (or contract) of a specific customer.
10. Related documents
- Based on the price type work: the Item Price Setup document (enters the figures), Sales Terms Agreements, Customer Order, Sale of Goods and Services, Invoice for Payment, the Price List printout.
- Price types rely on: the Items catalog (for whom prices apply), Currencies (price currency), the Item Prices register (where the values physically reside), VAT settings (16% rate).
How to check your release: Main Menu → Help → About — this shows the 1C:Enterprise platform version and configuration release.
This guide was prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4). When updating the configuration, verify field placement.