--- title: "Route approved construction change orders to billing" description: "Move approved construction changes into a controlled billing queue with scope versions, acceptance evidence and duplicate protection." canonical: https://www.stacksync.com/blog/approved-change-order-to-billing-queue-automating-construction-service-handoffs last_modified: 2026-09-18 --- # Approved Change Order to Billing Queue: Automating Construction Service Handoffs > 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 Move approved construction changes into a controlled billing queue with scope versions, acceptance evidence and duplicate protection. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 4 min read APP TIPS ## The operating decision Automate the handoff from an approved construction change order to billing by carrying the approved scope version, job reference, price basis, and authorization evidence into a reviewable queue. A workflow should check prerequisites and create the next permitted action; it should not infer approval from an email mentioning extra work. Keep the original contract, proposed changes, approved changes and billed changes distinct so an update cannot cause the same variation to be billed twice. Explore the complete [construction services and installation integration and automation hub](https://www.stacksync.com/industry/construction) for the systems and processes around this guide. ![Summary card: Route approved construction change orders to billing](https://www.stacksync.com/images/blog-highlights/icp-approved-change-order-to-billing-queue-automating-construction-service-handoffs.webp) ## What this looks like in construction services and installation In a commercial plumbing project, the customer requests an additional restroom connection after mobilization. A superintendent records the request, the estimator prices it, and the authorized customer representative approves a revised scope. Billing still waits because the approval is buried in correspondence. A workflow can assemble the approved revision and work evidence for finance. If the customer later changes the quantity, that is another controlled revision rather than an edit to the already billed item. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Change request | Project team | Capture requested work without treating it as accepted commercial scope. | | Approved change revision | Authorized approver | Store approval reference, approved amount and the specific revision covered. | | Work evidence | Field supervision | Link performed quantities and completion evidence to the approved change lines. | | Billing handoff | Finance | Use a unique job/change/revision reference and record the resulting invoice linkage. | ![Record ownership diagram: Change request, Approved change revision, Work evidence](https://www.stacksync.com/images/blog-diagrams/icp-approved-change-order-to-billing-queue-automating-construction-service-handoffs.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Define approval evidence Agree who may approve each type and value of change and how the decision is recorded. Store the approver, time, scope revision and attachment or system reference. A general project approval should not silently cover additional lines added afterward. The workflow should be able to show exactly what was accepted. 2. 02 Separate pricing from authorization An estimator can complete pricing before the customer or internal authority approves it. Keep those states separate. Include the pricing basis, quantities and exclusions in the revision passed forward so finance does not have to reconstruct whether the agreed amount includes freight, mobilization or after-hours work. 3. 03 Check the billing prerequisites Validate the job is active, the customer and billing terms are resolved, and the required work evidence is available. Some changes may be billable on approval while others require completed work; encode the actual contract rule. Do not substitute one universal completed flag for those different conditions. 4. 04 Create one owned handoff Use the approved change revision as the deduplication reference for the billing task or supported draft operation. Store the downstream identifier after success. If a timeout occurs, look for that identifier before retrying so the same change cannot create a second billing request. 5. 05 Handle later revisions explicitly When a previously approved change is revised, compare the new commercial version with what was already handed off or billed. Route the difference to finance with the original reference. A cancellation, credit or additional charge should follow its authorized process rather than erasing the historical record. ![5-step operating sequence: Route approved construction change orders to billing](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-approved-change-order-to-billing-queue-automating-construction-service-handoffs.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Approval covers only some lines Release only those lines and keep the remaining scope in an unresolved state. ### Customer approval predates the latest price Hold the handoff until the correct priced revision is approved. ### Change was already included on an invoice Show the existing invoice reference and send any difference for review instead of issuing a duplicate request. ## What to verify before expanding - The billing reviewer can open the exact approved scope. - Unapproved lines remain outside the billing queue. - A repeated trigger creates one handoff for one revision. - A later change preserves its relationship to the earlier invoice. ## 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 change request example and the exception your team handles most often, for example approval covers only some lines. - [Construction Installation Readiness: Coordinate Parts, Site Access, and Crew Release](https://www.stacksync.com/blog/construction-installation-readiness-coordinate-parts-site-access-and-crew-release) - [Construction Invoice Readiness: Match Work Completion, Customer Sign-Off, and Billing Evidence](https://www.stacksync.com/blog/construction-invoice-readiness-match-work-completion-customer-sign-off-and-billing-evidence) - [AI Invoice and Expense Processing for Construction Services: Prepare Job-Cost Evidence for Finance](https://www.stacksync.com/blog/ai-invoice-and-expense-processing-for-construction-services-prepare-job-cost-evidence-for-finance) - [Acumatica to Salesforce & HubSpot Integration](https://www.stacksync.com/blog/acumatica-salesforce-hubspot-integration) - [How to Sync HubSpot and Supabase in minutes with Stacksync](https://www.stacksync.com/blog/how-to-sync-hubspot-and-supabase-in-minutes-with-stacksync) 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) - [Acumatica construction management](https://www.acumatica.com/cloud-erp-software/construction-management/) - [Stacksync event triggers](https://docs.stacksync.com/guides/event-triggers) FAQ ## Frequently asked questions Can a CRM deal stage trigger billing? It can start a check, but it should not replace the required approval and completion evidence. The workflow needs the actual commercial authority for the change being billed. Does this require automatic invoice posting? No. A reviewable billing queue is often the right initial scope. Posting or releasing an invoice is a separate supported action that requires finance authority and explicit validation. What should operations and finance agree first? Agree the billable event, evidence required, approver roles and treatment of partial work. Those decisions matter more than the specific trigger used to start the workflow. 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 Acumatica integrations](https://www.stacksync.com/connectors/acumatica) - [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 Service Agreement Renewals for MEP Contractors: Coordinate Price Review and Customer Approval 5 min read read](https://www.stacksync.com/blog/service-agreement-renewals-for-mep-contractors-coordinate-price-review-and-customer-approval) [App tips Solar Project Change Orders: Route Equipment Swaps Through Approval and Revised Billing 5 min read read](https://www.stacksync.com/blog/solar-project-change-orders-route-equipment-swaps-through-approval-and-revised-billing) [Revops Acumatica to Salesforce & HubSpot Integration 10 min read read](https://www.stacksync.com/blog/acumatica-salesforce-hubspot-integration) ## 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/)