Full-cycle B2B payment in 1C-Bitrix
B2B clients don't pay with cards — they need an official invoice with a stamp and company details. Without automation, a manager has to manually issue an invoice, wait for confirmation from accounting, and mark the payment. This takes hours, and errors lead to delays. In 1C-Bitrix, you can set up a complete cycle: from collecting buyer's requisites to automatic confirmation of receipt to the current account. Our experience — over 7 years of development, dozens of projects with B2B payment. We use proven patterns — order user properties, bank REST APIs, PDF generation via FPDF. Result: payment processing time is reduced from two days to 20 minutes, operational costs drop by 70%. Non-cash payment is the standard method for B2B payments. In Bitrix, it is implemented by the built-in payment system Cash/BankTransfer, according to the official documentation.
Standard B2B payment flow
- The legal entity buyer places an order and selects "Payment by invoice".
- The system generates an invoice with seller's requisites.
- The buyer's accountant creates a payment order in the bank.
- Money arrives at the seller's current account.
- The manager or bank integration records the payment in Bitrix.
How to configure the "Bank Transfer" payment system in Bitrix?
Bitrix has a standard handler Cash / BankTransfer. Configure it in Store → Settings → Payment systems. Enter your company details: name, INN, KPP, current account, BIK, bank. Add instructions for the buyer — text that the client will see after selecting the payment method.
// Bank transfer payment parameters (entered in the admin section) // Logo, name, instruction text for buyer // In the payment system template — display requisites <div class="bank-details"> <p>Bank: Sberbank PJSC</p> <p>BIK: 044525225</p> <p>Account: 40702810XXXXXXX</p> <p>Corr. account: 30101810400000000225</p> <p>INN: XXXXXXXXXX</p> <p>KPP: XXXXXXXX</p> <p>Payment purpose: Payment for invoice No.<?= $order->getAccountNumber() ?></p> </div> Example of configuring order user properties
Buyer requisites collection form
When ordering, a legal entity must provide its details for invoicing and closing documents. Add order user properties via API:
// Adding order properties via Bitrix API // local/php_interface/init.php or setup script use Bitrix\Sale\Internals\OrderPropsTable; $props = [ ['NAME' => 'Company Name', 'CODE' => 'COMPANY_NAME', 'TYPE' => 'STRING'], ['NAME' => 'INN', 'CODE' => 'INN', 'TYPE' => 'STRING'], ['NAME' => 'KPP', 'CODE' => 'KPP', 'TYPE' => 'STRING'], ['NAME' => 'Legal Address','CODE' => 'LEGAL_ADDRESS','TYPE' => 'STRING'], ['NAME' => 'Bank Account', 'CODE' => 'BANK_ACCOUNT', 'TYPE' => 'STRING'], ['NAME' => 'Bank Name', 'CODE' => 'BANK_NAME', 'TYPE' => 'STRING'], ['NAME' => 'BIK', 'CODE' => 'BANK_BIK', 'TYPE' => 'STRING'], ]; In the checkout template, show these fields when "Payment by invoice" is selected. You can create a dependency via JavaScript: show the block only for the selected method.
Why automatic payment confirmation is critical
Manual payment marking is a source of delays. The accountant may forget, the manager may make a mistake. Automation solves the problem: payment received — order immediately moves to paid status. Options:
- 1C integration — if using 1C:Accounting, incoming payments are automatically synchronized with orders via the exchange module. It's reliable but requires configuring scheduled tasks.
- Bank client API — many banks (Sberbank, Tochka, Modulbank) provide APIs for reading statements. When a payment with the correct purpose appears, we automatically update the order status:
// Example: parsing Sberbank statement (SimpleBankStatementParser) $statement = parseBankStatement($statementXml); foreach ($statement->getTransactions() as $transaction) { if ($transaction->getType() !== 'credit') continue; // Find order number in payment purpose preg_match('/№(\w+-\d+)/', $transaction->getPurpose(), $matches); if (!isset($matches[1])) continue; $orderNumber = $matches[1]; $order = getOrderByAccountNumber($orderNumber); if ($order && abs($order->getPrice() - $transaction->getAmount()) < 0.01) { setOrderPaid($order->getId(), $transaction->getDate()); } } This approach requires customizing the parser for the specific bank format, but it pays off by removing human error. The savings on manual handling of one payment are substantial.
Real case: how we cut payment processing from 8 hours to 30 minutes
On one project with 200+ B2B orders per month, the manager spent half a day manually checking the current account and marking payments. We integrated the bank API and 1C. Result: payment confirmation now happens automatically in 30 minutes on average. The manager's workload dropped to zero for this task, and errors completely disappeared. The client saved about 80 hours of work per month.
How to generate PDF invoice for legal entities
After an order is placed, a legal entity needs an official PDF invoice. Bitrix does not generate PDF "out of the box" — we add third-party libraries. We use FPDF or mPDF:
// Invoice generation via FPDF or mPDF function generateInvoicePdf(Bitrix\Sale\Order $order): string { $pdf = new FPDF(); $pdf->AddPage(); $pdf->SetFont('Arial', 'B', 14); $pdf->Cell(0, 10, 'INVOICE No. ' . $order->getAccountNumber(), 0, 1, 'C'); // Seller's requisites // Product table // Total and signatures $path = '/tmp/invoice_' . $order->getId() . '.pdf'; $pdf->Output('F', $path); return $path; } The invoice is generated at the moment of order placement and sent to the buyer by email. Additionally, we save it to the file system for re-downloading from the personal account.
Comparison of manual and automatic payment processing
| Criteria | Manual marking | Automatic (API/1C) |
|---|---|---|
| Delay | from 1 hour to 2 days | 5–30 minutes |
| Errors | possible | eliminated |
| Load on managers | high | zero |
| Implementation cost | 0 (if manager exists) | 1-3 days of setup |
Automation processes payments 10 times faster than manual marking.
Turnkey setup process
- Analytics — we analyze the workflow, identify integration points.
- Design — architecture of the payment module, tool selection (HL-blocks for requisites, agents for processing).
- Implementation — configure payment system, collect requisites, generate PDF, integrate with bank API or 1C.
- Testing — verify all scenarios: successful payment, errors, refunds, partial payment.
- Deployment — roll out to production, train managers.
Timelines
| Task | Duration |
|---|---|
| Payment system and template setup | 0.5–1 day |
| Buyer requisites form | 0.5–1 day |
| PDF invoice generation | 1–2 days |
| Automatic confirmation via bank API | 2–4 days |
| 1C integration (if needed) | 2–5 days |
Total timeline — from 4 to 10 days, depending on complexity and integration needs.
How we guarantee results
We formalize all agreements in a technical specification. After delivery, you get full access to the code, an operation manual, and support for one month. Order turnkey setup — shorten your payment processing time. Get a consultation on your project — we'll suggest the optimal solution.