Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D95B Messages page.
UN/EDIFACT
DRAFT RECOMMENDATION

Payment order message

This message is available for formal trial for at least six months from the date of approval by UN/ECE/TRADE/WP.4.

Organisations are invited to trial this message. Comments on the results from the trial should be forwarded to their Rapporteur's Team Secretariat as soon as they are available. Based on the results of the trials, a UNSM may be issued.

The segments, composite data elements, data elements and codes for use in the trial of this message are contained in the Draft directory. However, this information may differ from that in the Standard directory (UNTDID), even for material having the same identifying tags.


Message Type:PAYORD
Version:D
Release:95B
Contr. Agency:UN
Status:2
Revision:2
Date:95-07-07
SOURCE:Joint development by PAEB and WEEB MD4

CONTENTS
Payment order message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
  5. MESSAGE DEFINITION
    1. Data segment clarification
    2. Data segment index (alphabetical sequence)
    3. Message structure
      1. Segment table

For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction


This message also occurs in the following versions of this standard:
D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B

0. INTRODUCTION

This specification provides the definition of the Payment order message (PAYORD) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

A Payment Order is sent by the Ordering Customer (or Payor or Agent on behalf of the Ordering Customer) to the Ordered Bank, to instruct the Ordered Bank to debit an account it services for the Ordering Customer, and to arrange for the payment of a specified amount to the Beneficiary (or Payee or Agent in favour of Beneficiary) in settlement of the referenced business transaction(s). Throughout this document, the term 'Ordering Customer' refers to either an Ordering Customer, or a Payor or Agent acting on behalf of the Ordering Customer; likewise the term 'Beneficiary' refers to either a Beneficiary, or a Payee or Agent acting on behalf of the Beneficiary.


1.2. Field of Application

This message may be applied for both national and international settlements. It is based on universal practice and is not dependent on the type of business or industry.


1.3. Principles

A Payment Order may cover the financial settlement of one or more commercial trade transactions, such as invoices, credit notes, debit notes, etc. It is not intended for use in securities trading.

The Ordered Bank may need a confirmation/authorization to be able to process the Payment Order Message, if the payment order(s) is (are) sent by a third party.


2. REFERENCES

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.


3. TERMS AND DEFINITIONS

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.


4. MESSAGE DEFINITION


4.1. Data Segment Clarification

This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.

0010 | UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Payment order message is PAYORD.

Note: Payment order messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element0065PAYORD
0052D
005495B
0051UN

0020 BGM, Beginning of message

A segment for unique identification of the Payment Order, the type of Payment Order and its function. The requirement for a response, e.g., related debit advice, may be indicated.

Note: The identification will be passed back to the Ordering Customer for reconciliation purposes; it would be used in the case of a cancellation or confirmation of a Payment Order.

0030 BUS, Business function

A segment identifying certain characteristics of the Payment Order, such as its business function. In so doing, it provides information about the message that may be used, for instance, for routing within an institution, for tariffing, or for the provision of some statistical information.

0040 PAI, Payment instructions

A segment specifying the conditions, guarantee, method and channel of payment for the Payment Order.

0050 FCA, Financial charges allocation

A segment specifying the method for allocation of charges and allowances (e.g., charges borne by the Ordering Customer, the Beneficiary or both), and identifying the Ordering Customer's account to which such charges or allowances should be directed where it is different from the principal account.

0060 DTM, Date/time/period

A segment identifying the date/time of creation of the message, the requested execution date and/or due date at the beneficiary's side as well as other dates and times relevant to the financial transaction.

0070 FTX, Free text

This segment contains the details of payment, which have to be passed from the ordered bank to the beneficiary through the banking chain together with the remittance details.

0080 Segment Group 1: RFF-DTM

A group of segments identifying a previously-sent message.

0090 RFF, Reference

A segment specifying the reference number of the previously-sent message.

0100 DTM, Date/time/period

A segment identifying the creation date of the referenced message.

0110 Segment Group 2: MOA-CUX-DTM-RFF

A group of segments identifying the monetary amount and, if necessary, the currencies, exchange rate and date for the payment.

0120 MOA, Monetary amount

A segment giving the amount of the payment.

0130 CUX, Currencies

A segment identifying the source currency and the target currency of the transaction when they are different. The rate of exchange is solely used when previously agreed between the Ordering Customer and the Ordered Bank.

0140 DTM, Date/time/period

A segment identifying the effective date and/or time the rate of exchange was fixed. The other occurrence identifies the reference date.

0150 RFF, Reference

A segment identifying other transactions to which funds associated with the Payment Order are related, such as a separate foreign exchange deal.

0160 Segment Group 3: FII-CTA-COM

A group of segments providing information about the financial institutions and accounts related to the Payment Order, together with details of any parties to be contacted in relation with the transaction. This group may also contain a single customer for the debiting and/or crediting side.

0170 FII, Financial institution information

