EDIFACT message guide · Healthcare and social
SUPCOT Superannuation contributions advice
The UN/EDIFACT message used to detail contribution payments made for 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 SUPCOT message?
SUPCOT is the UN/EDIFACT superannuation contributions advice. The directory defines it as a message sent by a party to an organization administering a superannuation scheme, detailing the contribution payments made for members of the scheme.
Superannuation is the term used in Australia and elsewhere for retirement savings schemes. Employers pay contributions for many employees into funds, and the advice tells the fund how much to credit to each member and for what type of contribution. Member details are maintained with SUPMAN.
How to read this diagram: the top row shows who sends SUPCOT, 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 SUPCOT 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.
When it is used
- Detailing employer and employee pension contributions
- Allocating a contribution payment to members
- Reporting contribution types and periods
Where it fits in the message flow
No other message routinely comes directly before or after SUPCOT; it is exchanged when the business event occurs. If the partners agree, the receiver confirms each interchange with a CONTRL syntax and service report.
Structure
Mandatory segments in SUPCOT (directory D.21A)
In UN/EDIFACT directory D.21A, the SUPCOT message has 34 segment positions arranged in 5 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)
- UNS
- MOA
- UNT
Practical example
SUPCOT in practice
An employer pays quarterly superannuation contributions for 300 employees to a fund. Its payroll system sends the fund a SUPCOT listing each member, the period, the employer contribution and any salary-sacrifice amounts, matching the payment made. The fund allocates the amounts to members' accounts.
Implementation
Implementation considerations for SUPCOT
- Check whether the jurisdiction mandates a different data standard.
- Identify members with the fund's member identifiers.
- Reconcile the advice total with the payment.
- Meet the contribution payment deadlines.
How ECOM helps
Automate SUPCOT with ECOM
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Industry
Financial Services
Secure file transfer and B2B integration for banks and financial institutions.
Solution
Enterprise Integration
Any-to-any integration across partners, systems, protocols, security requirements, formats and ERPs, in batch or real time.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related healthcare and social messages
Need help with SUPCOT?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.