1C: invoices, payments and cash desks
Bizos exchanges data with your 1C database through an HTTP service (the Bizos processing installed in 1C). This is a live connection to your database at an address like http://1c-server/base/hs/bizos/.
No Bizos processing in 1C? Connect the standard OData interface instead — read-only: counterparties, nomenclature and customer invoices. Payments and cash desks are not imported over OData yet. How to choose between HTTP and OData — 1C OData.
What is synchronized
| From 1C | Where in Bizos | Before |
|---|---|---|
| Employees, departments, positions | HR | yes |
| Categories and transactions | Finance → transactions | yes |
| Cash desks and bank accounts | Finance → Accounts | new |
| Customer invoices | Finance → Invoices (client matched by BIN or name, otherwise created) | new |
| Invoice payments | Invoice payment + movement on a cash desk or bank account + income | new |
| Payments without an invoice (receipts and outflows) | Movement on a cash desk or bank account | new |
Rules:
- Amounts arrive in minor units (or in major units with two decimals) — no rounding. The currency comes from 1C; if 1C leaves it empty, the organization base currency is used.
- If 1C does not say which cash desk or account a payment went to, the money lands on the default account in the same currency.
- «Paid» / «partially paid» is calculated by Bizos from payments. 1C only sets «draft», «issued» or «cancelled».
- Running the exchange again creates no duplicates: each 1C record is linked to one Bizos record.
- If your processing version does not expose invoices or payments yet, those sections are skipped. HR and transactions work as before.
To avoid double income: if the same payment also exists in 1C transactions, the processing sends its code in the payment (
transactionId). Bizos then links the payment to the transaction already loaded instead of creating a second one.
How to run the exchange
- Open Settings → Integrations → 1C (
/settings/integrations/1c). - On Setup, enter the server address, 1C login and password, click Verify, then Save. The password is stored encrypted and is never shown after saving.
- On Exchange, choose what to sync (everything or, for example, only invoices) and click Run sync.
An automatic exchange runs every 30 minutes. After three failures in a row the owner gets a notification.
Conflicts
A conflict means the record was changed both in 1C and in Bizos since the last exchange. What happens depends on the setting:
- 1C wins — 1C data overwrites Bizos.
- Bizos wins — the Bizos record stays as is.
- Manual — the record appears on the Conflicts tab with both versions (number, amount, date). Click «1C wins» or «Bizos wins».
Notes:
- An invoice amount from 1C cannot drop below the amount already paid. Such a record goes to the exchange errors.
- Payments are not edited in Bizos. If a payment is changed or cancelled in 1C, Bizos recalculates the invoice, the account movement and the income (or shows a conflict in manual mode).
- Bank account numbers (IBAN) are shown only masked in conflicts and in the activity log.
Access and security
- Only the owner or an admin can configure the connection, run the exchange and resolve conflicts. The «1C connector» module is required.
- The server address is checked: internal and cloud service addresses are blocked. For 1C inside the company network, the Bizos server administrator can allow private addresses.
- Every invoice/payment exchange is written to the activity log — counts only (created, updated, conflicts, errors), without passwords, IBANs or amounts.
See also: Invoices and payments, Accounts, Finance integrations, Roles and access.