Even the best accounting system does not live alone. Payments go through the bank, invoices through electronic document exchange, customers are kept in a CRM, and the warehouse works with barcode data terminals. If these systems are not connected to 1C, staff move data by hand, and errors and delays become normal. Here is which integrations pay off most and how to prepare the project so it does not drag on.
The integrations needed most often
- Bank. Loading statements and sending payment orders straight from 1C: the cash in the books always matches the bank account.
- Electronic document exchange. Issuing and receiving electronic invoices and other documents without re-entering them.
- CRM. Customers, deals and orders flow between the CRM and 1C: sales managers keep their familiar interface, and accounting gets accurate data.
- Warehouse and data terminals. Data collection terminals and barcode scanners speed up receiving, picking and stock counts.
- Online store and marketplaces. Stock, prices and orders are synchronised automatically.
- HR systems and time tracking. Employee data and hours worked reach payroll without manual spreadsheets.
Where to start: five steps
- Map your systems. List every program the company uses and the data that passes between them.
- Name an owner for each reference list. Customers may live in the CRM, items and prices in 1C. If a list has two owners, the data will inevitably drift apart.
- Choose the exchange method. Online through an API (REST/HTTP services, OData in 1C), on a schedule or via files. Online matters where every minute counts — for example, stock levels for an online store.
- Plan for errors. What happens if the bank or the CRM is down? You need a queue, retries and an exchange log so that no document is lost or duplicated.
- Test on a copy. The exchange is first checked on a copy of the database with real data, then switched on step by step.
Integration or microservice
Sometimes there is simply no system for a unit — for example, a mobile app for sales agents or an app for sensors on the shop floor. Then, instead of changing the 1C core, it is wiser to build a small separate service and connect it to the core through an API. The core stays standard and updatable, and the new unit evolves independently.
Typical mistakes
- Point-to-point integrations without an overall design — a year later nobody remembers which system changes what.
- No exchange log — errors surface only at the month-end reconciliation.
- Modifying the standard configuration instead of using extensions — every 1C update breaks the exchange.
- Going live without tests on real data.
Example: the bank exchange step by step
- An accountant creates payment orders in 1C and sends them to the bank with one click.
- The bank executes the payments, and the statement is loaded into 1C automatically on a schedule or on request.
- 1C matches incoming payments to customers and contracts by itself and lists the unrecognised ones separately for review.
- The exchange log records every operation: what was sent, what was received and which errors occurred.
As a result, reconciling the bank and the books stops being a separate month-end job and becomes a daily automatic process.
Who should take part in the project
Integration is not only a job for programmers. The process owner (for example, the CFO or the head of sales) approves how data moves, an IT specialist handles access rights and security, and the vendor of the other system provides API documentation and a test environment. Without them, the project turns into endless correspondence.
Security
Exchange keys and passwords are kept in protected settings, not in code; each integration gets only the rights it needs; data travels over an encrypted channel. This matters especially when banks and personal data are involved.
How to tell the integration works
- The exchange log has no unresolved errors, and new ones are handled within a day.
- Stock, payments and orders match in both systems in spot checks.
- Staff no longer move data by hand, and the helper Excel sheets are gone.
- Latency meets the requirements: minutes for online exchange, the agreed interval for scheduled exchange.
Questions and answers
Do we have to change 1C for an integration? Usually not: the exchange is built with extensions and standard mechanisms (HTTP services, OData), and the standard configuration stays updatable.
What if the other system has no API? Then file exchange, a database-level connection or an intermediate service is considered — the choice depends on security and reliability requirements.
Summary
A good integration is invisible: data simply appears where it is needed, once and without errors. If you want to connect 1C with your bank, e-document exchange, CRM or warehouse equipment, leave a request — we will start with a map of your systems and propose an exchange architecture.