Short answer: QuickBooks should remain authoritative for posted accounting records; the CRM may own lead stage and sales activity; the scheduling system may own confirmed appointments; and the operating system may own job status. Customer identity and shared fields require explicit ownership rules. A connected view should report conflicts instead of choosing silently.
Why “single source of truth” is often misunderstood
A business can have several systems of record without creating chaos. The problem begins when two systems are allowed to own the same fact with no precedence rule. “Customer” may exist everywhere, but the billing name, service address, sales stage, appointment time, and job status can each have a different responsible source.
The useful unit is not the application. It is the business object and field.
A starting authority matrix
| Fact | Typical authority | Reason | Conflict rule |
|---|---|---|---|
| Posted invoice, payment, account, tax, P&L | QuickBooks Online | The accounting ledger owns posted financial records. | Do not overwrite from a dashboard. Route correction to accounting. |
| Lead source, opportunity stage, sales owner | CRM | Sales activity is created and managed there. | Reject unknown stages; preserve the original CRM record ID. |
| Confirmed appointment, assigned resource, start time | Scheduling or field-service system | Capacity and dispatch depend on its current state. | Flag double bookings and stale updates; do not guess which wins. |
| Job completion and operational exception | Work-order or operating system | The team performing the work observes completion. | Require an explicit completion state and named owner. |
| Customer legal billing name | Usually accounting after posting | Financial documents must remain consistent. | Review proposed changes before synchronizing downstream. |
| Preferred contact method | CRM or customer record chosen by policy | The customer relationship team maintains it. | Timestamp changes and retain consent requirements. |
Write the rule before connecting the systems
- Name the object. Customer, lead, appointment, job, product, invoice, payment, employee, approval, or document.
- Name the authoritative field. “Customer” is too broad; billing name and service address may be governed differently.
- Name the writer. Identify which role and which system may create or change the field.
- Define identity. Preserve stable source IDs. Email addresses and names alone are unreliable matching keys.
- Define timing. State whether the view is real time, periodic, or refreshed on demand.
- Define failure behavior. Park ambiguous matches, report stale data, and avoid partial writes that make systems disagree.
Read-only first
A reporting connection usually needs less permission than an automation that changes records. Begin with read-only access when the objective is visibility. Prove that records match, filters behave correctly, and totals reconcile before proposing a write path.
If a write is later justified, isolate it behind an explicit action, schema validation, deterministic rules, human approval, and an audit trail. A model should not choose the winning record or calculate financial totals.
How to handle customer matching
Customer identity is often the hardest shared object. One company may appear under a legal name in QuickBooks, a short name in the CRM, and a contact name in the calendar. A responsible integration uses stable IDs and an explicit crosswalk. Exact email or phone matches can help, but they should not automatically merge unrelated records without a reviewed rule.
Keep three states: matched, unmatched, and ambiguous. “Ambiguous” is not a failure of the system; it is an honest request for review.
Reconciliation is part of the product
Connections drift. Authorization expires. Product names change. Staff create a new status. Historical records are edited. A command center should show the source timestamp and the last successful refresh, and it should compare important counts and totals against the authoritative source.
For financial reporting, the selected date range and cash-or-accrual basis must be visible. A sales report and profit-and-loss report can answer different questions even when both are correct.
What a connected view should expose
- The authoritative source and source record ID.
- The last successful refresh and expected freshness.
- The filters and accounting basis applied.
- Unmatched and ambiguous records.
- Failed connections and partial refreshes.
- A controlled link back to the source for correction.