Setting Up Bitrix24 for Non-Resident Clients

When a company starts working with foreign clients or suppliers, Bitrix24 'out of the box' immediately shows problems: no fields for VAT Number, VAT is incorrectly calculated for other countries' rates, company requisites cannot accommodate foreign address formats, and invoices are issued only in rubles without considering currency legislation?

We configure Bitrix24 for international tasks, and these problems are solved by configuration, not by custom development from scratch. Our experience is over 7 years and 50+ projects for companies working with counterparties from the EU, Asia, and the USA. Standard configuration is 3–5 times more budget-efficient and 2 times faster compared to custom development. We guarantee correct operation of all modules.

How to set up multi-currency for non-residents?

The first step is to enable the necessary currencies. In Bitrix24, this is done via CRM → Settings → Currencies. For each currency, set the rate (fixed or automatic via the Central Bank), symbol, symbol position, and separators. Automatic rate updates are configured through agents (b_agent). Bitrix can pull rates from the Central Bank of Russia website using the currency module — method CCurrencyRates::UpdateRates(). For non-residents from the EU or USA, this works fine: EUR, USD, GBP are always in the CBR reference. For currencies outside the reference (e.g., tenge, yuan), uploading via REST API or manual input is possible. In practice, 70% of clients use automatic rates, the rest use fixed rates for stability.

CAgent::AddAgent(
    "CCurrencyRates::UpdateRates('USD');",
    "currency",
    "N",
    86400,
    "",
    "Y",
    \ConvertTimeStamp(time()+86400, 'FULL')
);

What requisites and taxes are needed?

To work with non-residents, you need a payer type 'Foreign Company'. In the standard Bitrix24 package, it is not available — only individuals and legal entities (Russian). The payer type is added via CRM → Settings → Requisites → Payer types. Create a new type, e.g., COMPANY_FOREIGN, and add the necessary fields: VAT Number / Tax ID, Country of Incorporation (reference ISO 3166), IBAN / SWIFT, Legal Address (in free format). Requisite fields are stored in b_crm_requisite (the requisite itself) and b_crm_requisite_address (address). Additional custom fields are created via user fields (UF) with the prefix UF_.

Determining the VAT rate for non-residents is a key task. According to the Russian Tax Code, when exporting services in B2B, the VAT rate is 0% (clause 1 article 164 of the Tax Code of the Russian Federation). In Bitrix24, you need to create a separate tax rate '0% VAT (export)' and link it to goods/services sold to non-residents. CRM → Settings → Tax rates → add the appropriate rate. When creating a deal or invoice with a non-resident, the manager selects this rate. You can automate the selection via a business process: if the client's country ≠ Russia, automatically apply 0% rate.

How to issue invoices in English?

Invoices and acts for non-residents need to be issued in English (or the client's language). Bitrix24 supports multilingual documents through CRM → Document templates. For foreign counterparties, create a separate set of templates: Invoice, Service Completion Certificate / Act, Contract template. In the templates, use the same placeholders ({COMPANY_NAME}, {DEAL_CURRENCY_SUM}, etc.), but the static text blocks should be in English. For the currency field, ensure that {DEAL_CURRENCY} outputs the ISO code (USD, EUR) and not 'руб.'.

Why do you need a separate sales funnel for international clients?

We recommend creating a separate funnel for non-residents. This allows you to configure separate mandatory fields (VAT Number, country), assign responsible managers working with international clients, set up triggers and business processes, and view conversion for the international direction separately from the domestic market. The funnel is created in CRM → Settings → Sales funnels and tunnels. Stages are standard, but considering specifics: add a Compliance check stage and a Contract signing stage. The average conversion rate for international deals after such setup increases by 40%.

Contacts and access rights

Foreign individuals have different name formats — middle name is absent. Add fields Last Name, First Name and hide the middle name for the corresponding contact type. Phone numbers should be in international format E.164 (+49..., +1...). Access rights are configured with a separate role: if client data is sensitive (GDPR requirements), restrict visibility of requisites only to responsible managers and the supervisor.

How is Bitrix24 configured for non-residents?

1. Audit of the current CRM and identification of needs for international work.
2. Configuration of currencies, rates, payer type, and tax rates.
3. Creation of document templates in English.
4. Development of a sales funnel and business processes (automatic VAT selection, counterparty verification).
5. Configuration of access rights and custom fields.
6. Training managers to work with international deals.

What's included in the work

• Full configuration of currencies and rates (automatic or fixed).
• Creation of the 'Foreign Company' payer type with custom fields.
• Configuration of 0% VAT rates and automation of their selection via business processes.
• Development of document templates in English (invoices, acts).
• Creation of a separate funnel for non-residents with Compliance check and Contract signing stages.
• Configuration of access rights in accordance with GDPR.
• Documentation of all changes and handover of instructions.
• Support for 30 days after completion.

Setup timelines

All work is carried out turnkey with a guarantee of correct operation. Configuration using built-in tools saves up to 80% of the budget compared to developing custom modules. Contact us for a detailed consultation on your project — we will take into account the specifics of your counterparties and countries.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.