--- title: "Security installation acceptance before recurring billing" description: "Connect installation acceptance to the correct recurring-billing start decision for security integrators." canonical: https://www.stacksync.com/blog/new-security-installations-route-customer-acceptance-before-activating-recurring-billing last_modified: 2026-09-18 --- # New Security Installations: Route Customer Acceptance Before Activating Recurring 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 installation acceptance to the correct recurring-billing start decision for security integrators. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Security installation handoffs should distinguish installation completion, customer acceptance and the commercial start of recurring billing. A workflow can collect the required evidence and route activation to the authorized owner. It should not assume that a technician closing a task means the customer accepted every deliverable or that a monitoring or service agreement is ready to bill. Use the actual contract requirements, approved start date and verified system action for the recurring service. Explore the complete [fire, life-safety and security integrators integration and automation hub](https://www.stacksync.com/industry/construction/fire-life-safety-security-integrators) for the systems and processes around this guide. ![Summary card: Security installation acceptance before recurring billing](https://www.stacksync.com/images/blog-highlights/icp-new-security-installations-route-customer-acceptance-before-activating-recurring-billing.webp) ## What this looks like in fire, life-safety and security integrators An access-control integrator finishes hardware installation at a commercial building, but the customer still needs training and has not accepted the final handover package. The sales agreement includes a recurring service charge after an agreed acceptance condition. Operations wants to close the project, while finance needs a defensible billing start. The workflow should show the remaining handover requirements and route the final decision rather than starting billing from the installer's completed status. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Installation work package | Project manager | Identify the delivered scope and remaining completion items. | | Acceptance evidence | Authorized customer and project owner | Record the accepted version and any outstanding exclusions. | | Recurring agreement | Contract administration | Own the approved service term and commercial start conditions. | | Billing activation decision | Finance or contract authority | Record the permitted start date and resulting system reference. | ![Record ownership diagram: Installation work package, Acceptance evidence, Recurring agreement](https://www.stacksync.com/images/blog-diagrams/icp-new-security-installations-route-customer-acceptance-before-activating-recurring-billing.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Read the activation condition Identify the contractual event that starts recurring charges. It may involve acceptance, a specified date or another agreed condition. Record that rule explicitly for the project rather than adopting a generic installation-complete trigger across every customer. 2. 02 Gather the handover evidence Collect the installation completion record and the specific deliverables required for acceptance, such as approved documentation or training acknowledgement where applicable. The workflow should list what is present and what is missing without certifying technical performance from administrative records alone. 3. 03 Handle partial acceptance If the customer accepts only selected sites or parts of the scope, preserve that boundary. Determine whether the agreement permits a partial recurring start and route the decision to the authorized owner. Do not convert a signature for one building into acceptance of the whole rollout. 4. 04 Prepare the activation request Provide contract administration or finance with the agreement, accepted scope, approved date and evidence references. Invoke only the verified action allowed by the chosen systems and roles. If the initial scope is a task, confirm its receipt and ownership rather than labeling the recurring service active. 5. 05 Return the confirmed state After the owning process activates billing, return its reference and effective date to the project and CRM context. Check repeated acceptance updates and corrections so they cannot create a second recurring record. Retain the original handoff if an accepted date is later disputed. 6. 06 Handle an accepted project with an open punch item Record the exact effect of the open item under the customer's acceptance and billing rules. A minor remaining task may or may not prevent the recurring start; the workflow should not decide based on the word minor. Show the accepted scope, the excluded item and the authorized decision. That lets finance apply the actual commercial condition while the project team continues tracking the unfinished work to its proper owner. ![6-step operating sequence: Security installation acceptance before recurring billing](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-new-security-installations-route-customer-acceptance-before-activating-recurring-billing.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Customer signs with exclusions Route the exclusions and determine their effect on activation under the actual agreement. ### Only some rollout sites are accepted Keep site-level activation decisions and avoid starting charges for unaccepted scope. ### Acceptance date is corrected Send a reviewed correction to finance instead of silently changing the billing history. ## What to verify before expanding - Technician completion alone cannot activate recurring billing. - The start decision identifies the governing agreement condition. - Partial acceptance remains limited to the covered scope. - A repeated trigger cannot create a duplicate recurring record. ## 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 installation work package example and the exception your team handles most often, for example customer signs with exclusions. - [Security Installation Acceptance-to-Billing Workflows](https://www.stacksync.com/use-case/security-installation-acceptance-recurring-billing) - [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) - [Genies for Fire and Security Service Handoffs: Assemble Inspection, Asset, and Service-Agreement Evidence](https://www.stacksync.com/blog/genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence) - [Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) - [Building Triggers and Workflows on Top of Your Bidirectional CRM Sync](https://www.stacksync.com/blog/building-triggers-and-workflows-on-top-of-your-bidirectional-crm-sync) - [Salesforce–NetSuite Integration: Mapping and Setup](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) 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 Does this automatically activate operational monitoring? No. Commercial billing and operational service activation can require separate processes. Verify and authorize each action independently before connecting them. Who should approve the billing start date? The role designated by the agreement and your finance or contract process. The workflow should collect the evidence for that decision rather than invent an approval policy. Which acceptance-to-billing delays and corrections should we track? Measure time spent waiting for missing acceptance evidence, activation corrections and duplicate handoffs. These indicate whether the workflow improves the commercial transition after installation. 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 Fire-System Inspection Follow-Ups: Route Deficiency Records to Approved Remedial Work 5 min read read](https://www.stacksync.com/blog/fire-system-inspection-follow-ups-route-deficiency-records-to-approved-remedial-work) [App tips Fire and Security Handoff Exceptions: Missing Device IDs, Conflicting Site Records, and Unapproved Remediation 5 min read read](https://www.stacksync.com/blog/fire-and-security-handoff-exceptions-missing-device-ids-conflicting-site-records-and-unapproved-remediation) [App tips Genies for Fire and Security Service Handoffs: Assemble Inspection, Asset, and Service-Agreement Evidence 5 min read read](https://www.stacksync.com/blog/genies-for-fire-and-security-service-handoffs-assemble-inspection-asset-and-service-agreement-evidence) ## 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/)