2026-11-14
AI and 1C: scope a read-only pilot before granting access
Define one read-only 1C report for a Kazakhstan team: an access passport, KZT example, completeness checks and acceptance cases without document posting.
A manager asks: “Have AI explain every morning which invoices are still unpaid.” For the accounting team, this is more than connecting a chat interface to a database. They need to agree on the report that supplies the amounts, the organization, the reporting time and the definition of “unpaid.” Without that agreement, the agent may confidently summarize an incomplete selection even if it never changes any data.
A 1C read-only AI integration can start with one approved report and read-only permissions. The first deliverable is an explanation with verifiable source rows, not an accounting entry, a document correction or a message to a debtor. Access to a production infobase is acceptable only after checking the configuration, permissions and data to be transmitted, and obtaining the accountant’s acceptance. No single endpoint or role suits every company in Kazakhstan.
Start with a question for the accountant, before choosing an API
Choose one question: “Which items in the approved report have an outstanding amount as of the agreed time?” The answer must not quietly become “Who is late paying?” That second question requires contract terms, the dates obligations fall due and an agreed methodology. An invoice alone does not establish a debt, and a positive outstanding balance does not establish that payment is overdue.
A small company in Kazakhstan may have several organizations in one infobase, documents in Russian and Kazakh, and transactions in different currencies. The accountant therefore first selects a reference report and its settings: organization, period or as-of time, filters, currency, and rules for payments, returns and adjustments. A 1C specialist determines how to reproduce that specific result. The agent is not asked to infer accounting formulas from document names.
A useful output specification is: “Three sentences in Russian or Kazakh, the row count, total in KZT, report as-of time, retrieval time, and links to or identifiers of source rows.” If some readers cannot access the underlying documents, links must respect those permissions; having a link does not authorize disclosure of its contents. Translating the explanation does not change the organization code, document number, currency or amount.
An export, OData or a narrowly scoped HTTP service
Not every pilot needs continuous access. First decide which uncertainty you need to resolve.
On a phone, scroll the table horizontally.
| Option | What it can help you check | What it does not establish |
|---|---|---|
| An approved, de-identified export | Whether the question is clear, the answer structure works and a model is needed | Production data freshness, 1C roles or automatic completeness of the export |
| Restricted reads through OData | Access to agreed objects and fields in a specific web publication | Agreement with the accountant’s report or the absence of excessive permissions |
| A narrowly scoped report HTTP service | Return of a predefined result while hiding unnecessary structure | Absence of side effects without inspecting the handler; the service still needs to be developed |
The official 1C overview describes the standard REST interface as using OData version 3.0. It can read, create, update and delete data, and perform certain actions, including posting and unposting documents. OData does not mean read-only. A prompt saying “do not change anything” and an interface with a single read button do not remove the account’s permissions.
According to the 1Ci instructions, publishing the standard interface on a web server and selecting the objects it exposes are separate settings. Check permitted entities and field names against your own infobase metadata rather than copying another implementation’s example. Compatibility depends on the platform version, configuration, extensions, operating mode and hosting arrangements; the word “1C” in a hosting contract confirms none of these.
If the report needs complex business logic, a narrowly scoped service may be more suitable. However, a 1C HTTP service runs a handler written by a developer. The GET method itself does not guarantee that the handler never writes data or starts another operation. In this approach, inspect the code, execution permissions and side effects; blocking POST at the proxy is not enough.

