Working with 1C
1C data reaches Centa in two ways: Excel exports (available) and sync through 1C’s standard OData interface (beta). The trial balance sets opening balances, document registers provide invoices and acts, and transaction sheets provide payments. Centa never writes anything back to 1C.
- Author
- Centa AI editorial team · Centa AI product and content teamWrites the guides and product pages. Rates and deadlines are checked against the Tax Code text stored from LexUZ; feature statuses come from one list in the product code.
- Last updated
Which exports work
| Export | What Centa gets |
|---|---|
| Trial balance | Opening balances by account |
| Document register (type, number, date, amount, counterparty) | VAT invoices, acts, receipts, waybills |
| Contract register | Reference-only contracts (not debt) |
| Bank transactions | Payments with direction and purpose |
The header does not have to be in the first row: Centa finds the header row within the first ten. Rows that cannot be read are never invented — they are listed in a question.
OData sync
When your database publishes the standard OData interface, Centa can read documents and payments directly; entity names are configurable for your configuration.
If you are deciding whether to stay in 1C, see 1C or AI accounting and the accounting software page.