An invoice the customer can pay in two taps gets paid faster than an invoice whose bank details an accountant retypes by hand. A QR code on the invoice is the standard way to remove that barrier: the customer scans the code with a banking app, and all the details — account, amount, payment purpose — fill themselves in. Out of the box, Bitrix24 (Alaio) doesn't add such a code to invoices. Let's break down the kinds of payment QR codes there are, and how to generate them in the deal form automatically — with a robot at the right stage.
What kinds of payment QR codes are there?
Two fundamentally different kinds. A bank-details payment QR (a standardized format bank apps understand) is your banking details encoded into the code itself: payee name, bank account, BIC, amount, payment purpose. Any banking app can read it: one scan — and the transfer form is filled in. The code is static and works without online acquiring or any bank agreements — all you need is your bank account. The second kind is a QR with a link: inside is an ordinary URL, most often an instant-payment link from your bank or an acquiring payment page. This kind requires the bank or a payment service to generate the link, but in return it supports dynamic amounts and automatic payment confirmation. For B2B invoices to legal entities, the bank-details code is usually enough; instant-payment links are a story about payments by individuals.
QR from bank details: the Payment QR (GOST) robot
The Payment QR (GOST) robot assembles the payment code right inside a business process: on the input side — payee name, bank account, bank name, BIC, correspondent account, optionally the tax ID, tax registration code, amount, and payment purpose; on the output side — a PNG with the code, attached to a file field of the current deal, company, or smart process. The amount can be left empty — then the payer enters it, and the code becomes a universal "pay to our account" code. A typical combo: at the "Invoice sent" stage the robot drops the QR into a deal field, the next step emails the customer the invoice and the code — the rep does nothing. How file fields work and what you can do with them in workflows is covered in the breakdown of the File field.
QR from a link: instant payments, acquiring, and everything else
If you have a payment link — an instant-payment link from your bank, an acquiring page, a payment form — the Generate QR code robot turns it into a code: any text or URL on input, a PNG in a file field on output. Beyond payments, this covers adjacent tasks: a QR with a link to the company profile for a business card, a chat entry point, a link to a survey after the deal closes. The module size is configurable — the code stays readable both on screen and on a printed invoice.
How do you put the QR into the invoice itself?
Three working options, in order of increasing automation. Manually: the PNG sits in the form — the rep attaches it to the email along with the invoice. Semi-automatically: a workflow sends the customer an email where the invoice and the QR are two attachments taken from deal fields. Fully: if the invoice is built with a document template, next to the amount in figures the workflow also prepares the amount in words with the Amount in words (RUB) robot — the invoice comes out fully assembled with no manual edits. Getting the amount and the invoice itself approved before sending is a separate topic, covered in the article on invoice approval.
Frequently asked questions
Do you need an agreement with a bank? For the bank-details code — no: it's just structured requisites, and any banking app can scan it. For an instant-payment link — yes, the link is issued by your bank or payment service. Will Bitrix24 know about the payment? The bank-details code — no, it's a one-way transfer of requisites; the paid mark is set by accounting or a bank integration. Where does the image go? Into the specified file field of the current item — from there it's available to emails, workflows, and employees. Can the code live on a company instead of a deal? Yes, the robot works on any CRM entity with a file field.
In summary
A QR on the invoice means less manual entry on the customer's side and faster payment. The bank-details code is assembled from your own requisites with no bank or acquiring involved; the link-based code — from a ready payment link; both are generated by robots from the Roboteka catalog right at the deal stage. Free to install from Bitrix24 Market. If the scenario you need isn't there, describe the task and we'll build the robot for free.