Setting up the exchange of reconciliation reports between 1C and Bitrix24

Configuring Reconciliation Act Exchange Between 1C and Bitrix24

Reconciliation acts are documents that traditionally live only in 1C. But in B2B scenarios with Bitrix24, a demand arises: a manager needs to see the reconciliation act with a counterparty directly in the CRM, without switching to 1C. Or — a counterparty must be able to receive a reconciliation act through a self-service portal on the site.

What a Reconciliation Act Means in the Context of Integration

A mutual settlements reconciliation act in 1C is a report generated from the MutualSettlementsWithCounterparties register data for a period. The document contains:

• A list of transactions with the counterparty (shipments, receipts, returns)
• The closing balance (who owes whom)
• Signatures of the parties

In 1C this is either a report (ReconciliationAct) or a separate document (in some configurations).

Why Acts Are Needed in Bitrix24

Scenario 1: CRM. A manager is working on a deal with a counterparty in Bitrix24 CRM. They need to quickly check the current balance without opening 1C. Reconciliation act as a widget or tab in the company card.

Scenario 2: Client portal. A B2B client logs in to their personal account on the site and independently generates a reconciliation act for the required period. Downloads a PDF. Without calling the accountant.

Scenario 3: Automatic sending. Once a month, reconciliation acts are automatically sent to all counterparties with a non-zero balance — via email or via a Bitrix24 notification.

Technical Architecture: HTTP Service in 1C

To retrieve reconciliation act data on request from Bitrix24 — create an HTTP service in 1C.

Endpoint: GET /hs/reconciliation/act Parameters: counterparty_guid, date_from, date_to, api_key Response: JSON with act data or PDF (base64)

GET /hs/reconciliation/act?counterparty_guid=abc-123&date_from=2024-01-01&date_to=2024-03-31
Authorization: Bearer {api_key}

Response:

{
  "counterparty": "Romashka LLC",
  "period": {"from": "2024-01-01", "to": "2024-03-31"},
  "opening_balance": -15000.00,
  "transactions": [
    {"date": "2024-01-15", "document": "Sales Invoice #12", "debit": 45000, "credit": 0},
    {"date": "2024-01-20", "document": "Payment #456", "debit": 0, "credit": 45000}
  ],
  "closing_balance": -15000.00,
  "pdf_base64": "JVBERi0xLjQ..."
}

Integration with Bitrix24 CRM

To display the reconciliation act in the Bitrix24 company card — use the Activity or Timeline item mechanism via REST API.

A more convenient option — embedding via an embedded widget (iframe) in the CRM card:

1. In Bitrix24 settings: Applications → Integrations → CRM → Company card → Add widget
2. Widget URL: https://1c.example.com/reconciliation?guid={CONTACT.UF_1C_GUID}&period=current_month
3. The 1C service renders HTML with the reconciliation act table

This is the fastest approach — the manager sees up-to-date data without separate Bitrix24 development.

Automatic Act Generation and Distribution

A scheduled task in 1C (or in Bitrix24 via an agent) — once a month:

1. Get the list of counterparties with a non-zero balance
2. For each, generate a PDF reconciliation act (via ReconciliationAct.GenerateLayout() in 1C)
3. Upload the PDF to Bitrix24 Drive via REST API (disk.folder.uploadFile)
4. Create a task for the responsible manager: "Send reconciliation act to client {name}"
5. Or immediately send an email via messageService.send

Upload to Drive:

$bitrix24->call('disk.folder.uploadFile', [
    'id' => ACTS_FOLDER_ID,
    'data' => ['NAME' => "Reconciliation Act {$company} {$period}.pdf"],
    'fileContent' => base64_encode($pdfContent),
]);

Signing the Reconciliation Act

Ideally, the reconciliation act should be signed. For electronic document management — integration with EDI services (DIADOC, SBIS) is used. This is a separate task beyond the scope of simple 1C ↔ Bitrix24 exchange.

For automatic distribution without EDI: the PDF is generated in 1C and sent to the counterparty "for review." The signed scan is returned by the counterparty via email or uploaded to their personal account.

Case Study: B2B Portal with Self-Service

A wholesale supplier: 500 active counterparties. Every month the accountant spent 3–4 days manually distributing reconciliation acts. Counterparties called requesting acts for non-standard periods.

A personal account was implemented on the site (Bitrix): "Reconciliation Acts" tab. The counterparty selects a period → clicks "Generate" → request to the 1C HTTP service → PDF downloads directly in the browser.

Automatic distribution: on the 1st of every month — acts for the previous month to all counterparties with a non-zero balance. Generating 500 PDFs in 1C — 12 minutes. Uploading to Bitrix24 Drive and creating manager tasks — another 8 minutes via REST API.

The accountant stopped spending 3–4 days per month on manual distribution.