Setting up procurement (Federal Law 223) via Bitrix24

Procurement (Law 223-FZ) Setup in Bitrix24

Companies subject to Law 223-FZ must publish procurements on EIS (zakupki.gov.ru), maintain procurement plans, reports and protocols. The procurement department works in their own spreadsheets, correspondence, sometimes in 1C. Bitrix24 itself is not a specialized 223-FZ system, but can become the coordination hub of the process: structure tasks, store documents, control deadlines, and serve as interface between procurement and legal teams.

What is Configured in Bitrix24 for 223-FZ

CRM for Procurement Procedures. Each procurement is a deal in CRM. Funnel stages match procedure stages:

• Planning → Plan Publication → Documentation Preparation → Notice Publication → Application Receipt → Application Review → Winner Selection → Contract Conclusion → Execution → Archive

Custom deal fields: PROCUREMENT_PROCEDURE (list: request for quotes, request for proposals, competition, auction), INITIAL_PRICE (number), PROCUREMENT_SUBJECT (string), EIS_NUMBER (string), APPLICATION_DEADLINE (date), FINANCING (list: 44-FZ / 223-FZ / commercial).

Automation via Business Processes. Bitrix24 robots run when deals transition stages:

• When transitioning to "Notice Publication" stage: task for lawyer "Review documentation," task for responsible "Publish on EIS"
• 3 days before APPLICATION_DEADLINE: commission notification
• When transitioning to "Contract Conclusion" stage: task to approve contract via approval route

Documents by Templates. Bitrix24 generates standard documents (review protocol, evaluation protocol) from Word templates with field population from CRM via macros {DEAL.FIELD_NAME}.

Storing Procurement Documentation

Procurement documents are stored in Bitrix24 disk in folders tied to deal. Folder structure:

Procurements/
└── 2025/
    └── ZK-2025-042 Server Equipment Supply/
        ├── 01_Planning/
        ├── 02_Documentation/
        ├── 03_Participant_Applications/
        ├── 04_Protocols/
        └── 05_Contract/

Folder rights are assigned automatically via business process on deal creation: responsible and commission get access, others don't.

Timeline Control

Timelines in 223-FZ are strict: e.g., for request for quotes, publication period must be at least 5 business days. Bitrix24 manages timelines via:

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

Business days (unlike calendar days) Bitrix24 calculates accounting for production calendar — critical for correct 223-FZ timeline calculation.

Limitations and What is Configured Outside Bitrix24

Bitrix24 doesn't replace specialized EIS systems. Notice and documentation publication on zakupki.gov.ru happens via EIS personal account with digital signature — this is external tool. Bitrix24 only stores publication fact (date, IKZ number) as deal field and confirmation task.

For organizations with large procurement volume (50+ procedures yearly), use specialized module or integration with systems like "Kontur.Zakupki," "Tenderplan," RTS-tender — with data transmission to Bitrix24 via API for team coordination.

Setup Timeline

Configured Bitrix24 for 223-FZ reduces deadline miss risk, provides procurement history, gives management summary of all active procedures without asking each executor.