Forwarding and Consolidation Summary Message
UN/EDIFACT IFCSUM summarizes consolidated shipments — multiple individual consignments grouped into a single transport unit — for freight forwarders.
In this guide
EDIFACT IFCSUM moves from Freight Forwarder to Carrier / Terminal Operator (Forwarder → Carrier) 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 IFCSUM Works
Sender
Freight Forwarder
Receiver
Carrier / Terminal Operator
Direction
Forwarder → Carrier
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Logistics & Fulfillment
Sender — Freight Forwarder
EDI Transmission
IFCSUM
Forwarding and Consolidation Summary Message
UN/EDIFACT D.96A / D.01B
Receiver — Carrier / Terminal Operator
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT IFCSUM workflow. Steps: Consolidate Bookings, Generate IFCSUM, Send to Carrier, Terminal Receives Summary, Load Planning. Transmitted from Freight Forwarder to Carrier / Terminal Operator via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Gives forwarders and carriers a consolidated manifest view of everything moving within one container, trailer, or flight.
Sender
Freight Forwarder
Receiver
Carrier / Terminal Operator
Direction
Forwarder → Carrier
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 | Consolidation summary document reference. |
| TDT | Details of Transport | Transport unit (container/trailer) identification. |
| GID | Goods Item Details | Individual consignment detail within the consolidation. |
| CNT | Control Total | Total number of consignments or weight in the consolidation. |
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+IFCSUM:D:96A:UN'
BGM+785+CONS-1187+9'
TDT+20+CNTR9981122+++30'
GID+1+2:CT'
GID+2+3:CT'
CNT+16:2'
UNS+S'
UNT+8+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| Forwarder TMS | consolidation.container_number | TDT/8213 (Transport Means Identification) |
| Forwarder TMS | consolidation.consignment_count | CNT+16 (Control Total) |
Validation rules
- CNT totals must match the actual number of GID loops present.
- Each GID loop should trace back to an individual shipper booking/consignment reference.
Common errors & troubleshooting
Customs manifest rejected
Cause: Consignment count in CNT doesn't match the number of GID loops actually transmitted.
Fix: Auto-calculate CNT from the GID loop count rather than hardcoding it.
Frequently asked questions
Primarily freight forwarders and NVOCCs (Non-Vessel Operating Common Carriers) that consolidate multiple shippers' cargo into shared containers or transport units.
Still have questions about IFCSUM?
Ask EDI AI →