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

PRPAID Insurance premium payment

The UN/EDIFACT message used to notify premium or claim amounts to be collected, paid, not paid or partly paid, individually or in series.

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

What is the EDIFACT PRPAID message?

PRPAID is the UN/EDIFACT insurance premium payment message. The directory defines it as a message communicating parties use to notify the recipient about premium or claim amounts to be collected, evaluated, paid, not paid or partly paid, either individually or in series through bordereaux.

Intermediaries collect premiums from clients and pass them on to insurers, often in periodic settlements. PRPAID tells the insurer what was collected for which policies, what remains unpaid and what is being remitted, so both sides can reconcile their accounts.

How the EDIFACT PRPAID message worksDiagram of the UN/EDIFACT PRPAID Insurance premium payment message. Insurer, intermediary or client sends it to insurer or intermediary. It usually follows INSPRE. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: GEI (Processing information), RFF (Reference) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with NAD (Name and address) and UNS (Section control). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT PRPAID message worksInsurance premium payment: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSINSPREInsurance premiumPRPAIDSENDERInsurer, intermediaryor clientRECEIVERInsurer orintermediaryCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage PRPAIDUNH … UNTSTART OF MESSAGEGEIProcessing informationRFFReferenceDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9NADName and addressUNSSection control+ 2 conditional groups, starting with:DOCMOABlue 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 PRPAID. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT PRPAID message worksDiagram of the UN/EDIFACT PRPAID Insurance premium payment message. Insurer, intermediary or client sends it to insurer or intermediary. It usually follows INSPRE. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: GEI (Processing information), RFF (Reference) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with NAD (Name and address) and UNS (Section control). 2 conditional segment groups are listed by their trigger segment.How the EDIFACT PRPAIDmessage worksInsurance premium payment: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSINSPREInsurance premiumPRPAIDSENDERInsurer,intermediary orclientRECEIVERInsurer orintermediaryCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message PRPAID (UNH … UNT)START OF MESSAGEGEIProcessing informationRFFReferenceDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9NADName and addressUNSSection control+ 2 conditional groups, starting with:DOCMOABlue 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 PRPAID.Your trading partner's implementation guide adds itsown requirements.

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

  • Reporting premiums collected by a broker
  • Reporting unpaid or partly paid premiums
  • Settling claim payments between parties

Where it fits in the message flow

Usually follows INSPRE Insurance premium
This message PRPAID Insurance premium payment

Structure

Mandatory segments in PRPAID (directory D.21A)

In UN/EDIFACT directory D.21A, the PRPAID message has 35 segment positions arranged in 7 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
  • GEI
  • RFF
  • DTM
  • SG1 (NAD)
  • UNS
  • UNT

Practical example

PRPAID in practice

At the end of the month, a broker sends an insurer a PRPAID listing the premiums collected for each policy, two policies where clients paid only part, and one unpaid premium. It remits the total collected, and the insurer applies the payments and follows up the unpaid policy.

Implementation

Implementation considerations for PRPAID

  • Match payments to policies and premium notifications.
  • Report partial and non-payments explicitly.
  • Reconcile the reported total with the remittance.
  • Agree settlement periods with each insurer.

How ECOM helps

Automate PRPAID 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

Order-to-Cash Automation

Automate the flow from purchase order to payment across every customer channel.

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

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

Request a Demo Contact us