1C and HR: Automation of Hiring and Personnel Management
As of March 12, 2026, administrative liability for violations in the Unified System of Labor Contract Accounting has come into effect in Kazakhstan: information about the contract must be submitted to the USLCA within five working days after signing, and for delays or inaccurate data, fines can reach up to 150 MRP for large businesses — that's 648,750 tenge with an MRP of 4,325 tenge in 2026. Simultaneously, a new version of the configuration for payroll and personnel management (3.1.2.21) was introduced, which recalculates individual income tax on a progressive scale, social contributions, and form 200.00. For the HR department, this means a simple thing: the cost of manual errors has increased, but the number of mandatory operations has not.
In our practice at West Star Ltd, we regularly see how a two- or three-person HR department spends working days transferring the same data between the company's accounting system, the state portal hr.enbek.kz, and internal tables. The thesis of this article is simple: a significant part of hiring and personnel paperwork can indeed be automated through the integration of an accounting system based on 1C with external HR platforms and government services, but not all. Let's analyze what can be well automated, what works halfway, and where a human is still irreplaceable.
WHAT IS THE PERSONNEL CIRCUIT AND WHERE DOES IT BREAK
The personnel circuit of a company is not a single program but a chain. At the entry point is recruitment: job applications, responses, interviews, offers. Next comes processing: employment contract, hiring order, personal file, familiarization with internal documents. Then personnel support: transfers, vacations, sick leaves, business trips, salary changes. And at the exit — payroll, reporting, and dismissal. In most Kazakhstani companies, these stages live in different places: recruitment in chats and tables, processing in 1C, reporting partially in 1C, partially on hr.enbek.kz.
The circuit breaks at the junction points. A candidate passed an interview in one system — data is manually entered into the accounting system. A contract is processed in the accounting system — it is manually registered in the USLCA. An employee goes on vacation — the entry appears in the schedule but does not always reach the payroll on time. Each manual transfer is both lost time and the risk of a typo, which now has a price in MRP. Automating the personnel circuit is primarily about eliminating manual junctions, not replacing people with robots.
WHICH HIRING PROCESSES CAN BE REALLY AUTOMATED
Let's start with hiring, because this is where miracles are most often expected and disappointments occur. It is not "people selection" that is automated, but the routine around it.
First — collecting and initially sorting responses. Applications from the website, messengers, and job platforms can be consolidated into a single list with basic fields: name, contact, position, source. Duplicates are filtered out, and the candidate receives an automatic response that the application has been received. This removes mechanical work from the recruiter and prevents responses from getting lost.
Second — moving the candidate through the stages. Statuses "new," "phone interview," "technical interview," "offer," "rejection" become not notes in the recruiter's head but a clear state in the system, showing where the bottleneck is. Notifications about the next step are sent to both the candidate and the hiring manager.
Third — turning an accepted candidate into an employee without re-entering data. When an offer is accepted, the data collected at the recruitment stage should automatically form the basis of the employee's card in the accounting system: full name, ID, position, department, salary. This transition from "candidate" to "employee" without manual re-entry provides the most tangible effect and eliminates a whole class of errors.
What automation does not do — it does not decide whom to hire. The assessment of competencies, cultural fit, and motivation remains with people. Tools reduce the time spent on mechanics and free up the recruiter for the actual interview, but the final decision about the person is made by a human.
PERSONNEL ACCOUNTING AND CONNECTION WITH GOVERNMENT SYSTEMS
The second major block is personnel paperwork and mandatory reporting. Here, automation gives maximum returns because processes are formalized by law.
Electronic employment contracts on the hr.enbek.kz portal can already be signed through the portal and mobile application, and the signed contract is automatically registered in the USLCA. Electronic document management services with integration transmit contract information to the system without manual input. The practical meaning: if the contract is processed in the accounting system and registered in the state system, you physically cannot forget about the five-day deadline, thus eliminating the risk of a fine.
The portal provides electronic versions not only of the contract but also of the personal file, employment record book, employment certificate, and collective agreement. The electronic employment record book is formed based on contracts registered in the USLCA. This changes the logic: the HR specialist increasingly needs to maintain neither paper nor parallel electronic versions if the primary data correctly enters the state circuit from the accounting system.
The calculation part is a separate story. From January 1, 2026, a progressive income tax scale applies: income from the employer is taxed at a rate of 10 percent up to a threshold of 8,500 MRP per year and 15 percent above it. The updated configuration already knows how to calculate according to the new rules and prepare regulated reports, including form 200.00. Automation here is not about replacing the accountant but about ensuring they work according to the current methodology, not manually checking rates for each employee.
HOW THE INTEGRATION IS TECHNICALLY ARRANGED
Technically, the integration of the accounting system with external HR tools is built on standard mechanisms, not custom-made crutches. The accounting system on the 1C platform can send and receive data via the OData protocol: employee directories, departments, personnel documents are available as a regular web resource accessed by an external application. This allows, for example, a recruitment web platform to create a new employee card directly in the accounting system, and a reporting portal to retrieve current personnel data.
For scenarios requiring exchange with government services or messengers, an intermediate layer is usually placed between the accounting system and the outside world — a service that accepts requests, transforms data into the required format, and ensures that the exchange is idempotent, meaning a repeated launch does not create duplicates. In our practice, the reliability of this layer determines whether automation saves time or creates new problems. Good integration logs every operation, can retry failed transmissions, and clearly informs a person when something goes wrong, instead of silently losing data.
Notifications are a separate issue. Leave requests, transfer approvals, reminders about contract registration deadlines are conveniently displayed in the messenger the team uses every day. This is not a separate HR system but a thin layer over the accounting: the employee sees the request in the chat, the manager clicks "approve," and the status changes in the accounting system.
LIMITATIONS AND WEAK POINTS
Automating the personnel circuit is not a silver bullet, and it's more honest to name its weak points in advance.
First — the quality of the initial data. If the ID, positions, and departments in the accounting system are maintained carelessly, integration will simply spread this mess faster and more extensively across all linked systems. Automation amplifies both order and chaos.
Second — dependence on external systems. The hr.enbek.kz portal, reporting formats, and tax rules change, sometimes with short notice. Integration needs maintenance: what worked last quarter may require adjustments after a government service update. This is not a one-time project but a living mechanism.
Third — tokens and accesses. Exchange with external platforms relies on access keys that expire. If this is not monitored, data publication or transmission quietly stops working, and it is discovered at the worst moment. Monitoring is needed, not faith in "once set up and forgotten."
Fourth — the boundary of legal responsibility. The system can prepare and send information, but the responsibility for the correctness of the contract and compliance with deadlines remains with the employer. The tool reduces the likelihood of error but does not transfer responsibility to itself.
Fifth — resistance from people and the transition period. While some HR specialists maintain processes the old way alongside the new system, you get double work and desynchronization. Automation gives effect only when the old manual path is closed, and this is a managerial, not a technical decision.
Sixth — for small companies with infrequent hires, deep automation may simply not pay off. Five processes a year are cheaper to do manually than to build and maintain integration. Scale matters.
PRACTICAL CONCLUSION
An HR specialist should start not with platform implementation but with tidying up the directories in the accounting system and an honest process map: where exactly data is manually transferred. These points are the first candidates for automation, and often closing two or three junctions gives more than a large project.
The HR department head should view the personnel circuit as a continuous flow from response to dismissal, not as a set of separate programs. The key question is not "which HR system to buy," but "where does our flow break and how much does it cost in hours and risk of fines." The answer to this determines the order of work.
The owner should evaluate automation by return on investment and risk reduction, not by fashion. If the company is growing and the number of employees is measured in tens and hundreds, the integration of the accounting system with government services and recruitment pays off quickly due to saved time and absence of fines. If hiring is rare, it is wiser to automate only reporting and contract registration, leaving recruitment manual. In any case, it is worth budgeting not only for implementation but also for maintenance — government systems and laws in Kazakhstan change regularly, and live integration requires care.
FREQUENTLY ASKED QUESTIONS
Can you completely dispense with an HR specialist after automation?
No. Automation removes mechanical data transfer and reduces the risk of errors, but hiring decisions, contentious personnel situations, and legal responsibility remain with people. The number of HR specialists does not change, but the content of their work does — less routine, more essence.
What is the deadline for registering an employment contract in the USLCA and what happens for a delay?
Information is submitted within five working days from the signing date. From March 12, 2026, fines are provided for violations of deadlines and procedures — from 30 MRP for officials to 150 MRP for large businesses. There are 30 working days to correct incorrectly submitted information.
Do you need a separate HR platform or is the accounting system enough?
It depends on the processes. For processing, personnel accounting, and reporting, the capabilities of the accounting system plus the state portal are often sufficient. A separate recruitment platform is justified when the flow of candidates is large and recruiting is a constant function, not an episode.
What most often breaks in such integrations?
Three things: expired access keys to external services, changes in formats on the side of government systems, and garbage in the initial data. All three are treated not by one-time setup but by monitoring and regular maintenance.