--- title: "EDIFACT IFTSTA | Stacksync" description: "EDIFACT IFTSTA International Multimodal Status Report: mapping identifiers, validation examples, related messages and 1 partner references." canonical: https://www.stacksync.com/edi/edifact/intern-international-multimodal-status-report last_modified: 2026-09-15 --- EDIFACT transaction code # EDIFACT IFTSTA International Multimodal Status Report > 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 EDIFACT IFTSTA International Multimodal Status Report: explore its business purpose, mapping identifiers, validation tests and 1 partner references across 1 listed channels. Standard EDIFACT Code IFTSTA Partner references 1 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) Implementation guide ## EDIFACT IFTSTA mapping and validation EDIFACT IFTSTA International Multimodal Status Report is used when a transport event or status is reported. Preserve consignment, equipment, event time and location so the multimodal transport status in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **multimodal transport status** consignment, equipment, event time and location | Define which combination of consignment, equipment, event time and location identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the multimodal transport status** ID assigned by the receiving system and processing result | Preserve events from multiple transport legs without collapsing them into one carrier status. Handle delayed or repeated status messages without reversing the latest known state. | | Check the processing result | **Processing status for the multimodal transport status** Original document reference and matching response | Reconcile the multimodal transport status with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [EDIFACT IFTMIN Shipping Instruction](https://www.stacksync.com/edi/edifact/instru-instruction) **shipping instruction:** transport instructions are ready for execution. - [EDIFACT IFTMBC Booking Confirmation](https://www.stacksync.com/edi/edifact/bookin-booking-confirmation) **transport booking confirmation:** a provider responds to a booking. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when a transport event or status is reported. Name the operational owner of the multimodal transport status and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map consignment, equipment, event time and location. Confirm qualifiers, code lists, units and date/time meaning against the agreed EDIFACT version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic multimodal transport status data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful multimodal transport status processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved IFTSTA sample and the agreed version and partner guide are available. - The mapping tests pass with realistic multimodal transport status data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out multimodal transport status without processing it twice. ### Related documents and resources - [EDIFACT IFTMIN Shipping Instruction](https://www.stacksync.com/edi/edifact/instru-instruction) - [EDIFACT IFTMBC Booking Confirmation](https://www.stacksync.com/edi/edifact/bookin-booking-confirmation) - [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) **Sources.** Sources reviewed 2026-09-15. - [UN/EDIFACT message directory (reference release)](https://service.unece.org/trade/untdid/d04b/trmd/trmdi1.htm) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) ## Find your trading partner for EDIFACT IFTSTA 1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context. - [BASF](https://www.stacksync.com/edi/basf) [View](https://www.stacksync.com/edi/basf/edifact-intern-international-multimodal-status-report) FAQ ## EDIFACT IFTSTA questions ### What is EDIFACT IFTSTA International Multimodal Status Report used for? IFTSTA is used when a transport event or status is reported. It carries information for the multimodal transport status. Match it to your business system using consignment, equipment, event time and location. ### Which partners list EDIFACT IFTSTA? The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ### What should I map for EDIFACT IFTSTA? Start with consignment, equipment, event time and location and the target multimodal transport status. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test IFTSTA error handling? Preserve events from multiple transport legs without collapsing them into one carrier status. Handle delayed or repeated status messages without reversing the latest known state. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### How does IFTSTA relate to other EDI messages? EDIFACT IFTMIN Shipping Instruction; EDIFACT IFTMBC Booking Confirmation are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete. ### What is the difference between IFTSTA and IFTMIN? IFTSTA is used when a transport event or status is reported. IFTMIN is used when transport instructions are ready for execution. Each message represents a different business step. Keep their record references connected and track the processing result for each message. ## 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)