# Solar CRM integration test sheet

Use fictional records in an authorised test. Keep outbound messages, payments and provider submissions suppressed unless the specific live test is approved. A pass needs observed evidence; a diagram or Connected label is not enough.

| Test | Evidence to inspect | Observed result | Owner / next action |
| --- | --- | --- | --- |
| Correct source and destination account | Account identity and record references | | |
| Same notification delivered twice | One intended destination outcome; duplicate handling explained | | |
| Older update arrives late | Current state preserved or conflict clearly exposed | | |
| Customer/site mismatch | Incorrect association identified before proceeding | | |
| Provider is unavailable | Known state retained, error and observation time visible | | |
| Accepted offer with processing deposit | Acceptance remains separate from collection | | |
| Job exists in two tools | Scheduling, evidence and billing owner agreed | | |

Record event time, receipt time, last successful sync and the source that establishes the final state. This worksheet is an evaluation method, not a claim that every product handles every test.

Guide: https://www.arcsolar.com.au/resources/solar-crm-integration-checklist