EDIFACT message guide · Healthcare and social
PAYDUC Payroll deductions advice
The UN/EDIFACT message an employer uses to detail payments made by payroll deduction on behalf of employees to a service organization.
- Sent by
- Employer or its representative
- Received by
- Service organization, such as an insurer or union
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT PAYDUC message?
PAYDUC is the UN/EDIFACT payroll deductions advice. The directory defines it as a message sent by a party, usually an employer or its representative, to a service-providing organization, detailing payments made by payroll deduction on behalf of employees to that organization.
Deductions can cover insurance premiums, union dues, loan repayments or charitable giving. The organization receives one payment from the employer and uses the advice to credit each employee's account. It saves the organization from collecting each amount from employees individually.
How to read this diagram: the top row shows who sends PAYDUC, 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 PAYDUC 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 union dues deducted from wages
- Detailing insurance premiums paid by payroll deduction
- Reporting loan repayments deducted from pay
Where it fits in the message flow
No other message routinely comes directly before or after PAYDUC; 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 PAYDUC (directory D.21A)
In UN/EDIFACT directory D.21A, the PAYDUC message has 33 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
- PAI
- FII
- DTM
- SG4 (GEI)
- UNS
- MOA
- UNT
Practical example
PAYDUC in practice
An employer deducts health insurance premiums from 600 employees' salaries each month. It sends the insurer a PAYDUC listing each employee, the policy reference and the amount deducted, together with one payment. The insurer credits each policy and follows up two employees whose deductions stopped.
Implementation
Implementation considerations for PAYDUC
- Identify employees with references the organization recognizes.
- Reconcile the advice total with the payment.
- Report changes, such as stopped deductions.
- Protect employees' personal data under applicable law.
How ECOM helps
Automate PAYDUC 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 PAYDUC?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.