Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
You close the month, open the turnover balance sheet, and see: settlements with a customer are "stuck" on the wrong account. An advance from a client landed on 1210 instead of 3520, or a purchase landed on 3310, even though this is an accountable person. The cause is almost always the same — the partner or contract has not been assigned the required financial accounting group for settlements, or no accounts have been set up for the group. This catalog is the very "switch" that decides which account debts and advances will land on. Let's figure out how it works and how to set it up once so that postings are generated correctly.
1. Purpose
The catalog defines analytical groups by which the program determines the accounts for settlements with partners: receivables, payables, and advances. The group itself is just a label (a name). Accounts are linked to it separately, in the financial accounting accounts settings. The group is assigned to a partner, a contract, or specified in rules, and when posting documents it pulls in the required accounts of the Kazakhstan chart of accounts.
2. Where to find it
Path in the interface:
Master Data and Administration → Master Data → Financial Accounting Groups for Settlements.
If the item is not visible, enable visibility: Master Data and Administration → Financial Result and Controlling → Financial Accounting of Items and Settlements — the checkbox must be enabled, otherwise the entire block of financial accounting groups is hidden.
A quick way to open the list is a navigation link. Copy it, click in 1C Tools → "Go to navigation link" (or Alt+F1) and paste:
e1cib/list/Справочник.ГруппыФинансовогоУчетаРасчетов
The accounts themselves for the groups are set up in a separate place: Master Data and Administration → Financial Accounting Settings → Financial Accounting Accounts Setup (register "Settlement Accounts with Partners").
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 can see the platform version (e.g., 8.3.24) and the configuration release — the line "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)". Check the instructions against this exact number: the location of menu items may shift slightly between releases.
3. How to fill it in
The catalog is deliberately simple. All the "magic" is not in the group's record, but in where you later specify it and which accounts you link to it.
Group record fields
| Field | Required | Why it's needed and what happens if it's wrong |
|---|---|---|
| Name | Yes | The name by which you will select the group in a partner's record and in a contract. Make it descriptive: "Customers (KZT)," "Suppliers (KZT)," "Foreign currency settlements," "Accountable persons." If you name it abstractly ("Group 1"), in six months you won't remember where to assign it, and you'll assign it to the wrong counterparties. |
| Parent (group) | No | The catalog is hierarchical. Folders are convenient when there are many groups (separately for sales, purchases, other settlements). Does not affect postings. |
There's nothing else to fill in on the record itself — accounts are not specified here.
Step 2. Link accounts to the group (this is the main part)
Open Financial Accounting Accounts Setup → Settlement Accounts with Partners and create a row:
- Organization — your company (required). If left blank, the setting will apply to all organizations; convenient for one company, dangerous for several — accounts will "drift."
- Financial accounting group for settlements — the one you created (required).
- Settlement account — the main debt account. For customers — 1210, for suppliers — 3310 (required).
- Advance account — for customer advances 3520/3510, for supplier advances 1610 (required, otherwise the advance will land on the debt account and distort the turnover balance sheet).
- Deferred income/expense account, packaging account, etc. — fill in if used; for standard trade, debt and advance accounts are sufficient.
If the row is not created, when posting a document the program will not find the account and will issue an error (see section 8).
Step 3. Assign the group to a partner or contract
- Partner/Counterparty record → settlement settings section → "Financial accounting group for settlements." Set in bulk for all individual customers, suppliers, etc.
- Contract/Agreement — if settlements with the same partner go through different accounts (for example, regular supply and a loan), the group in the contract overrides the partner's group. This is a point setting.
Priority is simple: contract → partner. Whatever is filled in closer to the document takes effect.
4. Worked example with postings
Company LLP "Astana-Trade" sells goods to customer LLP "Client".
Initial data:
- Goods excluding VAT: 1,000,000 ₸
- VAT 16%: 160,000 ₸
- Total payable: 1,160,000 ₸
- Cost of goods: 700,000 ₸
Setup: for customers, a group "Customers (KZT)" is set up, settlement account 1210, advance account 3520. The group is set in the record of LLP "Client".
Prepayment scenario. The client first transferred an advance of 1,160,000 ₸, then received the goods.
Upon receipt of funds (document "Receipt of Non-Cash Funds"):
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1030 | 3520 | 1,160,000 | Advance received from customer |
Note that the money landed on 3520 (advance), not on 1210 — precisely because the advance account is specified in the group. Without it, the amount would have landed on 1210, and the client would have shown "negative receivables."
Upon sale of goods (document "Sale of Goods and Services"):
| Dr | Cr | Amount, ₸ | Meaning |
|---|---|---|---|
| 1210 | 6010 | 1,000,000 | Sales revenue |
| 1210 | 3130 | 160,000 | VAT payable 16% |
| 7010 | 1330 | 700,000 | Cost of goods written off |
| 3520 | 1210 | 1,160,000 | Offset of previously received advance |
Result: the client's balance closed at zero, revenue and VAT are reflected, cost of goods is written off. All settlement accounts (1210 and 3520) were substituted from the financial accounting group for settlements. If the group had not been assigned, the advance offset would not have gone through, and both a debt and an advance would have been hanging simultaneously on the client.
5. Operation types (what the catalog covers)
The catalog does not have separate "operation types" — it is not a document. But it determines accounts for all types of settlements:
- settlements with customers (receivables 1210 / advances 3520, 3510);
- settlements with suppliers (payables 3310 / advances 1610);
- settlements with accountable persons and other receivables/payables (if you set up separate groups for them);
- foreign currency settlements — it is convenient to set up a separate group for these to control exchange rate differences.
6. What is generated upon posting
The catalog itself does not post anything. It participates in the posting of settlement documents and affects:
- Postings to Kazakhstan chart of accounts — 1210, 1610, 3310, 3520, etc. are substituted from the accounts linked to the group.
- The "Settlements with Partners" register and accounting (statutory) registers — filled in with the correct accounts.
- ESF and SNT are not generated directly by the catalog. Electronic invoices (ESF) are issued from the sale/purchase document in the ESF IS, and SNT — when goods are moved. But correct settlement accounts are needed so that statutory accounting reconciles with the turnover balance sheet after ESF upload.
7. Printed forms
The catalog has no printed forms of its own. It is auxiliary. Printed forms (Invoice for Payment, Waybill, Act, ESF, Certificate of Work Performed) are generated from settlement documents, where this group only sets the accounts. To verify the setup, use reports: "Statement of Settlements with Customers/Suppliers" and the standard turnover balance sheet for accounts 1210/3310.
8. Common errors
"Settlement account not filled in for the financial accounting group for settlements…" Appears when posting a sale/receipt. Cause: the group is assigned to the partner, but there is no row with accounts in "Financial Accounting Accounts Setup." Solution — create a row with the organization, group, and accounts 1210/3520 (or 3310/1610).
Advance landed on 1210 instead of 3520. The "Advance account" field is not filled in the setup row. Add the advance account and repost the funds receipt documents.
No group at all selected for the partner. The "Financial accounting group for settlements" field is empty in the counterparty's record → the document either does not post, or takes accounts from the general "for empty group" setting. Assign the group in bulk using the batch attribute change processing.
Different accounts for one partner got mixed up. You conduct both regular sales and a loan with the counterparty, but there is only one group. Set up a second group and specify it in a separate contract — the contract will override the partner's setting.
Old documents did not change after the group was changed. The catalog only affects new postings. After changing the group or accounts, repost the documents for the period (batch reposting), otherwise the old postings will remain with the old accounts.
9. FAQ
Question — Answer are given below.
10. Related documents and objects
Where the group comes from:
- The "Partners" / "Counterparties" catalog — the main place where the group is assigned.
- "Sales Terms Agreements" and "Contracts" — point-specific override.
Where the group takes effect (settlement documents):
- "Sale of Goods and Services," "Return of Goods from Customer";
- "Purchase of Goods and Services," "Return of Goods to Supplier";
- "Receipt/Write-off of Non-Cash Funds," "Cash Receipt/Payment Order";
- "Debt Adjustment," "Offset."
Related financial accounting catalogs:
- "Item Financial Accounting Groups" — define item accounts (1330), revenue (6010), cost of goods sold (7010), VAT (3130);
- "Financial Accounting Accounts Setup" — the register where specific Kazakhstan accounts are linked to groups.
How to find out your release
Help → About the Program. The window shows the platform version (8.3.x) and the configuration release. This manual was prepared for "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21. In other releases, the location of menu items may differ.
Note: this manual is current for release 3.4.5.21 of the "Trade Management for Kazakhstan" configuration (edition 3.4). Kazakhstan rates and norms are given as of 2026 (VAT 16%, MCI 4,325 ₸, minimum wage 85,000 ₸).