--- title: "Security Installation Acceptance-to-Billing Workflows" description: "Route the evidence needed to start recurring charges after a security installation." canonical: https://www.stacksync.com/use-case/security-installation-acceptance-recurring-billing last_modified: 2026-09-21 --- Fire, life-safety and security integrators # Security Installation Acceptance-to-Billing Workflows > 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 ![Fire, life-safety and security integrators systems connected through Stacksync two-way sync: Salesforce, NetSuite, HubSpot, Acumatica, Supabase](https://www.stacksync.com/images/industry-heroes/icp-fire-life-safety-security-integrators-800.webp) Connect installation completion, required handover evidence, customer acceptance and the approved recurring-billing start. The workflow makes each prerequisite visible and routes the activation decision to the authorized owner. A completed technician task does not establish every commercial condition. Installation teams close the job while finance still needs to know which scope the customer accepted and when billing may start. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem US fire, life-safety, alarm and access-control integrators with 100–1,000 employees that supply equipment and deliver installation or recurring service. ### Use the actual agreement condition Define the event and evidence that authorize recurring charges for the specific project. ### Handle partial acceptance Keep site or scope boundaries visible when only part of a rollout has been accepted. ### Prevent duplicate activation Record the destination reference so repeated acceptance updates cannot create another recurring handoff. The process, end to end ## Follow the work across systems an access-control rollout is technically complete at several locations, but one site still awaits handover review. The workflow shows the accepted portion and routes the remaining decision instead of marking the entire rollout billable. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) Scope your implementation ## Bring these details to the demo - Recurring-start contract condition - Required handover documents - Authorized acceptance roles - Verified billing activation action Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [New Security Installations: Route Customer Acceptance Before Activating Recurring Billing](https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing) Connect installation acceptance to the correct recurring-billing start decision for security integrators. - [Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) Turn inspection findings into owned commercial follow-ups while preserving technical review and customer authorization. [Explore all fire, life-safety and security integrators integration and automation guides ↗](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) ## Common evaluation questions ### Does it activate monitoring operations too? Commercial billing and operational activation are separate actions and must be scoped independently. ### Who decides the start date? The designated finance or contract authority applies the agreement to the recorded evidence. ### Can finance retain final review? Yes. The workflow can prepare an owned activation packet without releasing financial changes automatically. ### Does this workflow need two-way sync in place first? It helps. Two-way sync keeps the Salesforce installation record and the NetSuite recurring agreement pointed at the same customer, site and accepted scope. Then add this workflow to collect handover evidence and route the billing activation decision to the finance or contract authority. Genies come next if coordinators want the acceptance evidence, remaining handover items and agreement condition gathered into one packet for that approver. EDI enters only when supplier shipment documents for the installed equipment need to reach NetSuite, a transport separate from the billing handoff.