Turnkey digital employees for finance, legal, procurement, and operations

Digital employees and domain agents: reconciling contracts, primary records, estimates, and filings under the organization’s rules

The Autonomous Non-Profit Organization “Research Institute of System Synthesis” (the institute) builds digital employees—domain software assistants and autonomous agents for legal, financial, procurement, and operational work. Template bots built in visual workflow editors break on multi-page documents and invent non-existent legal provisions, so the institute builds its systems as a personal verification instrument and legal safeguard for the specialist on the job. The program takes over the routine reconciliation of contracts, primary accounting records, estimates and statutory filings inside the familiar working environment without retraining staff, keeps trade secrets inside the perimeter, and checks every action through the MITR gateway before execution.

The institute builds a digital assistant, an accounting contour, a link between systems, or a software agent under the organization’s rules; every action of the agent is checked before execution, and the work goes in five steps from the conversation to support.01 · WHAT IS BUILTBot, records, link, and agentbotdatalinkagentfrom simple to complexFirst the simplest thing that closes the task,and only then a software agent.02 · WHAT IS JUDGEDThe organization’s rulesRULE₽paymentrecordletterAn agent gets access only through a check ofevery action; rules and data stay with the customer.03 · HOW THE WORK GOESFive steps1conversation2survey3agreement4build and acceptance5supportEvery step is checked by an instrument rather thanby a report; the work keeps a log.The institute builds a digital assistant, an accounting contour, a link between systems, or a software agent under the organization’s rules; every action of the agent is checked before execution, and the work goes in five steps from the conversation to support.01 · WHAT IS BUILTBot, records, link, and agentbotdatalinkagentfrom simple to complexFirst the simplest thing that closes the task,and only then a software agent.02 · WHAT IS JUDGEDThe organization’s rulesRULE₽paymentrecordletterAn agent gets access only through a check ofevery action; rules and data stay with the customer.03 · HOW THE WORK GOESFive steps1conversation2survey3agreement4build and acceptance5supportEvery step is checked by an instrument rather thanby a report; the work keeps a log.
The institute builds a digital assistant, an accounting contour, a link between systems, or a software agent under the organization’s rules; every action of the agent is checked before execution, and the work goes in five steps from the conversation to support.

Operational risks and domain tasks brought to the institute

In practice business automation meets two obstacles: fragile visual workflows that fail on real multi-page documents and quiet resistance from domain specialists when a tool is presented as a means of surveillance or staff reduction. The institute addresses the task from the standpoint of the specialist and the executive responsible for a verifiable outcome.

Role in the organization Operational risk and routine What changes at the workplace
Legal counsel, litigator, head of legal Late-night review of forty-page counterparty contracts and opposing court filings takes hours, while general-purpose language models and plain vector search cannot tell an active statute from a repealed one, cite overturned appellate rulings and miss hidden penalties. Counsel sends a contract or pleading into the working contour and within twenty seconds receives an exact discrepancy summary naming the page and clause of any overturned ruling or hidden penalty, an exact state-duty calculation and a draft schedule of disagreements grounded in verified court acts.
Chief accountant, economist, chief financial officer Manual entry of details and line items from primary documents into the accounting system, manual recalculation of estimates and the risk of missing statutory filing deadlines in state registers (pledges, leasing, net assets, charter amendments) expose the accountant and director to fines and subsidiary liability under Article 61.11 of Federal Law No. 127-FZ of 26 October 2002 “On Insolvency (Bankruptcy)” and Article 53.1 of the Civil Code of the Russian Federation. The assistant reconciles every amount, tax rate, taxpayer identification number, registration number and fiscal receipt with the accounting database, flags arithmetic mismatches in estimates and prepares draft statutory disclosures ahead of deadline.
Procurement specialist, estimator, settlement clerk Line-by-line comparison of commercial proposals, technical specifications, bills of materials, item codes and complex returns dulls human attention by the end of the day and creates the risk of approving an inflated price or a substituted item. The program performs mechanical reconciliation of tables, unit prices and procurement or fiscal constraints, handing the specialist a verified posting draft and a clear list of deviations.
Business owner and chief executive officer Senior specialists burn out on mechanical routine, while improvised no-code workflows collapse as request volume grows, demand constant developer intervention and risk leaking trade secrets and personal data under Federal Law No. 152-FZ of 27 July 2006 “On Personal Data”. One domain expert equipped with a verified contour of assistants handles the workload of an entire department without expanding headcount; credentials to banking and accounting systems are never handed to the language model, and every action passes a check inside the perimeter.

