Work through the SBIS documents waiting on your decision
Connect SBIS (Saby) to the AI agent: EDI documents, counterparties, tasks, signing certificates. The agent builds shipment registers and shows what awaits signing.
How the agent works with СБИС
The agent calls the SBIS service methods: it requests document lists with a type filter and page-by-page navigation, reads attachments and document flow states, your own organizations and units, counterparties and invitations, tasks and service stages, certificates and machine-readable powers of attorney. Out of that come a register of outgoing shipping documents for the period and a list of the incoming ones waiting on your decision, with the counterparty, the amount and the date received.
A selection in SBIS always runs through a filter and pages, so every document for a period is a traversal rather than a single request, and the agent makes sure it reached the end instead of passing off the first page as the total. The second feature of the domain: exchange is two-sided, and a document will not reach a counterparty who is not connected to EDI. So the agent checks the other side by INN and KPP in advance and prepares a list of invitations.
The agent writes exactly as far as the application has permissions to: save a document, attach files, assemble a package for sending. With signing the line runs along the key type: a qualified signature held on a token is put on by a person, and there the agent takes the document up to the signature and stops, while a company server certificate it activates and signs with itself. It starts that only on a direct command: a signature is legally binding and never a pipeline step. It reviews server certificate validity ahead of time and shows which ones run out before the nearest reporting date.
The agent works with the token Saby issues after you sign in and confirm access; if Saby revokes it, the agent asks you to sign in again instead of failing silently. The account permissions narrow the selection on the service side: a closed section returns a refusal rather than an empty list, and the agent tells the two apart. It holds the request rate itself, and when there really are no documents for the period it says so directly.
Integration scenarios
Documents waiting for a signature
The agent shows the incoming EDI documents that need a decision, with the counterparty, the amount and the date received.
Register of outgoing shipping documents
The agent collects outgoing shipping documents for the period and names the ones the counterparty never responded to.
Counterparty readiness for EDI
The agent checks by INN and KPP whether a counterparty is connected to electronic document exchange and prepares a list of invitations.
Signing certificate control
The agent reviews the company server certificates and shows which of them stop being valid before the nearest reporting date.
Where documents got stuck
The agent walks the tasks and internal document flow stages and shows at which step and with whom a document has been sitting longer than the rest.
A package ready to send
The agent assembles a package for sending where the application has write rights: saves the document, attaches the files and takes it up to the signature, which is put on by an employee or by the company server certificate on your command.
СБИС examples
Из 78 контрагентов 12 не подключены к ЭДО в СБИС.
- 12 без подключения, на них уходит 40% бумажных отгрузочных
- 5 подключены, но приглашение висит непринятым с мая
- список к приглашению собрал по ИНН и КПП, отправлять по вашей команде
How to connect
Before you connect
- A Saby employee account with access to the sections you need
- A server certificate with its activation code if the agent signs
- A qualified signature held on a token is put on by a person
- Write rights for the signed-in employee if the agent saves documents
- 1
Sign in to Saby as the right employee
Sign in at online.sbis.ru with the employee's login and password. The agent works with their rights and sees exactly the sections open to them in Saby.
- 2
Pick the company and confirm access
If your Saby profile holds several companies, sign in to the one whose documents the agent needs. Saby then asks consent to access your data: confirm it.
FAQ
With the Connect via Saby button: sign in to your Saby account and confirm access for the Sam Reshu application, no keys to copy. If signing in does not suit you, connect with the service key of your own application from Settings, Security, Connections to Saby.
Electronic document exchange documents with attachments and states, your own organizations and units, counterparties and invitations, tasks and service stages, certificates and machine-readable powers of attorney.
It can, if the application has write permissions: SBIS allows saving a document and attaching files. It can sign only with a company server certificate and only on your command; a qualified signature held on a token is put on by a person.
The agent acts with the rights of the employee who signed in to Saby when connecting and sees exactly what that employee sees. To leave the agent only the document exchange, connect Saby as an employee whose role opens only those sections.