Automating Invoice Issuance in 1C-Bitrix: Turnkey Setup

Introduction – The Pain Point

Imagine a manager spending 30 minutes manually creating an invoice in Word, then losing it in email correspondence — and the client never pays on time. In B2B sales, this is critical: without an invoice, the accountant won't process the payment. We've seen dozens of projects where automating document flow shortened the deal cycle by 2-3 days. Setting up a proper invoicing system is the first step toward financial discipline.

We often encounter clients losing deals simply because the invoice wasn't issued on time or arrived in the wrong format. In B2B, without an invoice the deal stalls: the accountant needs a documented basis for payment. Configuring correct document flow is one of the first tasks when launching an online store on Bitrix. In our practice, we've automated this process for over 60 projects, saving clients an average of $1,500 per month in manual work.

Problems We Solve

• Manual generation: Managers spend hours creating invoices in Word or Excel, making errors in details. A custom solution reduces this time by 80%.
• Lost documents: Invoices get stuck in email threads, never reaching the accounting department. Automated sending eliminates this issue.
• Numbering conflicts: When multiple managers work in parallel, duplicate numbers appear, violating tax regulations. Our custom numbering avoids duplicates.
• No online payment: Clients can't pay immediately via a link — the deal drags on. Adding a payment link speeds up payment by 2 days on average.

Consider: the standard Bitrix24 solution delivers 80% of functionality in 1 day, while a custom system gives 100% control but requires 3–5 days of development. A custom solution is 3 times more flexible than the standard one, especially if you work with dozens of legal entities and multiple currencies.

How We Issue Invoices in Bitrix24

Bitrix24 CRM has a built-in invoice module. A manager creates an invoice directly in CRM, links it to a deal, and sends it to the buyer via email. Payment is processed through the built-in acquiring (Tinkoff, Sberbank, YooKassa) or by bank details. To get started, you need:

• Configure the invoice template (company details, logo)
• Connect a payment system
• Set up automatic sending at a certain deal status

Basic setup takes half a day and costs from $500. If integration with 1C is needed, add another day ($800).

When a Custom Invoicing System Is Needed

On a regular website (not Bitrix24), there is no built-in invoice module. If you have an online store on the Bitrix "Small Business" or "Business" edition without CRM, you'll need to build a custom system based on the Sale module. This is justified when:

• Non-standard numbering is required (e.g., branch prefix)
• A custom PDF template with INN/KPP/bank account fields is needed
• Integration with external accounting (1C, MyWarehouse) is required

For storing custom invoice templates, we use infoblocks v2.0, and for flexible settings — HL-blocks. This allows quick adaptation to changes in legislation.

Why Correct Invoice Numbering Matters

Tax authorities and accounting require sequential numbering without gaps. In Bitrix24, an invoice gets a number automatically, but when exchanging with 1C via CommerceML, conflicts can arise. We implement reliable numbering through our own table:

CREATE TABLE b_invoices (
    id              SERIAL PRIMARY KEY,
    order_id        INT REFERENCES b_sale_order(ID),
    invoice_number  VARCHAR(32) UNIQUE NOT NULL,  -- FS-{year}-00123
    user_id         INT,
    company_name    VARCHAR(256),
    inn             VARCHAR(12),
    kpp             VARCHAR(9),
    legal_address   TEXT,
    amount          DECIMAL(10,2),
    currency        CHAR(3) DEFAULT 'RUB',
    status          VARCHAR(16) DEFAULT 'draft',  -- draft|sent|paid|cancelled
    due_date        DATE,
    paid_at         TIMESTAMP,
    created_at      TIMESTAMP DEFAULT NOW()
);

Generating the PDF invoice using mPDF is 2x faster than alternatives:

function generateInvoicePdf(array $invoice, array $orderItems): string
{
    $mpdf = new Mpdf\Mpdf(['mode' => 'utf-8', 'format' => 'A4']);

    $html = renderInvoiceTemplate($invoice, $orderItems);
    $mpdf->WriteHTML($html);

    $path = DOCUMENT_ROOT . '/upload/invoices/invoice_' . $invoice['id'] . '.pdf';
    $mpdf->Output($path, 'F');

    return $path;
}

Numbering with a year prefix and sequential number:

function nextInvoiceNumber(): string
{
    $db = Bitrix\Main\Application::getConnection();
    $year = date('Y');

    $last = $db->queryScalar("
        SELECT MAX(CAST(SPLIT_PART(invoice_number, '-', 3) AS INT))
        FROM b_invoices
        WHERE invoice_number LIKE 'FS-" . $year . "-%'
    ");

    $next = ((int)$last + 1);
    return sprintf('FS-%d-%05d', $year, $next);
}

The PDF template is fully customizable: we add the logo, INN/KPP fields, bank details. The file is saved on the server and automatically sent to the client. We can also configure cloud storage or integration with EDO.

Step-by-Step Invoice Setup Process

1. Audit of current documents and requirements.
2. Choice of solution: standard CRM or custom. The custom solution is a faster implementation for complex needs.
3. Invoice template setup (details, logo, PDF).
4. Payment gateway connection (YooKassa, Tinkoff, Sber).
5. Automatic email sending based on deal status.
6. 1C integration via CommerceML (if needed).
7. Testing of numbering, sending, and payment.

What's Included in Turnkey Setup

We offer a comprehensive "Invoices in Bitrix Turnkey" service:

• Audit of current document flow
• Designing invoice structure (fields, numbering, templates)
• Developing/configuring the module (CRM or custom)
• Integration with payment systems (YooKassa, Tinkoff, Sber)
• PDF generation with customization options
• Automatic email sending setup
• 1C integration via CommerceML (invoice exchange)
• Documentation and manager training

Comparison: Standard vs Custom Solution

A custom solution is 3 times more flexible and can save significant time in reduced manual work.

Guarantees

We guarantee stable system operation: all invoices are numbered without duplicates, PDF files open correctly in any viewer. Our specialists are Bitrix-certified, with over 8 years of platform experience. For additional information, refer to the official 1C-Bitrix documentation.

Want a consultation on invoice setup? Order an audit, and we'll propose the optimal solution. Contact us for a free consultation — we'll find a solution that fits your budget and tasks.

How can you avoid typical mistakes when connecting payment systems on 1C-Bitrix?

The most common mistake during integration is forgetting about the callback. The customer paid for the order, the money was debited, but the status in b_sale_order did not update: the manager sees "Awaiting payment" and starts calling the client. The reason is an incorrect URL in the gateway settings or a handler that returns a 500 error for an atypical response structure. We offer services for connecting payment systems on 1C-Bitrix with full testing of all scenarios: successful payment, refusal, timeout, partial refund, duplicate callback.

Why are callbacks critical?

Each payment gateway sends a notification to your server. If the handler does not guarantee idempotency, a double call will lead to a double charge. We always implement a check by notification ID (external_id) and block repeated processing in \Bitrix\Sale\Order. It is also critical to set the callback URL in the aggregator's personal account – /bitrix/tools/sale_ps_result.php for the standard module. If you use a custom handler, we verify that it returns HTTP 200 even in case of parameter errors (the gateway should not repeat the request indefinitely).

use Bitrix\Sale\Order;
use Bitrix\Main\Application;

// Get notification data
$data = Application::getInstance()->getContext()->getRequest()->toArray();
// Check signature (depends on aggregator)
if (!checkSignature($data, 'SECRET_KEY')) {
    die('FAIL');
}
// Find order by external ID
$order = Order::loadByExternalId((int)$data['order_number']);
if ($order && $order->isPaid() === false) {
    $order->setField('PAYED', 'Y');
    $order->save();
}
echo 'OK';

How do we optimize payment flow for higher conversion?

How to choose a payment aggregator for 1C-Bitrix?

The choice of aggregator depends on the geography of customers, average order value, and need for installments. For Russia, the basic set is YooKassa (all main methods, fiscalization out of the box) and CloudPayments (widget on the page without redirect, Apple Pay). If you work with large corporate clients, add Sberbank (SberPay, SBP). For international sales, use Stripe or PayPal. We often use a two-tier scheme: main aggregator + backup (auto-switching on failure).

What payment gateways and methods do we use?

YooKassa

One contract – all main methods: Visa/MasterCard/MIR cards, YooMoney, SberPay, internet banking, installments. Fiscalization under 54-FZ out of the box (via the sale module). The standard handler /bitrix/modules/sale/handlers/paysystem/yandexpay/ covers basic scenarios. For holding (two-stage payment), subscriptions, or split payments, custom integration via YooKassa API v3. Callback is configured to /bitrix/tools/sale_ps_result.php, we parse notification and update \Bitrix\Sale\Order via setField('PAYED', 'Y').

CloudPayments

Focused on conversion: the payment widget directly on the checkout page, without redirect to an external domain. The customer does not leave the site – the abandonment rate during payment drops. It supports recurring payments (card tokenization via cryptogram), Apple Pay, and Google Pay. 3D Secure with intelligent routing – requested only for high fraud risk. Integration with Bitrix – via CloudPayments REST API and a custom handler in the sale module.

Tinkoff Payment

API integration via TinkoffPaymentAPI (ready-made module or manual implementation). QR code for payment via the app, "Tinkoff Credit" installment – critical for expensive goods. Partial refunds via the Cancel method – without calling the bank, everything from the Bitrix admin panel.

Sberbank (SberPay and SBP)

SberPay – payment via push notification or QR, SBP – commission 0.4–0.7% vs 1.5–2.5% for cards. This is a significant savings on volume. Holding via registerPreAuth / deposit API. Note that SberPay requires a separate agreement with the bank.

Apple Pay and Google Pay

Payment in two clicks, without entering card data. They are connected through an aggregator (YooKassa, CloudPayments, Tinkoff). Important nuances:

• Apple Pay requires domain verification: the file apple-developer-merchantid-domain-association in /.well-known/. Without it, the button will not appear.
• Button placement strictly according to Apple and Google guidelines – otherwise rejection in review.
• Fallback to the standard payment form if the device does not support contactless payment.

How do we handle installments, BNPL, and 54-FZ compliance?

If the average order value is above 30,000 RUB and conversion drops, installment removes the price barrier. We connect:

• Tinkoff Installment (3–24 months)
• Buy with Sber
• Mokka / Dolyami – BNPL: 4 payments, 0% for the buyer

Integration: widget with monthly payment calculation on the product card ("from 2,500 RUB/month"), order data transfer to the bank via API, status processing (approval, rejection, awaiting documents) in OnSaleStatusOrder handlers.

Fiscalization under 54-FZ is a mandatory requirement. The fine for a missing receipt is up to 100% of the payment amount. In accordance with Federal Law No. 54-FZ, an electronic receipt must be sent to the buyer. We connect ATOL Online, Orange Data, Module.Kassa, Evotor, Shtrikh-M. Setup in Bitrix – the "Cash Registers" section in the sale module:

• VAT rate, item and method of payment – an error in any field can lead to a fine during inspection.
• Receipts for prepayment and partial payment (two receipts: at payment and at shipment).
• Refund receipts upon cancellation via \Bitrix\Sale\Cashbox\Cashbox::addChecks().
• Monitoring: if the receipt is not sent, an alert to the manager.

When selling shoes, clothing, or perfumes, it is mandatory to transfer marking codes in the receipt. Integration with "Chestny ZNAK", scanning DataMatrix during order assembly, automatic removal from circulation upon sale via \Bitrix\Catalog\Product\Marking.

Payment support: refunds, multicurrency, security

Refunds

Full and partial refund without calling the bank – via the aggregator API (refund / cancel). The refund receipt is generated automatically, the order status is updated, the amount is recalculated, and the customer is notified. Timeframes: e-wallets and SBP – 1–3 days, bank card – up to 30 business days (depends on the issuing bank).

Multicurrency

Price types in b_catalog_price for each currency, rates via the Central Bank API (\Bitrix\Currency\CurrencyManager::updateCBRFRates()) or manual input. Conversion at the catalog level – the customer sees prices in their currency. For accepting dollars/euros, we connect Stripe, PayPal. We take into account conversion fees when calculating margin.

Security

Card data is processed on the certified gateway side (PCI DSS) – the card number never passes through your server. Anti-fraud at the aggregator level. Logging all events in b_sale_order_change for audit. Anomaly monitoring: transaction spike, atypical geography – alert.

How we work and estimated timelines

1. Analysis – what payment methods are needed, markets, transaction volume, current aggregator.
2. Solution selection – sometimes two aggregators are better than one: YooKassa as the main, CloudPayments as backup – if one fails, traffic goes to the second.
3. Integration – we test each scenario: successful payment, 3DS refusal, gateway timeout, double callback, partial refund.
4. Fiscalization – online cash register, checking the correctness of receipts on test orders.
5. Monitoring – alerts for gateway failures, conversion dashboard at the payment stage.

What is included in the work

• Full setup of selected payment systems in 1C-Bitrix: modules, handlers, callbacks, testing.
• Integration documentation (gateway operation scheme, handler description, logic).
• Training your manager to work with payment modules and refunds.
• Technical support during launch and the first 2 weeks of operation.
• Monitoring – we set up alerts for errors and conversion drops.

All work is performed by certified 1C-Bitrix developers. We guarantee the operability of each scenario. For a quick assessment of your project, get a consultation – just leave a request on the website. Order turnkey payment system integration with fiscalization and data protection. Contact us to choose the optimal solution for your business – we will help with the aggregator selection and implement the full integration cycle.