Requisites in Bitrix24 are the legal details of both parties: My Requisites store your own legal entities for inserting into invoices and contracts, while the requisites in company and contact cards hold your counterparties' details. As long as requisites are filled in by hand, typos in the tax ID and outdated bank accounts make their way into your documents. Let's break down how they are structured, auto-fill by tax ID, and — the help docs' blind spot — how to read and fill requisites automatically inside business processes.
How are requisites structured and where do you fill them in?
Your own legal entities: CRM → Settings → My Requisites — one entry per legal entity or sole proprietor; they are inserted into documents as the "seller's requisites". Counterparties: the "Requisites" block in a company or contact card; a single card can hold several sets (a legal entity plus a separate division). Each set is built from a requisite template — "Organization" or "Sole Proprietor" — with fields for the tax ID (ИНН), tax registration code (КПП), state registration number (ОГРН), addresses, and bank details. One important detail: bank details are a separate tab inside the set, and in document templates they are inserted through their own fields, not the organization's fields.
How does auto-fill by tax ID work?
In the requisite card, type the tax ID into the search box — Bitrix24 will pull the name, tax registration code, state registration number, and legal address from the government registry. This removes manual entry at creation time, but it does not solve two problems: bulk-filling a database you have already accumulated (you cannot click through hundreds of companies by hand) and keeping data current — a counterparty has relocated or changed its name, while your CRM holds details from two years ago. Both are solved by automation: in a business process, the Company requisites by tax ID robot fetches fresh data by tax ID and writes it into the card's requisites — a bulk run across the database is done by launching the process over a list of companies, and keeping data current is done by the same robot on a schedule or when a deal moves to the "Contract" stage.
How do you use requisites in business processes?
There are three typical tasks. Read a requisite for a check or a document: the Get company requisite (tax ID / registration code / bank account) robot returns the value of a requisite field into a process variable — for example, before generating a contract the process verifies that the tax ID and bank account are filled in, and only then creates the document. Find a company by tax ID: the Find company by tax ID robot looks up an existing card — a mandatory check before creating a new company from an inquiry, otherwise counterparty duplicates multiply. Fill in bank details: the Bank by BIC robot returns the bank name and correspondent account from a BIC — the manager enters nine digits and the rest fills itself in.
Requisites in documents: what to check before generation
A document template draws requisites from both parties: the seller's from My Requisites, the buyer's from the card. Three common failures. Empty fields: the contract ends up reading "Tax ID: __" — guard against it with a completeness check in the process before generation. Several requisite sets on a counterparty: the default set is inserted into the document — check the "Primary" flag in the card. Several of your own legal entities: insertion is controlled by the choice of My Requisites in the template settings and in the generation form — if managers mix up legal entities, split the documents across separate templates.
Frequently asked questions
How do requisites differ from company fields? Fields are card properties (industry, segment); requisites are a legal block with their own structure. In filters and reports requisites are only available to a limited degree, which is why the tax ID is often duplicated into a regular field — that's normal practice, and the Company requisites by tax ID robot can fill both places. Can you block a deal without requisites? Yes: a completeness check at a stage plus a return with a task. Where does the tax ID data come from? From government registries via data services; for Roboteka's robots the source is configured on the application's side.
In summary
Order in requisites means auto-fill by tax ID instead of manual entry, a check before generating documents, and a lookup by tax ID before creating companies. All three robots are in the Roboteka catalog and install from the Marketplace for free. If the scenario you need is missing — describe the task and we'll build the robot.