A segment identifying the financial institution (e.g., bank) and relevant account number and currency for each party involved in the transaction. The Ordering Customer may indicate the previously agreed choice of financial institution for payment.

0180 CTA, Contact information

A segment identifying a person or a department for the financial institution specified in the FII segment and to whom communication should be directed.

0190 COM, Communication contact

A segment providing a communication number for the party identified in the FII segment and optionally for the contact identified in the associated CTA segment.

0200 Segment Group 4: NAD-CTA-COM

A group of segments identifying the name and address of the non-financial institutions involved in the transaction and their contacts.

0210 NAD, Name and address

A segment identifying the name and address of the non-financial parties associated with the Payment Order and their functions.

0220 CTA, Contact information

A segment identifying a person or a department for the party specified in the NAD segment and to whom communication should be directed.

0230 COM, Communication contact

A segment providing a communication number for the party identified in the NAD segment and optionally for the contact identified in the associated CTA segment.

0240 Segment Group 5: INP-FTX-DTM

A group of segments containing instructions from the Ordering Customer relating to parties identified in the NAD and FII segments. It specifies action to be taken by the identified parties, and the date (and optionally time) by which such action needs to be taken.

0250 INP, Parties to instruction

A segment identifying the party to enact the instruction and the parties to be contacted at or by the associated financial institution on matters concerning the execution of the payment. It specifies where appropriate the instruction in coded form.

0260 FTX, Free text

A segment providing free text instruction relating to the associated INP segment.

0270 DTM, Date/time/period

A segment specifying the earliest and the latest dates and times by which the instruction specified in the INP and/or FTX segments needs to be carried out.

0280 Segment Group 6: GIS-MOA-LOC-NAD-RCS-FTX

A group of segments providing information for subsequent use by regulatory authorities requiring statistical and other types of data. It also identifies the regulatory authority for which the information is intended followed by the information itself.

0290 GIS, General indicator

A segment identifying what processing should be completed for regulatory authorities.

0300 MOA, Monetary amount

A segment giving the amount and the currency of each transaction to be reported.

0310 LOC, Place/location identification

A segment giving the different origins/destinations (places) of goods/investment/services.

0320 NAD, Name and address

A segment identifying the recipient of the associated informative text.

0330 RCS, Requirements and conditions

A segment giving the nature (e.g. goods, transport services) and direction of each transaction to be recorded in coded form.

0340 FTX, Free text

A segment giving information, in coded or clear form, to provide information relevant to regulatory authorities requirements.

0350 Segment Group 7: DOC-DTM

A group of segments providing brief structured cross references to transactions to which the Payment Order relates.

0360 DOC, Document/message details

A segment identifying the document(s) relating to the payment order.

0370 DTM, Date/time/period

A segment identifying the date of issue of the document(s) described in the preceding DOC segment.

0380 Segment Group 8: AUT-DTM

A group of segments specifying the details of authentication.

0390 AUT, Authentication result

A segment specifying the details of any authentication (validation) procedure applied to the Payment Order message.

0400 DTM, Date/time/period

A segment identifying the date and where necessary, the time of validation.

0410 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.


4.2. Data segment index (Alphabetical sequence by tag)

AUT Authentication result
BGM Beginning of message
BUS Business function
COM Communication contact
CTA Contact information
CUX Currencies
DOC Document/message details
DTM Date/time/period
FCA Financial charges allocation
FII Financial institution information
FTX Free text
GIS General indicator
INP Parties to instruction
LOC Place/location identification
MOA Monetary amount
NAD Name and address
PAI Payment instructions
RCS Requirements and conditions
RFF Reference
UNH Message header
UNT Message trailer

4.3. Message structure


4.3.1. Segment table

├─UNH Message header ×1 (M)
├─BGM Beginning of message ×1 (M)
├─BUS Business function ×1 (C)
├─PAI Payment instructions ×1 (C)
├─FCA Financial charges allocation ×1 (C)
├─DTM Date/time/period ×4 (M)
├─FTX Free text ×5 (C)
├─Segment Group 1 ×5 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 2 ×1 (M)
├─MOA Monetary amount ×1 (M)
├─CUX Currencies ×1 (C)
├─DTM Date/time/period ×2 (C)
└─RFF Reference ×1 (C)
├─Segment Group 3 ×4 (C)
├─FII Financial institution information ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 4 ×6 (C)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 5 ×4 (C)
├─INP Parties to instruction ×1 (M)
├─FTX Free text ×1 (C)
└─DTM Date/time/period ×2 (C)
├─Segment Group 6 ×10 (C)
├─GIS General indicator ×1 (M)
├─MOA Monetary amount ×1 (C)
├─LOC Place/location identification ×2 (C)
├─NAD Name and address ×1 (C)
├─RCS Requirements and conditions ×1 (C)
└─FTX Free text ×10 (C)
├─Segment Group 7 ×10 (C)
├─DOC Document/message details ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 8 ×5 (C)
├─AUT Authentication result ×1 (M)
└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D95B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.