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

IPPOMO Motor insurance policy

The UN/EDIFACT message insurers, intermediaries and clients use to exchange motor policy proposals, confirmations, adjustments and renewals.

Sent by
Insurer, intermediary or client
Received by
Insurer, intermediary or client
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT IPPOMO message?

IPPOMO is the UN/EDIFACT motor insurance policy message. The directory defines it as a message exchanged between insurers, intermediaries and clients to transfer details of the proposal, confirmation, adjustment and renewal of a motor policy.

Motor policies cover the vehicle, the drivers, the use and the cover chosen. Brokers place large numbers of motor policies with insurers, and exchanging them as structured data speeds up quotation and issue of cover, including for fleet policies with frequent vehicle changes. It is one of the insurance policy messages.

How the EDIFACT IPPOMO message worksDiagram of the UN/EDIFACT IPPOMO Motor insurance policy message. Insurer, intermediary or client sends it to insurer, intermediary or client. It usually starts the exchange. It is usually followed by INSPRE. 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 SG3 loop with ICD (Insurance cover description), the required SG7 loop with PNA (Party identification) and the required SG12 loop with DOC (Document/message details) and UNS (Section control). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT IPPOMO message worksMotor insurance policy: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIPPOMOSENDERInsurer, intermediaryor clientRECEIVERInsurer, intermediaryor clientCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINSPREInsurance premium2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage IPPOMOUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG3 · repeats up to 9ICDInsurance cover descriptionMandatory group SG7 · repeats up to 999PNAParty identificationMandatory group SG12 · repeats up to 9DOCDocument/message detailsUNSSection control+ 8 conditional groups, starting with:PNADOCADRCTAEVEPYTRODDTMBlue 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 IPPOMO. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT IPPOMO message worksDiagram of the UN/EDIFACT IPPOMO Motor insurance policy message. Insurer, intermediary or client sends it to insurer, intermediary or client. It usually starts the exchange. It is usually followed by INSPRE. 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 SG3 loop with ICD (Insurance cover description), the required SG7 loop with PNA (Party identification) and the required SG12 loop with DOC (Document/message details) and UNS (Section control). 8 conditional segment groups are listed by their trigger segment.How the EDIFACT IPPOMOmessage worksMotor insurance policy: who sends it, where itfits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeIPPOMOSENDERInsurer,intermediary orclientRECEIVERInsurer,intermediary orclientCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYINSPREInsurance premium2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message IPPOMO (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG3 · repeats upto 9ICDInsurance cover descriptionMandatory group SG7 · repeats upto 999PNAParty identificationMandatory group SG12 · repeatsup to 9DOCDocument/messagedetailsUNSSection control+ 8 conditional groups, starting with:PNADOCADRCTAEVEPYTRODDTMBlue 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 IPPOMO.Your trading partner's implementation guide adds itsown requirements.

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

  • Sending motor insurance proposals
  • Confirming cover and issuing policies
  • Adding or removing vehicles on fleet policies
  • Renewing motor policies

Where it fits in the message flow

This message IPPOMO Motor insurance policy
Usually followed by INSPRE Insurance premium

Structure

Mandatory segments in IPPOMO (directory D.21A)

In UN/EDIFACT directory D.21A, the IPPOMO message has 218 segment positions arranged in 37 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
  • SG3 (ICD)
  • SG7 (PNA)
  • UNS
  • UNT

Practical example

IPPOMO in practice

A company adds 12 new vans to its fleet insured through a broker. The broker sends the insurer an IPPOMO adjustment adding the vehicles with their registration numbers, values and use. The insurer confirms the cover and notifies the additional premium with an INSPRE.

Implementation

Implementation considerations for IPPOMO

  • Validate vehicle and driver data at entry.
  • Distinguish proposals, confirmations, adjustments and renewals.
  • Protect drivers' personal data under applicable law.
  • Keep cover dates exact for compliance with motor insurance laws.

How ECOM helps

Automate IPPOMO with ECOM

Industry

Financial Services

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

Industry

Trucking and Transportation

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

Solution

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

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

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

Request a Demo Contact us