---
title: "Receipt of Funds (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/postuplenie-denezhnyh-sredstv-buhgalteriya-dlya-kazahstan-en
source: BuhGPT
---

# Receipt of Funds (Accounting for Kazakhstan 3.0.74.2)

> **TL;DR:** Important Note on Object Type The object is declared in the task as Document Documents.CashReceipt with a navigation link e1cib/list/Document.CashReceipt . However, the attached evidence ( source: kb_unified:acckz30 ) clearly describes a report in the data composition system (

---

Important Note on Object Type

The object is declared in the task as Document Documents.CashReceipt with a navigation link e1cib/list/Document.CashReceipt. However, the attached evidence (source: kb_unified:acckz30) clearly describes a report in the data composition system (DCS): period parameters (StartPeriod, EndPeriod, Frequency), grouping settings, filters, additional fields, detail mode, a single ReportForm, and the purpose "analytical representation of cash flow data." There are no signs of a conducted document (movements in registers, table parts of the primary document, document number/date) in the evidence.

Therefore, the object is described below as a report — in accordance with the actual structure from the evidence. The classifier "Document" and the link e1cib/list/... in the source data are apparently incorrect; the correct navigation is through the "For the Manager" section. This is the only discrepancy that truly requires verification in the specific configuration delivery.

1. Identification

Parameter
Value

Full Name
Report.CashReceipt (in the task — Documents.CashReceipt, see note above)

Type according to evidence
Report (DCS)

Synonym
"Cash Receipt"

Configuration
Accounting for Kazakhstan, ed. 3.0 (3.0.74.2)

Accounting Currency
Tenge (₸)

Subsystem
Accounting / Management Reporting, section "For the Manager"

Mechanism
Data Composition System (DCS)

Purpose. The report generates an analytical representation of the organization's cash receipts for the period. It is used by accountants and financial managers to monitor cash inflows broken down by accounts, counterparties, contracts, and other dimensions. It supports flexible configuration of groupings, filters, and detailing, detail mode down to primary documents, and scheduled distribution.

Where to find in 1C: section "For the Manager" → "Cash Receipt". (The link specified in the task e1cib/list/Document.CashReceipt is applicable only if the object in your delivery is indeed a document; for the report, the command to open the report form from the specified section is used.)

2. Parameters and Settings (Header Attributes and Table Parts)

2.1 Report Parameters (Header)

Name
Type
Mandatory
Purpose

StartPeriod
xs:dateTime
ShowError
Start date of the period. Mandatory for selecting cash movements.

EndPeriod
xs:dateTime
ShowError
End date of the period. Sets the right boundary of the analyzed interval.

Frequency
xs:decimal
ShowError
Interval of breakdown (day, month, quarter, etc.). Controls the detail by time.

OrganizationListRepresentation
xs:string
DontCheck
Text representation of selected organizations for the report header.

AdditionalFieldsPlacement
xs:decimal
DontCheck
Placement of additional analytical fields in the layout (in rows/columns).

DetailMode
xs:boolean
DontCheck
Detailing flag: when enabled, the report is built as a breakdown to another report with special grouping logic.

2.2 Table Parts (Layout Settings)

Grouping

Manages the analytical dimensions of the report (account, counterparty, contract, etc.).

Name
Type
Purpose

Usage
xs:boolean
Flag for including grouping in the report.

Field
xs:string
Identifier of the field from the data composition scheme.

Representation
xs:string
Displayed name of the grouping to the user.

GroupingType
EnumRef.StandardReportDetailingType
Method of grouping (totals/details).

AdditionalFields

List of additional indicators to include in the report.

Name
Type
Purpose

Usage
xs:boolean
Flag for including the field in the output.

Field
xs:string
Identifier of the additional field.

Representation
xs:string
Displayed name of the field.

3. Forms

Form
Purpose

ReportForm (single, ~389 control elements)
Main user form. Contains panels for setting period and organization parameters, grouping settings, filters, sorting, conditional formatting, as well as a table document for displaying results. From it, the formation, breakdown, and printing/saving of the report are initiated.

Separate list/item forms are absent — this is characteristic of a report object, not a document.

4. Key Module Procedures

BSL-evidence is not attached. For the report in DCS in the standard configuration "Accounting for Kazakhstan," standard handlers are expected:

- Report object module → OnResultComposition — programmatic adjustment of the composer before output: substitution of period/organization parameters, addition of calculated fields and formatting.

- Report form → OnCreateOnServer — initialization of default parameters (current period, current organization), setting available groupings and visibility of panels.

- Report form → OnOpen / BeforeFormation — restoration of saved user settings, checking the filling of mandatory parameters (StartPeriod, EndPeriod, Frequency).

- Handler for the "Generate" command — launching the composition, output to a table document.

- Breakdown / BreakdownHandler — processing the transition to DetailMode for detailing down to primary documents (payment documents, bank/cash operations).

- Handlers of the scheduled distribution mechanism (saving and sending the generated report version).

Specific names of procedures and lines require verification according to your delivery module — they are not in the evidence.

5. Data Sources (instead of conducting and movements)

As a report, the object does not perform conducting and does not generate movements/entries — this is a fundamental difference from a document. It only reads data from registers.

The source is the registers of cash accounting of the standard chart of accounts of the RK. Inflow is formed by debiting cash accounts:

- 1010 — cash in hand;

- 1030 — cash in current bank accounts.

Typical correspondences that enter the report as "receipt":

Operation
Entry

Payment from the customer to the current account
Dr 1030 — Cr 1210 (short-term receivables from customers)

Payment from the customer to cash
Dr 1010 — Cr 1210

Return from the supplier / other inflow
Dr 1030 (1010) — Cr 3310 and others.

The report aggregates these turnovers by selected groupings (account, counterparty, contract, cash flow article) for the period StartPeriod … EndPeriod with a step of Frequency. All amounts are in tenge (₸).

Note on Kazakhstan-2026: the cash flow report does not perform tax calculations. Relevant parameters for configuration 3.0.74.2 (VAT rate 16%, MRP 4,325 ₸, MSP 85,000 ₸, basic deduction for PIT 30 MRP/month and no more than 360 MRP/year, PIT 10% up to 8,500 MRP annual income and 15% above, OPE 10% with a base cap of 50 MSP, OPE rate 3.5%, VOSMS 2%, OSMS 3%, SO 5%, social tax 6%) are applied in source documents (payments, salaries, sales with VAT on account 3130, income on 6010, cost of goods sold on 7010), while this report includes already formed cash turnovers.

6. Related Objects and Transitions

- Breakdown — from the report result, it is possible to transition to primary documents that underlie the receipts: bank statements/payment receipts to the account (turnovers on 1030), cash orders (turnovers on 1010).

- Reference dimensions: "Organizations," "Counterparties," "Counterparty Contracts," "Bank Accounts," "Cash Flow Articles" — used as fields for groupings and filters.

- Electronic documents of the RK (ESF/IS ESF, STS) — are related not to the report, but to the documents of sale/receipt that form the debt closed by these funds; they do not directly enter the cash flow report.

- "Input based on" is not applied for the report (this is a document function).

7. Extension Points

- User settings DCS — adding/changing groupings (Grouping) and additional fields (AdditionalFields), filters, sorting, and conditional formatting without changing the configuration; saving report variants.

- Configuration extension — overriding the handler OnResultComposition and form procedures (OnCreateOnServer, BeforeFormation) to add custom fields, parameters, or additional filters.

- Data composition scheme (DCS) — adding calculated fields, data sets, and resources; expanding the list of available dimensions.

- Distribution mechanism — setting up automatic distribution of the generated version on a schedule.

- Breakdown (DetailMode) — connecting custom detailing logic to other reports/documents.

It is not allowed to extend the object as a document (adding movements in registers, conducting, input based on) — the report does not have these mechanisms.

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