Separate copy or extract
Analysis runs on a prepared copy or on files produced inside the company infrastructure.
Data diagnostics and control
The system receives an agreed data set from a database copy or controlled extract, validates its quality, and connects transactions into a broader business picture. The live database remains unchanged, and an expert forms the conclusions.
De-identified demonstration data
Controlled environment
The data transfer method is agreed with the client. The analysis uses read-only access and makes no changes to the accounting system.
Analysis runs on a prepared copy or on files produced inside the company infrastructure.
Only necessary objects, fields, and periods are extracted.
Algorithm versions, input files, and outputs are linked by checksums and can be independently repeated.
Ongoing monitoring can use a dedicated read-only route, but only after agreeing access, the exact data scope, and refresh rules.
How the work is structured
A controlled copy or extract becomes a passport of scope, quality, and limitations.
Reproducible indicators and comparisons form the factual report.
Procurement, cost, sales, cash, and operations are connected into explainable chains.
An expert assesses context, materiality, and alternative explanations.
Priority indicators receive sources, refresh frequency, and response rules.
Useful checks become a repeatable control layer with a history of signals and decisions.
First deliverable
The report shows both measured facts and analytical limits. A missing source is never replaced with an assumption.
The figures illustrate the report format. Available objects, transaction volumes, and method coverage depend on the configuration and actual data quality.
Analysis examples
Calculations show what changed and which transactions formed the change.
The reasons for changed purchasing terms and their business meaning are established through further analysis.
| Item | Organisation | Supplier | Average price | Volume | Vs minimum |
|---|---|---|---|---|---|
| M16 bolt | Organisation A | Supplier 1 | RUB 101.50 | 18,000 | — |
| M16 bolt | Organisation B | Supplier 1 | RUB 128.00 | 12,500 | +26.1% |
| M16 bolt | Organisation C | Supplier 2 | RUB 119.40 | 8,200 | +17.6% |
A price difference is a fact that prompts review of specification, volume, logistics, payment terms, and contract date.
Data enrichment
Additional sources help establish whether an accounting entry is supported by independent operational events.
1C, banking transactions, payments, and accounting entries.
CRM, registers, fiscal data, deals, returns, and relationship history.
Warehouse movements, balances, stock counts, and process events.
Employees, access, event logs, registries, and counterparty data.
Each source is added independently, with a clear purpose and its own quality assessment.
One signal is built from several independent facts. The system shows which parts of the chain are supported and which still require data or review.
Three facts agree and one source is absent. The event is passed to a human for review; the cause is not inferred automatically.
Controlled use of AI
The analytical core remains deterministic: Python, registered SQL templates, and rules produce the same indicators on every run.
Completeness, amounts, trends, and document links are produced by reproducible code.
The model maps fields, groups names, and drafts hypotheses over prepared facts.
An expert checks mappings and alternative explanations, determines significance, and forms conclusions.
The LLM has no connection to 1C, SQL, or accounting data: it receives only minimal de-identified context, and an expert checks every proposal. A local model can be used, or the LLM can be disabled entirely.
First step
Describe your questions, and I will propose an approach.