The access passport: exactly what may be read
Keep the first pilot’s flow easy to inspect:
Employee → agent → single-report tool → validation gateway → approved export or 1C service → answer with sources → accountant.
The model proposes parameters in a defined schema. The gateway checks the user, organization, permitted as-of time, fields and limits, then constructs the request itself. The model receives neither a 1C password nor an arbitrary URL or filter expression. The agent has no write tool; the dedicated 1C account is denied modification, deletion, posting and unposting. Checking the network route does not replace checking permissions within the infobase.
Complete the passport before the first real request. The following fields are for agreement between IT and accounting; they are not a ready-made 1C role.
On a phone, scroll the table horizontally.
| Passport field | What to record | Reason to stop |
|---|---|---|
| Infobase and version | Configuration, platform release, extensions, test environment and owner | Unknown version or settings changed without rechecking |
| Question and source | One report, its version and calculation rules, and a reference result | A different report methodology or an amount of unknown origin |
| Organization and reader | Permitted organizations, reader roles and row restrictions | Another organization’s data or a user without permission to see the result |
| Fields and transmission | Row identifier, organization, outstanding amount and currency; a separate decision on data recipients | Bank details, personal data or another field outside the agreement |
| Time and completeness | Report as-of time, time zone, retrieval time and completion of all pages | Stale data, unknown time or a truncated response |
| Prohibitions and shutdown | No modification, deletion, posting or messaging; who revokes access | A prohibited operation succeeds, or access cannot be revoked quickly |
For dates, specify Asia/Almaty and UTC+5 rather than relying on the server’s time zone. A historical period-end report and a report “as of now” are different requests. Acceptable data age depends on the process and must be agreed, rather than taken from a universal standard.
Read permission still leaves room for a data leak. Specify separately which fields reach the model, where they are processed and stored, who reads the answers, what enters the logs and when it is deleted. Do not export bank details or personal information “just in case.” This is access-boundary design, not a legal opinion on compliance with Kazakhstan’s requirements. If the processing environment has not been agreed, use synthetic data rather than production documents.
An example: KZT 200,000 that cannot be called overdue
The following is an entirely synthetic example. It does not describe a customer, a working integration or GolemWorkers results. For this illustration, an accountant has approved the source approved-test-report-v1 for organization DEMO-KZ-A. The report as-of time is 2026-11-14T09:00:00+05:00; retrieval time is 2026-11-14T09:02:00+05:00. Two rows contain outstanding amounts: DEMO-101 has 120,000 KZT and DEMO-102 has 80,000 KZT. Under this illustrative contract, the source already accounts for the agreed payments and adjustments; how to obtain the equivalent result from a real configuration still needs checking.
The arithmetic is straightforward: 120000 + 80000 = 200000 KZT. The harder part is saying no more than the data supports. The rows contain no payment due dates, so the answer must not say “overdue debt of KZT 200,000,” initiate collection or draw a tax conclusion. An acceptable explanation is: “The complete agreed report for DEMO-KZ-A as of 09:00 contains two items with an outstanding total of 200000 KZT. The data was retrieved at 09:02; payment due dates were not checked.” The accountant must be able to see both rows and reconcile them with the source.
The example’s complete=true parameter is a declaration in the illustrative fixture input, not an automatic guarantee. A real adapter must demonstrate that all pages were completed, no part of the response was lost and the result matches the reference report. A 100-row limit does not justify a company-wide total if another 20 rows remain. When currencies differ, do not automatically add the amounts or convert them without a separate rule and an exchange-rate source.
There is also a crucial distinction between zero and unknown. An empty result that was successfully retrieved and confirmed complete means zero matching rows within the agreed scope, not an absence of obligations altogether. An access error, timeout or interrupted export means “result unknown.” Substituting zero would produce a polished but incorrect report.

How to accept a pilot and recognize an imitation
The artifact package contains the passport, a completed example, source JSON and the locally runnable report_fixture.py. The command python3 report_fixture.py checks ten synthetic cases:
- Complete, agreed KZT selection: status
READY, total200000.00. - Attempted POST:
DENY_METHOD, no total (null). - A row from another organization:
DENY_SCOPE. - An extra bank field:
DENY_FIELDS. - An incomplete selection:
HOLD_PARTIAL. - A different report as-of time:
HOLD_TIME. - A USD row among KZT rows:
HOLD_CURRENCY. - A complete empty result:
EMPTY_CONFIRMED, total0.00. - A failed read:
UNKNOWN_READ, no total (null). - A different report source:
HOLD_SOURCE.
This is an ordinary deterministic policy check, not a test of a connected 1C system, an LLM quality test or proof that a production infobase is secure. The fixed dates check exact agreement with the illustrative fixture contract; a production freshness policy needs its own implementation. The JSON, field names and codes are the artifact’s format, not ready-to-use object or API names for a particular configuration.
In a test copy with synthetic documents, a 1C specialist must separately verify actual denial of modification, deletion, posting and unposting, and confirm that other organizations’ data and extra fields are inaccessible. Within the authorized test, check the account through direct access that bypasses the gateway as well. Otherwise, the gateway might block writes while the same credentials still permit them directly. For a custom service, inspect its handlers. Check test-document state before and after; do not change production documents for this test.
The accountant reconciles the selection and totals with the reference report using identical settings and as-of time. The engineer checks all pages, errors and logs, while future users assess the explanations in Russian and Kazakh. A request identifier, report version, agreed scope, time, validation result and link to protected evidence are sufficient for the log. There is no need to copy the whole infobase into logs. An incorrect total is not the only reason to stop: a successful prohibited action or disclosure of another organization’s rows also shuts down the pilot until the problem is fixed and acceptance repeated.
When an agent helps, and when a report is enough
If the task is to add the same numbers every day and display a table, first try a standard report and a schedule. A model helps when it needs to understand an employee’s question in Russian or Kazakh, select a permitted tool and clearly explain a verified result. It should not reinvent accounting rules or expand the data scope on its own initiative.
A general-purpose agent can be taught the workflow: which report to select, when to ask for clarification, how to show sources and how to refer an exception to the accountant. Authorization, logging and evidence-display components can be reused; mapping objects in a particular 1C configuration and accepting the report remain separate work. A demonstration of actions on a Windows/AX test setup does not establish a production integration with the accounting system.
The next step is to prepare a description of one process, rather than a password. Specify the configuration and versions, required report and its owner, organization, frequency, permitted fields, processing environment and rejection criteria. For choosing a task, see the article on the first business process; for estimating costs, see the pilot budget in KZT.
Describe your process to discuss a limited GolemWorkers pilot. The form asks for a task description; do not submit passwords, access keys or internal customer documents through it. Whether your configuration can be connected, the development required and ongoing support are determined after assessment, not promised on the basis of its name.