AI Document Agent Integration with EDO (Diadoc, SBIS)

Electronic document management systems (EDO) store terabytes of documents but don't understand their content. They only transfer and sign. We change that: AI Workforce connects to your Diadoc or SBIS and processes documents like an experienced employee — read, analyze, fill in, make decisions. Accounting receives hundreds of invoices, acts, UPD daily. Each document must be manually opened, checked against the order, posted in 1С, and signed. Errors are inevitable: missed requisites, discrepancies in amounts, missed deadlines. AI Workforce solves these problems by automatically processing documents from receipt to posting. Reducing FTE costs by 70% through automation is a typical result after implementation. The project pays for itself in 4–6 months. Typical project cost starts from $50,000 with ROI in 4–6 months, saving 70% on document processing costs. Order a pilot in 2 weeks and see the effect.

We are ISO 27001 certified and have 5+ years of experience in EDI automation. With 20+ successful implementations, we guarantee results.

We build an agent layer on top of your infrastructure. AI agents become a participant in the document flow, but fully automated. The agent layer includes five types of agents: document reception, classification, data extraction, validation, and actions (signing, routing). Each agent solves its task using fine-tuned models and RAG pipelines for document workflow automation. This modular architecture allows flexible configuration for any business processes.

After connecting to the EDO API, the system starts monitoring incoming documents. A new document enters the receiver agent, which downloads its content. Then the classifier determines the document type and routes it to the appropriate extractor. The extracted data undergoes validation, and the action agent decides: sign, reject, or send for manual review. The entire cycle takes seconds. Our AI workforce integrates with Diadoc, SBIS, and 1С for seamless document workflow automation. Using RAG and fine-tuned BERT, we perform 3-way matching and data extraction.

How AI Workforce connects to EDO?

[EDO system (Diadoc / SBIS / 1С-EDO)]
    ↕ REST API / SOAP / Webhook
[AI Integration Layer]
    ├── Document Receiver Agent
    ├── Classification Agent
    ├── Extraction Agent
    ├── Validation Agent
    └── Action Agent (signing, rejection, routing)
    ↕
[Internal systems: 1С, ERP, CRM, DB]

Diadoc: API Integration

Diadoc provides REST API with OAuth 2.0. Key endpoints:

• GET /v1/GetNewEvents — get new documents (polling or webhook)
• GET /v1/GetDocument — download document body (XML for formalized, PDF/DOCX for non-formalized)
• POST /v1/PostMessage — send a signed document
• POST /v1/Delete — reject with comment

For signing, we use CryptoPro DSP API or a local crypto provider. The agent calls signing through a separate secure service, does not store keys.

SBIS: Integration via WebAPI

SBIS uses JSONRPC API (SBIS WebAPI). Authentication via SID session. Main methods:

• СБИС.ЗаписатьДокумент — create and send
• СБИС.СписокДокументов — get list with filtering
• СБИС.ПрочитатьДокумент — get content

Specific to SBIS: documents often come in SBIS-XML format, requiring a custom parser. We place an intermediate converter to unified JSON. Our custom parser is documented in our integration guide.

Why AI is faster than manual processing?

Compare with a full-time document clerk:

Which documents does AI process automatically?

Formalized invoices, UPD, certificates — accuracy 97–99%. Non-formalized PDF and Word — accuracy 90–95% after custom fine-tuning. All exceptions are routed to humans. For non-formalized documents, we use fine-tuned BERT or prompt-based GPT-4o, achieving quality sufficient for industrial operation. Our extraction pipeline achieves 95% accuracy after 2 weeks of training on your data.

How do agents process documents?

Classification and Routing

The first agent is the classifier. It determines the document type and route:

The classifier is trained on your document corpus (fine-tuned BERT or prompt-based GPT-4o). Accuracy 97–99% for formalized, 90–95% for non-formalized.

Three-Way Matching

Key task of AI Workforce in finance is automatic reconciliation of order, delivery note, and invoice. The agent checks items, quantity, price, totals. When discrepancy exceeds threshold → flag for manual review; when aligned → automatic signing and payment initiation. Uses 3-way matching with thresholds:

• Amount: ±0.5% (rounding tolerance)
• Quantity: 0% (exact match)
• Items: fuzzy matching with 85% threshold

Integration with 1С

Two-way synchronization via 1С REST API (oData) or COM objects:

• From 1С to EDO: automatic creation and sending of outgoing documents
• From EDO to 1С: creation of documents based on received ones (UPD → Goods receipt, Certificate → Service receipt)

For 1С:ERP, we use the "Electronic Document Exchange" subsystem with an extension for AI validation before posting.

Exception Handling and Human Control

Not everything goes through automatically. The system routes exceptions:

• New counterparty → verification via Federal Tax Service/Unified State Register of Legal Entities → manual approval
• Amount above threshold → mandatory manual authorization
• Data discrepancy → notification and blocking
• Expiration → automatic renewal or escalation

Monitoring and SLA

Key metrics in production:

• Straight-through processing rate — share of documents without manual intervention: target 70–85%
• Processing latency — up to 5 minutes for standard documents
• Extraction accuracy — >98% for formalized
• False positive rate — <5%

Security and Compliance

• Digital signature is stored in HSM or secure crypto service
• AI agent has no direct access to keys
• Full audit trail for tax authorities
• Compliance with Federal Law No. 63-FZ on Electronic Signatures

Implementation Timeline

Brief Implementation Scheme

1. Audit of current document flows and preparation of API access to EDO.
2. Deployment of agent layer: receiver, classifier, extractor.
3. Setup of 3-way matching and 1С integration.
4. Pilot launch for 2–3 weeks on real data.
5. Optimization of thresholds and exception routes.
6. Production launch with full monitoring.

Common integration issues: Diadoc API limits (no more than 100 requests per minute per session), SBIS-XML and XML UPD format differences (intermediate converter required), incorrect item settings in 1С (leading to false discrepancies), lack of webhook notifications from some operators (polling must be configured). We address all these nuances during the audit phase.

What's included

• Integration documentation (flow diagrams, agent configurations, API call descriptions)
• Configured AI agents: receiver, classifier, extractor, validator, action agent
• UI for exception handling and manual control
• Operator training (2–3 days)
• Support for 2 weeks after production launch
• Source code transfer (if required) for in-house maintenance

After the pilot, you get a working prototype ready for industrial scaling. Get a consultation for more details.

We have implemented AI Workforce at 20+ large enterprises. Our accumulated experience allows us to predict bottlenecks and configure the system in 12 weeks turnkey. Contact us to evaluate your document pipeline.