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

IFTMCS Instruction contract status

The UN/EDIFACT message a carrier or forwarder sends back to state the actual details, terms and charges of a transport service.

Sent by
Carrier or forwarder providing the service
Received by
Party that issued the instruction
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT IFTMCS message?

IFTMCS is the UN/EDIFACT instruction contract status message. The directory defines it as a message from the party providing transport or forwarding services to the party that issued the instructions, stating the actual details, terms and conditions of the service and of the consignment, with charges where applicable. It can also be used to exchange contract information between carriers.

In ocean shipping, IFTMCS commonly carries the draft or final bill of lading data back to the shipper after shipping instructions (IFTMIN) were received, so the shipper can check the details before documents are issued.

How the EDIFACT IFTMCS message worksDiagram of the UN/EDIFACT IFTMCS Instruction contract status message. Carrier or forwarder providing the service sends it to party that issued the instruction. It usually follows IFTMIN. It is usually followed by IFTSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 10 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTMCS message worksInstruction contract status: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMINInstructionIFTMCSSENDERCarrier or forwarderproviding the serviceRECEIVERParty that issued theinstructionCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTSTAInternationalmultimodal statusreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IFTMCSUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 10 conditional groups, starting with:LOCTODRFFGORCPITCCTDTNADGIDEQDBlue 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 IFTMCS. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IFTMCS message worksDiagram of the UN/EDIFACT IFTMCS Instruction contract status message. Carrier or forwarder providing the service sends it to party that issued the instruction. It usually follows IFTMIN. It is usually followed by IFTSTA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message). 10 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTMCSmessage worksInstruction contract status: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMINInstructionIFTMCSSENDERCarrier orforwarderproviding theserviceRECEIVERParty thatissued theinstructionCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYIFTSTAInternational multimodal statusreport2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IFTMCS (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPS+ 10 conditional groups, starting with:LOCTODRFFGORCPITCCTDTNADGIDEQDBlue 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 IFTMCS.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends IFTMCS, 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 IFTMCS 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

  • Returning draft bill of lading data for checking
  • Confirming the contract details of a shipment
  • Reporting the charges for a transport service

Where it fits in the message flow

Usually follows IFTMIN Instruction
This message IFTMCS Instruction contract status
Usually followed by IFTSTA International multimodal status report

Structure

Mandatory segments in IFTMCS (directory D.21A)

In UN/EDIFACT directory D.21A, the IFTMCS message has 149 segment positions arranged in 41 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

IFTMCS in practice

After receiving shipping instructions for a container to Singapore, the carrier sends the forwarder an IFTMCS with the draft bill of lading: parties, cargo description, container and seal numbers, weights and freight charges. The forwarder spots a misspelled consignee name, corrects it with an updated IFTMIN, and the carrier issues the final bill of lading.

Implementation

Implementation considerations for IFTMCS

  • Compare returned contract details with the original instructions automatically.
  • Correct discrepancies before documents are finalized.
  • Store the returned charges for later freight audit.
  • Confirm whether the carrier sends drafts, finals or both.

How ECOM helps

Automate IFTMCS 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.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

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 IFTMCS?

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

Request a Demo Contact us