Which 1C configurations can be integrated with AI?+
We begin by checking your configuration, release and customisations. ERP, trade management, accounting and industry solutions may require different objects and exchange methods. We confirm compatibility in a test database before finalising the implementation scope.
Does the existing configuration need to change?+
We assess available interfaces and whether AI logic can run in a separate service. If required operations are unavailable, we agree an extension or customisation with the support team, including its impact on updates and testing procedures.
Will AI post documents independently?+
That is a separate project decision. The scope can be limited to reading data or preparing drafts. If posting is required, we define permitted document types, checks, owner approval and error-handling rules; the model does not receive unrestricted accounting access.
Can this work without a direct connection to the 1C database?+
Yes. We design interaction through supported interfaces and application services. We do not use direct writes to database tables for AI integration: operations must preserve the accounting system's validations and relationships.
What happens after a 1C update?+
The project includes a list of dependent objects and regression scenarios. We check interface changes in a test environment, then agree the release. The scope of further adaptation to new versions is defined by the support terms.
How much does development cost, and how are timelines determined?+
We assess the use cases, data readiness, number of integrations, quality requirements and deployment needs. After discovery, we define stage boundaries, deliverables and acceptance procedures. Infrastructure, model and ongoing support costs are considered separately from development. The precise timeline and budget depend on the agreed scope.
Can the solution run in our company's infrastructure?+
We consider on-premises, cloud and hybrid deployment. The choice depends on data requirements and the availability of models and computing resources. Before implementation, we agree on external requests, access rights, logging and required safeguards with IT and information security teams.
What does the team receive after launch?+
A working solution within the agreed scope, architecture and integration documentation, operating instructions and validation results. Code handover, component rights, access and training are specified in the contract. Ongoing support and SLAs are agreed to meet your company's requirements.