--- title: "Solar closeout exceptions for serials, scope and acceptance" description: "Resolve solar closeout evidence conflicts before marking a customer handover packet complete." canonical: https://www.stacksync.com/blog/solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence last_modified: 2026-09-18 --- # Solar Closeout Exceptions: Missing Serial Numbers, Changed Equipment, and Incomplete Handover Evidence > 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 Resolve solar closeout evidence conflicts before marking a customer handover packet complete. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Solar closeout exceptions should separate missing equipment identity, inconsistent scope revisions, absent technical records and incomplete customer handover. A Genie can identify the gap and assemble the evidence needed to resolve it. The exception should name the affected device or document, its source, the responsible owner and the blocked action. The agent must not fill missing serials, reuse another project's evidence or treat a delivered file as customer acceptance. 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 closeout exceptions for serials, scope and acceptance](https://www.stacksync.com/images/blog-highlights/icp-solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence.webp) ## What this looks like in solar installation and O&M services A solar installation has one inverter identifier missing from the asset list. A photograph appears to show a serial but is unclear, and the purchase record still references the original model replaced during construction. The handover folder also contains an unsigned document. An agent could produce a polished package while these problems remain hidden. A useful exception process keeps the conflicting identity, final-scope question and acceptance gap separate until each owner resolves it. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Missing identifier case | Asset or field owner | Confirm the device identity from appropriate project evidence. | | Scope discrepancy | Project manager | Resolve differences between original orders and approved final equipment. | | Technical-document gap | Qualified document owner | Provide the required authentic record for the actual project. | | Handover acceptance state | Project administration | Distinguish prepared, delivered and accepted evidence where acceptance is required. | ![Record ownership diagram: Missing identifier case, Scope discrepancy, Technical-document gap](https://www.stacksync.com/images/blog-diagrams/icp-solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Preserve the uncertainty Show the unreadable or conflicting source rather than converting it into an apparently verified value. If an image supports several possible serial readings, ask for a clearer capture or another authoritative reference. A confidence score should never substitute for a verified equipment identifier. 2. 02 Check the approved change history Compare the document or asset record with the final accepted scope and approved substitutions. The original purchase order may be valid history but wrong for the installed-equipment packet. Route the discrepancy to the project owner with the relevant revision references. 3. 03 Reject cross-project shortcuts When a document is missing, do not copy a similar record from another installation or infer that the same result applies. The agent can locate templates for a human to complete, but the final evidence must identify the actual project, equipment and responsible party. 4. 04 Separate delivery from acceptance Track whether a packet is assembled, internally approved, sent to the customer and accepted if the agreement requires acceptance. These states need different evidence. An email delivery event or uploaded file should not become proof of customer approval. 5. 05 Resolve and rerun the affected checks Store the confirmed identifier, corrected scope relationship or supplied document with the review decision. Recheck the impacted packet sections and update the version. Preserve the prior delivery history if the customer already received a packet, and route any correction through the project's communication process. 6. 06 Differentiate a missing record from a missing review The required document may exist but still await the designated owner's acceptance. Track those states separately so the project manager asks for the correct action. Repeatedly requesting a document that is already present wastes time; treating presence as approval creates a false complete state. The Genie should show the source file, its current review status and the exact owner decision still required for the handover obligation. ![6-step operating sequence: Solar closeout exceptions for serials, scope and acceptance](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-solar-closeout-exceptions-missing-serial-numbers-changed-equipment-and-incomplete-handover-evidence.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Serial photograph is unreadable Request better evidence and leave the identifier unresolved rather than guessing characters. ### Closeout file describes the original model Compare with the approved substitution and obtain the correct equipment documentation. ### Customer received but did not accept the packet Keep delivery and acceptance states distinct and follow the agreed handover process. ## What to verify before expanding - Uncertain serials never appear as verified identifiers. - Every technical record belongs to the actual project. - Final scope controls which equipment documents are required. - A corrected packet preserves its earlier delivery history. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-solar-installation-service) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real missing identifier case example and the exception your team handles most often, for example serial photograph is unreadable. - [AI Project Closeout for Solar Installers](https://www.stacksync.com/use-case/genies-solar-project-closeout) - [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 Equipment Supplier EDI: Reconcile Panels, Inverters, and Partial Project Deliveries](https://www.stacksync.com/blog/solar-equipment-supplier-edi-reconcile-panels-inverters-and-partial-project-deliveries) - [Solar Installer Customer Handoffs: Align HubSpot Opportunities With Acumatica Project Accounts](https://www.stacksync.com/blog/solar-installer-customer-handoffs-align-hubspot-opportunities-with-acumatica-project-accounts) - [Distinguish Solar End Customers from Installation Partners](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) - [Check Solar Installation Readiness Across Salesforce and NetSuite](https://www.stacksync.com/blog/check-solar-installation-readiness-across-salesforce-and-netsuite) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync HubSpot connector and object support](https://docs.stacksync.com/two-way-sync/connectors/hubspot) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) - [Stacksync Genies](https://www.stacksync.com/ai-agents) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can OCR output be treated as a verified serial number? It can be a candidate value, but the workflow should require the level of verification your asset process defines, especially when the image is unclear or conflicts with other records. Should one missing document block the entire project closeout? That depends on the required handover and commercial conditions. Mark the affected obligation explicitly and let the authorized project owner decide which actions may proceed. What recurring exception should we fix upstream? Repeated missing or unclear identifiers suggest improving field capture and equipment association at installation. Better source evidence reduces both manual review and the risk of an incomplete handover packet. 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 HubSpot integrations](https://www.stacksync.com/connectors/hubspot) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips Genies for Solar Project Closeout: Assemble Serial Numbers, Completion Evidence, and Handover Records 5 min read read](https://www.stacksync.com/blog/genies-for-solar-project-closeout-assemble-serial-numbers-completion-evidence-and-handover-records) [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 Distinguish Solar End Customers from Installation Partners 7 min read read](https://www.stacksync.com/blog/distinguish-solar-end-customers-from-installation-partners) ## 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/)