Checked on release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).
The counterparty sent a reconciliation act, but you have a discrepancy: their advance is closed, while your payment is "hanging" separately from the debt. You open the turnover for account 1210 (or 3310) and see two lines for one buyer — shipment by itself, payment by itself, no offset. The reason is almost always the same: calculations are conducted "By calculation documents", and the payment does not specify the very calculation document to which it relates. If the original shipment is not in the database (you switched to a new program, entered balances, shipped in another system) — there is nothing to link the payment to. This is where the object "Calculation document with the counterparty (manual accounting)" is needed: it creates a "fictitious" link to the primary document that is not in the database, so that 1C correctly reconciles the advance with the debt.
1. Purpose
Service document. Its only task is to act as a link (calculation document) in mutual settlements that are conducted by documents when there is no real primary document in the database. It does not create any accounting entries or tax movements itself — it only provides other documents with an "anchor" to which the payment, offset, or initial balance is attached.
2. Where to find
This document usually does not have a separate menu item — it is created "on the fly" from the "Calculation document" field in other objects (entering balances, receipt/write-off of money, offset of advances) by the selection button → Create.
To see the entire list of already created documents, open them directly via the navigation link:
- Menu "Service" (or "File" — depending on the mode) → "Go to navigation link…"
- Insert:
e1cib/list/Document.CalculationDocumentWithCounterparty - Click "Go" — a journal of all manual accounting calculation documents will open.
2a. How to know your release
"Help" → "About the program". In the opened window: platform version (for example, 8.3.2x) and configuration release — line "Accounting for Kazakhstan, version 3.0 (3.0.74.2)". If your release is older or newer — the location of the fields may differ slightly, but the logic remains the same.
3. How to fill
The document is short — there are few fields, but each affects whether the debt will "collapse" with the payment.
| Field | Mandatory | Why and what will happen in case of error |
|---|---|---|
| Organization | ✅ | The company for which the debt is maintained. If you make a mistake — the payment will not find the document in the context of its organization and will not close anything. |
| Date | ✅ | Critical. Based on the date, 1C builds the repayment queue (usually FIFO). Set the date of actual debt occurrence (the date of shipment/advance), not today's date — otherwise, the offset will "eat" the wrong document. |
| Counterparty | ✅ | Buyer or supplier. The context in which the balance hangs. |
| Contract | ✅ | This determines the type of mutual settlements and currency. The contract must be the same as in the payment/shipment, otherwise the balance will not reconcile — there will be two opposing lines. |
| Amount | ✅ | The amount of debt/advance that this "anchor" replaces. In the currency of the contract calculations. |
| Currency | ✅ (inherits from the contract) | Tenge ₸ by default. For currency contracts — the currency of the contract; the amount in tenge will be converted at the rate in the consumer documents, not here. |
| Comment | — | Write where the debt came from ("balance as of 01.01.2026", "shipment by ESF №… from the old database"). It will help during the new reconciliation in six months. |
The main rule: the trio "Organization + Counterparty + Contract" must match letter for letter in this document and in the document that refers to it. Otherwise, there will be no offset.
4. Analyzed example with entries
Situation. From 01.01.2026 you switched to a new database. LLP "Altyn" owes you 1,160,000 ₸ for goods shipped in December 2025 (the sale was in the old system, it is not in the new database). In January, the buyer pays.
Step 1. Create a manual accounting calculation document (date — 31.12.2025):
- Organization — yours;
- Counterparty — LLP "Altyn";
- Contract — "Supply of goods №15" (mutual settlements by documents);
- Amount — 1,160,000 ₸.
It does not generate any entries — it just appears in the list as a link.
Step 2. Enter the initial balance (document "Entering initial balances", accounting section "Settlements with buyers", account 1210). In the line in the "Calculation document" field, select the object created in step 1. The entry is made by the entering of balances:
| Dr | Cr | Amount, ₸ | Content |
|---|---|---|---|
| 1210 | 000 (auxiliary account for entering balances) | 1,160,000 | Debt of LLP "Altyn" as of 01.01.2026 |
Now there is a debt on account 1210, "attached" to our calculation document.
Step 3. Payment is received (document "Receipt of money" / statement). In the line, specify the same contract and in the "Calculation document" select the same manual accounting object:
| Dr | Cr | Amount, ₸ | Content |
|---|---|---|---|
| 1030 | 1210 | 1,160,000 | Payment from LLP "Altyn" |
Since the payment refers to the same calculation document as the balance, the balance on 1210 collapses to zero. The discrepancy in the reconciliation act is closed. Note: VAT is not touched here — it was "included" in the December sale; for new shipments in 2026, the RK rate is 16%.
5. Types of operations
The document does not have a separate attribute "Type of operation" — it is a universal link. In practice, it is used for four scenarios:
- Accounts receivable from buyers — debt on account 1210, which is not in the database.
- Accounts payable to suppliers — advance issued/debt on 3310.
- Entering initial balances for settlements when switching to the program.
- Offset / adjustment of debt, when opposing obligations need to be consolidated into one link.
6. What is formed when posting
Honestly and straightforward: nothing in accounting and taxes.
- No entries. Dr/Cr are formed by consumer documents (entering balances, payment, offset) that refer to it.
- ESF and CNT are not created. This is not a sales document — electronic invoices in the ESF system and accompanying invoices (CNT) are issued from sales/movement documents, not from here.
- No movements in VAT registers.
- The document only becomes available as a value in the "Calculation document" field and participates in the selection of mutual settlements.
If you expect an entry from it — you are using the wrong document; you need "Sale", "Receipt", or "Entering balances".
7. Print forms
The service document does not have its own print forms — there is nothing to print, the primary document lives in the documents that refer to it. From related objects, you can print:
- Reconciliation act of mutual settlements (section "Sales"/"Purchases") — there this debt will already be taken into account;
- print forms of consumer documents (invoice, waybill, payment order).
8. Common errors
"Contractor's contract is not filled in" — when trying to save. The contract is a defining field for the type of mutual settlements. Select the contract under which the debt actually hangs.
Payment does not close the debt, there are two lines in the turnover for 1210. Reason: different contracts (or different calculation documents) are specified in the payment and in this document. Open both, bring them to the same trio "Organization–Counterparty–Contract" and the same calculation document, repost both.
"Mutual settlements under the contract are conducted by calculation documents" — warning during selection. This is a signal that the "Calculation document" field is mandatory and must be specified; if there is no real primary document — create a manual accounting document directly from this field.
Offset "ate" the wrong debt. Reason — incorrect date. FIFO extinguishes the earliest document. Set the correct date of obligation occurrence in the manual accounting document.
Currency debt matches in currency but not in tenge. Remember: the rate and ruble-tenge amount are set by the consumer document, not this object. Check the rate in the payment/balance.
9. FAQ
How to select the type of operation (advance/debt) in this document? You can't — there is no operation type attribute. Whether it is an advance or a debt is determined by the document that refers to it and the accounting account in it (1210/1610, 3310/3510).
Does it create entries? No. This is a reference object. All entries are made by consumer documents: entering balances, receipt/write-off of money, offset of advances.
Is an ESF or CNT issued for it? No. Electronic documents are formed from sales and movements. Neither the ESF system nor CNT is involved here.
Why is it needed at all if it doesn't move anything? So that when accounting "by calculation documents" the payment has something to attach to when the original primary document is not in the database — when switching to the program, when entering balances, when closing discrepancies in reconciliation.
What date to set? The date of actual debt/advance occurrence, not today's date. It affects the repayment queue during the offset.
Why did the payment not close the debt, although the amounts are equal? Almost always — different contracts or different calculation documents in the payment and in the balance. Bring the trio "Organization–Counterparty–Contract" and one calculation document together, repost both.
Can one such document close several shipments? It's better not to. For each debt/advance, make a separate link with the correct date and amount — this way reconciliation and FIFO work cleanly. One "common" document confuses the breakdown by deadlines.
Does it affect VAT in the declaration? No, it does not create movements in VAT registers. VAT has already been accounted for (or will be accounted for) in sales documents at a rate of 16%.
Where to delete it if created by mistake?
Open the list via the navigation link e1cib/list/Document.CalculationDocumentWithCounterparty, but first make sure that no one refers to it (check related documents), otherwise the payment will "hang" again.
Can a reconciliation act be made for it? Separately — no. But the established debt will appear in the standard "Reconciliation act of mutual settlements" and in the turnover for the settlement account.
10. Related documents
Based on what it is created / where it is selected:
- Entering initial balances (settlements with buyers/suppliers) — the main consumer;
- Receipt / Write-off of money, bank statement — "Calculation document" field;
- Adjustment of debt / Offset of advances.
What replaces it in "normal" life:
- Sale of goods and services — if the shipment were in the database, the calculation document would be it (and ESF/CNT would be issued for it);
- Receipt of goods and services — similarly for accounts payable.
Essentially, this object is a "patch" in place of the missing primary document. As soon as a real sale or receipt appears in the database, you should refer to them, and the manual accounting document should be removed from the chain.
How to know your release
"Help" → "About the program": there you will find the platform version and configuration release. This manual has been checked on "Accounting for Kazakhstan", version 3.0, release 3.0.74.2. In other releases, the composition of fields practically does not change — the object is service and minimal.
Prepared for release 3.0.74.2 "Accounting for Kazakhstan" (version 3.0).