--- title: "Aspen (Pubnet SAN/ISA ID) EDI Integration | Stacksync" description: "Aspen (Pubnet SAN/ISA ID) EDI implementation planning: define the trading relationship, document requirements, record mapping and acceptance tests." canonical: https://www.stacksync.com/edi/aspen-pubnet-sanisa-id last_modified: 2026-09-15 --- # *Aspen (Pubnet SAN/ISA ID)* EDI integration guide. Plan your Aspen (Pubnet SAN/ISA ID) EDI integration: the trading relationship, required documents, source system and business responses. Start with the current partner guide and sample files. [Book an EDI demo](https://www.stacksync.com/book-a-demo) Explore EDI documents | | | | | --- | --- | --- | | Listed documents | Confirm | Obtain the partner guide | | Listed channels | Confirm | Identify your trading relationship | | Implementation | Plan | Map, validate and reconcile | ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Implementation guide ## Aspen (Pubnet SAN/ISA ID): EDI implementation plan Plan the business records your ERP or warehouse needs to exchange with Aspen (Pubnet SAN/ISA ID), using the trading partner examples below. A verified document list for Aspen (Pubnet SAN/ISA ID) is not available here. These are planning examples; confirm the required documents with the partner before implementation. **Document examples to confirm with your partner** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) Planning example; partner requirement unconfirmed | **purchase order or sales order** buyer purchase order, order line and trading-party identifiers | Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. | | [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/x12/855-purchase-order-acknowledgment) Planning example; partner requirement unconfirmed | **purchase-order response** original purchase order, response revision and order line | Test a partially accepted order with a backordered line and retain both outcomes. Do not treat a syntax acknowledgment as acceptance of price, quantity or delivery dates. | | [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) Planning example; partner requirement unconfirmed | **shipment notice (ASN)** shipment, order, package and item references | Reconcile item quantities through shipment, order and packaging levels against the physical shipment. Test split shipments for one purchase order and prevent the second ASN from replacing the first. | | [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice) Planning example; partner requirement unconfirmed | **accounts-receivable or accounts-payable invoice** invoice number, purchase order and invoice line | Reconcile line amounts, allowances, charges and tax to the invoice total. Submit the same invoice twice and verify that it cannot create a second payable. | ### Implementation steps 1. #### Choose the trading account and channel Ask Aspen (Pubnet SAN/ISA ID) for the supplier or customer account, business unit, implementation guide and testing contact. Record what still needs confirmation before work starts. 2. #### Map records and assign owners Start with purchase order or sales order, purchase-order response, shipment notice (ASN). For each document, assign the source system, destination record, stable identifiers and person responsible for exceptions. Agree whether a change updates an existing record or creates a new event. 3. #### Test a complete exchange Run a successful exchange and the failure cases in the mapping table. Track delivery, document validation and processing in your business system separately. Agree on the Aspen (Pubnet SAN/ISA ID) production handoff and save the results of each approved test. 4. #### Check results after launch Match records between systems using buyer purchase order, order line and trading-party identifiers. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries. ### Go-live checklist - The required EDI documents, versions and sample files are agreed. - Sender and receiver IDs, test connections and production connections are agreed with the channel owner. - Delivery receipts, document validation and business responses have monitoring and a named owner. - Tests cover duplicates, partial processing and reconciliation with realistic business records. ### Related documents and resources - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [Evaluate your integration requirements](https://www.stacksync.com/blog/integration-evaluation-worksheet) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) ## EDI document examples to discuss with Aspen (Pubnet SAN/ISA ID) Use these trading partner examples to plan the exchange. Confirm which documents Aspen (Pubnet SAN/ISA ID) requires for your account. Obtain the current partner guide before mapping fields. - [X12 850 Purchase Order](https://www.stacksync.com/edi/x12/850-purchase-order) - [X12 855 Purchase Order Acknowledgment](https://www.stacksync.com/edi/x12/855-purchase-order-acknowledgment) - [X12 856 Ship Notice Manifest](https://www.stacksync.com/edi/x12/856-ship-notice-manifest) - [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice) Document flow ## Example document relationships for Aspen (Pubnet SAN/ISA ID) Where each document sits in its trading cycle, based on the transaction sets a trading partner typically trades. Confirm the current Aspen (Pubnet SAN/ISA ID) requirements with the partner. These are example relationships; the trading agreement determines the required sequence. ### Order-to-cash All example steps listed 1. 850 Purchase Order 2. 855 Purchase Order Acknowledgment 3. 856 Ship Notice / Manifest (ASN) 4. 810 Invoice LEGACY EDI MIGRATION FUND ## Still with a legacy EDI vendor? Ask about a contract buyout. Stacksync can buy out your current contract with SPS Commerce, Cleo, TrueCommerce, or OpenText. Eligibility and terms are confirmed on a call. [Check your eligibility for the EDI migration fund](https://www.stacksync.com/book-a-demo) | | | | --- | --- | | | [Migrate from SPS Commerce](https://www.stacksync.com/sps-commerce-alternative) | | | Migrate from Cleo | | | Migrate from TrueCommerce | | | Migrate from OpenText | SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Related references ## Partners with related document listings Compare document requirements for similar business processes. [Quebec Health Ministry 85 docs · 17 channels](https://www.stacksync.com/edi/quebec-health-ministry) [The Home Depot 48 docs · 11 channels](https://www.stacksync.com/edi/the-home-depot) [Walmart 32 docs · 8 channels](https://www.stacksync.com/edi/walmart) [Nordstrom 28 docs · 8 channels](https://www.stacksync.com/edi/nordstrom) [JCPenney 25 docs · 20 channels](https://www.stacksync.com/edi/jcpenney) [Amazon 24 docs · 4 channels](https://www.stacksync.com/edi/amazon) [Target 23 docs · 4 channels](https://www.stacksync.com/edi/target) [NEXCOM (Navy Exchange Service Command) 20 docs · 2 channels](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [Sprouts Farmers Market 19 docs · 2 channels](https://www.stacksync.com/edi/sprouts-farmers-market) [Ulta Beauty 18 docs · 3 channels](https://www.stacksync.com/edi/ulta-beauty) [KeHE Distributors 18 docs · 5 channels](https://www.stacksync.com/edi/kehe-distributors) [United Natural Foods, Inc. (UNFI) 17 docs · 4 channels](https://www.stacksync.com/edi/united-natural-foods-inc-unfi) [Macy's 17 docs · 5 channels](https://www.stacksync.com/edi/macys) [GovX Inc. 15 docs · 3 channels](https://www.stacksync.com/edi/govx) [AAFES (Army and Air Force Exchange Service) 15 docs · 3 channels](https://www.stacksync.com/edi/aafes-army-and-air-force-exchange-service) [AT&T Inc. 14 docs · 2 channels](https://www.stacksync.com/edi/att) [Dot Foods, Inc. 14 docs · 2 channels](https://www.stacksync.com/edi/dot-foods-inc) [Starbucks Coffee Company 14 docs · 3 channels](https://www.stacksync.com/edi/starbucks) [Neiman Marcus 14 docs · 3 channels](https://www.stacksync.com/edi/neiman-marcus) [Boscov's Department Stores 13 docs · 2 channels](https://www.stacksync.com/edi/boscovs-department-stores) [Lowe's 13 docs · 2 channels](https://www.stacksync.com/edi/lowes) [Browse the full directory](https://www.stacksync.com/edi) FAQ ## Aspen (Pubnet SAN/ISA ID) EDI questions ### Which EDI documents are listed for Aspen (Pubnet SAN/ISA ID)? This entry does not include a verified Aspen (Pubnet SAN/ISA ID) document list. The suggested X12 850 Purchase Order, X12 855 Purchase Order Acknowledgment, X12 856 Ship Notice Manifest, X12 810 Invoice documents are planning examples; their use by the partner is unconfirmed. Request the current partner guide and sample exchanges before implementation. ### How should I choose the Aspen (Pubnet SAN/ISA ID) EDI channel? Obtain the business-unit name, supplier/customer number, implementation guide and transport contact from Aspen (Pubnet SAN/ISA ID). Confirm the connection method with the partner’s EDI contact. ### Which identifiers should the Aspen (Pubnet SAN/ISA ID) mapping preserve? For X12 850 Purchase Order, plan around buyer purchase order, order line and trading-party identifiers. For X12 855 Purchase Order Acknowledgment, use original purchase order, response revision and order line. Use the partner guide to locate these values and check their allowed formats. ### Does a successful EDI receipt mean Aspen (Pubnet SAN/ISA ID) accepted the business document? Track delivery, document validation and business processing separately. An AS2 message disposition notification (MDN) confirms transport receipt; an X12 997 or 999 reports technical validation. Use the agreed business response or reconciliation report to confirm that the order, shipment or invoice was processed. ### What should be tested before launching Aspen (Pubnet SAN/ISA ID) EDI? Map buyer item numbers to seller SKUs and explicitly convert case quantities to the agreed unit. Resend one purchase order and confirm that only one sales order is created. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch. ## Your last integration took months. Your next one takes a prompt. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)