972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Transport

IFTMBC Booking confirmation

The UN/EDIFACT message a carrier or forwarder sends to confirm, conditionally accept, hold or reject a booking.

Sent by
Carrier or forwarder providing the service
Received by
Shipper or forwarder that booked
Standard
UN/EDIFACT · Batch message
X12 equivalent
301 Confirmation (Ocean)

What is the EDIFACT IFTMBC message?

IFTMBC is the UN/EDIFACT booking confirmation message. The directory defines it as a message from the party providing forwarding or transport services to the party booking them, confirming the booking of the consignment concerned. The confirmation can state that the booking is accepted, pending, conditionally accepted or rejected, along with the conditions.

An accepted confirmation gives the shipper the booking number, the vessel and voyage, cut-off times and where to collect empty equipment. Those details drive container pickup, loading and the shipping instructions that follow.

How the EDIFACT IFTMBC message worksDiagram of the UN/EDIFACT IFTMBC Booking confirmation message. Carrier or forwarder providing the service sends it to shipper or forwarder that booked. It usually follows IFTMBF and IFTMBP. It is usually followed by IFTMIN. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTMBC message worksBooking confirmation: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBFFirm bookingIFTMBPProvisional bookingIFTMBCSENDERCarrier or forwarderproviding the serviceRECEIVERShipper or forwarderthat bookedCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTMINInstruction2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IFTMBCUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:LOCRFFTDTNADGIDEQDBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for IFTMBC. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IFTMBC message worksDiagram of the UN/EDIFACT IFTMBC Booking confirmation message. Carrier or forwarder providing the service sends it to shipper or forwarder that booked. It usually follows IFTMBF and IFTMBP. It is usually followed by IFTMIN. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 6 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTMBCmessage worksBooking confirmation: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMBFFirm bookingIFTMBPProvisional bookingIFTMBCSENDERCarrier orforwarderproviding theserviceRECEIVERShipper orforwarder thatbookedCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTMINInstruction2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IFTMBC (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 6 conditional groups, starting with:LOCRFFTDTNADGIDEQDBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for IFTMBC.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends IFTMBC, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around IFTMBC and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Confirming a firm or provisional booking
  • Rejecting a booking for lack of space or equipment
  • Confirming with changed sailing or conditions

Where it fits in the message flow

Usually follows IFTMBF Firm bookingIFTMBP Provisional booking
This message IFTMBC Booking confirmation
Usually followed by IFTMIN Instruction

Structure

Mandatory segments in IFTMBC (directory D.21A)

In UN/EDIFACT directory D.21A, the IFTMBC message has 73 segment positions arranged in 22 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • UNT

Practical example

IFTMBC in practice

A carrier receives an IFTMBF for three reefer containers. It has space on the requested vessel but only two reefers at the origin depot. It sends an IFTMBC conditionally accepting the booking for two containers on that vessel and the third on the next sailing, with cut-off dates. The forwarder accepts the split and informs the trader.

Implementation

Implementation considerations for IFTMBC

  • Process the confirmation status (accepted, pending, conditional or rejected), not just its arrival.
  • Store cut-off dates where operations teams can act on them.
  • Watch for updated confirmations after schedule changes.
  • Match confirmations to bookings by the booking reference.

How ECOM helps

Automate IFTMBC with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Industry

3PL and Warehousing

Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related transport messages

All 36 transport messages

Need help with IFTMBC?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us