Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D02B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Multiple payment order message

Version:D
Release:02B
Contr. Agency:UN
Revision:5
Date:2003-02-13
SOURCE:D6 Finance (SWG)

CONTENTS
Multiple payment order message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
    2. Segment index (alphabetical sequence by tag)
    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.3, 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 Multiple payment order message (PAYMUL) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional definition

A Multiple 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 specified amounts to several Beneficiaries (or Payees) 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 (sending) 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 Multiple 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 Multiple 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.
  • Charges may be borne on account(s) different of the account(s) held by the Ordering Customer.
  • Several debit accounts, execution dates and currencies may be specified.
  • The Ordered Bank may need a confirmation/authorization (e.g. AUTHOR message) to be allowed to process the Multiple Payment Order message.
  • The only way to modify a Multiple Payment Order message is to cancel the whole message or part thereof (e.g. by the use of the FINCAN message). In that respect, one to many order(s) could be cancelled within the message, avoiding to be obliged to cancel the whole message.

2. REFERENCES

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


3. TERMS AND DEFINITIONS


3.1. Standard terms and definitions

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


4. MESSAGE DEFINITION


4.1. Segment clarification

This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.

The following semantic principles applying to the message are intended to facilitate the understanding of the message:

The Multiple Payment Order message is structured in three levels:

A,B, and C. In the Branching Diagram, level A corresponds to page 1, level B corresponds to page 2, and level C corresponds to pages 3 and 4.

-A level contains data related to the whole message and is contained in Segment Group 1 and Segment Group 2 and the Heading section.

-B level contains data from the debit side (one debit account, one currency, one execution date) and data which applies to all further details of C level(s) and is contained in Segment Group 3 through Segment Group 9.

-C level contains mainly data related to the credit side, and this data is considered as unique for each payment transaction and is contained in Segment Group 10 through Segment Group 21.

  • The structure of the message is designed to allow several B levels, each B level being followed by its related C levels.

Where a choice of code or text is given only the code element should be used wherever possible.

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Multiple payment order message is PAYMUL.

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

Data element0065PAYMUL
0052D
005402B
0051UN

0020 BGM, Beginning of message

A segment by means of which the sender must uniquely identify the PAYMUL message using its type and number and when necessary its function.

Note: The identification will be passed back to the ordering customer for reconciliation purposes, if a reference is not quoted in the B- level.

0030 DTM, Date/time/period

A segment specifying the date and if required the time when the message is created.

0040 BUS, Business function

A segment providing information to the ordered bank to route the message, or for tariffing or for the provision of some statistical information.

0050 Segment Group 1: RFF-DTM

A group of segments identifying any previously sent message.

0060 RFF, Reference

A segment specifying the reference number of another message.

0070 DTM, Date/time/period

A segment identifying the creation date of the referenced message.

0080 Segment Group 2: FII-CTA-COM

A group of segments identifying the financial institutions involved in the multiple payment order and the routing functions with their contacts.

0090 FII, Financial institution information

A segment identifying the financial institutions associated with the transaction in coded or uncoded form and their function.

0100 CTA, Contact information

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

0110 COM, Communication contact

A segment providing communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.

0120 Segment Group 3: NAD-CTA-COM

A group of segments identifying the ordering party, which is valid for all payment orders.

0130 NAD, Name and address

Name and address for the ordering customer.

0140 CTA, Contact information

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

0150 COM, Communication contact

A segment identifying communication type(s) and number(s) of person(s) or department(s) specified in the associated CTA segment.

0160 Segment Group 4: LIN-DTM-RFF-BUS-FCA-SG5-SG6-SG7-SG8-SG9-SG10-

SG11 This segment group contains information regarding the debit side of this transaction and details which are pertinent to all payments specified in the message. Certain payment details may be provided either in segment group 4 or in segment group 11,

0170 LIN, Line item

A segment identifying the line item by a current line number.

0180 DTM, Date/time/period

A segment identifying the date, at which an order has been requested to be executed or acted upon.

0190 RFF, Reference

A segment specifying the reference of the single debit amount on the debit side of the Transaction (B level).

Note: The identification will be passed back to the Ordering Customer for reconciliation purposes.

0200 BUS, Business function

A segment identifying certain characteristics of the payment orders stored on level C, such as business function.

0210 FCA, Financial charges allocation

A segment specifying the method for allocation of charges and allowances (e.g. charges to be borne by the ordering customer), and identifying the ordering customer's account to which such charges or allowances should be directed where it is different from the principal account. This constitutes a default specification and may be overridden at detail level.

