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

1. Identification

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

2.2 Table Part “Products”

Assortment of product items in the invoice.

2.3 Table Part “Services”

List of services provided to the buyer.

2.4 Table Part “Fixed Assets”

Transfer of fixed assets.

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

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:

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.