ERP for a Holding in Kazakhstan: Bringing Several Companies into One Dashboard

In short. A holding needs an ERP when group reporting is assembled by hand and the numbers are outdated by the time they are ready. A working system brings every company's accounting into one dashboard: cash flow and P&L for each company and for the group, a CRM pipeline, planning and Kazakhstan payroll taxes. 1C stays for statutory accounting, and the management layer is built on top of it.

Signs that spreadsheets are no longer enough

• The group report takes days to assemble and is outdated by the meeting.
• Each company keeps records in its own format, and intra-group transfers are counted twice.
• The owner sees revenue but not cash flow or upcoming cash gaps.
• Sales live in a CRM, money in 1C, the plan in Excel, and the numbers never match.

What a holding ERP should include

Module	What it gives you
Multi-tenancy	Each company keeps its own books; the owner sees the group and every company separately
Cash flow and P&L	Reports are built from postings rather than assembled by hand
Consolidation	Intra-group transfers are counted once, with no double counting
CRM and pipeline	Deals, plan versus actual, import from Bitrix24 or amoCRM
Budgets	Responsibility centres, plan versus actual, scenarios, cash gaps
Staff and Kazakhstan taxes	Headcount, salaries, individual income tax, pension and health contributions, exports for accounting

How an ERP coexists with 1C

1C handles statutory accounting and reporting well, so there is no need to replace it. A custom system adds what is inconvenient in 1C: real-time management reporting for the group, a sales pipeline, planning, an owner's dashboard and a customer portal. Data moves between the systems through an integration rather than manual re-entry.

Off-the-shelf ERP or custom development

• An off-the-shelf ERP starts faster if the group's processes fit its logic and customisation is minimal.
• A custom system makes sense when the group structure, reports and integrations are non-standard, and owning the code costs less than licences and customisation.
• A hybrid — 1C for accounting plus a management layer built for your group — often turns out to be the most practical option.

Where to start

1. Problem review — 1–2 weeks. Which companies are in the group, which reports the owner needs, which systems are already in place.
2. Prototype — 2–4 weeks. A group dashboard on real data from one or two companies.
3. Iterative development. Module by module: cash flow and P&L, CRM, budgets, staff.
4. Launch and support. Team training, on-call support, development from a shared backlog.

How Kemel does it

Kemel is a multi-tenant ERP platform built by 105: finances of every group company in one dashboard, cash flow and P&L reports, a CRM pipeline with deal import from Bitrix24, planning and budgeting, and automatic calculation of Kazakhstan payroll taxes. More on the case page.