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

INSPRE Insurance premium

The UN/EDIFACT message insurers and intermediaries use to notify premiums due from a client, with the detail needed to request payment.

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

What is the EDIFACT INSPRE message?

INSPRE is the UN/EDIFACT insurance premium message. The directory defines it as a message communicating parties use to notify the recipient about premiums due from a client, carrying all the information needed to produce a detailed request for payment.

A premium notification identifies the policy, the period covered, the premium components such as base premium, taxes and fees, and the due dates. Brokers and agents use it to bill clients and to reconcile what they collect with what they owe the insurer. Payment and collection status then travel in PRPAID.

How the EDIFACT INSPRE message worksDiagram of the UN/EDIFACT INSPRE Insurance premium message. Insurer or insurance intermediary sends it to intermediary, client or other insurer. It usually follows IPPOAD. It is usually followed by PRPAID. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: DTM (Date/time/period) and body and segment groups: the required SG1 loop with ATT (Attribute), the required SG2 loop with NAD (Name and address), the required SG3 loop with DTM (Date/time/period), the required SG4 loop with ICD (Insurance cover description) and the required SG5 loop with MOA (Monetary amount) and CUX (Currencies) and MOA (Monetary amount). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT INSPRE message worksInsurance premium: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIPPOADInsurance policyadministrationINSPRESENDERInsurer or insuranceintermediaryRECEIVERIntermediary, client orother insurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPRPAIDInsurance premiumpayment2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage INSPREUNH … UNTSTART OF MESSAGEDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9ATTAttributeMandatory group SG2 · repeats up to 9NADName and addressMOAMonetary amount+ required SG3 (DTM) and 4 conditional groups, starting with:INDATTTAXDTMBlue 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 INSPRE. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT INSPRE message worksDiagram of the UN/EDIFACT INSPRE Insurance premium message. Insurer or insurance intermediary sends it to intermediary, client or other insurer. It usually follows IPPOAD. It is usually followed by PRPAID. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: DTM (Date/time/period) and body and segment groups: the required SG1 loop with ATT (Attribute), the required SG2 loop with NAD (Name and address), the required SG3 loop with DTM (Date/time/period), the required SG4 loop with ICD (Insurance cover description) and the required SG5 loop with MOA (Monetary amount) and CUX (Currencies) and MOA (Monetary amount). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT INSPREmessage worksInsurance premium: who sends it, where it fitsand what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSIPPOADInsurance policy administrationINSPRESENDERInsurer orinsuranceintermediaryRECEIVERIntermediary,client or otherinsurerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYPRPAIDInsurance premium payment2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message INSPRE (UNH … UNT)START OF MESSAGEDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9ATTAttributeMandatory group SG2 · repeats upto 9NADName and addressMOAMonetary amount+ required SG3 (DTM) and 4 conditionalgroups, starting with:INDATTTAXDTMBlue 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 INSPRE.Your trading partner's implementation guide adds itsown requirements.

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

  • Notifying a broker of premiums due on policies
  • Billing new business, renewals and adjustments
  • Providing premium breakdowns including taxes

Where it fits in the message flow

Usually follows IPPOAD Insurance policy administration
This message INSPRE Insurance premium
Usually followed by PRPAID Insurance premium payment

Structure

Mandatory segments in INSPRE (directory D.21A)

In UN/EDIFACT directory D.21A, the INSPRE message has 30 segment positions arranged in 9 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
  • DTM
  • SG1 (ATT)
  • SG2 (NAD)
  • SG3 (DTM)
  • MOA
  • UNT

Practical example

INSPRE in practice

An insurer renews 400 commercial policies placed through a broker. It sends the broker an INSPRE listing each policy, the renewal period, the premium, insurance premium tax and fees, and the due date. The broker invoices its clients from the data and later reports collections to the insurer.

Implementation

Implementation considerations for INSPRE

  • Break down premium, taxes and fees as the recipient needs them.
  • Reference policy numbers both parties hold.
  • Reconcile notified premiums with collections.
  • Follow the market's agreed standards where they exist.

How ECOM helps

Automate INSPRE with ECOM

Industry

Financial Services

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

Solution

Financial Document Automation

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

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

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

Request a Demo Contact us