AI Integration in ECM: Automating Incoming Documents

Incoming documents — the bottleneck of any organization

A scanned contract arrives by email → the operator opens it → manually enters the details into 1C → selects the type → launches the approval process. On average, 8 minutes per document. With 500 documents per month, that's 67 hours of purely mechanical work. Our AI integration reduces this to 45 seconds per document, with 89% processed without human intervention. The problem is compounded by the variety of formats: PDF, scans, DOCX, email attachments. Each requires preprocessing, and manual entry errors lead to approval failures. We build an AI layer that understands the content of any document, extracts key details, classifies, and automatically launches workflows in your ECM. No templates — only trained models tailored to your document flow. Our team's experience: over 20 successful implementations, 5+ years in NLP and MLOps.

How does AI process documents faster than an operator?

AI processes an incoming document 10–15 times faster than a human: 45 seconds vs. 8 minutes. Moreover, requisites extraction accuracy reaches 94% (vs. 85% with manual entry). The system works around the clock, requires no breaks, and makes no fatigue-related errors.

Investment in AI integration pays off in an average of 6 months. For example, with a document flow of 500 units per month, savings amount to about 1.2 million rubles per year due to freed operator time and reduced errors.

Why is fine-tuning BERT critical for accuracy?

A base document classification model (cointegrated/rubert-tiny2) yields about 80% accuracy on typical documents. However, each company uses unique template contracts, invoices, and acts. Fine-tuning BERT on your corpus (from 500 labeled instances) boosts accuracy to 94% and above. We use Hugging Face Transformers for fine-tuning and inference. Below is a sample classifier implementation.

from transformers import pipeline, AutoTokenizer, AutoModelForSequenceClassification
import torch

class DocumentClassifier:
    DOCUMENT_TYPES = [
        "договор", "счёт-фактура", "накладная", "акт",
        "приказ", "служебная записка", "коммерческое предложение",
        "доверенность", "устав", "протокол", "письмо входящее"
    ]

    def __init__(self, model_path: str = "cointegrated/rubert-tiny2"):
        # Для production — дообученный BERT на корпусе документов компании
        self.tokenizer = AutoTokenizer.from_pretrained(model_path)
        self.model = AutoModelForSequenceClassification.from_pretrained(
            model_path,
            num_labels=len(self.DOCUMENT_TYPES)
        )
        self.model.eval()

    def classify(self, text: str) -> dict:
        # Берём первые 512 токенов (шапка документа несёт основную семантику)
        inputs = self.tokenizer(
            text[:2000],
            return_tensors="pt",
            truncation=True,
            max_length=512,
            padding=True
        )
        with torch.no_grad():
            logits = self.model(**inputs).logits

        probs = torch.softmax(logits, dim=-1)[0]
        top_idx = probs.argmax().item()

        return {
            "type": self.DOCUMENT_TYPES[top_idx],
            "confidence": float(probs[top_idx]),
            "alternatives": [
                {"type": self.DOCUMENT_TYPES[i], "score": float(probs[i])}
                for i in probs.topk(3).indices.tolist()
                if i != top_idx
            ]
        }

[Incoming document]
PDF/scan/DOCX/email
         ↓
[Document Preprocessor]
OCR (Tesseract/Google Cloud Vision) → normalized text
         ↓
[AI Processing Pipeline]
  ├── Classification: document type
  ├── NER: counterparty, dates, amounts, details
  ├── Summary: brief content
  └── Routing: determine approval route
         ↓
[ECM API]
Create card + launch workflow

Requisites extraction: combination of NER and LLM

For quick extraction of standard fields (INN, dates, amounts) we use regex and NER. For complex cases — LLM (GPT-4o-mini or local LLaMA via LangChain). The combination yields 94% accuracy on real documents. For non-standard requests, we employ RAG with vector databases (ChromaDB, pgvector), allowing search across a database of previously processed documents.

from langchain_openai import ChatOpenAI
import re
from datetime import datetime

