---
title: "“CashShift” Document — Technical Description (Accounting for Kazakhstan 3.0.74.2)"
country: KZ
lang: en
author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti)
date: 2026-10-14
canonical: https://buhgpt.kz/suraqtar/dokument-kassovayasmena-tehnicheskoe-opisanie-buhgalteriy-en
source: BuhGPT
---

# “CashShift” Document — Technical Description (Accounting for Kazakhstan 3.0.74.2)

> **TL;DR:** 1. Identification Parameter Value Object type Document (Documents) Object name КассоваяСмена Full name Документ.КассоваяСмена Synonym “Cash shift” Configuration Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) Purpose Registration and control of fiscal cash-register s

---

1. Identification
Parameter
Value
Object type
Document (Documents)
Object name
КассоваяСмена
Full name
Документ.КассоваяСмена
Synonym
“Cash shift”
Configuration
Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2)
Purpose
Registration and control of fiscal cash-register shifts on cash register equipment (CRE/cash registers) in accordance with the legislation of the Republic of Kazakhstan
Where to find it in 1C
“Connected Equipment” section → “Cash Shift.” Navigation link: e1cib/list/Документ.КассоваяСмена
Purpose (detailed). The document records the beginning and end of a fiscal shift on connected CRE, the number of receipts issued and fiscal documents (FDs), as well as data exchange statuses with the fiscal data operator (FDO). It is used daily by cashiers and retail outlet administrators to comply with fiscal accounting requirements. This is a service (registration) document: it reflects the device’s fiscal events but is not an accounting document for a business transaction.
Important: the document does not affect accounting records or cash and inventory balances. Revenue received during the shift is recorded by separate documents (cash register receipts / retail sales report), rather than by the “Cash Shift” itself.
2. Header Attributes and Tabular Sections
Below is the standard set of fiscal-shift document fields for this object type. The specific set of attributes depends on the version and should be verified against the metadata of release 3.0.74.2 (verification in the specific build is required).
2.1. Standard Attributes
Attribute
Type
Purpose
Номер
String
Document number
Дата
Date
Date and time when the shift record was registered
Организация
СправочникСсылка.Организации
Organization that owns the CRE
Ответственный / Автор
СправочникСсылка.Пользователи
User who registered the shift
Комментарий
String
Free-form note
2.2. Fiscal Shift Attributes (Header)
Attribute
Type
Purpose
РабочееМесто / Касса ККМ
CatalogRef
Connected workstation (cash register) on which the shift was opened
Устройство / ФискальныйРегистратор
СправочникСсылка.ПодключаемоеОборудование
Specific CRE on which the shift is being run
НомерСмены
Number
Sequential shift number on the device
Статус
EnumRef
Shift state: “Open” / “Closed”
ДатаОткрытия
Date
Time when the shift was opened
ДатаЗакрытия
Date
Time when the shift was closed (Z report)
КоличествоЧеков
Number
Number of receipts issued during the shift
КоличествоФД
Number
Number of fiscal documents
НомерПервогоФД / НомерПоследнегоФД
Number
Range of fiscal documents for the shift
СуммаНаличными / СуммаБезналичными
Number
Shift totals by payment type (for reconciliation)
СтатусОФД
String / Enum
Result of data exchange with the fiscal data operator
КоличествоНепереданныхДокументов
Number
FDs not transmitted to the FDO (discrepancy control)
2.3. Tabular Sections
As a rule, tabular sections are not provided for the fiscal-shift service document or are for reference purposes only (for example, an FDO data exchange log). The main information is stored in the header attributes. (The availability of tabular sections must be verified in the release metadata.)
3. Forms
Form
Purpose
Document form (ФормаДокумента)
Viewing and editing shift parameters: device, status, receipt/FD counters, and FDO status. Closing an active shift on the connected fiscal device is initiated from the form
List form (ФормаСписка)
Viewing open and closed shifts, filtering by workstation and status, and searching for open shifts to close
Selection form (ФормаВыбора)
Selecting a specific shift from other documents/data processors (for example, to link receipts to a shift)
4. Key Module Procedures
The attached evidence does not include the source code (BSL) of the modules. Below are standard handlers for this object type; the path/line will be available when the source files are provided. Key fact from the evidence: the ОбработкаПроведения handler is absent — the document does not generate register entries.
Object module:
- ОбработкаЗаполнения(ДанныеЗаполнения) — populates attributes upon creation (organization, workstation, shift number).

