1C:Accounting — Integration

This integration connects 1C:Accounting Enterprise (edition 3.0) to your cenaly/cenaly.ru account over the standard 1C:Enterprise OData protocol — no manual file export/import required. Connect it as an extension in the App Store (admin.cenaly.ru/app-store) — the "1C" card.

Connecting#

Before you start: you need the Premium plan or higher (the integration is part of the "Inventory" feature) and a location in one of the countries where 1C is used — Russia, Belarus, Kazakhstan, Uzbekistan, Kyrgyzstan, Armenia, Azerbaijan, Georgia, Moldova, Tajikistan, Turkmenistan, Ukraine. Elsewhere the "1C" card is not shown in the catalog, and with a lower plan you get an upgrade prompt instead of the connection form.

Cloud 1C (e.g., 1C:Fresh) is supported — a direct HTTPS connection:

Open the App Store, find the "1C" card and click "Configure" — the card opens in a modal right on the catalog page, and the location is picked in the header of that window.
The first field of the form is "Connection mode": choose "Cloud 1C (1C:Fresh)" (the second option, "Local 1C (via Hardware Bridge)", is still disabled — see below). Then fill in the OData base URL, the infobase user and the password.
Click "Test connection" — the system reads your base description ($metadata), reports how many entity sets it found there, and warns if nomenclature or counterparties are missing under their standard names.
Once verified, run syncs with the "Sync now" button — manually, whenever needed.

A local 1C base behind your network perimeter (via Cenaly Hardware Bridge) is under development and not yet available. Direct connection to a cloud base already works today.

What gets synced#

Nomenclature (Catalog_Номенклатура) → flows into your product catalog under Inventory.
Counterparties (Catalog_Контрагенты) → flow into your supplier directory.

Each record gets a stable ID tied to its 1C record — re-running the sync updates existing products and suppliers instead of creating duplicates.

Known limitations#

The integration is a direct pull from 1C into cenaly (one-way at this stage):

Unit of measure isn't carried over automatically — new products are created with a default "pcs" unit; adjust manually if needed.
Product category isn't mapped automatically from the 1C nomenclature group — sort new products into cenaly categories manually.
Barcode is picked up only if your base publishes it right in the nomenclature card (in a standard 1C configuration barcodes often live in a separate subordinate register) — otherwise the "Артикул" (SKU) field is used, so an SKU may end up in the barcode field. Check barcodes after the first sync.
For counterparties the name, full name and tax ID are carried over. Bank details are not — in 1C they live in a separate bank-accounts directory, which is out of scope at this stage; fill them into the supplier card manually.
The connected card already shows the "Sales document" (retail sales report or goods & services sale) and "Stock master" (cenaly or the 1C stock register) settings — they belong to the future document push into 1C and do not affect today's import. When the push arrives, documents will always be created unposted for the accountant to review and post.

Inventory — the product catalog nomenclature from 1C flows into
App Store — connecting the integration
Evotor — a similar integration for Evotor POS terminals

FAQ#

Do I need a separate 1C license for the integration?#

The integration uses the standard OData interface built into 1C:Enterprise 8.3 — no separate license is required for the integration itself, just access to your base.

Does sync happen automatically?#

At this stage, sync is triggered manually with the "Sync now" button — an automatic schedule isn't wired up yet.

Does data flow both ways?#

Currently only from 1C into cenaly (nomenclature and counterparties). Pushing invoices and sales reports back into 1C is under development.

What if my 1C runs locally, not in the cloud?#

Direct cloud connection works today. Connecting a local base via the Cenaly Hardware Bridge is under development — check with support for the current status.

🟡 1C:Accounting