Reconcile practice-management records after a sync
Record the connection, time range, operation, and created, updated, and skipped counts. Wait for a background job to finish before starting another one.
Validate a representative sampleCheck at least one existing mapped record, one newly imported record, and one expected skipped record. Compare:
- client or contact identity;
- project, matter, or case name and identifier;
- company relationship and responsible staff;
- timekeeper, date, duration, activity category, and billable status;
- expense date, category, amount, and attachment;
- document project, name, category, and access; and
- source-system status or stage.
If data reached the wrong record, stop automatic synchronization. Correct the mapping and determine whether the imported record should be edited, archived, or merged according to company policy. Do not delete records blindly; they may already be referenced by time, invoices, or relationships.
Reconcile totalsUse matching date ranges, company scope, currencies, statuses, and filters in both systems. A difference can result from skipped records, approval status, non-billable work, rounding, time zones, or sync direction rather than a failed connection.
Escalate without secretsProvide record IDs or URLs, timestamps with time zone, mapping names, counts, and the exact error. Never include passwords, personal access tokens, API keys, client secrets, or authorization codes.
Related articles: Why am I seeing incorrect billable totals?, Troubleshoot sync, authorization, mapping, and duplicate-data issues.