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

COPAYM Contributions for payment

The UN/EDIFACT message an enterprise uses to declare the information for paying its social contributions to the responsible authority.

Sent by
Enterprise (employer)
Received by
Social contribution authority
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT COPAYM message?

COPAYM is the UN/EDIFACT contributions for payment message. The directory defines it as a message from an enterprise providing the information it must declare for the payment of its social contributions to the responsible authority. It may be used to declare contributions based on wages paid and other bases.

The declaration summarizes wages and contributions due for the period, so the authority can match the payment it receives and maintain the contribution records of the employer and its employees. Corrections are declared similarly.

How the EDIFACT COPAYM message worksDiagram of the UN/EDIFACT COPAYM Contributions for payment message. Enterprise (employer) sends it to social contribution authority. It usually follows SOCADE. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), GEI (Processing information) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification), UNS (Section control), the required SG2 loop with PNA (Party identification) and UNS (Section control). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT COPAYM message worksContributions for payment: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSSOCADESocial administrationCOPAYMSENDEREnterprise (employer)RECEIVERSocial contributionauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage COPAYMUNH … UNTSTART OF MESSAGEBGMBeginning of messageGEIProcessing informationDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats up to 9PNAParty identificationUNSSection controlMandatory group SG2 · repeats up to 9,999PNAParty identificationUNSSection control+ 4 conditional groups, starting with:COTLOCPAIAUTBlue 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 COPAYM. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT COPAYM message worksDiagram of the UN/EDIFACT COPAYM Contributions for payment message. Enterprise (employer) sends it to social contribution authority. It usually follows SOCADE. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message), GEI (Processing information) and DTM (Date/time/period) and body and segment groups: the required SG1 loop with PNA (Party identification), UNS (Section control), the required SG2 loop with PNA (Party identification) and UNS (Section control). 4 conditional segment groups are listed by their trigger segment.How the EDIFACT COPAYMmessage worksContributions for payment: who sends it, whereit fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSSOCADESocial administrationCOPAYMSENDEREnterprise(employer)RECEIVERSocialcontributionauthorityCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYNo business reply expected2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message COPAYM (UNH … UNT)START OF MESSAGEBGMBeginning of messageGEIProcessing informationDTMDate/time/periodBODY AND SEGMENT GROUPSMandatory group SG1 · repeats upto 9PNAParty identificationUNSSection controlMandatory group SG2 · repeats upto 9,999PNAParty identificationUNSSection control+ 4 conditional groups, starting with:COTLOCPAIAUTBlue 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 COPAYM.Your trading partner's implementation guide adds itsown requirements.

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

  • Declaring monthly or quarterly social contributions
  • Supporting payment of contributions
  • Correcting previous declarations

Where it fits in the message flow

Usually follows SOCADE Social administration
This message COPAYM Contributions for payment

Structure

Mandatory segments in COPAYM (directory D.21A)

In UN/EDIFACT directory D.21A, the COPAYM message has 46 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
  • BGM
  • GEI
  • DTM
  • SG1 (PNA)
  • UNS
  • SG2 (PNA)
  • UNS
  • UNT

Practical example

COPAYM in practice

At the end of each month, an employer's payroll system calculates the social contributions due. It sends the authority a COPAYM with the total wages, the contribution bases and the amounts due by contribution type, and pays the total. The authority matches the payment to the declaration.

Implementation

Implementation considerations for COPAYM

  • Calculate contributions with the current rates and ceilings.
  • Reconcile the declaration with the payment made.
  • Meet the declaration and payment deadlines.
  • Follow the authority's current specification.

How ECOM helps

Automate COPAYM with ECOM

Solution

Financial Document Automation

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

Solution

Enterprise Integration

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

Industry

Healthcare

Secure B2B integration and file transfer for providers, suppliers, distributors and healthcare partners.

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

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

Request a Demo Contact us