© 2018 ProgM

Nachricht PAYDUC: D

NamePAYDUC
VersionD
Release18B
BeschreibungPayroll deductions advice message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A service segment starting and uniquely identifying a message. The message type code for the Payroll deductions advice message is PAYDUC. Note: Payroll deductions advice messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 PAYDUC D B UNMandatory
BGM0A segment for unique identification of the Payroll Deductions Advice message, the type of Payroll Deductions Advice and its function.Mandatory
PAI0A segment specifying the payment means (e.g. cheque or direct bank transfer) and, if required, the payment channel for the Payroll Deductions Advice. The payment conditions may also be specified.Mandatory
FII0A segment identifying the financial institution (e.g. bank) and account number of the issuing party, and, where required, the receiving party.Mandatory
DTM0A segment specifying the date, and if required the time, that the payment associated with this Payroll Deductions Advice message has been sent. If needed, repeating segments may include the message date, the date and time associated with any validation keys and other dates relevant to the whole of the message.Mandatory
CUX0A segment giving the currency and the associated exchange rate of the total amount paid to the service organisation in relation to this advice.Optional
PYT0A segment to indicate payment terms applicable to the whole message, such as the number of periods covered by the payroll deductions advice.Optional
FTX0A segment for free text information in coded or clear form, to give further clarification when required to the Payroll Deductions Advice message. It should be noted that the use of clear text may require special processing of this segment.Optional
SG10SG1Optional
RFF1A segment for referencing payment instruments, e.g. a reference to a check payment or bank transfer.Mandatory
DTM1A segment specifying the issue date of a payment instrument associated with this message, e.g. the date of a cheque.Optional
SG20SG2Optional
NAD1A segment identifying the name and address of the parties associated with the Payroll Deductions Advice and their functions. Examples are: the employer, the recipient system and the name and address of the payer's financial institution if required.Mandatory
SG31SG3Mandatory
CTA2A segment giving additional contact information of a person or department specified in the NAD segment and to whom communication should be directed.Mandatory
COM2A segment specifying communication contact number.Optional
SG40SG4Optional
GEI1A segment relevant to the processing of segment group 6, to indicate whether all individual employee payment details, or only changes from a nominated standard payment are provided.Mandatory
RFF1A segment identifying each individual service group.Mandatory
MOA1A segment giving the monetary amounts for standard payments (if applicable, both the previous and the new standard) for a service group, the commission amounts if any, and the (net) total payment amount for a service group included in the total payment. If required, other monetary amounts relevant to a service group may also be given.Mandatory
BUS1A segment to provide additional identification for each individual service group.Optional
CUX1A segment identifying the currency and associated exchange rate of the monetary amounts calculated for a service group.Optional
SG51SG5Optional
DTM2A segment specifying the date when a payment was deducted from the payroll.Mandatory
SG62SG6Mandatory
UGH3A segment to head, identify and specify an anti-collision segment group. Note: 0087, the value shall be the segment group number of the UGH/UGT segment group as stated in the message specification. It shall be identical to the value in 0087 in the corresponding UGT segment.Mandatory
SG73SG7Mandatory
NAD4A segment identifying the name of the employee (service group member) for whom payments are made by pay deduction.Mandatory
RFF4A repeating segment providing the reference identification of the employee as referred to by the originating party (e.g. the employer) and by the service group (these references may differ).Optional
MOA4A segment giving the monetary amount deducted for an employee to pay the service group. When changes only are specified in the GEI segment of segment group 4, the previous standard amount needs to be stated together with either the actual payment included in the total remittance, or the variation from the standard amount. The status data element needs to be used to indicate a permanent or temporary variation. If required, the current standard amount may also be given.Mandatory
AJT4A segment indicating the reason for an adjustment to the standard payment amount.Optional
PYT4A segment giving the number of pay periods and, if required, the pay frequency (as part of the type of period).Optional
FTX4A segment for free text information in coded or clear form, to give further information at the employee level if required. This may be used, for example, to further specify the reason for a variation from the standard monetary amount. It should be noted that the use of clear text may require special processing of the FTX segment information.Optional
DTM4A segment indicating the dates.Optional
UGT3A segment to end and check the completeness of an anti- collision segment group. Note: 0087, the value shall be the segment group number of the UGH/UGT segment group as stated in the message specification. It shall be identical to the value in 0087 in the corresponding UGH segment.Mandatory
UNS0A service segment placed at the start of the summary section to avoid segment collision.Mandatory
MOA0A segment giving the total amount paid to the service organisation in relation to this advice.Mandatory
CNT0A segment to provide message control totals as required. It should be noted that a balancing monetary total is always provided by the total amount paid to the service organisation.Optional
AUT0A segment to specify the results of the application of an authentication procedure, enabling to check the authenticity of the sender and the integrity of the data.Optional
UNT0A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.Mandatory