Document "Business Trips of Organizations" - Technical Description (Accounting for Kazakhstan 3.0.74.2)

1. Identification of the Object

Purpose. The document is intended for registering and accounting for business trips of the organization's employees. It is used by HR specialists and accountants to record the assignment of employees to business trips: specifying periods, purposes, and sources of funding. The document has a informational and HR nature and serves as the basis for subsequent accounting of travel expenses and the calculation of daily allowances by other documents. It is used regularly — for each assignment of employees on business trips, both within Kazakhstan and abroad.

Where to find in 1C: section “Personnel Management” → “Business Trips of the Organization” (document journal for personnel accounting in the “Payroll and Personnel” section).

2. Header Attributes and Table Parts

Header Attributes

Additionally, the header typically includes attributes for the purpose of the business trip and the source of funding (used in the scenario of group changes of business trips and when filling out the printed form of the certificate).

Table Part “EmployeesOfTheOrganization”

Contains a list of employees being sent on business trips with individual periods.

If any of the mandatory fields are not filled in — 1C will not process the document and will issue an error “Field … is not filled in”.

3. Forms

Printed form: “Business Trip Certificate” — generated based on the document data (scenario 3.4).

4. Key Module Procedures

The attached evidence does not include BSL export with the binding path:string, therefore below is the typical set of handlers for documents of this type in BK 3.0. The presence of specific procedures should be verified with the object modules in the configurator.

Object Module:

• FillProcessing — filling in attributes when entering based on / creating.
• FillCheckProcessing — control of mandatory fields (Organization; for table part rows — Employee, StartDate, EndDate). This mechanism issues the error “Field … is not filled in”.
• ConductProcessing — absent (see section 5).

Document Form Module:

• Mass filling command for the employee list (scenario 3.2) — selection of all employees of the department or by list.
• Handlers OnChangeStartDate / OnChangeEndDate of the table part — control of period correctness.
• Command to print the business trip certificate.

General Print Module / Document Manager:

• Procedure for generating the printed form “Business Trip Certificate”.
• Handler for group changes of attributes (scenario 3.5), including changing the source of funding.

Requires verification (version-specific): exact list of procedures and their signatures in 3.0.74.2 — see the object/form module in the configurator.

5. Conducting and Movements

The document is not a conducting document. The object module lacks the handler ConductProcessing — the document does not generate movements in accounting and accumulation registers and does not create accounting entries.

The document has an informational and accounting nature and serves as a basis for subsequent documents that reflect expenses in accounting. Further movement of money and recognition of business trip expenses is documented separately (advance report, advance payment, calculation of daily allowances), where entries are formed. For the context of the RK, the corresponding amounts are reflected according to the standard chart of accounts of Kazakhstan, for example:

VAT rate when reflecting expenses on confirming documents — 16% (RK norm 2026). Electronic confirmation of expenses — through ESF (ESF IS), when moving TMC — SNT. Accounting currency — tenge (₸).

The conducting of the document “BusinessTripsOrganizations” merely records the fact of sending on a business trip and makes the document available as a basis; it does not generate movements.

6. Related Objects and Input Based On

The document serves as a basis for:

• documents for accounting business trip expenses and calculating daily allowances (advance report and related operations);
• printed form “Business Trip Certificate”.

Uses data from objects:

• Directory “Organizations” (attribute Organization);
• Directory “Employees” / “Individuals” (table part “EmployeesOfTheOrganization”);
• Directory “Departments of Organizations” — when mass selecting employees of the department (scenario 3.2);
• elements of sources of funding — during group changes (scenario 3.5).

Accruals related to the business trip (for reference, RK norms 2026). When calculating daily allowances and taxing business trip payments in supporting documents, the current rates of Kazakhstan are applied:

• MPR = 4,325 ₸, MZP = 85,000 ₸;
• basic tax deduction for PIT = 30 MPR per month (not more than 360 MPR per year);
• PIT 10% up to 8,500 MPR annual income and 15% above;
• OPV 10% (base ceiling — 50 MZP), OPVR 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%.

Excess daily allowances that exceed the established non-taxable limit are included in the employee's income and taxed at the specified rates in the accrual documents.

7. Extension Points

For modifications without removing from support, use configuration extensions:

• Adding attributes/columns — new header attributes or columns of the table part “EmployeesOfTheOrganization” (for example, country of business trip, foreign business trip indicator) through an extension.
• Form Handlers — subscriptions/overriding OnCreateOnServer, BeforeSaving, command handlers for mass filling of the employee list.
• Fill Check — extension FillCheckProcessing for additional control (for example, overlapping periods of business trips for one employee).
• Printed Forms — adding custom layouts through the “Additional Reports and Processes” mechanism or overriding the printing of the business trip certificate.
• Input Based On — extension of the composition of supporting documents generated from the business trip.
• Event Subscriptions — reaction to the recording/conducting of the document for your own integration (HR EDI, notifications).

When adding your own conducting logic, remember: the typical document does not generate movements — introducing ConductProcessing in the extension should only be done with a conscious modification of the accounting scheme.