class DocumentExtractor:
    EXTRACTION_PROMPT = """Извлеки реквизиты из документа.

Текст документа:
{text}

Тип документа: {doc_type}

Извлеки (верни null если не найдено):
- contractor_name: название контрагента
- contractor_inn: ИНН контрагента
- contract_number: номер договора/счёта
- contract_date: дата документа (ISO 8601)
- total_amount: сумма (число)
- currency: валюта (RUB/USD/EUR)
- payment_deadline: срок оплаты (если есть)
- subject: предмет договора (1-2 предложения)
- signatory: подписант со стороны контрагента

Верни JSON."""

    def __init__(self):
        self.llm = ChatOpenAI(model="gpt-4o-mini", temperature=0)

    def extract_requisites(self, text: str, doc_type: str) -> dict:
        # Сначала быстрое regex-извлечение
        fast_extract = self._regex_extract(text)

        # LLM для пропущенных полей и валидации
        llm_result = self.llm.invoke(
            self.EXTRACTION_PROMPT.format(
                text=text[:3000],
                doc_type=doc_type
            )
        )

        import json
        llm_data = json.loads(llm_result.content)

        # Мерджим: regex имеет приоритет для числовых полей (точнее)
        return {**llm_data, **fast_extract}

    def _regex_extract(self, text: str) -> dict:
        result = {}

        # ИНН: 10 или 12 цифр
        inn_match = re.search(r'\bИНН[:\s]*(\d{10,12})\b', text)
        if inn_match:
            result["contractor_inn"] = inn_match.group(1)

        # Суммы с валютой
        amount_match = re.search(
            r'(\d[\d\s,]*\.?\d*)\s*(руб|рублей|RUB|USD|EUR)',
            text, re.IGNORECASE
        )
        if amount_match:
            amount_str = amount_match.group(1).replace(' ', '').replace(',', '.')
            result["total_amount"] = float(amount_str)

        return result

Integration with ECM: Directum, 1C, DocsVision

Integration is built through official REST APIs. Example for Directum: upload file, fill card, launch workflow. Similar logic for 1C:Document Management and DocsVision.

class SEDIntegration:
    """Интеграция с 1С:Документооборот, Directum, DocsVision"""

    def push_to_directum(self, extracted: dict, original_file: bytes) -> dict:
        """Создаёт карточку документа в Directum"""
        import requests

        # Загружаем файл
        upload_response = requests.post(
            f"{self.directum_url}/api/v1/documents",
            headers={"Authorization": f"Bearer {self.token}"},
            files={"file": original_file}
        )
        doc_id = upload_response.json()["id"]

        # Заполняем карточку
        card_response = requests.patch(
            f"{self.directum_url}/api/v1/documents/{doc_id}/properties",
            headers={"Authorization": f"Bearer {self.token}"},
            json={
                "DocumentType": extracted["type"],
                "Counterparty": extracted.get("contractor_name"),
                "INN": extracted.get("contractor_inn"),
                "Amount": extracted.get("total_amount"),
                "DocumentDate": extracted.get("contract_date"),
                "Subject": extracted.get("subject")
            }
        )

        # Запускаем маршрут согласования
        route = self._determine_route(extracted)
        requests.post(
            f"{self.directum_url}/api/v1/documents/{doc_id}/workflow/{route}",
            headers={"Authorization": f"Bearer {self.token}"}
        )

        return {"doc_id": doc_id, "route": route}

    def _determine_route(self, extracted: dict) -> str:
        """Определяет маршрут согласования по параметрам документа"""
        amount = extracted.get("total_amount", 0)
        doc_type = extracted.get("type", "")

        if doc_type == "договор":
            if amount > 1_000_000:
                return "contract_large"      # директор + юрист + финансы
            elif amount > 100_000:
                return "contract_medium"     # руководитель + юрист
            else:
                return "contract_standard"   # только руководитель
        elif doc_type == "счёт-фактура":
            return "invoice_approval"
        return "standard"

What's included: stages and results

We provide the full implementation cycle:

1. Document flow analysis — route schemas, document types, volume.
2. Model development — classifier and NER fine-tuning.
3. ECM integration — REST API, workflow setup.
4. Testing on real documents — up to 1000 instances.
5. Launch and operator training.

Deliverables:

• Architecture and API documentation.
• Access to trained models and code.
• Operator training on the system.
• Technical support for one year.

Typical mistakes in AI integration for document management

• Ignoring OCR quality. If scans are poor (resolution <150 DPI, creases), accuracy drops. Solution: image preprocessing — deskewing, binarization.
• One model for everything. Classification and NER require different architectures. Combining them in one model reduces accuracy for both tasks.
• No human-in-the-loop. Documents with confidence <0.8 should be checked by an operator. Otherwise errors propagate through the system.

Implementation results: case study and company metrics

Case study: a manufacturing company, 500 incoming documents per month. Before implementation: 2 operators spent 40% of their working time on manual requisites entry. After: automatic requisites extraction accuracy 94% (verified on 1000 documents), 89% of documents processed without operator intervention, operators handle only exceptions (confidence < 0.8) and disputed routes. Incoming document processing time decreased from 8 minutes to 45 seconds. Time savings — over 60 hours per month, equivalent to the cost of two operators.

We have completed over 20 AI integrations in ECM for companies with document flows ranging from 200 to 5000 documents per month. Team experience: 5+ years in NLP and MLOps. We use only licensed solutions and official APIs.

Contact us for a free evaluation of your project. Order a pilot processing of 100 documents — we will show accuracy on your data.