--- title: "Solar O&M visit billing workflow for Salesforce and NetSuite" description: "Connect solar O&M visit evidence to coverage and billing review without assuming every completed visit is chargeable." canonical: https://www.stacksync.com/blog/solar-service-visits-route-confirmed-repair-completion-into-o-m-billing last_modified: 2026-09-18 --- # Solar Service Visits: Route Confirmed Repair Completion Into O&M Billing > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect solar O&M visit evidence to coverage and billing review without assuming every completed visit is chargeable. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision A solar O&M billing workflow should join the service visit, asset context, performed work, agreement coverage and customer evidence before finance receives the handoff. A technician's completed status does not establish that all work is chargeable. Separate included service, warranty questions, additional authorized repairs and follow-up recommendations. The workflow can assemble the packet and route unresolved items while qualified service staff and finance retain their respective decisions. Explore the complete [solar installation and O&M services integration and automation hub](https://www.stacksync.com/industry/construction/solar-installation-service) for the systems and processes around this guide. ![Summary card: Solar O&M visit billing workflow for Salesforce and NetSuite](https://www.stacksync.com/images/blog-highlights/icp-solar-service-visits-route-confirmed-repair-completion-into-o-m-billing.webp) ## What this looks like in solar installation and O&M services A solar service provider visits a commercial installation after an equipment alert. The technician performs inspection and a repair, then recommends additional work for a later date. The agreement includes some service activity but requires separate approval for certain replacements. Billing needs to know which actions occurred, which were authorized and which remain recommendations. A workflow can preserve that distinction and avoid treating the entire visit narrative as an invoice. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Service visit | Dispatch | Keep asset, site, date and originating request linked. | | Performed work evidence | Technician and supervisor | Identify actual tasks and parts separately from recommendations. | | Coverage and authorization | Contract and service owners | Determine included work and approved additional scope. | | Billing handoff | Finance | Receive the reviewed chargeable evidence and unresolved exceptions. | ![Record ownership diagram: Service visit, Performed work evidence, Coverage and authorization](https://www.stacksync.com/images/blog-diagrams/icp-solar-service-visits-route-confirmed-repair-completion-into-o-m-billing.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Identify the service obligation Link the visit to the agreement and asset relationships valid at the time. Ownership or contract changes can make today's customer record different from the one that governed the visit. Preserve the applicable term so the reviewer does not judge historical work using only current coverage. 2. 02 Structure the completion evidence Separate observations, tests, completed repairs and future recommendations. Capture the parts and time evidence required by the billing model. The workflow should ask for missing data rather than infer that every mentioned part was installed or every recommendation was performed. 3. 03 Review included and additional work Have the responsible service or contract owner classify the work under the agreement. Keep warranty or coverage uncertainty explicit. Additional customer authorization should identify the relevant repair scope and price basis instead of relying on a general permission to visit the site. 4. 04 Prepare the finance packet Assemble the approved chargeable lines with the visit, customer and agreement references. Include any excluded work and the reason so billing does not have to repeat the review. Use a supported draft or task operation, and retain the destination identifier once the handoff succeeds. 5. 05 Handle later corrections If the service supervisor changes a part quantity or coverage decision, compare it with the packet already handed off. Route the change to finance with the original reference. Do not create another complete invoice request or overwrite a posted record through a casual status update. 6. 06 Split repeat visits from additional scope A return visit may finish an earlier authorized repair, investigate a new issue or perform separately approved work. Keep the visit relationship and scope classification explicit rather than combining all activity under the original case. Finance needs to know whether the second visit adds a chargeable line or completes evidence for a prior handoff. The service owner should decide that classification with the agreement and actual performed work available. ![6-step operating sequence: Solar O&M visit billing workflow for Salesforce and NetSuite](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-solar-service-visits-route-confirmed-repair-completion-into-o-m-billing.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Visit occurs during an ownership transition Use the reviewed relationship effective at the visit date and route ambiguity to contract administration. ### Technician recommends further repair Keep that scope outside completed and billable work until separately performed and authorized. ### Replacement may fall under warranty Hold the affected charge classification for the designated reviewer. ## What to verify before expanding - Every chargeable line has performed-work and authorization evidence. - Recommendations remain separate from completed repairs. - The agreement context matches the visit date. - A revised closeout refers to the original finance handoff. ## Connect this process to the rest of your operation [Explore Stacksync workflows](https://www.stacksync.com/workflow-automation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real service visit example and the exception your team handles most often, for example visit occurs during an ownership transition. - [Solar Equipment Change-Order Workflows](https://www.stacksync.com/use-case/solar-equipment-change-order-workflows) - [Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing](https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing) - [Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) - [Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence](https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence) - [Blu Banyan and Stacksync: A Partnership Built for the Next Era of Solar and Construction Operations](https://www.stacksync.com/blog/blubanyan-stacksync-partnership) - [Qualify and Route Commercial Solar Inquiries in HubSpot](https://www.stacksync.com/blog/qualify-and-route-commercial-solar-inquiries-in-hubspot) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can completed service automatically produce an invoice? Only when the required coverage, authorization and evidence checks are satisfied and the exact financial action is verified. A finance review queue is often an appropriate first scope. Does this determine equipment performance or safety? No. Technical assessment belongs to qualified service personnel. The workflow uses their recorded decisions to coordinate the administrative and billing handoff. How do you tell whether the O&M billing handoff is improving? Measure closeout packets returned for missing coverage or authorization evidence, time to resolve those gaps and corrections after finance review. Those metrics reveal where the handoff needs improvement. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Integration architecture](https://www.stacksync.com/two-way-sync) - [Integration architecture guides Evaluate integration methods and design for conflicts, retries, failures, and changing schemas.](https://www.stacksync.com/blog#topic-integration-architecture) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Check Solar Installation Readiness Across Salesforce and NetSuite 8 min read read](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) [App tips Identify Equipment Allocation, Permit, and Crew Blockers 7 min read read](https://www.stacksync.com/blog/identify-equipment-allocation-permit-and-crew-blockers) [Data engineering Solar Fleet Ownership Changes: Align Salesforce Asset Owners With NetSuite Billing Customers 5 min read read](https://www.stacksync.com/blog/solar-fleet-ownership-changes-align-salesforce-asset-owners-with-netsuite-billing-customers) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)