---
title: "Document \"Invoice to Customer\" - Technical Description (Accounting for Kazakhstan 3.0.74.2)"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-09-07
canonical: https://buhgpt.kz/suraqtar/dokument-schetnaoplatupokupatelyu-tehnicheskoe-opisanie-b-en
source: BuhGPT
---

# Document "Invoice to Customer" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

> **TL;DR:** 1. Identification Parameter Value Object Type Document (Documents) Name InvoiceToCustomer Full Path Document.InvoiceToCustomer Synonym “Invoice to Customer” Configuration Accounting for Kazakhstan, ed. 3.0 (3.0.74.2) Interface Section “Sales” → “Invoices to Customers” Navigati

---

1. Identification

Parameter
Value

Object Type
Document (Documents)

Name
InvoiceToCustomer

Full Path
Document.InvoiceToCustomer

Synonym
“Invoice to Customer”

Configuration
Accounting for Kazakhstan, ed. 3.0 (3.0.74.2)

Interface Section
“Sales” → “Invoices to Customers”

Navigation Link
e1cib/list/Document.InvoiceToCustomer

Purpose. The document formalizes a preliminary commercial offer from the supplier (organization) to the buyer (counterparty) for the sale of goods, provision of services, or transfer of fixed assets. It serves as a commercial/financial document rather than an accounting one: it does not generate accounting entries, but serves as a basis for registering future payments, tracking payment and shipment statuses, printing the invoice form, and controlling the buyer's accounts receivable (account 1210 — short-term accounts receivable from customers and clients).

All monetary indicators are maintained in tenge (₸); when working with a foreign currency contract, the conversion is performed at the exchange rate on the document date.

2. Attributes of Header and Table Parts

2.1 Header Attributes

Attribute
Purpose
Mandatory

Organization
Supplier (our organization) on behalf of which the invoice is issued
Mandatory

Counterparty
Buyer to whom the invoice is issued
Mandatory

StructuralUnit
Warehouse / department from which the shipment is planned
Mandatory

Contract
Contract with the buyer (type “With Buyer”); defines the currency of settlements and type of prices
Filled in according to the counterparty

Date, Number
Document numbering details
Automatically filled

Currency (document/settlements)
Currency of the invoice; by default — tenge (₸)
From the contract

PriceType
Type of prices for the nomenclature for auto-filling in the table part
From the contract

PaymentStatus
Not paid / Partially paid / Paid
Manually/massively controlled

ShipmentStatus
Not shipped / Partially shipped / Shipped
Manually/massively controlled

PayBy
Payment deadline for the invoice
Optional

VATIncluded / Excluded (VAT accounting flag)
Determines whether VAT is included in the price or added on top. The VAT rate in the RK for 2026 is 16%
According to accounting policy

Comment
Arbitrary comment
Optional

Responsible
Author user
Automatically

2.2 Table Part “Products”

Assortment of product items in the invoice.

Column
Purpose
Mandatory

Nomenclature
Product from the nomenclature directory
Mandatory

Quantity
Quantity for sale
Mandatory

Amount
Line amount
Mandatory

Price
Price per unit (from price type)
Calculated

VATRate / VATAmount
Rate (16%) and tax amount for the line
Calculated

UnitOfMeasurement
Unit of measurement for the nomenclature
From the nomenclature

2.3 Table Part “Services”

List of services provided to the buyer.

Column
Purpose
Mandatory

Nomenclature
Service from the nomenclature directory
Mandatory

Quantity
Volume of service
Mandatory

Amount
Line amount
Mandatory

Price, VATRate, VATAmount
Price, rate (16%) and VAT amount
Calculated

2.4 Table Part “Fixed Assets”

Transfer of fixed assets.

Column
Purpose
Mandatory

FixedAsset
Object of fixed assets
Mandatory

Amount
Line amount
Mandatory

VATRate, VATAmount
Rate (16%) and VAT amount
Calculated

Example of VAT calculation: with a product amount excluding tax of 100,000 ₸ and the VAT rate in the RK of 16%, the VAT amount = 16,000 ₸, total amount including VAT = 116,000 ₸ (account for VAT payable — 3130).

3. Forms

Form
Purpose

DocumentForm
Main form for creating and editing the invoice: header, table parts “Products”/“Services”/“Fixed Assets”, status management, selection and printing commands

ListForm
List of invoices to customers with filtering, commands for bulk changing payment and shipment statuses, input based on

