Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Channel
Plan a reliable EDI exchange for CTSI-Global / Phillips Medisize (via CTSI) (ISA ID: CTSI5383). Explore 2 document references, map them to your business records and test the complete workflow before launch.
Implementation guide
Build a reliable EDI workflow for CTSI-Global / Phillips Medisize (via CTSI) (ISA ID: CTSI5383). Use 2 document types to plan record mapping, prevent duplicate processing and reconcile results in your business systems.
The document list is based on the linked partner reference. Confirm the required messages, versions and directions for your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| X12 110 Air Freight Details And InvoiceListed for Phillips Medisize (via CTSI) (ISA ID: CTSI5383) | air-freight payable carrier invoice, air waybill and billing revision |
|
| X12 210 Motor Carrier Freight Details And InvoiceListed for Phillips Medisize (via CTSI) (ISA ID: CTSI5383) | freight invoice carrier invoice, shipment reference and charge line |
|
Confirm the supplier or customer account, sender and receiver IDs, test environment and current guide for Phillips Medisize (via CTSI) (ISA ID: CTSI5383). Compare other CTSI-Global channels before reusing a mapping.
Start with air-freight payable, freight invoice. 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.
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 CTSI-Global production handoff and save the results of each approved test.
Match records between systems using carrier invoice, air waybill and billing revision. Assign an owner to missing responses, duplicates and rejected records. Test recovery before enabling automatic retries.
Document catalog
2 EDI transactions listed in this catalog.
Document flow on this channel
This channel lists 2 of the 3CTSI-Global document types; other entries appear on CTSI-Global channels (listed below). Example relationships are shown below; confirm the required sequence in the channel guide.
Network onboarding
The directory associates CTSI with 1 partner entries across 2 channels. Confirm transport, network enrollment, commercial terms and testing with the channel owner before implementation.
X12 110 Air Freight Details And Invoice; X12 210 Motor Carrier Freight Details And Invoice. Confirm which documents, directions and versions apply to your account.
Phillips Medisize (via CTSI) (ISA ID: CTSI5383) lists 2 distinct document types. Match the channel to your business unit, account and delivery arrangement; compare the other channel links before choosing a connection. Confirm access and enrollment with the channel owner.
For X12 110 Air Freight Details And Invoice, plan around carrier invoice, air waybill and billing revision. For X12 210 Motor Carrier Freight Details And Invoice, use carrier invoice, shipment reference and charge line. Use the partner guide to locate these values and check their allowed formats.
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.
Resend one invoice and verify that accounts payable creates only one liability. Reconcile revised freight charges against the earlier bill instead of adding a second invoice. Also test missing responses and recovery after a destination failure. Assign an owner to each failure and obtain partner approval before launch.
Related references
Compare the document lists for other CTSI-Global channels.
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
