--- title: "Construction supplier EDI from PO to shipment and invoice" description: "Connect construction supplier EDI documents to job purchase orders without confusing acknowledgments with acceptance or delivery." canonical: https://www.stacksync.com/blog/supplier-purchase-order-edi-for-construction-services-connect-orders-acknowledgments-deliveries-and-invoices last_modified: 2026-09-18 --- # Supplier Purchase-Order EDI for Construction Services: Connect Orders, Acknowledgments, Deliveries, and Invoices > 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 construction supplier EDI documents to job purchase orders without confusing acknowledgments with acceptance or delivery. Author Alexis Favre · Co-Founder & CTO Published September 18, 2026 Read time 5 min read APP TIPS ## The operating decision Supplier EDI for construction services should connect the contractor's purchase order to the supplier acknowledgment, shipment details, receiving evidence and invoice. Preserve purchase-order and line references throughout the exchange. In an X12 flow, the 850, 855, 856 and 810 serve different commercial purposes; partner specifications determine their exact use. A technical acknowledgment does not prove equipment was accepted, shipped or received. Keep EDI transport separate from the ERP record actions it may initiate. 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: Construction supplier EDI from PO to shipment and invoice](https://www.stacksync.com/images/blog-highlights/icp-supplier-purchase-order-edi-for-construction-services-connect-orders-acknowledgments-deliveries-and-invoices.webp) ## What this looks like in construction services and installation A mechanical contractor buys equipment for two active projects from one distributor. The supplier acknowledges part of the order, backorders a control module and later sends two shipments. Accounts payable receives an invoice before the second delivery reaches the site. Without line-level references, procurement sees the order as accepted while installation assumes everything is available. EDI is useful when these distinct events remain attached to the correct job and purchase lines. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Purchase order and line | Procurement | Keep job allocation, supplier item, ordered quantity and unit attached to each line. | | Supplier acknowledgment | Supplier, reviewed by procurement | Represent accepted quantity, changed dates and substitutions without treating them as receipts. | | Shipment and receipt | Supplier and receiving team | Keep shipment notice separate from physical acceptance at the warehouse or site. | | Supplier invoice | Accounts payable | Match billed lines to the purchase and receiving evidence under the agreed policy. | ![Record ownership diagram: Purchase order and line, Supplier acknowledgment, Shipment and receipt](https://www.stacksync.com/images/blog-diagrams/icp-supplier-purchase-order-edi-for-construction-services-connect-orders-acknowledgments-deliveries-and-invoices.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Agree the trading-partner contract Obtain the supplier's implementation guide, identifiers, transport setup and supported document versions. Confirm which acknowledgments are expected and what they mean commercially. Generic X12 knowledge is insufficient for a live exchange because each partner constrains fields, codes, references and exception responses. 2. 02 Map purchase lines to jobs Preserve the buyer purchase-order number, line identifier, supplier item and unit of measure. Add the approved job or allocation relationship in the ERP mapping. A supplier may split one line into several shipments, so the design should not assume one document equals one complete delivery. 3. 03 Interpret supplier changes Route changed delivery dates, quantities or substitutions to procurement. Do not let a supplier acknowledgment automatically change the installation promise or approved specification. Record the buyer's acceptance where needed and keep the original order available for comparison with the revised commercial state. 4. 04 Reconcile shipment and receiving evidence Use shipment notices to prepare receiving and investigate expected deliveries. Let the receiving process record actual quantities, condition and site acceptance. A carrier tracking event or an 856 message should not silently create proof that the contractor accepted undamaged equipment at the intended location. 5. 05 Link invoices and exceptions Compare invoice references and quantities with the purchase and receipt records. Route early billing, price differences and missing line references to accounts payable with the supporting documents. Make processing repeatable by preserving interchange and transaction identifiers alongside the resulting ERP references. 6. 06 Keep transport success out of commercial status Record document transmission, technical processing and business review as separate results. A message that reached the supplier may still contain a rejected line or a changed delivery promise. Procurement should be able to find that commercial response without asking the integration team to inspect transport logs. When the response is missing, show an outstanding acknowledgment task rather than declaring the purchase accepted from transmission success alone. ![6-step operating sequence: Construction supplier EDI from PO to shipment and invoice](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-supplier-purchase-order-edi-for-construction-services-connect-orders-acknowledgments-deliveries-and-invoices.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Supplier changes an item Hold the affected line for approved substitution review; do not rewrite the required equipment specification. ### Delivery is split across sites Retain shipment and receipt allocation by job and location so quantities cannot be counted twice. ### Document is retransmitted Recognize the prior transaction and reconcile its processing status before creating another ERP action. ## What to verify before expanding - Every supplier document resolves to the intended purchase order. - Acknowledged quantity remains distinct from received quantity. - Duplicate transmission cannot duplicate the mapped business action. - A price or unit mismatch reaches an owned review queue. ## Connect this process to the rest of your operation [Explore Stacksync EDI](https://www.stacksync.com/edi) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real purchase order and line example and the exception your team handles most often, for example supplier changes an item. - [Two-Way Sync for Construction Service Companies: Which Records to Connect First](https://www.stacksync.com/blog/two-way-sync-for-construction-service-companies-which-records-to-connect-first) - [HubSpot–Acumatica for Construction Services: Customers, Projects, and Invoice Status](https://www.stacksync.com/blog/hubspot-acumatica-for-construction-services-customers-projects-and-invoice-status) - [Salesforce–NetSuite for Construction Service Groups: Accounts, Jobs, and Approved Commercial Data](https://www.stacksync.com/blog/salesforce-netsuite-for-construction-service-groups-accounts-jobs-and-approved-commercial-data) - [NetSuite Integration Failing? Fix Duplicate Data Fast](https://www.stacksync.com/blog/netsuite-integration-failing-fix-duplicate-data-fast) - [Acumatica to Salesforce & HubSpot Integration](https://www.stacksync.com/blog/acumatica-salesforce-hubspot-integration) 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) - [X12 transaction sets](https://x12.org/products/transaction-sets) FAQ ## Frequently asked questions Is a 997 proof that the supplier accepted our order? No. A functional acknowledgment addresses processing of the transmitted document. Commercial acceptance, shipment and physical receipt require their own evidence and agreed partner messages. Does EDI replace two-way sync? They serve different boundaries. EDI exchanges business documents with trading partners; two-way sync maintains mapped records across connected internal systems. A workflow can connect the two while preserving their separate states. Which supplier should we pilot first? Choose a supplier with recurring volume, clear implementation documentation and a manageable order pattern. Include a partial shipment and a changed acknowledgment in testing, not only a complete uncomplicated order. About the author Alexis Favre Co-Founder & CTO Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering. [All posts by Alexis Favre](https://www.stacksync.com/blog/author/alexis-favre) 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 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 Approved Finish Schedule to Material Purchase: Automate Commercial Flooring Procurement Handoffs 5 min read read](https://www.stacksync.com/blog/approved-finish-schedule-to-material-purchase-automate-commercial-flooring-procurement-handoffs) [App tips Construction Installation Readiness: Coordinate Parts, Site Access, and Crew Release 5 min read read](https://www.stacksync.com/blog/construction-installation-readiness-coordinate-parts-site-access-and-crew-release) [App tips Construction Invoice Readiness: Match Work Completion, Customer Sign-Off, and Billing Evidence 5 min read read](https://www.stacksync.com/blog/construction-invoice-readiness-match-work-completion-customer-sign-off-and-billing-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/)