Contracts with Counterparties (Documents.ContractsWithCounterparties)

1. Identification

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

2.2 Table Parts

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

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%:

Example: goods for 1,000,000 ₸ without VAT → VAT = 160,000 ₸ (16%), receivable on 1210 = 1,160,000 ₸.

Receipt from supplier (ContractType = With supplier):

Payment / receipt of money:

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)