1C Document Printing from Bitrix24: Setup and Automation

Print 1C Documents Straight from Bitrix24

A manager works in Bitrix24 CRM — manages deals, communicates with clients via built-in messenger. At some point, an invoice needs to be issued. Previously, this meant: open 1C, find the counterparty, create a document, save as PDF, return to Bitrix24, attach the file. Five context switches for one action. Setting up 1C document printing from Bitrix24 eliminates this switching. We configure this connection so the manager never has to leave the CRM. The entire operation — from button press to receiving the PDF — takes seconds. This reduces invoice issuance time from hours to minutes and eliminates errors from manual data copying. Our experience shows that such integration pays for itself within the first month.

By "printing 1C documents from Bitrix24" we mean several related scenarios:

• Generating a PDF document (invoice, UPD, waybill, certificate) in 1C — directly from a deal or contact card in Bitrix24
• Sending the document to the client — via email, messenger, or a download link
• Saving the document in Bitrix24 Drive — linking it to a deal or contact

Technically, this is implemented via an HTTP service in 1C that receives a request from Bitrix24 and returns the ready PDF.

HTTP Service in 1C for Document Generation

We create an HTTP service in 1C (UT, KA, ERP) with a POST /hs/documents/print method. Request:

{ "document_type": "invoice", "order_id": "bitrix_order_123", "counterparty_guid": "abc-123-def...", "items": [ {"guid": "product-guid", "quantity": 5, "price": 1500.00}, {"guid": "product2-guid", "quantity": 2, "price": 3200.00} ], "date": "2024-03-15", "api_key": "secret-key" } 

The 1C service:

1. Finds or creates the counterparty by counterparty_guid
2. Creates the document (Invoice / Customer Order / UPD)
3. Generates the printed form via the standard PrintingForm mechanism
4. Returns the PDF in base64

{ "success": true, "document_number": "Inv-00001234", "document_date": "2024-03-15", "document_1c_guid": "document-guid...", "pdf_base64": "JVBERi0xLjQ..." } 

Error handling and logging are added at each stage — guaranteeing transparency of the integration's operation.

Button in the Bitrix24 Interface

The manager needs a "Issue Invoice" button right in the deal card. Implemented via:

Option 1: Bitrix24 Application (Marketplace). The developed application adds a tab to the deal card. The manager sees a form: document type selection (invoice/waybill/certificate), list of items from the deal, a "Generate" button.

Option 2: Widget via REST API. Bitrix24 allows embedding custom interfaces in the CRM card via CRMActivityUI.EntityDetail.

Option 3: Robots/Triggers. When a deal moves to a certain status, an invoice is automatically generated in 1C and attached to the deal. No manager involvement.

Option 3 is the most automated. Suitable if the document logic is standard (one invoice type for all deals of that type).

Linking Deal Items to 1C Items

To ensure the invoice in 1C contains the correct items, the deal items in Bitrix24 must have an XML_ID matching the 1C item GUID.

This is achieved via the Bitrix24 product catalog synchronized with 1C (either through exchange via a Bitrix site or through direct synchronization of the Bitrix24 catalog with 1C via REST API).

If there is no catalog synchronization, items can be passed by name, but then 1C will create "unknown items" and the accountant will have to clarify them manually.

Which Documents Can Be Printed

Each document type can be a separate endpoint in the 1C HTTP service or a parameter document_type in a single endpoint.

Case Study: Reducing Invoice Issuance Cycle (from our practice)

A manufacturer of equipment: the cycle from order acceptance to sending an invoice to the client took 2–4 hours (waiting for the accountant to open 1C and issue the invoice). The client could call earlier.

After integration: the manager in the Bitrix24 deal card clicks "Issue Invoice", fills in quantity and date — within 3 seconds the invoice PDF is attached to the deal and sent to the client via email through a task. The accountant receives a notification about the created invoice in 1C.

Chief accountant: "Previously, issuing an invoice took up to 30 minutes, now it's 5. Errors are gone."

The cycle was reduced from 2–4 hours to 5 minutes. The integration was 10 times faster than manual transfer. We eliminated cases of "forgotten" invoices that previously got stuck in the manager's task list. Savings amounted to about 300,000 rubles per month in accounting labor costs, saving the company nearly 2 million rubles per year. Additionally, we configured automatic invoice creation when a deal is moved to the "Invoice Issued" status — via a Bitrix24 robot that calls a webhook, triggering an HTTP request to 1C.

How Long Does Setup Take?

The timeframe depends on complexity. Basic setup for one document type (invoice) takes 1-2 days. A full cycle with robots and all documents takes up to 5 days. We determine exact timelines after auditing your current document flow scheme.

Typical Integration Mistakes

• Incorrect item GUID: synchronize the product catalog
• Missing API key in 1C: check the request header
• 1C server overload: add request rate limiting

What Is Included in the Work

• Audit of current document flow scheme and 1C configurations
• Development of the HTTP service in 1C for the required document types
• Creation of a button in the Bitrix24 deal card (application/widget/robot)
• Item synchronization setup (if required)
• Testing of all scenarios: normal operation, errors, load
• Training for managers and accountants
• Operational documentation and integration scheme

Why Automate Printing?

Manual data transfer from Bitrix24 to 1C is a source of errors: mixed-up counterparties, incorrect amounts, forgotten invoices. Integration eliminates the human factor and speeds up the operation by 5-10 times. We guarantee the solution's operability at all stages: from design to support.

Order a preliminary assessment of your project — we will analyze the document types, load, and existing architecture. Contact us for a consultation.