--- title: "Modular progress-billing exceptions for finance review" description: "Resolve the modular billing evidence gaps an AI-prepared review must not silently complete." canonical: https://www.stacksync.com/blog/modular-progress-billing-exceptions-partial-deliveries-unapproved-variations-and-missing-acceptance-records last_modified: 2026-09-18 --- # Modular Progress-Billing Exceptions: Partial Deliveries, Unapproved Variations, and Missing Acceptance Records > 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 the modular billing evidence gaps an AI-prepared review must not silently complete. Author Ignacio Malpartida · GTM Engineer Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Modular progress-billing exceptions should identify whether the missing decision concerns delivered scope, approved variation, acceptance evidence or previous billing. A Genie can gather the records and explain the gap, but it must not invent an acceptance date, treat performed extra work as an approved charge or assume a partial delivery satisfies the whole milestone. Keep each exception linked to the governing contract requirement and assign it to the person authorized to resolve that issue. Explore the complete [modular and prefab building supply and installation integration and automation hub](https://www.stacksync.com/industry/construction/modular-prefab-building-installation) for the systems and processes around this guide. ![Summary card: Modular progress-billing exceptions for finance review](https://www.stacksync.com/images/blog-highlights/icp-modular-progress-billing-exceptions-partial-deliveries-unapproved-variations-and-missing-acceptance-records.webp) ## What this looks like in modular and prefab building supply and installation A modular project has three modules at the site, one still at the factory and a customer acceptance record that names only two. The field team also performed an additional installation task after an informal request. Finance receives a packet labeled delivery complete. The exception review should show the actual module states, the acceptance boundary and the unapproved variation, rather than returning a single confident ready-to-bill result. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Delivery-scope exception | Logistics and project owners | Reconcile the exact modules delivered, missing or disputed. | | Variation approval gap | Commercial authority | Resolve whether additional scope is approved and under which revision. | | Acceptance gap | Authorized customer or project owner | Provide the evidence required by the agreement for the affected scope. | | Prior-billing conflict | Finance | Compare the proposed amount and milestone with existing invoice references. | ![Record ownership diagram: Delivery-scope exception, Variation approval gap, Acceptance gap](https://www.stacksync.com/images/blog-diagrams/icp-modular-progress-billing-exceptions-partial-deliveries-unapproved-variations-and-missing-acceptance-records.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Tie each exception to a requirement State the contract milestone, affected scope and evidence needed to proceed. Missing acceptance is actionable when the reviewer can see which modules and which agreement condition are involved. Avoid a generic incomplete packet message that sends finance back through every source system. 2. 02 Reconcile partial delivery carefully Compare dispatched, received and accepted modules one by one. A carrier document can support movement, while a site record supports receipt and a separate decision may support acceptance. Preserve those differences and let finance determine the permitted partial-billing treatment. 3. 03 Keep variations outside the baseline Link additional work to its proposed or approved change record. Performed work and approved price are separate facts. Send the commercial owner the exact missing authorization rather than asking the model to infer acceptance from a site conversation or project note. 4. 04 Check existing financial references Look for the same milestone, module scope or approved variation in prior handoffs and invoices. A corrected packet should not become a new charge merely because it has a new document version. Show the overlap to finance before resuming any downstream action. 5. 05 Resume after the owned decision Store the corrected delivery scope, supplied acceptance evidence or approved variation reference. Recalculate only the affected review and retain the previous result. If finance must adjust an issued document, route the change through the authorized correction process rather than editing synchronized totals directly. 6. 06 Track the value of an unresolved decision carefully Finance may want to see the amount affected by a missing acceptance or variation approval. Label that amount according to its actual meaning: proposed, scheduled or previously billed. Do not present every held item as recognized revenue or an approved receivable. The exception queue should support prioritization while preserving the financial distinctions that the accounting process owns and that the agent is not authorized to infer. ![6-step operating sequence: Modular progress-billing exceptions for finance review](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-modular-progress-billing-exceptions-partial-deliveries-unapproved-variations-and-missing-acceptance-records.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### One acceptance record omits a delivered module Keep that module's acceptance unresolved and request the appropriate evidence. ### Site instruction has no commercial approval Route the variation to the designated authority and preserve it as unapproved until resolved. ### Revised packet overlaps a previous invoice Identify the overlapping scope and ask finance to determine the correct adjustment. ## What to verify before expanding - Every hold identifies the governing milestone and affected scope. - Partial receipt cannot imply whole-project acceptance. - Unapproved variations remain distinct from the baseline. - A corrected packet cannot duplicate already billed scope. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-modular-prefab-building-installation) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real delivery-scope exception example and the exception your team handles most often, for example one acceptance record omits a delivered module. - [Genies for Modular Progress-Billing Reviews: Assemble Factory Milestones, Delivery Proof, and Site Acceptance](https://www.stacksync.com/blog/genies-for-modular-progress-billing-reviews-assemble-factory-milestones-delivery-proof-and-site-acceptance) - [Prefab Supplier EDI: Reconcile Component Orders With Factory Receipts and Direct-to-Site Deliveries](https://www.stacksync.com/blog/prefab-supplier-edi-reconcile-component-orders-with-factory-receipts-and-direct-to-site-deliveries) - [Modular Building Manufacturers: Align Salesforce Project Configurations With NetSuite Orders and Milestones](https://www.stacksync.com/blog/modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones) - [Modernize Legacy EDI Without Replacing Your ERP](https://www.stacksync.com/blog/modernize-legacy-edi-systems) - [Secure EDI Processing in Multi-Cloud Environments](https://www.stacksync.com/blog/secure-edi-processing-in-multi-cloud-environments) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [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 Should missing acceptance always block all progress billing? Apply the actual contract rule to the affected scope. Some agreements permit partial treatment and others do not; the Genie should expose the evidence rather than invent that policy. Can the agent infer approval from an email saying looks good? It can present the message as evidence, but the authorized reviewer must determine what it approves and whether it meets the agreed requirement for the specific scope. Which details should finance track for each modular billing exception? Track exception age, owner, affected milestone and recurring missing evidence. That makes the commercial bottleneck visible and helps project teams collect the right records earlier. 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 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 Modular Progress-Billing Reviews: Assemble Factory Milestones, Delivery Proof, and Site Acceptance 5 min read read](https://www.stacksync.com/blog/genies-for-modular-progress-billing-reviews-assemble-factory-milestones-delivery-proof-and-site-acceptance) [App tips Modular Building Delivery Releases: Coordinate Site Readiness, Transport Booking, and Receiving Acceptance 5 min read read](https://www.stacksync.com/blog/modular-building-delivery-releases-coordinate-site-readiness-transport-booking-and-receiving-acceptance) [App tips Prefab Design Freeze to Factory Release: Route Approved Revisions Through Procurement and Scheduling 5 min read read](https://www.stacksync.com/blog/prefab-design-freeze-to-factory-release-route-approved-revisions-through-procurement-and-scheduling) ## 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/)