International Multimodal Status Report Message
UN/EDIFACT IFTSTA reports shipment status and milestones across a transport chain, the EDIFACT counterpart to the X12 214.
In this guide
EDIFACT IFTSTA moves from Carrier / Forwarder to Shipper / Consignee (Carrier → Shipper) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT IFTSTA Works
Sender
Carrier / Forwarder
Receiver
Shipper / Consignee
Direction
Carrier → Shipper
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Logistics & Fulfillment
Sender — Carrier / Forwarder
EDI Transmission
IFTSTA
International Multimodal Status Report Message
UN/EDIFACT D.96A / D.01B
Receiver — Shipper / Consignee
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT IFTSTA workflow. Steps: Milestone Event, Generate IFTSTA, Send to Shipper, Platform Ingests Update, Display Milestone, Exception Notification. Transmitted from Carrier / Forwarder to Shipper / Consignee via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Provides shippers and forwarders with in-transit visibility across multimodal freight movements.
Sender
Carrier / Forwarder
Receiver
Shipper / Consignee
Direction
Carrier → Shipper
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Status report document reference. |
| LOC | Place/Location Identification | Location of the status event. |
| STS | Status | Status code and reason for the event. |
| DTM | Date/Time/Period | Date and time of the status event. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+IFTSTA:D:96A:UN'
BGM+23+STAT-9982+9'
STS+1:CD:ZZZ'
LOC+147:COLUMBUS:139:6'
DTM+132:20230921:102'
UNS+S'
UNT+6+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| Carrier Tracking Event | event.status_code | STS/9015 (Status Description Code) |
| Carrier Tracking Event | event.timestamp | DTM/2380 (Date/Time) |
Validation rules
- STS status codes must be from the agreed carrier status code list.
- Events should be transmitted with accurate DTM timestamps to preserve chronological order downstream.
Common errors & troubleshooting
Visibility platform shows conflicting statuses
Cause: Multiple IFTSTA messages arrived out of sequence due to network retries.
Fix: Sequence status updates by DTM timestamp rather than message receipt order.
Frequently asked questions
IFTSTA delivers the same milestone data in a machine-readable format that can feed directly into a shipper's own systems, rather than requiring manual lookup on a carrier's website.
Still have questions about IFTSTA?
Ask EDI AI →