0220 Segment Group 5: MOA-CUX-DTM-RFF

A group of segments containing the currency of the single amounts in level C, currency to be transferred, plus the total of all single amounts of level C.

0230 MOA, Monetary amount

A segment specifying the total amount and the currency to be transferred.

0240 CUX, Currencies

A segment specifying the source currency and the destination 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.

0250 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.

0260 RFF, Reference

A segment identifying the deal between ordered bank and ordering customer.

0270 Segment Group 6: FII-CTA-COM

A group of segments containing an account servicing bank including the account to be debited. Another occurrence can be used to specify the account for the return of unsuccessful transactions. If the ordering party is not quoted separately in the NAD-segment on level-B or level-A, then this group also contains the information of the ordering party.

0280 FII, Financial institution information

A segment identifying the financial institution and relevant account number with the currency.

0290 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.

0300 COM, Communication contact

A segment providing a communication number for the party identified in the FII segment.

0310 Segment Group 7: NAD-CTA-COM

A group of segments identifying the ordering party mutually exclusive with NAD-segment on level-A for the ordering party (Ordering customer and payor). Furthermore, one contact party can also be quoted in this group.

0320 NAD, Name and address

A segment identifying the name and address of the non-financial institutions associated with the PAYMUL.

0330 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.

0340 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.

0350 Segment Group 8: 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.

0360 INP, Parties and instruction

A segment identifying the party originating the instruction and the parties to be contacted. It specifies where appropriate the instruction in coded form.

0370 FTX, Free text

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

0380 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 segment(s) needs to be carried out.

0390 Segment Group 9: GEI-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.

This group is mutually exclusive with Segment Group 15.

0400 GEI, Processing information

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

0410 MOA, Monetary amount

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

0420 LOC, Place/location identification

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

0430 NAD, Name and address

A segment identifying a party related to the associated informative text.

0440 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.

0450 FTX, Free text

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

0460 Segment Group 10: PRC-FTX

A group of segments - mutually exclusive with level -C- containing the details of payment, which are determined for all payments on level C.

0470 PRC, Process identification

A segment identifying the kind of free text following this segment.

0480 FTX, Free text

A segment for information in coded or in clear form to provide information from the ordering customer to the beneficiary.

0490 Segment Group 11: SEQ-MOA-DTM-BUS-RFF-PAI-FCA-SG12-SG13-

SG14-SG15-SG16 This segment group contains information regarding the Beneficiaries of the payments. Certain payment details may be provided either in segment group 11 or in segment group 4, but not in both.

0500 SEQ, Sequence details

A segment identifying the beginning of the credit side of the transaction (C level) by a sequential number, which may also be used for reconciliation purposes.

0510 MOA, Monetary amount

A segment giving the amount value of the payment. It is the amount to be transferred. The currency is quoted on the debit side of the transaction (level B).

0520 DTM, Date/time/period

A segment identifying date(s)/time(s) related to the beneficiary's side.

0530 BUS, Business function

A segment identifying business information (per credit) for the payment order.

0540 RFF, Reference

A segment identifying a transaction from the ordering customer to the beneficiary and/or from the ordering customer to the ordered bank.

0550 PAI, Payment instructions

A segment specifying the conditions, method and channel of payment for the payment order.

0560 FCA, Financial charges allocation

A segment specifying the method for allocation of charges and allowances and identifying the ordering customer's account to which such charges or allowances should be directed where it is different from the principal amount. This segment is mutually exclusive with the FCA segment in Segment Group 4.

0570 Segment Group 12: FII-CTA-COM

A group of segments containing the beneficiary's bank and the account and if necessary up to two intermediary banks.

0580 FII, Financial institution information

A segment identifying the financial institution and relevant account number with the currency.

0590 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.

0600 COM, Communication contact

A segment providing a communication number for the party identified in the FII Segment and optionally for the intermediary banks.

0610 Segment Group 13: NAD-CTA-COM

A group of segments identifying the name and address of the beneficiary and one contact party.

0620 NAD, Name and address

A segment identifying the name and address of the non-financial institutions associated with the payment on the beneficiary's side.

0630 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.

0640 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.

0650 Segment Group 14: 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.

0660 INP, Parties and instruction

A segment identifying the party originating the instruction and the parties to be contacted. It specifies where appropriate the instruction in coded form.

0670 FTX, Free text

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

0680 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 segment(s) needs to be carried out.

0690 Segment Group 15: GEI-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.

0700 GEI, Processing information

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

0710 MOA, Monetary amount

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

0720 LOC, Place/location identification

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

