AI for documents: EDI, 1C and source paperwork
The agent reads incoming EDI documents from Diadoc and SBIS, matches UPD forms, acts and invoices against 1C settlements and assembles the monthly closing package.
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.
The agent assembles the quarterly reconciliation statement from 1C and EDI data, matches documents on both sides and prepares the file to send to the counterparty.
The agent checks an incoming invoice: counterparty details, match against the contract and amount, duplicates — and says whether it's safe to pay.
The agent assembles the reconciliation act in SBIS for a counterparty, matches it against settlements in 1C and shows the lines where the two sides disagree.
The AI agent parses the Diadoc and SBIS inbox — UPD forms, acts and VAT invoices — matches them against 1C and shows what awaits signing and what is unposted.
The agent checks the month's source documents, assembles the closing package per customer, finds missing acts and UPD forms and drafts emails to counterparties.
Source documents are how a business proves the deal happened. An invoice, a delivery note, an act, a UPD, a VAT invoice: some arrive over EDI into Diadoc or SBIS, some by email as PDFs, some on paper — and an accountant enters all of it into 1C. The trouble lives in the seams. The counterparty signed a UPD in Diadoc and the document never reached the database. An invoice is paid but the act for the service never came. A delivery note differs from the invoice by rounding, and nobody compared them. Each of those gaps is cheap on the day it appears and expensive at quarter close, when the books stall on one unexplained line. This cluster holds five scenarios around that flow.
Today the flow is processed by eye. In the morning someone opens Diadoc, looks through the inbox, downloads attachments, checks details and amounts against what is entered in 1C, and files everything away. In parallel the same person hunts for the closing documents missing from last month and emails counterparties asking for the act. At twenty counterparties that is half a day a month; at two hundred it is one person's permanent job, and all of it is comparing the same fields over and over. The mistakes are predictable: a duplicated invoice, a payment to outdated bank details, a document signed by the counterparty and lost between Diadoc and the database. Worse, they surface at the quarterly reconciliation rather than on the day.
The agent reads the inbox in Diadoc and SBIS, parses each document — details, number, date, amounts and line items — and matches it against what is posted in 1C over OData. The output is three lists: documents waiting for your signature; documents the counterparty signed that never reached the database; mismatches in amounts or bank details with the exact field that differs. Separate scenarios check an incoming invoice before payment, assemble a reconciliation act per counterparty, and prepare the monthly closing package together with emails to whoever has not sent an act yet. Signing, posting and payment stay with a person: access to 1C is read-only and the agent never signs an EDI document on your behalf. Inbox triage runs on a schedule, with a morning digest in Telegram.
Common questions
Which EDI systems are supported?
Kontur.Diadoc and SBIS (Saby): incoming and outgoing documents, counterparties and signing status are read through their APIs. Accounting data comes from 1C over OData, so matching happens directly, with no file exports and no retyping of details.
Which document types does the agent handle?
Invoices, delivery notes, service acts, UPD forms and VAT invoices — from EDI, from PDF attachments in email and from scans. It extracts the details, number, date, amounts and line items from each and checks them against the contract and against 1C.
Will the agent sign a document for us?
No. Signing with an electronic signature stays with your employee: the agent shows what is waiting for a signature and explains why a document cannot be accepted as it stands. Access to 1C is read-only too, so posting stays with the accountant.
How is the monthly closing package assembled?
The agent compares shipments and payments for the period against what was signed over EDI and finds the customers whose act or UPD is missing. For each it drafts an email listing the missing documents, and the package goes into a folder and a summary table.