Frames | No Frames

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

Authorization message

Version:D
Release:97A
Contr. Agency:UN
Revision:2
Date:96-12-13
SOURCE:Western European EDIFACT Board MD4

CONTENTS
Authorization 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. 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:
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 Authorization message (AUTHOR) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.


1. SCOPE


1.1. Functional Definition

An Authorization Message is sent by the Ordering Customer (or Payor or Agent on behalf of the Ordering Customer) or by a third party having authority on the Ordering Customer's payments to the Ordered Bank, to authorize the Ordered Bank to execute a given financial transaction.

This financial transaction might relate to both multiple messages like PAYMUL and DIRDEB, and single instruction messages like PAYORD and PAYEXT.

An Authorization Message could also be sent from the Ordered Bank to the Ordering Customer or its Authorization Authority to request authorization for a given financial transaction.

Throughout this document the term 'Original Message' refers to the message to be authorized.


1.2. Field of Application

This message may be applied to 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

  • The authorization carried by the message applies to the whole original message (i.e. to all instructions within the message) or to individual debit transactions and their related credits.
  • The AUTHOR message may also authorize a single transaction in a multiple direct debit transaction.

2. REFERENCES

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


3. TERMS AND DEFINITIONS


3.1. Standard 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 Segment Table which indicate mandatory, conditional and repeating requirements.

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

The Authorization message is structured in three levels: A, B, and C.

Level A Segment Groups 1, 2, 3 and 9 contains general data related to the whole message.

Level B Segment Groups 4 and 5 contains data identifying the message or transaction to be authorized.

Level C Segment Groups 6 to 8 contains the authorization.

The structure of the message is designed to allow several B levels, each B level being followed by its realted 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 Authorization message is AUTHOR.

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

Data element0065AUTHOR
0052D
005497A
0051UN

0020 BGM, Beginning of message

A segment for unique identification of the Authorization message, its type and number and its function, i.e., specifying if it is an authorization or request for authorization.

0030 DTM, Date/time/period

A segment containing the creation date of the Authorization Message.

0040 BUS, Business function

A segment providing information for routing of the message.

0050 Segment Group 1: RFF-DTM

A group of segments identifying the message to be authorized and possibly the request for an authorization which has been previously sent.

0060 RFF, Reference

A segment referring to the message that has to be authorized or to a previously-sent request for authorization.

0070 DTM, Date/time/period

A segment indicating the date and time of creation of the message referenced in the RFF segment or possibly the payment date.

0080 Segment Group 2: FII-CTA-COM

A group of segments identifying the financial institutions involved in the Authorization message.

0090 FII, Financial institution information

A segment identifying the Ordered Bank acting for the Ordering Customer and/or Payor and the relevant account number and currency.

0100 CTA, Contact information

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

0110 COM, Communication contact

A segment providing communication numbers for the financial institution identified in the FII segment and optionally for the contact identified in the associated CTA segment.

0120 Segment Group 3: NAD-CTA-COM

A group of segments identifying the parties involved in the exchange of the message.

0130 NAD, Name and address

A segment identifying the name and address of the non-financial parties involved in the exchange of this message. (Sender and Recipient).

0140 CTA, Contact information

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

0150 COM, Communication contact

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

0160 Segment Group 4: LIN-SG5-SG6-SG7-SG8

A group of segments identifying a message or a group of transactions in a message or a specific transaction in a multiple message.

0170 LIN, Line item

A segment specifying the beginning of details referring to the message/transaction to be authorized.

0180 Segment Group 5: RFF-DTM

A groups of segments specifying reference numbers, dates and/or times needed to identify a referenced message or transaction.

0190 RFF, Reference

A segment indicating reference number(s) for the message or transaction to be authorized.

0200 DTM, Date/time/period

A segment specifying the date/time of the referenced message or transaction.

0210 Segment Group 6: SEQ-GIS-DTM-MOA-DOC

A group of segments identifying the authorization of the message/transaction.

0220 SEQ, Sequence details

A segment identifying the beginning of the details needed to give the authorization.

0230 GIS, General indicator

A segment specifying the kind of authorization given to the referenced message/transaction in a coded form.

0240 DTM, Date/time/period

A segment identifying dates related to the referenced message/transaction.

0250 MOA, Monetary amount

A segment giving the amount of the referenced message/transaction.

0260 DOC, Document/message details

A segment identifying referenced numbers of the referenced message/transaction.

0270 Segment Group 7: FII-CTA-COM

A group of segments identifying the financial institutions associated with the referenced message/transaction.

0280 FII, Financial institution information

A segment identifying a financial institution related to the referenced message/transaction.

0290 CTA, Contact information

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

0300 COM, Communication contact

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

0310 Segment Group 8: NAD-CTA-COM

A group of segments identifying the name and address of non-financial parties associated with the referenced message/transaction.

0320 NAD, Name and address

A segment identifying a non-financial party related to the referenced message/transaction.

0330 CTA, Contact information

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

0340 COM, Communication contact

A segment identifying communications types and numbers for the persons or departments specified in the associated CTA segment.

0350 CNT, Control total

A segment identifying the type of control checks and totals.

0360 Segment Group 9: AUT-DTM

A segment group identifying the authentication procedures used.

0370 AUT, Authentication result

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

0380 DTM, Date/time/period

A segment defining the validation date/time.

0390 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
CNT Control total
COM Communication contact
CTA Contact information
DOC Document/message details
DTM Date/time/period
FII Financial institution information
GIS General indicator
LIN Line item
MOA Monetary amount
NAD Name and address
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 (C)
├─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)
├─Segment Group 5 ×5 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×1 (C)
├─Segment Group 6 ×9999 (C)
├─SEQ Sequence details ×1 (M)
├─GIS General indicator ×1 (M)
├─DTM Date/time/period ×2 (C)
├─MOA Monetary amount ×1 (C)
└─DOC Document/message details ×5 (C)
├─Segment Group 7 ×2 (C)
├─FII Financial institution information ×1 (M)
├─CTA Contact information ×1 (C)
└─COM Communication contact ×5 (C)
└─Segment Group 8 ×2 (C)
──├─NAD Name and address ×1 (M)
──├─CTA Contact information ×1 (C)
──└─COM Communication contact ×5 (C)
├─CNT Control total ×5 (C)
├─Segment Group 9 ×5 (C)
├─AUT Authentication result ×1 (M)
└─DTM Date/time/period ×1 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D97A 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 Simplify Legacy Data Integration with Stylus Studio XML Enterprise Edition - Free Download!
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-2011 All Rights Reserved.