Directory   Messages   Segments   Composites   Data elements   Codes Meaning of the change indicators
  UN/EDIFACT  D.03A (Batch) Syntax version 3 Issue date 2003-06-23  
  Message type specification PAYORD
PAYORD 3 Payment order message  

TBG5 Finance

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.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
The Payment order message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.

This message may be applied for both national and international settlements.

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.

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


3.1 Standard terms and definitions
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.


4.1 Data segment clarification
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
  Generated by GEFEG.FX