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 · Insurance

IFTICL Cargo insurance claims

The UN/EDIFACT message used to exchange cargo insurance claim information for a single consignment between parties in the transport chain.

Sent by
Insured party, broker or claims agent
Received by
Cargo insurer or its agent
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT IFTICL message?

IFTICL is the UN/EDIFACT cargo insurance claims message. The directory describes it as a message for exchanging cargo and transport information related to cargo insurance claims between trading partners in the transport chain worldwide, covering a single consignment.

A cargo claim brings together the insured consignment, the transport details, the parties, the loss or damage found and the amounts claimed. Exchanging it as structured data lets insurers, brokers, surveyors and claims agents process claims without rekeying documents. It can be used by any party in the claim process.

How the EDIFACT IFTICL message worksDiagram of the UN/EDIFACT IFTICL Cargo insurance claims message. Insured party, broker or claims agent sends it to cargo insurer or its agent. It usually follows IFTMCA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG5 loop with TDT (Transport information) and the required SG8 loop with LOC (Place/location identification), the required SG10 loop with NAD (Name and address) and the required SG12 loop with STS (Status). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTICL message worksCargo insurance claims: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMCAConsignment adviceIFTICLSENDERInsured party, brokeror claims agentRECEIVERCargo insurer or itsagentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IFTICLUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG5 · repeats up to 99TDTTransport informationMandatory group SG8 · repeats up to 99LOCPlace/location identificationMandatory group SG10 · repeats up to 99NADName and addressMandatory group SG12 · repeats up to 99STSStatus+ 9 conditional groups, starting with:DOCRFFNADCTAMOAGIDEQDBlue 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 IFTICL. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IFTICL message worksDiagram of the UN/EDIFACT IFTICL Cargo insurance claims message. Insured party, broker or claims agent sends it to cargo insurer or its agent. It usually follows IFTMCA. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG5 loop with TDT (Transport information) and the required SG8 loop with LOC (Place/location identification), the required SG10 loop with NAD (Name and address) and the required SG12 loop with STS (Status). 9 conditional segment groups are listed by their trigger segment.How the EDIFACT IFTICLmessage worksCargo insurance claims: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIFTMCAConsignment adviceIFTICLSENDERInsured party,broker or claimsagentRECEIVERCargo insurer orits agentCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IFTICL (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG5 · repeats upto 99TDTTransport informationMandatory group SG8 · repeatsup to 99LOCPlace/locationidentificationMandatory group SG10 · repeats upto 99NADName and address+ required SG12 (STS) and 9 conditionalgroups, starting with:DOCRFFNADCTAMOAGIDEQDBlue 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 IFTICL.Your trading partner's implementation guide adds itsown requirements.

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

  • Submitting a cargo insurance claim
  • Passing claim details between brokers, agents and insurers
  • Reporting surveyed loss or damage for a consignment

Where it fits in the message flow

Usually follows IFTMCA Consignment advice
This message IFTICL Cargo insurance claims

Structure

Mandatory segments in IFTICL (directory D.21A)

In UN/EDIFACT directory D.21A, the IFTICL message has 83 segment positions arranged in 28 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
  • SG5 (TDT)
  • SG10 (NAD)
  • SG12 (STS)
  • UNT

Practical example

IFTICL in practice

A container of electronics arrives with water damage. The consignee's broker submits an IFTICL to the cargo insurer with the insurance certificate, the transport details, the damage found by the surveyor and the amount claimed. The insurer's claims system opens a file and requests the carrier's documents for a recovery claim.

Implementation

Implementation considerations for IFTICL

  • Reference the insurance certificate or policy declaration for the consignment.
  • Include transport details needed for recovery against carriers.
  • Attach or reference survey reports and supporting documents.
  • Track claim status through to settlement.

How ECOM helps

Automate IFTICL with ECOM

Industry

Trucking and Transportation

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

Industry

Financial Services

Secure file transfer and B2B integration for banks and financial institutions.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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

Related messages

Related insurance messages

All 18 insurance messages

Need help with IFTICL?

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

Request a Demo Contact us