Setting Up Expense Approval via Bitrix24
We often see a familiar picture: a manager pays for a taxi to a client out of their own pocket, takes a photo of the receipt, and sends it to the accountant in chat with a note 'reimburse me'. The accountant loses the message among dozens of others. Two weeks later, the manager reminds them; the accountant searches for the receipt in the conversation, doesn't find it, and asks to send it again. Expenses without a system mean lost documents, an opaque budget, and constant conflicts. In companies with 20+ employees, manual expense processing takes up to 5 hours per week — time that could be spent on business development.
Our experience shows: automating expense approval in Bitrix24 solves this problem in 2–3 days of setup. We have implemented such projects for 50+ companies — from retail to IT. In this article, we'll break down how to build a transparent process: from request submission to accounting report.
Structure of the Approval Process
Expense approval in Bitrix24 is built on a smart process or a list with a business process. Each expense is a separate card with fields:
-
Amount — numeric field with limit checking
-
Expense Category — directory: transport, entertainment, office supplies, subscriptions, equipment
-
Description — text field with justification
-
Receipt/Invoice — file field for attaching scans
-
Expense Date
-
Project/Department — link for analytics
How to Set Up Approval Routes?
The route depends on the amount and expense category. Below is a table of basic rules:
| Amount |
Route |
| Low |
Department head → Accounting |
| Medium |
Department head → Financial director → Accounting |
| High |
Department head → Financial director → CEO → Accounting |
Threshold amounts and routes are configured in the business process designer. Conditional branches determine who receives the request at each step. Each approver sees the expense card with the receipt and can: approve (the request moves to the next), reject (return to author with a comment), or return for revision (author corrects and resubmits). For more on designing business processes, see helpdesk.bitrix24.ru.
Why Is It Important to Set Budget Limits?
For each department or project, a monthly budget is set by expense category. When a request is submitted, the business process checks whether the limit for the category in the current month is exceeded. If exceeded, the request still goes for approval but with a note 'Budget exceeded'. The approver makes a decision with this information in mind. The current expense budget is visible to the manager in the report: spent / remaining for each category.
| Category |
Typical Budget |
Exceeding Frequency |
| Transport |
Varies |
15% of requests |
| Office supplies |
Varies |
5% |
| Entertainment |
Varies |
20% |
Attaching Documents
The employee attaches a photo of the receipt or invoice scan directly into the expense card. The file is saved on Bitrix24 Drive in a structured folder: Expenses / Current Year / Month / Last Name. Accounting receives all documents in one place — no need to collect from chats and email.
Reporting
Management and accounting see:
- Expense summary — by period, department, category.
- Request status — how many are pending, approved, rejected.
- Budget — actual vs. plan for each department and category.
- Average approval time — to identify bottlenecks.
What Is Included in the Work
We provide a complete package:
- Setting up a smart process with custom fields.
- Designing approval routes with conditional branches.
- Budget limits with automatic checking.
- Drive integration for receipt storage.
- Notifications, deadlines, escalations.
- Ready-made expense and budget reports.
- Employee training (1 hour).
- Written process documentation.
We guarantee setup within 3 business days. Experience: 10+ years, over 100 projects.
How We Do It: Step by Step
- Analyze current process and expense types.
- Design smart process and business process scheme.
- Configure fields, routes, budgets.
- Test on sample requests.
- Train the team.
- Hand over for operation with support.
Comparison: approval via Bitrix24 processes requests 3 times faster than manual correspondence, and the number of lost receipts approaches zero.
Case Study: Setup for a Coffee Chain
For one chain of 20 locations, we set up a hybrid route: operational expenses (coffee, milk) were approved by location managers with a fixed budget, while entertainment expenses were approved by the central office. The problem was that baristas often purchased inventory without approval. After implementing a smart process with a mandatory 'Receipt' field and a limit per category, the number of unapproved purchases dropped by 90%. The solution took 2 days, including training 20 employees.
How to Evaluate Automation Efficiency?
Implementing an expense approval system in Bitrix24 yields measurable results. In a company with 50 employees, manual expense processing took 2 hours per day. After setting up the process, the time dropped to 15 minutes — 8 times faster. After a month, accounting noted a complete disappearance of lost receipts. Such indicators are achieved through clear routes and automatic notifications.
If you want to establish transparent expense accounting and eliminate chaos — according to Bitrix24 documentation, setup is available via REST API. Contact us for a consultation. Request a detailed implementation plan, and we will assess your process in one day.
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.
