Simple is not easy

1C

1C in a Heterogeneous IT Landscape

1C:Enterprise covers accounting, sales, and manufacturing in CIS enterprise, but the platform delivers results only where it fits.

1C is well suited as an accounting and operations core (accounting, sales, warehouse, CIS statutory reporting); for high-load real time, complex integration logic, and custom product scenarios, it is not deeply modified, but extended with external services.

~48%1C market share in the CIS ERP market (80% of the 60% domestic segment, end of 2024)
+10–12%ERP market growth in CIS in 2024
>150 usersthe threshold after which 1C requires a server cluster and special architecture for load
until 10.2026free access to the 1C: Development Copilot AI assistant with an ITS subscription

1C suite

1C should stay the accounting core, not a point of fragile coupling

The 1C section should lead the reader to outcomes: fewer manual reconciliations, transparent data exchanges, changes without a cascade of rework, business logic next to the core rather than inside the monolith.

200+1C systems can be connected through a single managed API
1 perimeteraccounting, warehouse, sales, EDI and BI linked through clear data exchanges
SLAsupport is measured by service recovery, not ticket count

Implementation

First the process and data owners, then configuration, migration, training and production operation.

Integrations

Exchanges run over API/ESB/queues with monitoring, retry delivery and an error log.

Transferability

Customization is moved into services beside 1C, so platform updates don't break the business.

1CAPI/ESBqueuemonitoringwebsite/CRM/EDI/BI

Industry solutions

What you can do with 1C

All Solutions

Capabilities

1C Capabilities

1C core (standard, vendor-supported): accounting, sales, warehouse, CIS statutory reportingFit zone: accounting and operational processes, document workflows, FTS reportingCaution zone: high-load real time, complex product logic, custom integrationsESB/API layer: routing integrations, a single contract, failure isolationBusiness-Logic Microservices Next to 1C (Scaled Independently)External systems: marketplaces, product labeling/EGAIS, WMS/TMS, BIAI layer: MCP server, LLM assistant, natural-language data queriesIntegration: Enterprise Data (XDTO/XML), documented contracts, portability
Applicability map. In the center is the standard vendor-supported 1C core (accounting, sales, warehouse, CIS statutory reporting). On the left is the green zone, where 1C is appropriate; on the right is the red zone, where you should NOT go deep (high-load real time, complex product logic, custom integrations). At the bottom is the ESB/API layer, through which 1C exchanges data with business-logic microservices, marketplaces, labeling, BI, and AI/MCP. Exchange arrows are labeled 'Enterprise Data (XDTO/XML), documented contracts'. Bottom caption: 'we do not fork the core, we move logic nearby, ensuring portability and no vendor lock-in'.

Standard configuration under support, without forking the core

vendor updates install normally, and support costs do not grow because of accumulated customizations

Business Logic in Microservices Next to 1C

heavy computations and product scenarios do not slow down the accounting core and scale separately

Integration via ESB/API, not point to point

new systems connect in days, not by rewriting integrations; failure of one system does not take the others down

Integration via the Enterprise Data standard (XDTO/XML)

data moves between configurations and external systems without modifying 1C or losing vendor support

Documented Exchange Contracts

the main cost driver is removed: undocumented integration; handover between teams without archaeology

1C server cluster for load and fault tolerance

stable operation with 150+ users and 24/7 uptime without performance degradation

Portability and removal of vendor lock-in within the 1C core

changing a contractor or team without rewriting the system; the company owns the architecture instead of depending on one provider

AI Layer Over 1C Data via MCP/LLM

natural-language queries against corporate data and faster development without touching the accounting core

Approach

How We Implement 1C

Minimal core modification

We do not fork or patch the 1C core. 1C stays on the standard upgradable version, while business logic is moved into separate nearby microservices, so platform updates do not break your customizations.

International Standards, Not Homegrown Hacks

Where a mature international solution exists, we use it instead of inventing our own protocol or platform. Before writing code, we study how the problem is already solved in the industry.

Transferability

The solution is loosely coupled and documented: it can be handed over between teams and contractors without rewriting. You are not tied to us.

AI compatibility

1C in the AI Stack

MCP Server on Top of 1C Databases

through Model Context Protocol, the LLM requests data, reads metadata, and creates objects without changing the configuration, so AI works outside the accounting core

1C: Development Copilot

the official 1C AI assistant speeds up code and query writing; it is free with ITS subscription until October 2026, lowering the entry barrier for projects

Natural Language Access to Corporate Data

knowledge bases with neural networks answer questions about 1C data in natural language, with no exports or manual reports

AI Assistant in the Query Console

in standard configurations (1C:UT), AI generates a query skeleton, speeding up analytics without deep platform changes

Projects

Cases

All cases

Contacts

Let's Discuss Your Project

Leave your current contact details and describe your task. We will come back with clarifying questions and a proposal for the next step.