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

1. Identification

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

2.2. Fiscal Shift Attributes (Header)

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

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

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

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.