Ready domain contours and work without changing habits

Staff do not need to learn new dashboards, study prompt writing or leave their familiar software because the assistant plugs into the existing environment. A specialist places incoming documents into a regular desktop folder, continues working inside the standard accounting or customer-relationship system, or forwards a file in a secure corporate messenger to receive a verification report and draft reply within half a minute. An organization can enable a ready domain contour or commission a custom build from simple to complex.

  1. Legal and litigation contour (for counsel and experts): checks counterparty contracts and pleadings within thirty seconds for hidden penalties and overturned court rulings, calculates state duty and assembles draft claims and discrepancy schedules without fabricated citations.
  2. Financial and registry contour (for accounting and finance teams): reconciles primary documents and estimates with the accounting database, tracks corporate events and prepares mandatory filings for state registers with an immutable verification log.
  3. Operational and settlement contour (for commercial teams and settlement desks): calculates multi-tier discounts and returns, reconciles invoices and waybills, and prepares fiscal receipts from a corporate chat or accounting system after checking every figure before posting.
  4. Procurement and infrastructure contour (for purchasing and engineering teams): compares commercial proposals, technical specifications and estimates line by line against price caps and stop factors, and in information infrastructure protects databases and servers from destructive commands by coding and operations agents.
  5. Custom build (a bot, corporate service, system link or specialized agent): when a ready contour is not enough, the institute builds the solution in steps from a reference assistant, internal service, or system integration up to an autonomous agent governed by the MITR pre-execution check, where every decision leaves a verifiable receipt.

Basic reference assistants and integrations are built with open tools and standard development means, while domain contours that touch databases and money rest on the pre-execution verification core set out on the page MITR.


How the work goes

Step What happens
Conversation The task is named: what costs time or money and what the result should be. That is enough for a first letter.
Survey Which systems take part, which actions are irreversible, who signs the rules, what counts as acceptance. The survey yields the scope, the timing and the price.
Agreement An agreement with the institute: scope, acceptance procedure, timing, support.
Build and acceptance Every step is checked by an instrument rather than by a report; the work has a log; acceptance runs on the customer’s own examples.
Support Under the agreement: rules and data stay with the customer, and changes are made by the log.

Rules, data, keys to the systems and the log of the work stay with the customer. What exactly stays with the customer when MITR is installed is set out on the page A pilot of MITR at a customer.


What already works

  • The institute’s own setup. Development, checking and record keeping at the institute are done by software agents under the same rules that are offered to a customer, and their actions pass through MITR: 3,877 checks of coding-agent commands, 623 calls from services and 30 requests over the Model Context Protocol as of 25 October 2026. How this is organized is told on the page Institute.
  • Legal services. The judicial-decision analysis portal sudfact.ru in the Judicial Fact Registry (SUDFACT) holds 14,899 court acts as of 25 October 2026, and the state-duty calculator computes the duty under the Tax Code of the Russian Federation (both in Russian). Both were built and are run in the way offered to a customer.
  • Open tools. The packages mcp-sentinel, iss-ledger-117 and iss-agent-kit under the Apache-2.0 license install without a network; the customer’s engineer sees the method on his own examples before any agreement (packages and checksums).

Scope and assumptions

  • Timing or price before the survey: they depend on the systems involved and on which actions are irreversible.
  • That a neural network does not make mistakes. The program’s action is checked, not its text; a mistake in text remains possible, a mistake in action is stopped by a rule.
  • Replacing people. The program takes over execution; decisions, the signing of rules and responsibility stay with the organization’s people.
  • Certification. Internal automation does not require it; at significant objects of critical information infrastructure the established procedure applies, and this work does not replace it.

Contact

A conversation about a task starts with a letter to af@isslab.ai or a message to the scientific director in Telegram, @afishchuk, with the subject “Automation”. In a first message it is enough to name what takes the time and what the result should be. Correspondence is in English or Russian.

Autonomous Non-Profit Organization (ANO) “Research Institute of System Synthesis”, edition of 11 November 2026. This page is for information and is not a public offer: the scope and terms of work are set by an agreement.