Workflow guide

Connect CRM, proposals and invoicing

The goal is not to move every field everywhere. It is to preserve the commercial context needed for the next decision without creating duplicate sources of truth.

Last verified · Sep 2, 2026

Decision summary

Use one owner for each record

The CRM owns relationship and opportunity context. The accepted proposal owns scope and commercial terms. The invoicing or accounting system owns the financial record.

What to check

  • Pass stable IDs between systems.
  • Do not overwrite authoritative financial data from the CRM.
  • Log and reconcile failed handoffs.

Decision criteria

These criteria define the page. A product is not rewarded for affiliate availability or commission.

  • Record ownership
  • Stable identifiers
  • Trigger
  • Field mapping
  • Failure recovery
  • Audit and reconciliation

Map the minimum data

Common fields include client identity, billing contact, opportunity ID, accepted scope, amount, currency, billing schedule and owner. Every field needs a reason to cross the boundary.

Use explicit triggers

A signed document, approved internal status or paid deposit can be a trigger. Avoid ambiguous statuses that create work before the commercial commitment is complete.

Make failure visible

A silent failed automation is worse than a manual checklist. Record errors, notify an owner and provide a safe way to replay or complete the step.