- ПередЗаписью(Отказ, РежимЗаписи, РежимПроведения) — validates the “Open → Closed” status transition and prevents a shift from being reopened on the device.

- ОбработкаПроверкиЗаполнения(Отказ, ПроверяемыеРеквизиты) — checks that the device, workstation, and opening/closing dates have been completed.

Form module:
- ПриСозданииНаСервере — configures the visibility/availability of elements depending on the shift status.

- ЗакрытьСмену command — calls the connected-equipment driver, generates the Z report, populates the receipt/FD counters and FDO status, and sets the status to “Closed.”

- Filter handlers in the list form — filter by the РабочееМесто and Статус attributes.

Interaction with equipment: shift opening/closing operations are performed through the “Connected Equipment” subsystem (equipment manager and CRE driver), rather than directly in the document module.
5. Posting and Register Entries
The document does not create register entries. According to the evidence, the ОбработкаПроведения handler is absent from the object module.
- It does not generate accounting entries.

- It does not create entries in accumulation registers (cash balances, inventory balances, and settlements) or in information registers used for accounting purposes.

- It does not affect balances in the standard chart of accounts of the Republic of Kazakhstan.

This is consistent with the document’s role: it registers a CRE fiscal event, not a business transaction.
Where Revenue Accounting Is Recorded (for Context)
The “Cash Shift” itself does not generate entries, but related retail documents (cash register receipt / retail sales report) record revenue under the standard chart of accounts of the Republic of Kazakhstan. Indicative entries for retail sales in Kazakhstan (2026):
Transaction
Debit
Credit
Receipt of payment (cashless/acquiring payment to the current account)
1030
1210
Recognition of sales revenue
1210
6010
VAT accrued for payment (rate 16 %)
6010 (or 1210)
3130
Write-off of the cost of goods sold
7010
1330
Settlements with suppliers
3310
1030
VAT example: for revenue of 100 000 ₸ including VAT at a rate of 16 %, the VAT amount = 100 000 × 16 ⁄ 116 ≈ 13 793 ₸ (account 3130), and revenue excluding VAT ≈ 86 207 ₸ (account 6010). The 16 % rate is the standard rate in the Republic of Kazakhstan for 2026 (not 12 %).
These entries are generated not by the “Cash Shift” document, but by retail documents; they are included here to provide a complete picture of the fiscal process.
6. Related Objects and Create Based On
Relationship
Object
Nature of relationship
Workstation / cash register
Cash register/workstation catalog
The shift is linked to a specific cash register
Device
“Connected Equipment” catalog
Physical CRE that generates the Z report
Retail receipts / retail sales report
Retail trade documents
Receipts are linked to the open shift; the shift groups sales for the period
FDO
External fiscal data operator service
Transmission of FDs and monitoring of status and untransmitted documents
Electronic documents
E-invoices (E-invoicing IS), SNT
Issued for sales transactions; they are not generated directly from the “Cash Shift”
Create based on. As a rule, the standard create-based-on scenario is not provided for the fiscal-shift service document: the document is created from the cash-shift management interface and the connected-equipment subsystem. (The set of create-based-on commands must be verified in the release.)
7. Extension Points
- Object module handlers (ПередЗаписью, ОбработкаПроверкиЗаполнения) — adding custom shift-status and integrity checks through a configuration extension.

- Event subscriptions (ПередЗаписью/ПриЗаписи) — integration with external sales accounting or cash-register monitoring systems.

- Form extensions — adding reconciliation attributes (cash/cashless), buttons for retransmitting FDs to the FDO, and additional filters in the list form.

- CRE driver integration — connecting third-party fiscal register models through the “Connected Equipment” subsystem.

- Reporting/monitoring — generating reports on open/closed shifts and discrepancies with the FDO based on the document attributes.

Because the document is not posted, there is no need to extend ОбработкаПроведения; all customization is performed at the level of recording, validation, and forms.

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