Since 12 March 2026, employers in Kazakhstan can be fined for failing to register employment contracts in the unified employment contract system (ESUTD), for registering them late, or for submitting incomplete or inaccurate data. For a small business the first violation costs 60 MCI, or 259,500 tenge; for a large company it is 150 MCI, or 648,750 tenge. A new contract must be registered within five working days of signing, and any amendment within 15 calendar days. On top of that, updated rules in force since 17 May require an employee's consent to the employer receiving their employment history to be given in the employer's digital HR system and signed with an electronic digital signature (EDS). Against this backdrop, electronic HR document management has stopped being a "nice digital upgrade" and become the practical way to avoid fines and the paper chase between HR, accounting and the new hire.
At West Star Ltd we integrate 1C with HR platforms, government portals and messengers, and almost every project starts from the same picture. The contract is signed on paper, the scan sits in someone's inbox, the data is typed into 1C by hand, and the record reaches ESUTD "when someone gets around to it". Each link works on its own, but together they leave gaps, and those gaps are where violations come from. Below is how we assemble the process into a single chain in which a document is created once, signed once and then flows to every system automatically.
Why electronic HR document management is no longer optional
The Labour Code of Kazakhstan has long allowed employment contracts, amendments and supplements to be concluded as electronic documents certified with an EDS. Paper is not banned, but the paper route has become more expensive: every signed copy still has to be pushed through ESUTD separately, and the employer now pays for every miss.
A detail that is often overlooked: the penalty is not only for "forgot to register". Under Article 98 of the Code of Administrative Offences, as of March 2026 incomplete submissions and incorrect or inaccurate data are punishable too. A typo in an individual identification number, the wrong job title, or a start date that does not match the hiring order are all formally violations. A repeat violation within a year costs more: 80 MCI for a small business and 200 MCI for a large one.
The Ministry of Labour stresses that there are no automatic fines for late registration: sanctions can only follow an official inspection, and the first step is usually an order to fix the violation. Still, relying on an inspector's leniency is a poor strategy when a company handles dozens of hires, transfers and dismissals a month. If staff arrive seasonally, as in retail or logistics, manual record-keeping breaks down exactly in the peak weeks.
There is a less obvious reason as well. Electronic document management in HR is about more than contracts. Hiring, transfer and leave orders, personal data consent, acknowledgement of internal rules and job descriptions, occupational safety briefings: on paper these documents get lost, are kept in incomplete sets and surface at the worst possible moment, during an inspection or a labour dispute. An electronic archive with digital signatures and timestamps answers "who signed what, and when" in a minute.
How the process works: from offer to ESUTD without paper
In our experience, electronic HR document management that actually works rests on one principle: every document has a single source of data. Most often that is 1C:Salary and HR Management or the HR module of 1C:Accounting, and everything else, whether an employee portal, a messenger or ESUTD, receives data from there rather than retyping it.
Onboarding a new employee
A typical scenario looks like this. The HR officer creates a candidate card in 1C and generates a package: the employment contract, the hiring order, the personal data consent and the acknowledgement sheets. The candidate receives a link, in a browser or in a Telegram bot, and signs the package with their own EDS via NCALayer or the eGov mobile app. We have already covered in detail how to automate signing documents with an EDS; HR uses the same mechanics, just with a different set of documents.
Then the manager signs, and the system immediately does three things: it stores the signed files in the electronic archive linked to the employee card, switches the status in 1C to "hired", and creates a task to send the data to ESUTD. One of our clients in the service sector, which hires 30 to 40 people per season, used to spend about an hour of HR time on each hire, plus a trip to the office for the employee. After moving to the electronic chain, the HR side shrank to about ten minutes: check the data and press "send".
Connecting 1C and ESUTD
Contract data is submitted to ESUTD through the employer's account on the unified digital employment platform "Electronic Labour Exchange", signed with an EDS. Standard 1C configurations for Kazakhstan can send electronic employment contracts directly, and for a small company that is often enough. Things get complicated when HR data lives in several places: some employees are kept in one database, some in another, and new contracts are created in a separate HR platform.
In that case we build a 1C integration with an intermediate layer that validates the data before it is sent. Before submission to ESUTD it checks the format of the identification number, whether the job title matches the staffing table, the start date and the contract term. The system also watches deadlines: on the fifth working day the person responsible for an unsent contract gets a reminder, and the manager sees a summary of overdue items.
Hiring is the most visible part, but not the riskiest. In practice the most frequent errors come with changes: an employee was moved to another position, given a raise or switched to a different schedule, yet the supplementary agreement was signed "later" or never sent to ESUTD at all. Fifteen calendar days sounds generous until the changes land at year end, when HR is simultaneously closing out leave, bonuses and next year's staffing table. So our chain covers not just the contract but every document that changes its terms: the transfer order is generated in 1C, the employee signs the supplementary agreement on their phone, and the data goes to ESUTD along the same route as at hiring.
Dismissal follows the same logic. The order, the final settlement, the termination record in ESUTD and handing documents to the employee should be tied to a single task, not held in the HR officer's head.
HR signatures are a separate story. The employer signs submissions with the legal entity's EDS, and some companies still pass a single key around on a USB stick. We recommend deciding up front who signs which HR documents with which keys and making the signature part of the EDS and NCALayer infrastructure, so it becomes a step in the process rather than a reason to call around asking "where is the stick?". We described the other HR processes around 1C, such as recruiting, onboarding and records, in our article on automating hiring and personnel management.
Limitations and risks
Electronic HR document management saves time, but it has honest limits worth knowing before you start.
- Not every employee has an EDS. A courier, a seasonal worker or a foreign specialist may not have a valid key. You need a fallback paper route and a clear rule for who handles such cases and how.
- Keys expire. An EDS has a limited validity period, and a manager's expired key on a day of mass hiring stops the whole process. Key expiry dates should be tracked just like contract deadlines.
- Personal data. An HR archive holds identification numbers, addresses, family status and medical certificates. Storage must meet the requirements of the personal data law, and access must be split by role.
- Integration will not fix bad data. If the staffing table in 1C is out of date or job titles are spelled inconsistently, automatic submission just spreads the errors faster. You have to start by cleaning up the reference data.
- The rules keep changing. In 2026 alone the ESUTD procedure was updated several times, with some provisions taking effect in stages. An integration needs ongoing maintenance, not "build it and forget it".
- An electronic contract does not replace HR expertise. The system will fill in a template, but it will not tell you whether the right type of contract was chosen or whether a civil-law contract looks like an employment contract in substance. That is still work for a lawyer or an experienced HR officer.
What specialists, managers and owners should do
HR specialists should start with an inventory: which documents are produced at hiring, transfer and dismissal, where each is created and who signs it. This stage usually reveals that half the documents are duplicated and a third of the data is typed into two or three systems by hand: the first candidates for automation.
Managers need to see the process as a whole, not in pieces. A useful question for the team: how many days on average pass between signing a contract and the record appearing in ESUTD, and who knows that number? If there is no answer, the risk of a fine already exists. A good system shows that figure on one screen.
Owners should run simple economics. One fine is 259,500 tenge for a small business and 346,000 tenge for a medium one for a first violation. Setting up an electronic chain for a company with 50 to 200 employees usually costs about as much as one or two such fines, and the hours saved in HR and accounting keep paying it back every month. If you want an estimate for your own processes, just get in touch: we will review your current setup and show where it breaks.
The value of electronic HR document management is not that it removes paper, but that it removes the pauses: between the signature and the record, between the order and the report, between "done" and "registered". In 2026, those pauses are exactly where the fines hide.
FAQ
Is it mandatory to sign employment contracts electronically?
No. An employment contract can be made on paper or as an electronic document signed with both parties' EDS. What is mandatory is registration: data on every contract must be entered in ESUTD, a new contract within five working days of signing and amendments within 15 calendar days. The electronic form simply makes that registration easier and faster.
What is the fine for not registering a contract in ESUTD in 2026?
Since 12 March 2026, under Article 98 of the Code of Administrative Offences, a first violation is fined at 30 MCI for officials, 60 MCI for small businesses and non-profits, 80 MCI for medium and 150 MCI for large businesses. With the MCI at 4,325 tenge, that is 129,750 to 648,750 tenge. Submitting incomplete or inaccurate data is also punishable.
Can data be sent to ESUTD directly from 1C?
Yes. Standard 1C configurations for Kazakhstan can send electronic employment contracts, with the data signed by the employer's EDS. Companies with several databases or a separate HR platform usually set up an integration that validates the data and tracks deadlines before submission.
What if a new employee does not have an EDS?
Process the documents on paper and register the contract in ESUTD as usual, then suggest that the employee obtain an EDS through eGov for future documents. It is important to define the paper scenario in advance and track its deadlines too, otherwise the exception quickly becomes the rule.