Friday, 20 September 2024

Example of an EDIFACT Message Structure

 Here’s a simplified example of an EDIFACT Invoice (INVOIC) message:

UNOA:1
UNB+UNOA:1+SENDERID+RECEIVERID+210710:1234+000000001' UNH+EDIFACT001+INVOIC:D:93A:UN:1.6' BGM+380+123456789+9' DTM+3:20210710:102' RFF+ON:123456' NAD+BY+12345::9' CUX+2:USD:4' LIN+1++123456:UP' PIA+1+ABC123:SA' QTY+47:100' PRI+AAA:9.99' TAX+7+VAT+++:::5' UNT+14+EDIFACT001' UNZ+1+000000001'
  • UNB (Interchange Header): Identifies the beginning of the interchange and includes sender and receiver information.
  • UNH (Message Header): Identifies the start of a message and specifies the message type (INVOIC).
  • BGM (Beginning of Message): Contains basic information about the message, such as document number and type.
  • DTM (Date/Time/Period): Provides date and time information.
  • RFF (Reference): Includes references such as order numbers.
  • NAD (Name and Address): Identifies the buyer.
  • CUX (Currency): Specifies the currency used.
  • LIN (Line Item): Details each line item in the invoice.
  • PIA (Additional Product Id): Provides additional product identification.
  • QTY (Quantity): Details the quantity of the item.
  • PRI (Price): Provides pricing information.
  • TAX (Tax Details): Includes tax information.
  • UNT (Message Trailer): Marks the end of the message.
  • UNZ (Interchange Trailer): Marks the end of the interchange.

No comments:

Post a Comment

Comparison Between EDI and API

Comparison between  EDI (Electronic Data Interchange) and API (Application Programming Interface) in the context of B2B data exchange: ...