--- title: "EDIFACT Message Types | Directory | Stacksync" description: "Browse 12 EDIFACT document types: business purposes, mapping decisions, validation examples and partner/channel reference pages." canonical: https://www.stacksync.com/edi/edifact last_modified: 2026-09-15 --- # EDIFACT message types > 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 Explore 12 EDIFACT document types and references for 8 trading partners. Find the message you need to map orders, shipments, invoices and other business records. UN/EDIFACT defines messages for business exchanges. ORDERS is a purchase order, DESADV is a despatch advice and INVOIC is an invoice message. The directory also covers transport messages such as IFTMBF for firm booking and IFTMBC for booking confirmation. Choose the release and partner guide before mapping fields. ## Choose a document by its business purpose ORDERS represents the order, ORDRSP the response, DESADV the despatch advice and INVOIC the invoice. ORDCHG addresses order changes. Agree which messages your partner uses and how references connect orders, shipments and invoices; this is an example relationship, not a mandatory sequence for every partner. Open a document below for its mapping identifiers, acceptance tests and related messages. Then choose the relevant partner and channel to review the document requirements for your account. [Start a field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) · [Review production readiness](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) Primary reference: [EDIFACT document directory](https://service.unece.org/trade/untdid/d04b/trmd/trmdi1.htm). Use the release specified by your trading partner. ## EDIFACT document reference entries Click a message type for mapping guidance, reference segments and partner references. - [DESADV Despatch Advice despatch advice](https://www.stacksync.com/edi/edifact/desadv-despatch-advice) 5 partners - [DESADV Despatch Advice despatch advice](https://www.stacksync.com/edi/edifact/despatch-advice) 5 partners - [IFCSUM Forwarding and Consolidation Summary forwarding and consolidation summary](https://www.stacksync.com/edi/edifact/forwar-forwarding-and-consolidation-summary) 1 partner - [IFCSUM Forwarding and Consolidation Summary forwarding and consolidation summary](https://www.stacksync.com/edi/edifact/forwarding-and-consolidation-summary) 1 partner - [IFTMBC Booking Confirmation transport booking confirmation](https://www.stacksync.com/edi/edifact/bookin-booking-confirmation) 1 partner - [IFTMBC Booking Confirmation transport booking confirmation](https://www.stacksync.com/edi/edifact/booking-confirmation) 1 partner - [IFTMBF Firm Booking transport booking request](https://www.stacksync.com/edi/edifact/firm-booking) 1 partner - [IFTMBF Firm Booking transport booking request](https://www.stacksync.com/edi/edifact/firmbo-firm-booking) 1 partner - [IFTMIN Shipping Instruction shipping instruction](https://www.stacksync.com/edi/edifact/instru-instruction) 1 partner - [IFTSTA International Multimodal Status Report multimodal transport status](https://www.stacksync.com/edi/edifact/intern-international-multimodal-status-report) 1 partner - [IFTSTA International Multimodal Status Report multimodal transport status](https://www.stacksync.com/edi/edifact/international-multimodal-status-report) 1 partner - [INVOIC Invoice invoice or qualified credit/debit note](https://www.stacksync.com/edi/edifact/invoic-invoice) 5 partners - [INVRPT Inventory Report inventory report](https://www.stacksync.com/edi/edifact/inventory-report) 2 partners - [INVRPT Inventory Report inventory report](https://www.stacksync.com/edi/edifact/invrpt-inventory-report) 2 partners - [ORDCHG Purchase Order Change Request purchase-order change](https://www.stacksync.com/edi/edifact/ordchg-purchase-order-change-request) 1 partner - [ORDCHG Purchase Order Change Request purchase-order change](https://www.stacksync.com/edi/edifact/purchase-order-change-request) 1 partner - [ORDERS Purchase Order purchase order](https://www.stacksync.com/edi/edifact/orders-purchase-order) 6 partners - [ORDERS Purchase Order purchase order](https://www.stacksync.com/edi/edifact/purchase-order) 6 partners - [ORDRSP Purchase Order Response purchase-order response](https://www.stacksync.com/edi/edifact/ordrsp-purchase-order-response) 3 partners - [ORDRSP Purchase Order Response purchase-order response](https://www.stacksync.com/edi/edifact/purchase-order-response) 3 partners - [SLSRPT Sales Data Report sales activity report](https://www.stacksync.com/edi/edifact/sales-data-report) 2 partners - [SLSRPT Sales Data Report sales activity report](https://www.stacksync.com/edi/edifact/slsrpt-sales-data-report) 1 partner FAQ ## EDIFACT questions ### What do UN/EDIFACT message codes identify? UN/EDIFACT defines messages for business exchanges. ORDERS is a purchase order, DESADV is a despatch advice and INVOIC is an invoice message. The directory also covers transport messages such as IFTMBF for firm booking and IFTMBC for booking confirmation. Choose the release and partner guide before mapping fields. ### Which EDIFACT messages relate to an order process? ORDERS represents the order, ORDRSP the response, DESADV the despatch advice and INVOIC the invoice. ORDCHG addresses order changes. Agree which messages your partner uses and how references connect orders, shipments and invoices; this is an example relationship, not a mandatory sequence for every partner. ### Are EDIFACT and X12 messages interchangeable? Messages can have related business purposes, such as INVOIC and X12 810, but they use different syntax, structures and qualifiers. Translate the business record using the applicable releases and partner guides; do not assume a one-to-one field mapping. ## Connect EDI to your business systems 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. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)