Production Calendars — Technical Description of the Object (Accounting for Kazakhstan 3.0.74.2)

Important Clarification on Object Type

The object is declared in the accompanying metadata as a Document (Documents.ProductionCalendars, navigation link e1cib/list/Document.ProductionCalendars). However, the attached evidence and actual implementation in standard 1C configurations (including "Accounting for Kazakhstan") clearly describe a directory:

• reference attribute type — DirectoryReference.ProductionCalendars;
• there is an element form and a list form (not a document form);
• there are no document attributes (Date/Number), no posting;
• data is stored not in the document, but in the related information register.

Furthermore, the object is described as a directory — this corresponds to the evidence and actual metadata. The correct navigation link is: e1cib/list/Directory.ProductionCalendars. If in your delivery the object is indeed reclassified as a "Document" — this is a version-specific distinction, requiring verification in the configurator of the specific build.

1. Identification

Purpose. The directory maintains information about working, non-working, and holiday days, taking into account the transfer of non-working days according to the legislation of the RK. Calendars are used in calculating working time norms, planning work, and calculating wages (accruals based on salary/rate, average payment, vacation pay, sick leave — all rely on the norm of days/hours from the calendar). It changes rarely: usually once a year when a new classifier is released or when transfers are established by acts of the RK government.

Note on the applicability of tax numerical norms. The production calendar does not participate in tax accounting and does not operate with VAT rates (in RK for 2026 — 16%), MRP, or deductions. It provides the working time norm to the payroll subsystem, where the 2026 rates are already applied (individual income tax, pension contributions, social health insurance, etc. — see section 5). Therefore, VAT rates/accounting plan accounts are not applicable to the directory itself.

2. Attributes and Table Parts

2.1 Header Attributes (directory attributes)

2.2 Table Parts

Table parts are absent. This is characteristic of this object: the list of specific days with their types is stored not in the directory itself, but in the subordinate information register.

Information Register ProductionCalendarData (storage of days):

Thus, the directory sets the "header" of the calendar, while the register provides its content by days. The element form visualizes these records in the form of a calendar grid.

3. Forms

4. Key Procedures of Modules

BSL code in evidence is not attached — exact names of procedures and their lines in the modules require verification in the configurator of build 3.0.74.2. Below are the typical responsibilities of handlers for this type of object and the listed commands.

Module of form ElementForm:

• OnCreateOnServer — building the calendar grid from records of the register ProductionCalendarData for the selected year, initializing conditional formatting of days (non-working/holidays).
• ChangeDay (command) — changing the type of day for the selected date (working ↔ non-working ↔ holiday) with subsequent recording in the information register.
• TransferDay (command) — arranging the transfer: linking the original date and the transfer date (TransferDate), correctly changing the types for both dates.
• FillByDefault (command) — filling the calendar with standard non-working days (Sat/Sun) and known holiday dates of the RK for the year, if BaseCalendar is present — inheriting its data.
• Print (command) — generating a printed form of the calendar for the year.
• BeforeWrite / AfterWrite — synchronizing the visual grid with the set of records in the information register (recording/deleting days).

Module of form ListForm:

• SelectFromClassifier (command) — calling the loading of calendars from the built-in classifier; creating directory elements and filling the register of days for the selected year.

Module of manager / directory object:

• ProcessFilling — filling attributes when creating a new calendar.
• Manager methods for reading the calendar (getting the type of day by date, calculating the norm of working days/hours for the period) — used by the payroll subsystem and work schedules.

5. Posting and Movements

The directory is not posted — the concepts of "posting", "movements in accumulation registers" and "accounting entries" are not applicable to it. Accordingly, the directory element does not generate records in accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) and does not participate directly in VAT (16% in RK for 2026), nor in ESF/SNT.

What happens instead of posting:

1. When editing the calendar, records are created/changed in the information register ProductionCalendarData (by days of the year). This is the only "result of the object's work" at the data level.

How the calendar is used further (downstream). The working time norm calculated by the calendar goes to the payroll calculation subsystem and affects the amounts of accruals; tax rules of the RK for 2026 are already applied to these amounts (with MRP = 4,325 ₸, MZP = 85,000 ₸):

• Individual Income Tax — 10% up to 8,500 MRP of annual income and 15% above; basic deduction 30 MRP/month = 129,750 ₸ (not more than 360 MRP/year);
• Pension Contributions 10% (base ceiling 50 MZP = 4,250,000 ₸/month), Additional Pension Contributions 3.5 %;
• Social Health Insurance 2%, Mandatory Social Health Insurance 3%, Social Tax 5%, social tax 6%.

These amounts are reflected in entries already in payroll calculation documents (according to the standard accounting plan of RK), and not in the production calendar. The calendar itself is a source of norm-days/hours for the basis of accruals.

6. Related Objects and Input Based On

Related objects:

• Information Register ProductionCalendarData — subordinate storage of days (see section 2.2).
• The directory itself (recursive link) through the attribute BaseCalendar — local calendars refer to the national one.
• Classifier of production calendars — source of data for the command SelectFromClassifier.
• Employee work schedules and payroll calculation documents — consumers of the working time norm from the calendar.

Input based on: for production calendars, the typical mechanism "Input Based On" is not provided (the object is a directory, edited directly or loaded from the classifier).

7. Extension Points

• Configuration extension — overriding/adding command handlers of the form (FillByDefault, TransferDay) to account for additional regional/corporate transfers.
• Subscriptions to events of the directory record and register ProductionCalendarData — for integration with external HR systems or logging changes to the calendar.
• Additional handlers / external processing (BSP) — mass loading/exporting of calendars, reconciliation with the production calendar from an external source.
• Attribute BaseCalendar as a standard customization point — building the hierarchy "national → industry → local" without modifying metadata.
• Printed form (command Print) — replacement/addition of the layout through the BSP layout mechanism.