0730 NAD, Name and address

A segment identifying the recipient of the associated informative text.

0740 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.

0750 FTX, Free text

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

0760 Segment Group 16: PRC-FTX-SG17-SG23

A group of segments containing the details of payment. The content of these segments is passed through the banking chain from the ordering customer to the beneficiary.

0770 PRC, Process identification

A segment identifying the kind of payment details.

0780 FTX, Free text

A segment providing free text instruction relating to the payment details.

0790 Segment Group 17: DOC-MOA-DTM-RFF-NAD-SG18-SG19-SG20

A group of segments providing details of all documents, e.g., invoices, statements, despatch advices, etc..., to which the Multiple Payment Order refers. It includes information on the monetary amounts for each document and on any adjustments (with an indication of the reason for adjustments) and discounts. For information purposes an indication of the tax element can be provided.

0800 DOC, Document/message details

A segment identifying the reference document against which payment is being made.

0810 MOA, Monetary amount

A segment giving the monetary amounts of each reference document (e.g., original amount, discount amount etc..). The amount due and the amount remitted are mandatory.

0820 DTM, Date/time/period

A segment specifying the date of the referenced document and indicating any other relevant dates applicable.

0830 RFF, Reference

A segment for the inclusion of any additional references related to the reference document.

0840 NAD, Name and address

A segment identifying a party name and address, either by coded identification or in a clear form.

0850 Segment Group 18: CUX-DTM

A group of segments specifying the currencies and the related dates/periods valid to the referenced document where different to the reference currency.

0860 CUX, Currencies

A segment identifying the currency and associated exchange rate of the referenced document where different to the remittance currency.

0870 DTM, Date/time/period

A segment specifying the date/time/period related to the rate of exchange.

0880 Segment Group 19: AJT-MOA-RFF-FTX

A group of segments indicating adjustment amounts and their referenced documents.

0890 AJT, Adjustment details

A segment indicating any adjustments to the amounts originally specified in the referenced document, and to which items such adjustments apply with the associated reason for adjustment.

0900 MOA, Monetary amount

A segment giving the monetary amounts of the adjustments of each reference document (e.g. original amounts, discount amount, etc.) The currency data elements should not be used.

0910 RFF, Reference

A segment for the inclusion of any additional references related to the reference documents.

0920 FTX, Free text

A segment providing free text information related to the payment details.

0930 Segment Group 20: DLI-MOA-PIA-DTM-SG21-SG22

A group of segments which may be used when required to provide details of individual line items in the reference document.

0940 DLI, Document line identification

A segment identifying a specific line item within the referenced document.

0950 MOA, Monetary amount

A segment giving the monetary amounts for this line item.

0960 PIA, Additional product id

A segment specifying item identification codes where required.

0970 DTM, Date/time/period

A segment specifying the date/time/period related to the line item.

0980 Segment Group 21: CUX-DTM

A group of segments identifying the currency and the related dates/periods of the line item where different to the remittance and document currency.

0990 CUX, Currencies

A segment identifying the currency and associated exchange rate of the line item, where different to the reference and target currency.

1000 DTM, Date/time/period

A segment specifying the effective date and/or time the rate of exchange was fixed.

1010 Segment Group 22: AJT-MOA-RFF-FTX

A group of segments indicating adjustment amounts and their referenced documents for this line item.

1020 AJT, Adjustment details

A segment indicating any adjustments to the amounts originally specified for this line item and the reason for the adjustments.

1030 MOA, Monetary amount

A segment giving the monetary amounts of the adjustment for this line item.

1040 RFF, Reference

A segment for the inclusion of any additional references related to the reference document.

1050 FTX, Free text

A segment providing free text information related to the payment details.

1060 Segment Group 23: GEI-MOA

A group of segments indicating the end of the details of payment and specifying hash total amounts for control purposes.

1070 GEI, Processing information

A segment identifying the end of the details of payment.

1080 MOA, Monetary amount

A segment indicating total amounts for control purposes.

1090 CNT, Control total

A segment identifying the kind of control-checks for the payment orders contained in the PAYMUL and identifying the totals according to the coded form.

1100 Segment Group 24: AUT-DTM

A group of segments specifying the details of any authentication (validation) procedure applied to the PAYMUL message.

1110 AUT, Authentication result

A segment specifying details of any authentication (validation) procedures applied to the PAYMUL message.

1120 DTM, Date/time/period

A segment identifying the validation date/time.

1130 UNT, Message trailer

A 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.


4.2. Segment index (alphabetical sequence by tag)