SelectForm
Selecting an invoice from other objects (for example, when entering payment documents based on)

Printed Forms
Form “Invoice to Customer” for delivery to the customer (print/PDF/send to e-mail)

4. Key Procedures of Modules

The document does not have movement registers, so the main logic is concentrated in the form modules and the object module (processing of attributes, statuses, selection, and printing). Below are the handlers confirmed by scenarios (evidence) and standard handlers of this type of object.

From evidence:

- ListForm → ChangeStatus (bulk change of payment/shipment statuses). When no selection is made (DocumentList.Count() = 0), a message is displayed: “The command cannot be executed for the specified object” (texts are provided according to release 3.0.68.1).

- Loading products from an Excel file — command of the document form that adds rows to the table part “Products” from an external table.

- Adding a product by barcode — handler for reading a barcode from a scanner with selection of nomenclature and adding a row.

- Price and currency recalculation — procedure for recalculating rows when changing the exchange rate, price type, or contract (scenario 3.2).

Standard handlers (general logic of the document type):

- OnChange of attributes Counterparty / Contract — filling in currency, price type, settlement accounts.

- Nomenclature.OnChange (in table parts) — auto-filling price by price type, unit of measurement, VAT rate.

- Quantity.OnChange / Price.OnChange / Amount.OnChange — mutual recalculation “quantity × price = amount” and VAT calculation (16%).

- CheckFillingProcessing (object module) — control of mandatory attributes: Organization, Counterparty, StructuralUnit, as well as mandatory columns of tables. If a field is not filled, posting is blocked with the error “Field … is not filled”.

- Commands for printing the invoice form.

Requires verification: exact names of procedures and modules may differ between sub-releases 3.0.6x/3.0.7x — the names of the form handlers correspond to the standard implementation of branch 3.0.

5. Posting and Movements

The document does not generate accounting entries and does not make movements in registers — there are no records in the metadata registers (register_records is empty). Posting marks the document as valid and updates statuses, but does not affect accounting and tax records.

Financial consequences arise from documents entered based on the invoice. Standard invoices in the RK involved in these documents:

Business Operation
Document-Basis
Standard Entry (RK)

Receipt of payment from the buyer (cashless)
Receipt to the settlement account
Dr 1030 — Cr 1210

Receipt of payment from the buyer (cash)
Cash receipt order
Dr 1010 — Cr 1210

Sale of goods (income)
Sale of goods and services
Dr 1210 — Cr 6010; VAT Dr 1210 — Cr 3130

Write-off of cost of goods sold
Sale of goods and services
Dr 7010 — Cr 1330

The VAT rate upon sale is 16%, the tax is reflected in account 3130 (VAT payable). Settlements with the buyer are conducted on account 1210.

Electronic support for sales: based on subsequent sales documents, ESF (electronic invoice in the ESF IS) and, when moving goods, SNT (accompanying invoice for goods) are generated. The invoice for payment does not generate electronic documents.

6. Related Objects and Input Based On

Filling in the invoice uses:

- Directories Counterparties, Organizations, Contracts, Nomenclature, StructuralUnits (Warehouses), FixedAssets;

- Register of price information for nomenclature (according to the specified price type).

Based on the invoice to the customer, the following are usually entered:

- Receipt to the settlement account — registration of cashless payment (Dr 1030 — Cr 1210);

- Cash receipt order — registration of cash payment (Dr 1010 — Cr 1210);

- Sale of goods and services — shipment with recognition of income (6010), VAT (3130), cost of goods sold (7010/1330);

- Invoice (ESF) — in the sales chain.

The invoice can also serve as a receiving document when entering based on a commercial proposal/order from the buyer (if available in the configuration).

7. Extension Points

- Configuration extension (adopt/borrowing forms): adding header attributes and columns of table parts, custom commands on DocumentForm/ListForm, handlers OnCreateOnServer, BeforeSaving.

- Event subscriptions: BeforeSaving/OnSaving/CheckFillingProcessing of the document — for additional control (credit limit, checking debt on account 1210, contract mandatory).

- Additional attributes and information (BSP mechanism “Properties”) — without changing metadata.

- Additional reports and processing — external printing of the form, alternative loading from Excel.

- Extension of bulk status commands — refinement of the handler ChangeStatus of the list form (considering the check DocumentList.Count() = 0).

- Integration with ESF/SNT — through sales documents entered based on the invoice.

---
_BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_