Setting up act generation from Bitrix24 to 1C

Configuring Act Generation from Bitrix24 to 1C

A completion act is a document by which the contractor confirms the delivery of a service. In Bitrix24, this moment is recorded by a deal status or funnel stage. The problem arises when CRM and accounting lead separate lives: a manager closes a stage, the accountant finds out a few days later, the act is delayed, and payment is too.

Integration resolves this through automatic data transfer from Bitrix24 to 1C when the required deal status is reached.

What document is generated in 1C

Depending on the 1C configuration, the target document varies:

Before configuring the integration, it is necessary to precisely determine which document the accountant uses for acts in the specific configuration — this defines the mapping rules.

Where act data comes from in Bitrix24

An act is built from three groups of data:

Deal parties. The contractor — the company's legal entity (requisites from Bitrix24 settings, "Organization Requisites" section). The client — the counterparty from CRM linked to the deal. TIN, KPP, and legal address are mandatory — without them, 1C will not create the document correctly.

List of services. Taken from the deal's product rows (crm.deal.productrows.get). Each item is a line in the act: name, quantity, unit of measurement, price, VAT rate. If CRM uses arbitrary service names, a mapping table to 1C nomenclature is required.

Amount and currency. A deal in Bitrix24 can be conducted in any currency — transferred to 1C with the exchange rate applied or in the local currency, depending on the accounting policy.

Data transfer mechanism

Option 1 — webhook on funnel stage change. The most common approach. Configured via "Settings" → "Webhooks" → "Outgoing webhook" for the ONCRMDEALSTAGEID event. When a deal transitions to the "Act Signed" stage (or any selected stage) — the handler is invoked.

The handler receives the deal ID and retrieves complete data via:

• crm.deal.get — deal requisites
• crm.deal.productrows.get — line items
• crm.requisite.get — counterparty requisites

Then it forms a request to the 1C OData service or an XML file for import.

Option 2 — business process with an "Create Act in 1C" action. Suitable for on-premise Bitrix24. An activity is created in the business process designer that calls an external handler. Advantage — the manager can launch the process manually without changing the deal stage.

Case study: digital agency with monthly closing

The agency manages 60–80 active projects. At the end of each month — an "act marathon": project managers close stages, the accountant manually transfers data to 1C, creates acts, sends them to clients. This process consumed 2–3 days at the end of every month.

After setting up the integration: closing the "Work Completed" stage in Bitrix24 automatically creates an act in 1C with a "Draft" status. The accountant sees the list of ready acts, reviews them, and posts them. The final act preparation phase was reduced from 2 days to 4 hours.

A notable issue encountered during setup: the agency uses non-standard service units of measurement ("hour", "project", "revision") that were not present in the OKEI reference book in 1C. Custom units had to be added to 1C and mapping defined in the handler.

Status synchronization: feedback from 1C

An act in 1C may be rejected by the accountant during review — due to incorrect requisites or amounts. Full integration also provides reverse status transfer to Bitrix24: if an act is rejected, a task is created for the manager in the deal with a description of the reason.

Implemented via a scheduled task in 1C that polls documents with the "Not Accepted" status and calls the Bitrix24 REST API (crm.activity.add to create an activity).

Full integration setup timeframe (both directions): 4–7 business days.