CRM and 1C integration: sales in the CRM, accounting in 1C — without typing everything twice

Why connect your CRM to 1C?

1C is a strong accounting system: taxes, ledger entries and statutory reports belong there. But the daily work of a sales team — leads, calls, quotes, orders, visits, payment reminders — is not what 1C was designed for. The healthiest model is simple: sales in the CRM, accounting in 1C, and an automatic exchange between them.

Without a connection, the same problems keep coming back: a salesperson promises goods that are not in stock because they cannot see the balance; the price list in the CRM is out of date; a customer has one name in 1C and another in the CRM; a payment is posted in 1C, yet the salesperson still chases the customer for the debt. Integration removes these conflicts because every piece of data gets one clear «owner».

Which data should flow in which direction?

The rule is simple: data is edited where it is created, and the other system reads it. In SBT CRM the exchange works like this:

• From 1C to the CRM: warehouses, products, prices and stock balances. Product cards and prices are changed in 1C, and salespeople always see the current price and balance in the CRM.
• From the CRM to 1C: customers (as counterparties), delivered orders (as sales documents) and payments.
• If you use the POS, receipts and returns are sent to 1C as well.
• If payroll is calculated in the CRM, the approved month goes to 1C as a payroll accrual document («Начисление зарплаты»).
• Records that cannot be sent are not lost: they stay in a queue and are retried automatically, and the error is shown on screen.

The technical side: connecting via OData

SBT CRM works with 1C:Enterprise 8.3 through the standard OData interface. This means no programming and no custom module in 1C: the 1C administrator enables the «Standard OData interface» in the configuration, publishes the database on a web server and creates a separate user for the exchange. In the CRM, you enter the 1C URL, user name and password in Settings and check the link with the «Test connection» button.

Because 1C configurations differ, the mapping of object and field names can be adjusted to your configuration. For typical configurations the default mapping is enough; for a customised configuration the fields are reviewed together with a 1C specialist.

Checklist before the first sync

• Back up the 1C database and, if possible, test on a copy first.
• Clean up product cards in 1C: duplicates, empty units, old and unused items.
• Decide in advance which 1C price type becomes the «sales price» and which the «wholesale price» in the CRM.
• Check customers' tax IDs: two counterparties with the same tax ID will cause confusion later.
• Agree in writing who edits what: products and prices in 1C, customers and orders in the CRM.
• During the first week, compare a few documents in both systems every day.

Typical mistakes

The most common mistake is editing the same data on both sides — for example, changing prices in both 1C and the CRM. After a few days nobody knows which figure is right. The second is moving a messy database as it is: duplicate products in 1C become duplicate products in the CRM. The third is sending an order to 1C before it is delivered. SBT CRM sends only delivered orders to 1C, so that cancelled and changed orders do not spoil the books.

1C integration in SBT CRM and consulting support

1C integration is included in the SBT CRM Business plan (299 AZN/month), together with orders, stock, POS and field sales. Compare plans at crm.sbt.az/pricing. You can try the system free for 7 days, no card required: crm.sbt.az/signup. For companies working with orders and stock, see crm.sbt.az/solutions/anbar-proqrami and crm.sbt.az/solutions/topdan-satis-proqrami.

SBT Consulting & Solutions is a team with tax and accounting experience, so we speak the same language as your accountant about price types, counterparties and document types in 1C. If you want to put your inventory in order before integrating, this article will help: crm.sbt.az/blog/excel-den-anbar-proqramina-kecid. Questions: info@sbt.az · +994 55 455 27 26.

Frequently asked questions

Do we need a 1C programmer?

Usually not. Enabling the standard OData interface and publishing the database on a web server is a job for the 1C administrator. If the configuration is heavily customised, a 1C specialist may be needed to check the field mapping.

Should products and prices be edited in the CRM or in 1C?

When 1C is connected, products, prices and balances come from 1C and should be changed there. Customers, orders and payments are created in the CRM and sent to 1C.

What happens if the internet drops or 1C is unavailable?

Records that cannot be sent stay in the queue and are retried automatically once the connection is back. An error notice is shown on screen.

Can we run inventory in SBT CRM without 1C?

Yes. SBT CRM has its own stock, POS and invoicing sections; 1C integration is optional.