1C:Accounting Integration (OData)

Self-service 1C connection for automatic turnover, balance, and nomenclature uploads—and what to do if the connection fails.

3 min readUpdated: Июнь 2026

In this article

  • · What Integration Gives You
  • · How to Connect
  • · If Connection Fails
  • · Account Mapping and Actual in Reports

What Integration Gives You

After 1C is connected, turnovers, balances, and nomenclature load automatically—no more Excel uploads.

The "Integrations" section is available on Pro and Enterprise plans.

How to Connect

You'll need the OData service URL for 1C, login, password, and register name.

  1. Open "Settings → Integrations → Connect 1C:Accounting".
  2. Enter the OData service URL, login, password, and register name.
  3. Click "Test Connection"—the system will make a real request to your 1C.
  4. If the test passes, click "Sync".
"Test Connection" makes a live request to your 1C. If it passes, data is accessible; if not, see the section below.

If Connection Fails

Make sure your 1C has the OData service published (on IIS/Apache web server) and the user has read rights to the register.

A typical HTTP 500 error is a 1C/web server issue, not Keiront. Your 1C admin fixes it by checking publication, user rights, and standard OData interface.

Account Mapping and Actual in Reports

After connecting, load the chart of accounts from 1C and set up mapping: which 1C account maps to which USALI line and with what sign (income +/expense −). The system suggests auto-mapping for revenue and expense accounts—you review and save.

Once mapping is saved and journal entries are loaded, actual amounts from revenue/expense accounts appear in the USALI P&L report. Rules for balance-sheet accounts (cash, bank, inventory, payables) are saved and used in the Cash Flow Statement and balance stages.

Details are in "1C Account Mapping Master → USALI".

FAQ

Is it safe to enter the 1C password?
Yes. The password is encrypted and used only for requests to your 1C.
Test connection gives HTTP 500
Almost always a 1C side issue: the OData service isn't published or is published with an error. Have your 1C admin check publication on the web server and user permissions.
Why doesn't actual appear in reports after connecting?
You need account mapping (1C accounts → USALI lines) and journal entry load. See "1C Account Mapping Master → USALI".
Was this helpful?

More in «Settings & Integrations»

All articles