What is EDI 850?

EDI 850 is a standard format used in Electronic Data Interchange (EDI) for transmitting purchase orders. This document facilitates the exchange of purchase information between trading partners, ensuring that orders are placed accurately and efficiently. Below, we will break down the structure of an EDI 850 transaction using an example.

Example of EDI 850:

Breakdown of EDI 850 Segments:

1. ISA Segment (Interchange Control Header):
   
   • Purpose: This segment marks the start of the EDI interchange and contains control information.
   • Example: ISA*00* *00* *ZZ*FRANPOS *ZZ*1111 *240801*0620*U*00401*000000001*0*P*>~
   • Key Elements:
     
     • FRANPOS: Sender ID.
     • 1111: Receiver ID.
     • 240801: Date (August 1, 2024).
     • 0620: Time (6:20 AM).
2. GS Segment (Functional Group Header):
   
   • Purpose: Defines the start of a group of related transaction sets.
   • Example: GS*PO*FRANPOS*1111*240801*0620*000000001*X*004010~
   • Key Elements:
     
     • PO: Indicates a purchase order.
     • 000000001: Group control number.
3. ST Segment (Transaction Set Header):
   
   • Purpose: Identifies the start of the transaction set.
   • Example: ST*850*911322654~
   • Key Elements:
     
     • 850: Indicates a purchase order.
     • 911322654: Transaction set control number.
4. BEG Segment (Beginning Segment for Purchase Order):
   
   • Purpose: Specifies the beginning of the purchase order.
   • Example: BEG*SA*NE*10728*20240801~
   • Key Elements:
     
     • SA: Purchase order type code.
     • 10728: Purchase order number.
     • 20240801: Date of the order (August 1, 2024).
5. CUR Segment (Currency Information):
   
   • Purpose: Indicates the currency of the transaction.
   • Example: CUR*BY*USD~
   • Key Elements:
     
     • USD: Currency code (U.S. Dollars).
6. PER Segment (Administrative Communications Contact):
   
   • Purpose: Provides contact information.
   • Example: PER*CP*Serhii's Serhii's *EM*sshykor@franpos.com*TE*~
   • Key Elements:
     
     • EM: Indicates an email contact.
7. N1 Segment (Name):
   
   • Purpose: Identifies the name of the buying party.
   • Example: N1*BY*Serhii's Company*ZZ*26014~
   • Key Elements:
     
     • BY: Indicates the buying party.
8. PO1 Segment (Baseline Item Data):
   
   • Purpose: Contains line item details such as item identification, quantity, and pricing.
   • Example: PO1*29129*1.00*OZ*12.00*CP*SK*asdqwe123*UP*asd123~
   • Key Elements:
     
     • 29129: Line item identification.
     • 1.00: Quantity ordered.
     • 12.00: Unit price.
9. PID Segment (Product/Item Description):
   
   • Purpose: Provides a description of the product or item.
   • Example: PID*F****asd3~
10. CTT Segment (Transaction Totals):
    
    • Purpose: Summarizes the total number of line items.
    • Example: CTT*5~
    • Key Elements:
      
      • 5: Number of line items.
11. AMT Segment (Monetary Amount Information):
    
    • Purpose: Specifies the total monetary amount for the order.
    • Example: AMT*TT*322.65~
    • Key Elements:
      
      • 322.65: Total amount in USD.
12. SE Segment (Transaction Set Trailer):
    
    • Purpose: Marks the end of the transaction set.
    • Example: SE*26*911322654~
13. GE Segment (Functional Group Trailer):
    
    • Purpose: Indicates the end of a functional group.
    • Example: GE*1*000000001~
14. IEA Segment (Interchange Control Trailer):
    
    • Purpose: Marks the end of the interchange.
    • Example: IEA*1*000000001~

Conclusion