Bitrix24 Integration with EIS (Unified Procurement Information System)
Every morning, a manager manually logs into zakupki.gov.ru, searches for tenders by keywords, copies data into a spreadsheet, and then creates a deal in CRM. At the same time, they need to monitor submission deadlines, prepare documents, and track results. One missed tender means a lost contract. One missed deadline means lost bid security, which can range from 200,000 to 1 million rubles. We automate this process: Bitrix24 integration with EIS handles monitoring, deal creation, and deadline control. By our estimates, savings on missed contracts and penalties reach 2 million rubles per year.
How the Integration Works
The integration uses open data from zakupki.gov.ru — XML feeds that the EIS publishes daily. The data collector downloads the files, parses them, and filters them according to your criteria. Matching procurements become Bitrix24 deals with a full card: number, amount, customer, deadlines, type. Then comes the tender sales pipeline, notifications, and analytics.
Data Collection and Parsing
| Source |
Format |
Update Frequency |
| EIS Open Data |
XML |
Daily |
| FTP Archives |
ZIP/XML |
Scheduled |
| Web Interface (fallback) |
HTML |
As needed |
The collector downloads archives, unpacks them, and parses the XML. For each procurement, it extracts: registry number, name, NMCC, OKPD2, customer (with TIN and region), deadlines, procurement type (44-FZ or 223-FZ), security requirements, and links to documentation. Processing one procurement takes less than a second, and the system handles peak loads of up to 1,000 tenders per day.
How to Configure Tender Filtering?
Without a filter, everything ends up in CRM — thousands of irrelevant procurements. We set up flexible selection rules:
- OKPD2 — a list of codes for your products/services.
- Keywords — in the name and description.
- Region — by delivery or customer location.
- NMCC — a range from minimum to maximum amount.
- Procurement type — only auctions, requests for quotations, etc.
- Exclusions — stop words, undesirable customers.
The settings are stored in the middleware configuration and can be edited without stopping the integration. The average filter reduces the flow by 80–90%.
Example of OKPD2 Filter Configuration
If a company sells office furniture, the filter includes codes 31.0 (furniture) and 95.24.10 (furniture repair). It excludes codes 16.29 (wooden products) and 28.49 (machine tools). The configuration is done through a list in a Bitrix24 user directory.
Creating Deals and the Pipeline
Each matching tender becomes a CRM deal:
- Name — procurement number + short description.
- Amount — NMCC.
- Contact/Company — customer (search by TIN, create if missing).
- Custom fields — registry number, procurement type, OKPD2, end date, security, link to EIS.
- Stage — "New Tender" (first pipeline stage).
- Responsible person — assigned by region or type.
Deduplication prevents duplicates: if a procurement already exists in CRM, only fields are updated (deadlines, documentation). The pipeline consists of stages: Analysis → Bid Preparation → Bid Submitted → Evaluation → Win/Loss → Contract. Each stage may require mandatory fields (e.g., offer price).
Compared to manual monitoring, the integration reduces search and data entry time by 10 times, and copy errors are reduced by 95%. That's 15 times faster than hiring an additional manager for the same work.
How Does the Integration Help Control Deadlines?
Missing a bid submission deadline means losing a contract and the bid security. The integration creates reminder tasks:
- 5 days before — notification to the responsible person.
- 2 days before — repeat notification + to the manager.
- 1 day before — urgent notification in the general chat.
- Deadline passed — the deal is automatically moved to "Overdue" (if the bid hasn't been submitted).
All deadlines are synchronized with the Bitrix24 calendar. Configured via business processes or middleware. You can read more about business processes in the official documentation.
What's Included in the Work
- Configuring the EIS data parser (source selection, schedule).
- Configuring filters according to your product range and regions.
- Creating a tender sales pipeline and custom fields.
- Configuring business processes for deadline control and notifications.
- Generating document templates (bid, commercial proposal).
- Training for employees (2–3 hours).
- Technical documentation and 1 month of support.
Our team has 10+ years of experience in Bitrix24 integrations with EIS and other government systems. We have completed over 40 projects for tender departments of various sizes.
Analytics: What Drives Wins
Based on CRM data, we build reports:
| Metric |
What It Provides |
| Conversion by procurement type |
Identify the most "passable" auctions |
| Average discount from NMCC |
Adjust pricing strategy |
| Department workload |
Redistribute tenders among managers |
| Top customers |
Strengthen work with repeat clients |
The integration collects evaluation results from EIS, records wins and losses. Analytics helps increase conversion by 15–20% in a month.
How to Get Started
We tailor the architecture to the specifics of your procurements: from monitoring a narrow OKPD2 to a full tender department with a pipeline, deadlines, and dashboards. Contact us to discuss details and see a demo on your data. Get a consultation on automating your tender department.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.