AI agent for 1C: reports, reconciliation, invoices
The agent reads your 1C over OData: it builds the P&L by unit, reconciles settlements, checks incoming invoices and matches EDI documents from Diadoc.
Scenarios for this job
Every scenario is a ready brief for the agent: the steps, the connected systems and the output. Open one and run it on your own data.
You know the company's profit. Which line of business brings it in you still work out by hand in Excel. The agent splits it straight from 1C.
The statement and 1C are forty thousand apart, and nobody knows where. The agent matches operations line by line and names every mismatch.
The counterparty sent their statement and the totals disagree. The agent merges Diadoc documents with 1C postings and shows whose document dropped out.
Invoices land in chat from different managers, and one person sends them all to the bank. The agent checks each against the 1C record and contract.
The same item is called three different things in 1C, the CRM and the marketplace. Sales land in one table, with the leftovers listed openly.
The report shows profit, the accounts show nothing. The agent lays out how much the business itself earned and how much went into kit and loans.
Signing the act closes the period, yet the balance gap isn't broken into rows. The agent merges SBIS and 1C line by line before you sign anything.
Dozens of documents sit in Diadoc, some unsigned simply because nobody got to them. The agent checks each one against the order in 1C.
Some acts came through EDI, some by email, some never came at all. The agent assembles the package per customer and names exactly what's missing.
Almost every hard fact about the business lives in 1C: postings and turnover, counterparties and contracts, orders, stock, mutual settlements. The data is not the problem; reaching it is. A simple question — how much do we owe this supplier, which document is still unposted, what is the margin for that unit — needs someone who knows which report holds it and which filters to set. The accountant is closing the period, the question is urgent, so it goes into a chat and waits its turn. What is lost there is not an hour but the habit of checking the numbers before a decision rather than after it.
The workaround is always the same: export to Excel. Once a week someone runs a couple of reports, drops the files into a chat, and the rest is merged by hand. Everything arriving over EDI — acts, invoices, UPD documents from Diadoc or SBIS — is checked by eye against what was entered in the database. The failures are standard: a document the counterparty signed but nobody posted, an invoice paid twice, a typo in bank details that only surfaces at the quarterly reconciliation. Each one is cheap the day it happens and expensive three months later.
The agent connects to your 1C publication over the standard OData interface and reads catalogues, documents and registers directly — no configuration work required. Accounting, Trade Management, ERP, Small Business, Payroll and HR and Document Flow are supported, along with custom configurations on platform 8.3. From there it answers the question instead of handing you a report: it builds the P&L by unit, merges 1C sales with CRM and marketplace data, reconciles the Tochka statement against postings, and checks the details and amount of an incoming invoice. Access is granted read-only: the agent posts nothing and edits nothing in the database — it shows what does not add up and leaves the action to you.
Common questions
Do we have to modify our 1C configuration?
No. The agent uses the standard OData interface: publish the database on a web server, open access and create a user with read rights. Nothing is written into the configuration, so vendor updates keep applying exactly as before.
Which 1C configurations are supported?
1C:Accounting, Trade Management, ERP, Small Business, Payroll and HR, and Document Flow — plus any custom configuration on platform 8.3: the agent reads the published metadata and works with whatever objects that publication exposes.
Does the agent write anything into 1C?
Not by default — access is granted read-only. It builds reports, finds discrepancies and prepares documents as external files, while posting stays with the accountant. That same limit is what rules out quiet back-dated corrections.
Can it see EDI documents as well?
Yes, once Diadoc or SBIS is connected. The agent matches incoming acts, invoices and UPD documents against what is posted in 1C and returns two lists: documents still waiting for an answer, and documents the counterparty signed that never reached your database.