Agree on the meaning of the data before connecting

The manager sees a successful transaction in CRM, but the accounting department has not yet received payment. This is not necessarily an integration error: systems can describe different events. Before setting up an exchange, make a list of objects and explain what each status means. Order, invoice, shipment and receipt of money must differ in both names and transition rules. Separately check the price, item, warehouse and currency: the same number in two fields does not guarantee the same meaning. It is useful to walk through one actual operation with the process owners and note where the data first becomes validated. Such analysis helps to find contradictions that cannot be corrected by simply increasing the synchronization frequency. We look at examples of different events and calculation rules in the article aboutWhy do CRM and the report show different sales amounts?.

Assign an owner to each field

The phrase “main system - 1C” is too general for a two-way exchange. The contact person can be specified in the CRM, the agreed item can be specified in the accounting system, and the specific delivery address can be specified in the order. For each field, indicate the source, who has the right to change it, where the change is sent, and how the conflict is resolved. These rules vary depending on the company's device and the configurations selected. The table below shows a possible way of describing it, and is not a mandatory diagram for any business. It is also important to distinguish between the default value and confirmed information: an empty field in a new draft should not automatically erase already verified details. It is better to send an ambiguous entry to the responsible employee along with the reason for the conflict.

Data Owner Map Example
DataPossible ownerExchange rule
Client manager contactCRMTransfer after checking connection with the client
Article and product unitAccounting systemMatch by stable key
Negotiation stageCRMStore separately from the fact of payment
Payment for the orderPayment accounting systemSubmit the fact of payment with a link to the order

Link records with strong keys

The company name, phone number and document number are not always suitable as the only key. The name changes, the client has several contacts, and numbers may be repeated in different organizations or periods. Describe what identifier links objects and how the correspondence between systems is stored. For items, check the characteristics, packaging and units of measurement separately: a similar name does not make two products one item. Initial matching of existing records requires attention to duplicates and manual checking of ambiguous pairs. Keep the basis of the connection and the history of its changes. A new request from an already known client remains a new request, and does not automatically disappear as a duplicate contact.

DEMONSTRATION EXAMPLE

Study situation: in CRM the offer is calculated per box, but in the accounting system the price refers to one piece. Passing a number without a unit and a packing factor produces a formally completed but incorrect record. The check should compare the quantity, unit and composition of the item together, and forward the ambiguous variant to the employee.

Separate redo, new change and conflict

One object can change in both systems while the exchange channel is unavailable. The rule “last date wins” does not always reflect the order of events or the authority of the author. Agree on how to account for the version, the origin of the change, and the transactions already processed. The available mechanisms depend on the API and configuration; The presence of an interface in itself does not guarantee the necessary protection against replays. Do not send a value received from another system back as a new user change without verification; this will cause exchange loops. Cancellation and deletion also require an explicit rule. For example, a deleted card should not be quietly recreated from the old queue. A controversial outcome requires an understandable state and a decision maker.

  • Repeating one operation returns to the already known result.
  • The new change is checked taking into account the version and owner of the field.
  • The conflict retains both grounds for manual analysis.
  • Cancellation is not lost when processing previously accumulated events.

Check the result after a failure

A timeout does not prove that the target system did not write anything. Before repeating, you need to establish the actual result in an accessible way: find the object via an external connection, check the status of the operation, or send the case for analysis. The log must link the source event, the transmission attempt, and the destination object. It is important for an employee to see which records are lagging, what error is blocking the exchange, and what can be fixed without a developer. Select the update frequency according to the task: the permissible contact delay and changes in the available balance may have different error costs. When showing an outdated value, keep the time of the last successful check. Quietly using the old balance as current hides the problem from the team and from the client.

Start with one testable route

In the first stage, limit the composition of the fields, the type of object and the direction of the record. On the test circuit, go through create, change, cancel, redo an event, and recover from one system being unavailable. Use separate accounts with consistent rights and test the shutdown without losing committed changes. Then work together to review the log and the actual state of the records on both sides of the exchange. The test result should show not only the number of successful transfers, but also the remaining conflicts, delays and human actions. Agree on expansion to new objects after such a check: integration of several processes at once makes it difficult to find the cause of discrepancies and increases the amount of manual approval. It helps to prepare a field map, conflict rules and repetition controlintegration with CRMwith a separate check of the capabilities of a specific 1C configuration.

Apply to your task

Describe one contact channel and the CRM used. Let's discuss fields, responsibilities, repetitions and the first route to check.

Parse the route of applications →
← Return to materials