1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | ETD |
| Full Name | Document.ETD / Documents.ETD |
| Synonym | Electronic Employment Contract |
| Configuration | Accounting for Kazakhstan, 3.0.74.2 |
| Interface Section | Human Resources → Electronic Employment Contract |
| Navigation Link | e1cib/list/Document.ETD |
Purpose. The document is intended for maintaining employment contracts with employees in electronic form with integration into the Unified System for Accounting Employment Contracts (USAEC) of the Republic of Kazakhstan. It is used by HR specialists for hiring, changing employment conditions (additional agreements), terminating contracts, recording social leaves, and reinstatements. It supports electronic signatures, automatic data export to USAEC, and status synchronization with the state system.
Lifecycle: formation → sending to USAEC → signing → updating/synchronizing status.
This is a HR document. It does not participate in the calculation of taxes and contributions and does not store monetary rates. The rates of the RK 2026 (VAT 16%, PIT 10/15%, EPP 10%, EPPF 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6%, PIT deduction 30 MRP, MRP 4,325 ₸, MZP 85,000 ₸) are applied in payroll calculation documents and tax reporting, not here.
2. Attributes of Header and Table Parts
Mandatory Header Attributes
| Attribute | Type (typical) | Purpose |
|---|---|---|
Organization |
ReferenceLink.Organizations | The employer organization on behalf of which the contract is concluded |
Employee |
ReferenceLink.Employees / Individuals | The employee — the party to the employment contract |
DateOfConclusion |
Date | The date of signing the employment contract / additional agreement |
DateOfStart |
Date | The date of commencement of employment relations |
If any of the listed fields are not filled, the document is not processed/sent — an error "Field ... is not filled" is issued.
Other Header Attributes (by form logic)
| Attribute | Purpose |
|---|---|
DateOfEnd |
The end date of the fixed-term contract. Mandatory for contract types "For a fixed term of at least one year" and "For a fixed term of less than one year (for small business entities)" |
Duration / type of duration |
Determines the requirements for filling in DateOfEnd |
EmployeeConsent |
Flag/indicator of the employee's consent to the processing of personal data (checks the value "1") |
| Status of USAEC, registration number | Stores the document's status in USAEC after synchronization |
Table Part "AttachedFilesETD"
| Column | Mandatory | Purpose |
|---|---|---|
DocumentType |
Yes | Classification of the attached file |
FileLink |
Yes (when sending) | Link to the document file; must be filled in each row when sending to USAEC |
3. Forms
| Form | Purpose |
|---|---|
DocumentForm |
Main form of ETD: entering attributes, working with attached files, sending to USAEC, signing, checking completeness when sending ETD and additional agreements |
ExtensionForm |
Form for extending the contract duration; checks the correctness of extension dates |
| List Form | Selection and navigation through documents (e1cib/list/Document.ETD) |
4. Key Module Procedures
From evidence (release 3.0.68.1; behavior preserved in 3.0.74.2):
| Procedure | Form | What it does |
|---|---|---|
CheckFillingWhenSendingETD |
DocumentForm |
Controls filling before sending to USAEC: presence of DateOfEnd for fixed-term contracts; filling of the FileLink column in each row of attached files |
CheckFillingWhenSendingAdditionalAgreement |
DocumentForm |
Checks that DateOfConclusion of the additional agreement is not later than the current day (StartOfDay(Object.DateOfConclusion) > StartOfDay(SessionDate)) |
CheckFillingProfessionalPayment |
DocumentForm |
Checks the employee's consent to the processing of personal data (Object.EmployeeConsent <> "1") |
CheckFillingAttributes |
ExtensionForm |
Controls that the end date of the extension is not earlier than the start date of the extension |
Diagnostics: Typical Errors
| 1C Message | Condition in Code |
|---|---|
| For the duration "For a fixed term..." the field must be filled | NOT ValueFilled(Object.DateOfEnd) |
| The end date of the extension must not be earlier than the start date %1 | DateOfEndExtension <> Date('00010101') AND DateOfEndExtension < DateOfStartExtension |
| The "File Link" column is not filled in row %1 | NOT ValueFilled(AttachedFile.FileLink) |
| The date of conclusion of the additional agreement must not be later than the current day | StartOfDay(Object.DateOfConclusion) > StartOfDay(SessionDate) |
| The field "Employee's consent to the processing of personal data" is not filled | Object.EmployeeConsent <> "1" |
Typical document handlers (common for the object type): FillingHandler, FillingCheckHandler, BeforeSaving, OnServerCreation/OnOpening form, handlers for sending and synchronizing with USAEC (web service/HTTP exchange).
5. Processing and Movements
The document does not generate accounting entries and does not make movements in registers. This is confirmed by evidence: register_records is empty. ETD is an HR document used for accounting employment contracts and interacting with USAEC.
Consequences:
- No movements in the RK chart of accounts (in particular, the document does not affect accounts 1210, 1030, 1330, 3310, 3130, 6010, 7010) and in accumulation/information registers of accounting.
- HR impacts (hiring, transfer, dismissal) on the calculation of salary, PIT, EPP, EPPF, VOSMS, OSMS, CO, and social tax are implemented by separate HR and payroll documents of the configuration, not ETD.
- "Processing" here essentially comes down to checking completeness and exchanging with USAEC (sending, signing, synchronizing status), not to generating movements.
6. Related Objects and Input Based On
Usage Scenarios (evidence):
| No | Scenario | When Applied |
|---|---|---|
| 3.1 | Creating a new ETD when hiring | Formalizing a new employee or concluding a contract for a new position |
| 3.2 | Creating an additional agreement to ETD | Changing employment conditions: transfer, salary change, work schedule |
| 3.3 | Registering social leave | Sick leave, maternity leave, and other social leaves |
| 3.4 | Terminating the employment contract | Dismissing an employee |
| 3.5 | Reinstatement | Reinstatement by court/state authority decision |
| 3.6 | Synchronizing with USAEC and updating status | Periodic status check in the state system |
| 3.7 | Refilling ETD with data from USAEC | Data in USAEC has been externally modified |
Related Objects:
- Directories:
Organizations,Employees/Individuals, positions/divisions (staffing schedule). - HR documents of the configuration (hiring, HR transfer, dismissal) with which ETD logically synchronizes.
- Attached files (file handling subsystem) and electronic signature mechanism.
- External system USAEC (web service of the government portal) — data receiver/source.
Input Based On: The typical source for creating ETD is HR documents (hiring/transfer); additional agreements and extensions are entered based on previously registered ETD.
7. Extension Points
- Additional filling checks — extension of
CheckFillingWhenSendingETD/CheckFillingWhenSendingAdditionalAgreementfor custom mandatory fields and corporate rules. - Exchange with USAEC — interception/complementing of sending and status synchronization procedures (message formats, logging, error handling of the web service).
- Attached files — extension of the composition of document types and validation rules
DocumentType/FileLink. - Forms (
DocumentForm,ExtensionForm) — adding attributes, commands, and elements through configuration extension. - Working with electronic signatures — integration of third-party cryptographic providers during signing.
When making modifications, use configuration extensions (borrowing forms and modules) to maintain support for standard updates.