--- title: "Contracts with Counterparties (Documents.ContractsWithCounterparties)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/dogovory-kontragentov-documents-dogovorykontragentov-en source: BuhGPT --- # Contracts with Counterparties (Documents.ContractsWithCounterparties) > **TL;DR:** ```html 1. Identification Parameter Value Full Name Document.CounterpartyContracts ( Documents.CounterpartyContracts ) Object Type Application metadata object that stores contract terms Synonym “Counterparty Contracts” Configuration Accounting for Kazakhstan, edition 3.0.74.2 --- ```html 1. Identification Parameter Value Full Name Document.CounterpartyContracts (Documents.CounterpartyContracts) Object Type Application metadata object that stores contract terms Synonym “Counterparty Contracts” Configuration Accounting for Kazakhstan, edition 3.0.74.2 Country of Accounting Republic of Kazakhstan (default currency — tenge, ₸) Purpose Storage of terms of settlements with counterparties (suppliers, buyers, partners) by organizations: currency, method of settlements, payment terms, price type, as well as special features — agency VAT, joint activity (simple partnership), SRP. Where to find: - Navigation link: e1cib/list/Document.CounterpartyContracts - Interface: section “Purchase” → “Counterparty Contracts” (as well as “Sale” → “Counterparty Contracts”); available from the directory Counterparties. The object is an element of regulatory reference information (contract terms), therefore in the basic logic it does not generate accounting entries by itself. It acts as analytics (subaccount) “Contracts” in primary documents and settlement registers (see section 5). 2. Attributes and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose Organization ReferenceLink.Organizations ShowError The organization on behalf of which the contract is concluded. Blocked from modification after the related documents are processed. ContractType EnumerationLink.ContractTypes ShowError Type of contract (with supplier, with buyer, other). Determines the logic of substitution in documents and the sign of debt. Blocked after document processing. SettlementCurrency ReferenceLink.Currencies ShowError Currency of settlements under the contract. Affects exchange rate differences and recalculation of amounts. Blocked after document processing. SettlementManagement EnumerationLink.SettlementManagementByContracts DontCheck Accounting method: “by contract as a whole” or “by settlement documents”. Determines the detail of analytics in settlement registers. PriceType ReferenceLink.PriceTypes DontCheck Default price type when selling/purchasing. Automatically substituted in documents. AgencyVATAccounting Boolean DontCheck Indicator of tax agent for VAT within the contract. Affects the formation of VAT entries (VAT rate RK 2026 — 16%). ContractNumber String DontCheck Number of the paper contract (for search). ContractDate Date DontCheck Date of signing the contract. ContractStartDate Date DontCheck Date of commencement (may differ from the date of signing). ContractEndDate Date DontCheck Date of expiration of the fixed-term contract. PaymentTermEstablished Boolean DontCheck Controls the visibility of the “PaymentTerm” field. PaymentTerm Number DontCheck Payment term in days from the document date; used to control overdue debt. JointActivityContract Boolean DontCheck Indicator of simple partnership/joint activity. Opens the table part “JointActivityParticipants”. PaymentConditions String (unlimited) DontCheck Text of payment conditions for printing in documents. Comment String DontCheck User's arbitrary notes. 2.2 Table Parts Table Part When Used Key Fields Purpose JointActivityParticipants When JointActivityContract = True Counterparty, ParticipationShare, Comment Composition of participants in a simple partnership and their shares for the distribution of results of joint activity. The indicator of hierarchy and grouping of contracts is preserved at the list level: contracts can be grouped by counterparties/types for ease of navigation. 3. Forms Form Purpose ElementForm / DocumentForm Main form for entering and editing contract terms. Manages the visibility of fields: PaymentTerm is shown when PaymentTermEstablished, table part of participants — when JointActivityContract, blocks key attributes (Organization, ContractType, SettlementCurrency) after the appearance of processed documents. ListForm List of contracts filtered by organization, counterparty, contract type; quick access to settlements. SelectionForm Selection of a contract in primary documents (invoice, waybill, act, payment documents) filtered by counterparty and organization. GroupForm (when hierarchy) Editing groups/folders for classifying contracts. 4. Key Module Procedures Evidence contains the structure of attributes and purpose, but does not contain BSL listings. Below are typical handlers for this type of object in BK 3.0. Specific path:string are specified for each delivery (version-specific). Object Module (ObjectModule): - FillProcessing(FillData, ...) — when entering based on counterparty/organization, transfers Organization, Counterparty, substitutes SettlementCurrency from settings and ContractType according to the context of the base document. - FillCheckProcessing(Refusal, CheckedAttributes) — control of mandatory attributes (Organization, ContractType, SettlementCurrency), check for non-empty table part of participants in joint activity, control of the correctness of action dates. - BeforeSaving(Refusal, ...) — blocking changes to key attributes (Organization, SettlementCurrency, ContractType) when there are processed documents for the contract. Form Module (FormModule): - OnCreationOnServer — initial setup of field visibility (PaymentTerm, table part of participants) and availability of blocked attributes. - PaymentTermEstablishedOnChange — toggling visibility/accessibility of the PaymentTerm field. - JointActivityContractOnChange — managing visibility of table part JointActivityParticipants. - ContractTypeOnChange — reconfiguration of available price types and logic of substitution in documents. - SettlementCurrencyOnChange — control of currency compatibility with already processed documents. 5. Processing and Movements The contract is the terms of settlements, therefore it does not create independent movements in the accounting register. It participates as analytics (subaccount “Contracts”) in entries and movements formed by primary documents. Below is the standard logic of RK for documents using the contract. 5.1 Registers where the contract is a measurement - Accumulation Register “SettlementsWithCounterparties” — measurements: Organization, Counterparty, Contract, SettlementDocument, Currency. Detail by SettlementDocument is included when SettlementManagement = “By settlement documents”. - VAT / ESF registers — when AgencyVATAccounting movements are formed for agency VAT. 5.2 Typical entries of documents by contract (plan of accounts RK) Sale to the buyer (ContractType = With buyer), VAT 16%: Dr Cr Content 1210 6010 Revenue recognized (income from sales), subaccount “Contracts” = this contract 1210 3130 VAT accrued payable on sales (16%) 7010 1330 Cost of goods sold written off Example: goods for 1,000,000 ₸ without VAT → VAT = 160,000 ₸ (16%), receivable on 1210 = 1,160,000 ₸. Receipt from supplier (ContractType = With supplier): Dr Cr Content 1330 3310 Goods received, subaccount “Contracts” = this contract 1420 3310 Offset VAT on receipt (16%) Payment / receipt of money: Dr Cr Content 1030 1210 Payment received from the buyer to the current account 3310 1030 Paid to the supplier from the current account Control of payment term (PaymentTerm, PaymentTermEstablished) is used by settlement reports to calculate overdue debt, but does not generate entries. 5.3 Electronic Documents The contract defines the parties and terms on the basis of which ESF (electronic invoice, ESF IS) and SNT (accompanying invoice for goods) are formed. The indicator AgencyVATAccounting determines the scheme for issuing ESF for agency VAT. 6. Related Objects and Input on the Basis Referencing the contract (using as an attribute/subaccount): - Sales documents: “Sale of goods and services”, “Invoice to the buyer”, “Act of completed works”. - Receipt documents: “Receipt of goods and services”, “Invoice from supplier”. - Payment documents: “Payment order (outgoing/incoming)”, “Cash receipt/payment order”. - VAT/ESF documents: “Invoice (issued/received)”, ESF, SNT. - Register “SettlementsWithCounterparties” and settlement reports (reconciliation act, statement by counterparties). Input on the basis: - From Counterparty — creating a new contract with auto-filling of organization and counterparty. - From the contract — input of invoice, sale/receipt, payment documents and reconciliation act with substitution of currency, price type and payment conditions. 7. Extension Points - Configuration extension: adding attributes (for example, responsible manager, contract category, credit limit) without removing from support; interception of FillCheckProcessing, BeforeSaving, OnCreationOnServer. - Subscriptions to events (BeforeSaving/OnSaving of the document) — integration with external systems (CRM, EDI), synchronization of contract terms. - Additional attributes and information (BSP mechanism) — extendable analytics by contract without changing metadata. - Exchange/conversion rules — exporting contracts to other databases (for example, UT/ZUP or exchange with ESF IS). - Field visibility management through re-definable form modules for industry-specific settings (SRP, joint activity). Reference norms RK 2026 (for sums in documents by contract) Indicator Value 2026 VAT Rate 16% MPR < ``` --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_