EDI in 1C for a Food Holding: SBIS Inside 1C

A large manufacturing and trading holding from the food industry came to our partners.

The company combines several plants, a network of distribution warehouses, and a wholesale division.

The business operates in a B2B model: tens of thousands of counterparties across the country, and hundreds of primary documents per day.

Accounting is kept in 1C:Enterprise 8, warehouse operations run in a WMS system, and primary documents are sent and received through EDI operators.

Company leadership set the task of moving all primary document workflows to digital form, speeding up interactions with suppliers and customers, reducing paper and courier costs, and eliminating the errors and delays that are inevitable with manual work.

Before the project began, the processes were typical of large CIS enterprises:

Manual handling of source documents. Invoices, delivery notes, and service completion acts were issued on paper.

Scans were filed into folders, and details were entered into 1C manually. Human error often led to mistakes in the details, with the amount, VAT, or date entered incorrectly.

Fixing errors took days, and document returns took weeks.

Each department worked on its own version of 1C with minimal configuration.

Differences in configurations meant that document standards, tax calculation methods, and even form layouts could vary.

Approving a document between departments turned into an exchange of files by email.

Documents were sent through different EDI operators.

Employees learned signing and approval statuses by logging into a specific operator's personal account or calling the counterparty.

This created chaos: month-end closing was delayed, and accounting could not tell which documents were already signed and which were still in progress.

The emergence of the Chestny Znak and Mercury traceability systems, mandatory labeling, and remote legally binding document signing all required constant IT system updates.

Some external services could not keep up with legal changes.

Knowing that no single universal solution can solve everything, the project team chose a comprehensive approach.

Our partners implemented the SBIS for 1C:Document Management module and at the same time carried out a deep process reorganization.

This module is an official extension from the developers, installed in 1C without removing support.

It adds new electronic document capabilities to the familiar 1C interface:

Each package received from SBIS automatically creates the corresponding document in 1C: an invoice, delivery note, UTD, or contract. The document card pulls in the main printable form, the linked XML file, and, if needed, an archive with attachments.

This archive can be downloaded directly from 1C without logging into the operator's personal account.

Now an accountant or manager prepares the document in 1C and sends it immediately through SBIS.

Both structured forms (UPD, invoice) and unstructured forms are supported.

A document can be created from an XML file attached to the internal record: the lawyer prepares the contract in their template, and the system automatically generates the XML and sends it to the counterparty.

The module supports bulk signing and mass processing of incoming packages.

This matters when 30 to 40 documents arrive every day from one supplier: the operator can process the whole batch in one go, and the manager can sign it with an electronic signature right away.

The 1C document card shows EDI status and counterparty status: "sent," "signed," "returned," and so on.

In addition, the card can store the digital signature, printable forms, and the full archive.

All of this is available to 1C users without going to the operator's website.

The system can automatically create tasks in 1C when a counterparty's status changes, create new counterparties when a document is received, and support multiple companies in a single database.

Our partners understood that a technical tool is only part of success.

That is why the project went through several mandatory stages:

First, the consulting team interviewed accountants, lawyers, and procurement and sales managers.

We mapped each document's path from creation to posting and analysis, identified bottlenecks, unclear roles, and duplicate operations.

This stage made it possible to create a single policy: which attributes are mandatory, who may sign the document, and how quickly approval must move.

The SBIS module was installed as an extension in the current 1C configuration.

We configured document templates, approval workflows, and auto-fill rules for fields such as supplier, company, and VAT, then defined user permissions and separated roles: who can create, who approves, and who signs.

We created instructions for administrators and users.

Integration with ERP and external systems.

Because the holding used several 1C modules (enterprise management, accounting, and warehouse management), our partners set up bidirectional data exchange between them.

We connected the SBIS module with the existing WMS and CRM systems so order and delivery statuses would update automatically.

Together with the IT team, we centralized the issuance of qualified electronic signatures for all departments.

We organized certificate storage, set up access rights for signing, and created a backup procedure.

Now managers can sign document batches in 1C in a couple of minutes without going to the operator's website.

We held a series of online training sessions for accountants, lawyers, and logistics specialists. We showed how to create and send documents, track statuses, invite counterparties, and work with archives.

Implementing the module and reorganizing processes led to clear financial and organizational benefits:

Eliminate manual entry and reduce errors.

Automatic field completion and automatic status synchronization reduced errors in primary documents.

If the accounting team used to correct dozens of invoices every Friday because of incorrect taxpayer IDs or amounts, now errors in details have almost disappeared.

All documents are stored in the 1C database, and archives are available from the document card with one click.

Lawyers and auditors no longer have to run around departments looking for a missing acceptance certificate, and inspectors receive the required document set in a minute.

New requirements, including labeling and Mercury,

Chestny Znak is integrated into 1C, and the SBIS module serves as the communication channel with operators.

The company no longer waits for updates from external services and instead configures the required forms and reports itself.

Any IT project in a large organization faces resistance and surprises.

Here are the main problems and how they were solved:

Fragmented 1C versions and custom-built software. Companies often customize 1C for their own needs, which makes integration more difficult.

Our partners created universal exchange points, identified key objects (documents, reference data), and wrote extensions for each configuration.

For highly custom-built configurations, adaptation took two months.

Counterparties' reluctance to join EDI.

Some suppliers refused to register in SBIS.

We developed automatic invitation mailings, prepared instructions, and even recorded a video, How to connect to our EDI.

Managers called large companies separately.

Usually within 3-4 weeks, most partners switched to exchange.

The item master directories for suppliers and customers did not match.

We developed a mechanism for automatic matching and regular synchronization.

During implementation, we imported existing reference data from suppliers' files, and when an incoming document was received, the system matched an equivalent by code or name, after which the item card was automatically created in 1C.

The project resulted not only in lower costs and less time spent.

The integration of 1C and SBIS gave the company strategic advantages:

A single interface for all documents.

Employees work in their familiar 1C environment: they prepare and sign documents, invite counterparties, and track statuses.

No need to open additional web portals.

Automatic exchange and status synchronization reduced the number of errors.

The system checks the taxpayer ID, registration reason code, and other details, matches the item master, and applies VAT.

Management sees the situation in real time: how many documents are in progress, whose approvals are stalled, and which suppliers most often delay signing.

This speeds up management decision-making.

Flexibility when legislation changes.

Any changes to document formats, the appearance of new reporting types, and traceability systems are implemented on the 1C side.

The SBIS module serves as a communication channel and does not limit functionality.

Easy scaling. In the future, new departments, subsidiaries, branches, and even independent partners can be connected to the system.

It is enough to issue them an electronic signature and configure the exchange rules.

"What worried us most was resistance from employees and counterparties.

But thanks to executive support, clear instructions, and precise procedures, resistance quickly faded.

People realized it had become easier: they no longer run to the archive or search for signatures, but sit in one window and see everything happening with the documents.

We also gained strong experience in automatic item matching and reference data synchronization, which we now use in other projects. What mattered was that we did not just bolt on a module, but changed how people work with documents.

This is important for the company's digital future

The project does not end with the module implementation. The company has ambitious plans:

Implement mobile apps for managers and couriers so they can sign documents and confirm receipt of goods on a tablet or smartphone.

Expand the link between EDI and CRM so the sales funnel automatically accounts for document signing events.

Data analysis in a BI system will help identify bottlenecks in interactions with specific