Wholesale
Sales sees stock and prices from accounting right in the deal card instead of asking accounting over a messenger.
Integration
CRM integration with BAS and 1C
Orders, counterparties, invoices and payments move between the CRM and your accounting system automatically. Sales stops retyping data, accounting stops reconciling two lists.
- Two-way exchange: CRM ↔ BAS/1C
- Counterparties, orders, invoices, payments, stock
- Works with BAS ERP, BAS Accounting, 1C 8.x
Free consultation
Who needs this
Manufacturing
A CRM order immediately becomes an accounting document; production status flows back to the manager.
Companies with separate accounting
Accounting stays in its system, sales in the CRM, and the data still matches without Excel exports.
Anyone keeping records twice
The classic case: a client exists in both systems with different details. The integration removes that drift.
What exactly we set up
The scope is agreed before we start: only the exchanges you actually need, with the direction of each one fixed in writing.
Counterparties and legal details
Creating and updating a counterparty with tax IDs, bank details and contact persons. Deduplication rules so twins do not multiply.
Orders and shipping documents
A CRM order becomes an accounting document with items, prices and discounts. Changes to the order are picked up.
Invoices and payments
The invoice is issued in accounting, the link lands in the deal card. A bank payment closes the invoice and moves the deal forward.
Products, prices, stock
The product catalogue and live stock inside the CRM, so nobody sells what is not there.
Exchange log and errors
Every exchange is logged. If a document fails, you get a notification with the reason instead of silence.
How the work goes
1. Audit of both systems
We look at how the accounting catalogues are built and what already exists in the CRM, and find the mismatches — the main source of pain later.
2. Field and rule map
We write down what maps to what, which system is the source of truth per field, and what happens with duplicates and conflicts.
3. Exchange on a test copy
We run real scenarios on a copy of the database: new client, order change, partial payment, return.
4. Launch and support
We move to the live database, watch the first days and fine-tune. You get an instruction and the exchange log.
What we connect
We build the integration on n8n as the integration layer. It works with any system that exposes an API or file exchange, so the list below is not a limit.
PlanfixKeyCRMKeepinCRMUspacyBAS ERPBAS Accounting1C 8.xCustom CRM with an API
CRM ↔ BAS/1C integration
Roughly 2–4 weeks depending on the number of documents in the exchange
- Audit of both systems and a field map
- Two-way exchange for the agreed entities
- Deduplication of counterparties and products
- Exchange log with error notifications
- Test environment before the live launch
- Instructions for sales and accounting
Frequently asked questions
We run an old 1C 8.2 without web services. Is this even possible?
Yes. If HTTP services are unavailable, we exchange through an intermediate layer: scheduled file import/export or a direct database connector. Slower than an online exchange, but the data matches.
Which system is the source of truth — CRM or accounting?
That is decided during the field mapping and fixed in writing per entity. Typically: clients and deals in the CRM; products, stock and financial documents in accounting.
What happens to duplicate counterparties?
Before launch we reconcile both databases and show the list of exact and near matches. The matching rule is agreed first, otherwise duplicates simply multiply.
Do we need an n8n licence?
No. Self-hosted n8n runs on your server or ours with no licence fees. You pay for the setup work, not for a subscription.