Bitrix24 for 223-FZ Procurement: Practical Setup Guide

Procurement Department Drowning in Excel

Procurement under Federal Law No. 223-FZ requires strict adherence to deadlines — missing a deadline can result in fines of up to 300,000 rubles. Bitrix24 can become a single center for procurement management, but without proper configuration it's just another tracking tool. We share practical experience: how to turn Bitrix24 into a procurement coordinator, reduce the load on the department, and eliminate human error. Automation pays off in 3–4 months, reducing late submissions by 70% and approval costs by 30%.

Why Bitrix24 Doesn't Cope 'Out of the Box'

Out-of-the-box Bitrix24 does not account for 223-FZ specifics: strict deadlines, special procedure stages, need for protocol generation, and interaction with the Unified Information System (EIS). Therefore, setup requires customization of CRM, business processes, and access rights. A properly configured system is a full-fledged procurement coordinator; without configuration, it's just a mailbox for emails.

What Is Configured in Bitrix24 for 223-FZ

CRM for Procurement Procedures

Each procurement is a deal in CRM. Pipeline stages correspond to procedure phases:

• Procurement Planning → Plan Publication → Documentation Preparation → Notice Publication → Bid Acceptance → Bid Review → Winner Determination → Contract Signing → Execution → Archive

Custom deal fields: PURCHASE_PROCEDURE (list: request for quotations, request for proposals, tender, auction), INITIAL_PRICE (number), PROCUREMENT_SUBJECT (string), EIS_NUMBER (string), BID_SUBMISSION_DEADLINE (date), FINANCING (list: 44-FZ / 223-FZ / commercial).

Automation via Business Processes

Bitrix24 robots trigger on deal stage transitions:

• When moving to the 'Notice Publication' stage: task for the lawyer 'Check documentation', task for the responsible person 'Publish on EIS'
• 3 days before BID_SUBMISSION_DEADLINE: notification to the commission
• When moving to the 'Contract Signing' stage: task for contract approval via approval route

Document Templates

Bitrix24 generates standard documents (review protocol, evaluation protocol) from Word templates filling fields from CRM using macros like {DEAL.FIELD_NAME}.

How to Organize Procurement Document Storage?

Documents are stored on Bitrix24 Drive in folders linked to the deal. Folder structure:

Procurement/ └── Current Year/ └── ZK-Current Number Server Equipment Supply/ ├── 01_Planning/ ├── 02_Documentation/ ├── 03_Participant_Bids/ ├── 04_Protocols/ └── 05_Contract/ 

Folder permissions are assigned automatically via business process when creating a deal: the responsible person and commission get access, others do not.

How Does Bitrix24 Control Deadlines?

223-FZ deadlines are strict: for example, for a request for quotations, the publication period must be at least 5 working days. Bitrix24 manages deadlines through:

• Date-type fields in deals with automatic deadline calculation via formulas
• Tasks with deadlines linked to the deal
• Notifications N days before deadline via robots

Bitrix24 calculates working days (as opposed to calendar days) considering the production calendar — this is critical for correct 223-FZ deadline calculation. Automatic deadline control reduces late submissions by 70%.

Compare: in Excel, average time per procurement is 8 hours; with configured Bitrix24, it's 2–3 hours. A 3–4x difference. This is achieved through automatic notifications, clear task routing, and a unified document base.

What Is Included in Bitrix24 Setup for 223-FZ?

Full deliverables include: setup documentation (pipeline description, user guides), system access, employee training, and warranty support. Get in touch with our engineers — they will design a solution tailored to your regulations.

Limitations and What Is Configured Outside Bitrix24

Bitrix24 does not replace specialized systems for EIS interaction. Publishing notices and documentation on zakupki.gov.ru is done through the EIS personal account with an electronic signature — that's an external tool. Bitrix24 only stores the publication fact (date, EIS number) as a deal field and a confirmation task.

For organizations with high procurement volume (50+ procedures per year), it is recommended to use a specialized module or integration with systems like 'Kontur.Zakupki', 'Tenderplan', RTS-tender — with data transfer to Bitrix24 via REST API for team coordination.

Setup Timelines

A properly configured Bitrix24 for 223-FZ reduces the risk of missed deadlines, provides a history of each procurement, and gives management an overview of all active procedures. Order a consultation on setup — our engineers will design the pipeline, configure business processes, and conduct training, ensuring stable operation.