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 · Healthcare and social

SUPMAN Superannuation maintenance

The UN/EDIFACT message used to send membership maintenance information about members of a superannuation (pension) scheme.

Sent by
Employer or its representative
Received by
Superannuation fund administrator
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT SUPMAN message?

SUPMAN is the UN/EDIFACT superannuation maintenance message. The directory defines it as a message sent by a party to an organization administering a superannuation scheme, specifying membership maintenance information about scheme members.

Maintenance covers new members, changes of personal details, salary changes and members leaving employment. Accurate member data lets the fund allocate contributions, sent with SUPCOT, to the right accounts. Some jurisdictions now prescribe their own data standards for superannuation messages; where they apply, they are used instead of EDIFACT.

How the EDIFACT SUPMAN message worksDiagram of the UN/EDIFACT SUPMAN Superannuation maintenance message. Employer or its representative sends it to superannuation fund administrator. It usually starts the exchange. It is usually followed by SUPCOT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and RFF (Reference) and body and segment groups: UNS (Section control) and the required SG3 loop with NAD (Name and address), DTM (Date/time/period) and the required SG7 loop with GEI (Processing information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SUPMAN message worksSuperannuation maintenance: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSUPMANSENDEREmployer or itsrepresentativeRECEIVERSuperannuation fundadministratorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYSUPCOTSuperannuationcontributions advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage SUPMANUNH … UNTSTART OF MESSAGEBGMBeginning of messageRFFReferenceBODY AND SEGMENT GROUPSUNSSection controlMandatory group SG3 · repeats many timesNADName and addressDTMDate/time/periodMandatory group SG7 · repeats up to 20GEIProcessing information+ 4 conditional groups, starting with:NADRELEMPMEMBlue 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 SUPMAN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT SUPMAN message worksDiagram of the UN/EDIFACT SUPMAN Superannuation maintenance message. Employer or its representative sends it to superannuation fund administrator. It usually starts the exchange. It is usually followed by SUPCOT. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and RFF (Reference) and body and segment groups: UNS (Section control) and the required SG3 loop with NAD (Name and address), DTM (Date/time/period) and the required SG7 loop with GEI (Processing information). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT SUPMANmessage worksSuperannuation maintenance: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeSUPMANSENDEREmployer or itsrepresentativeRECEIVERSuperannuationfundadministratorCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYSUPCOTSuperannuation contributions advice2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message SUPMAN (UNH … UNT)START OF MESSAGEBGMBeginning of messageRFFReferenceBODY AND SEGMENT GROUPSUNSSection controlMandatory group SG3 · repeatsmany timesNADName and addressDTMDate/time/periodMandatory group SG7 · repeatsup to 20GEIProcessing information+ 4 conditional groups, starting with:NADRELEMPMEMBlue 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 SUPMAN.Your trading partner's implementation guide adds itsown requirements.

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

  • Registering new members with a fund
  • Reporting changes in member details
  • Reporting members who leave employment

Where it fits in the message flow

This message SUPMAN Superannuation maintenance
Usually followed by SUPCOT Superannuation contributions advice

Structure

Mandatory segments in SUPMAN (directory D.21A)

In UN/EDIFACT directory D.21A, the SUPMAN message has 38 segment positions arranged in 10 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
  • RFF
  • UNS
  • SG3 (NAD)
  • UNT

Practical example

SUPMAN in practice

An employer hires 25 staff who choose the default fund. It sends the fund a SUPMAN registering each new member with personal details and start date. When contributions arrive with the next SUPCOT, the fund already has accounts for the new members.

Implementation

Implementation considerations for SUPMAN

  • Register members before their first contributions.
  • Protect members' personal data under applicable law.
  • Check whether the jurisdiction mandates a different data standard.
  • Reconcile member lists with payroll periodically.

How ECOM helps

Automate SUPMAN with ECOM

Solution

Enterprise Integration

Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.

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 healthcare and social messages

All 20 healthcare and social messages

Need help with SUPMAN?

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

Request a Demo Contact us