A sales platform and an invoicing system both store the customer's address. An employee corrects the address in one place. The next synchronization quietly puts the old version back.

The connection is working exactly as someone configured it. The missing decision is which system owns that piece of information and what should happen when two versions disagree.

Define the source of truth for each field

Ownership is often more precise than “the CRM owns customers.” The CRM might own contact details while the invoicing system owns tax information and payment status. Write these responsibilities down at field level where the distinction matters.

Map identifiers as well. Names and email addresses can change, and two people may share a company name. A stable external identifier gives the integration a better way to recognize an existing record than repeatedly guessing from text.

Describe the events that matter

List what should happen when a record is created, edited, merged or archived. Consider whether every update needs immediate delivery or whether a scheduled synchronization is acceptable. The answer depends on the operational need.

A warehouse picking a paid order has a different timing requirement from a monthly reporting export. Use that difference to decide what reliability and monitoring the connection needs. Avoid promising instant updates when the upstream system cannot provide them.

Plan for the second attempt

A request may succeed while its response is lost. If the integration tries again, it should not create a second invoice. Design record matching and repeat processing before treating retries as a universal fix.

Keep a record of what was attempted and what the receiving system confirmed. Staff need to distinguish pending work, a temporary failure and a case that needs manual correction. Silent failure is particularly difficult to repair once customers notice it first.

Grant the access the integration requires

Authentication identifies a caller; authorization determines what that caller may do. The integration needs explicit rules for the records and actions it can access. OWASP's access-control guidance is a useful technical reference for that distinction.

Keep credentials in the appropriate secure configuration, give the connection a named owner and decide how access is revoked when the integration is retired. Avoid sharing a person's everyday account simply because it already has broad permissions.

Test the awkward records

  • A customer whose details changed in both systems.
  • An event delivered more than once.
  • A request that times out after the receiver accepted it.
  • A record with missing optional information.
  • An account whose access has been removed.

Agreement on these cases is part of the integration deliverable. A connection becomes dependable when its business rules, failure handling and ownership are as clear as the path used to send the data.

Technical reference: OWASP: implement access control.