AJT Adjustment details
AUT Authentication result
BGM Beginning of message
BUS Business function
CNT Control total
COM Communication contact
CTA Contact information
CUX Currencies
DLI Document line identification
DOC Document/message details
DTM Date/time/period
FCA Financial charges allocation
FII Financial institution information
FTX Free text
GEI Processing information
INP Parties and instruction
LIN Line item
LOC Place/location identification
MOA Monetary amount
NAD Name and address
PAI Payment instructions
PIA Additional product id
PRC Process identification
RCS Requirements and conditions
RFF Reference
SEQ Sequence details
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)
├─DTM Date/time/period ×1 (M)
├─BUS Business function ×1 (C)
├─Segment Group 1 ×2 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 2 ×5 (C)
├─FII Financial institution information ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 3 ×3 (C)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 4 ×9999 (M)
├─LIN Line item ×1 (M)
├─DTM Date/time/period ×2 (C)
├─RFF Reference ×2 (C)
├─BUS Business function ×1 (C)
├─FCA Financial charges allocation ×1 (C)
├─Segment Group 5 ×1 (C)
├─MOA Monetary amount ×1 (M)
├─CUX Currencies ×1 (C)
├─DTM Date/time/period ×2 (C)
└─RFF Reference ×1 (C)
├─Segment Group 6 ×2 (M)
├─FII Financial institution information ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 7 ×3 (C)
├─NAD Name and address ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
├─Segment Group 8 ×1 (C)
├─INP Parties and instruction ×1 (M)
├─FTX Free text ×1 (C)
└─DTM Date/time/period ×2 (C)
├─Segment Group 9 ×10 (C)
├─GEI Processing information ×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 10 ×1 (C)
├─PRC Process identification ×1 (M)
└─FTX Free text ×1 (M)
└─Segment Group 11 ×99999 (M)
──├─SEQ Sequence details ×1 (M)
──├─MOA Monetary amount ×1 (M)
──├─DTM Date/time/period ×1 (C)
──├─BUS Business function ×1 (C)
──├─RFF Reference ×3 (C)
──├─PAI Payment instructions ×1 (C)
──├─FCA Financial charges allocation ×1 (C)
──├─Segment Group 12 ×3 (C)
──├─FII Financial institution information ×1 (M)
──├─CTA Contact information ×1 (C)
──└─COM Communication contact ×5 (C)
──├─Segment Group 13 ×3 (C)
──├─NAD Name and address ×1 (M)
──├─CTA Contact information ×1 (C)
──└─COM Communication contact ×5 (C)
──├─Segment Group 14 ×3 (C)
──├─INP Parties and instruction ×1 (M)
──├─FTX Free text ×1 (C)
──└─DTM Date/time/period ×2 (C)
──├─Segment Group 15 ×10 (C)
──├─GEI Processing information ×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 16 ×1 (C)
────├─PRC Process identification ×1 (M)
────├─FTX Free text ×5 (C)
────├─Segment Group 17 ×9999 (C)
────├─DOC Document/message details ×1 (M)
────├─MOA Monetary amount ×5 (C)
────├─DTM Date/time/period ×5 (C)
────├─RFF Reference ×5 (C)
────├─NAD Name and address ×2 (C)
────├─Segment Group 18 ×5 (C)
────├─CUX Currencies ×1 (M)
────└─DTM Date/time/period ×1 (C)
────├─Segment Group 19 ×100 (C)
────├─AJT Adjustment details ×1 (M)
────├─MOA Monetary amount ×1 (M)
────├─RFF Reference ×1 (C)
────└─FTX Free text ×5 (C)
────└─Segment Group 20 ×1000 (C)
──────├─DLI Document line identification ×1 (M)
──────├─MOA Monetary amount ×5 (M)
──────├─PIA Additional product id ×5 (C)
──────├─DTM Date/time/period ×5 (C)
──────├─Segment Group 21 ×5 (C)
──────├─CUX Currencies ×1 (M)
──────└─DTM Date/time/period ×1 (C)
──────└─Segment Group 22 ×10 (C)
────────├─AJT Adjustment details ×1 (M)
────────├─MOA Monetary amount ×1 (M)
────────├─RFF Reference ×1 (C)
────────└─FTX Free text ×5 (C)
────└─Segment Group 23 ×1 (C)
──────├─GEI Processing information ×1 (M)
──────└─MOA Monetary amount ×5 (C)
├─CNT Control total ×5 (C)
├─Segment Group 24 ×5 (C)
├─AUT Authentication result ×1 (M)
└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D02B 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.