EDI Implementation Guide 810 Invoice Accounting ANSI X12 Version 3010

Similar documents
810 Invoice. Introduction: Notes: Heading: Detail: Functional Group ID=IN

ANSI X12 version Invoice

ARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice

X12 Implementation Guidelines For Outbound Purchase Order v2001 (850O)

Pittsburgh Glass Works. X Purchase Order Specifications

X12 Implementation Guidelines For Inbound Price Catalog v (832I)

ARVINMERITOR P.O.'S 850 TRANSACTION SET WILL BE UTILIZED TO COMMUNICATE CONTRACTUAL INFORMATION REGARDING PART AND PRICE

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MARKET CENTER PROGRAM INVOICE (810) TRANSACTION SET

944 Warehouse Stock Transfer Receipt Advice

X12 Implementation Guidelines For. Inbound Primary Metals Advance Ship Notice V002002FORD. (856i Primary Metals)

810 Invoice. Introduction: Heading: Functional Group ID=IN

Functional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850

X12 Implementation Guidelines For. Outbound Non-Production (CPARS) Purchase Order Change Request (860)

850 - Purchase Order. Caterpillar Inc.

Menards Implementation Guidelines

GENERAL MOTORS IMPLEMENTATION GUIDELINES FOR ANSI X12 TRANSACTION SET 850 PURCHASE ORDER

05/11/1998 Ingram Book Company Purchase Order INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850)

820 Payment Order/Remittance Advice

830 Planning Schedule with Release Capability

EDI Implementation Guide for SAP ASN

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET

945 Warehouse Shipping Advice Version X12 Functional Group=SW

856 Ship Notice/Manifest Standard Carton Pack Structure

EDI Specifications Guide. 850 Supplier Purchase Order

EDI Implementation Guide 850 Purchase Orders Version 4010 Effective Date: 25 July 2008

DSD Invoice TRANSACTION SET 810 VERSION 4010

856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi X12 Version 4010

880 Grocery Products Invoice

830 Planning Schedule EDI Implementation Guide

862 Shipping Schedule

Weis Markets, Inc. Mapping Specifications 810 Invoice

EDI Implementation Guide 860 Purchase Order Changes Version 4010 Effective Date: 25 July 2008

843 Response to Request for Quotation

Inbound 855 (P.O. Acknowledgment) X12 Specification for Release

EDI Specifications Version 4010 / Transaction Set 310 Freight Receipt and Invoice (Ocean)

Martinrea International s EDI Specifications. AIAG version 4010 ANSI X (Planning Schedule)

940 Warehouse Shipping Order

852 Product Activity Data Version 04010

BERGEN BRUNSWIG DRUG COMPANY

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS SHIPPING INSTRUCTIONS (304) TRANSACTION SET

LOWE'S EDI. 856 Advance Ship Notice. Version:

325 Consolidation of Goods In Container

ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X

820 Payment Order/Remittance Advice

Electronic Data Interchange. 850 Purchase Order. Version 4030

830 Planning Schedule with Release Capability

LVS/ET Division. 862 Shipping Schedule

MMG 856 Inbound Ship Notice/Manifest Macy s Merchandising Group ANSI X.12 Version 4010 ANSI X.12 Document Mapping Effective 03/15/2016

EMPIRE ELECTRONICS, INC. Address Qualifier: 12 EDI Address: IMPLEMENTATION GUIDE

810 Invoice Functional Group ID=IN

This document defines the AAFES Business Requirements for the Purchase Order (REV 1).

EDI Specifications Version 4010 / Transaction Set 110 Air Freight Details and Invoice

Electronic Commerce Customer Guide

EDI Specifications Version 4010 / Transaction Set 858 Shipment Information

JCPenney 856 Ship Notice/Manifest Version 4030

856 Ship Notice/Manifest

Warehouse Shipping Advice - 945

812 Credit/Debit Adjustment. Author: Margie Waggoner Publication: 06/14/2013 Notes:

EDI Implementation Guide 856 Advance Ship Notice Version 4010

211 Motor Carrier Bill of Lading

820 Payment Order/Remittance Advice DRAFT

MAGNA. ANSI X12 - Version AIAG. Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE

Electronic Data Interchange Implementation Guide

COMMERCIAL AIRPLANES GROUP. SUPPLIER NETWORK Electronic Data Interchange. PCOS (Purchasing/Control On-line System) EDI Implementation Guide

830 Planning Schedule with Release Capability

Warehouse Shipping Order X12

The remainder of this document is divided into two parts. The first part is for webform vendors and the second part is for EDI vendors.

180 Return Merchandise Authorization and Notification

945 Warehouse Shipping Advice

FILE LAYOUT FOR 855 EDI TRANSACTION (OUTBOUND)

LOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1

810 Invoice. Introduction: Heading: Functional Group ID=IN

862: Shipping Schedule Outbound from TMD to Vendor

945 Warehouse Shipping Advice

EDI Specifications Version 4010 / Transaction Set 210 Carrier Truckload Shipments

Belk Stores 212 Delivery Manifest. X12/V4030/212: 212 Delivery Manifest

ORDERS Purchase Order Message

Martinrea International s EDI Specifications. AIAG version 4010 ANSI X (Planning Schedule)

KOHLER COMPANY VENDOR SHIP NOTICE LAYOUT (856) Kohler Description Number M = Mandatory O = Optional C = Conditional

846 Inventory Availability

211 Motor Carrier Bill of Lading

Purchase Order (850) Transaction Set

Lowe's EDI. 860 Purchase Order Change Request for PROCUREMENT Version: 5040

01/10/05 Warehouse Shipping Order - 940

862 Pull Loop System

K&G System Migration EDI SPECIFICATION

850 Purchase Order. Introduction: Heading: Functional Group ID=PO

855 PO Acknowledgment X12 Version 4010

811 Consolidated Service Invoice/Statement

LOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1

International Truck and Engine Corporation. Engine Group

MEDTRONIC. ANSI X Purchase Order Specifications

Grocery Products Invoice UCS

211 Motor Carrier Bill of Lading

Electronic Data Interchange 850 Pre-Pack Purchase Order (VICS Version ) March Powered By:

CSI EDI ASN 856 specification Version /21/ ASN Advance Shipping Notice. Version: ANSI X /21/2012 V 1.

PUBNET 2000 Version 3060 IMPLEMENTATION GUIDELINE FOR EDI 850

830 Planning Schedule with Release Capability

315 Status Details (Ocean) 4010 Implementation Guide for Customers

Warehouse Inventory Adjustment Advice - 947

Transcription:

810 Invoice Accounting ANSI X12 Version 3010

Transaction: 810 Page: 810-000 Description: Invoice Release Date: 05/30/97 Transaction Description Page No. 810 Invoice Purpose................................. 810-001 Contents/Organization..................... 810-002 Implementation Procedure................... 810-002 Transmission Frequency.................... 810-002 Header Level Segments ST.................................... 810-003 BIG................................... 810-004 CUR................................... 810-005 REF................................... 810-006 N1.................................... 810-007 N3.................................... 810-008 N4.................................... 810-009 N1.................................... 810-010 DTM.................................. 810-011 Detail Level Segments IT1.................................... 810-012 ITA.................................... 810-013 Summary Level Segments TDS................................... 810-014 TXI.................................... 810-015 CAD.................................. 810-016 ISS.................................... 810-017 CTT................................... 810-018 SE.................................... 810-019 s............................... 810-020

Transaction: 810 Page: 810-001 Description: Invoice Release Date: 04/29/97 Purpose To request payment for the shipment of material or the rendering of services to a Freightliner facility pursuant to a purchase order or other authorization to ship. This transaction conveys supplier identification, invoice number, date, Freightliner purchase order number and date, ship-to location, corresponding Shipment Identification Number (SID) and shipped material quantities and pricing as well as other defined information. The data transmitted in the 810 is used by Freightliner to facilitate on-line computer matching of invoice information to Freightliner facility material receipts; preferably facilitated by on-line receipt of material from an 856 (Ship Notice/Manifest) transaction. The Shipment Identification Number (SID) is the primary reference used by Freightliner in this process (please reference Shipment Identification Number topic as it relates to the 856 Ship Notice/ Manifest transaction presented on page 856-003 of this manual, for a complete discussion regarding Freightliner requirements pertaining to this data element.). Suppliers who have implemented the 856 transaction are expected to invoice Freightliner using the 810 transaction set. Freightliner requires that the 810 be generated from an integrated system that echoes back information provided by Freightliner via the EDI 866, 862, 830, or 850 transactions as applicable in addition to providing shipping information from the supplier s system. This requires that data received from Freightliner be stored in the supplier s system and retrieved when the 810 transaction is generated to preclude data entry of this information. An integrated supplier system ensures that the 810 data transmitted is valid and accurate.

Transaction: 810 Page: 810-002 Description: Invoice Release Date: 05/30/97 Contents/ Organization An EDI 810 transmission (ISA through IEA segment) can consist of multiple transaction sets, one transaction set (ST through SE segment) per invoice number. Each transaction set has a specific sequence for the data segments. Transaction sets are divided into the following areas: 1) Heading Area: Segments appearing here refer to the entire transaction set. 2) Detail Area: These segments are for detail information only and override any similar specification in the heading area. 3) Summary Area: Segments in this area contain control totals only, or actions performed on these totals. The Max Usage column refers to the maximum number of times a segment is permitted to appear, in succession, at that specific location within the transaction. Implementation Procedure The EDI 810 transaction is requested by Freightliner s Corporate Accounts Payable Department. The Accounting EDI Coordinator will test and implement the 810 transaction and will ensure that transmitted data is complete and that the reference numbers provided (SID) match to the shipment information (856 transaction if implemented) provided by the supplier. For the transmission of miscellaneous charges or allowances, it is recommended that you contact the Accounting EDI Coordinator to discuss the use of appropriate codes within the ITA segment. Freightliner may require an NTE segment (not shown in this documentation) on direct ship invoicing. The Accounting EDI Coordinator will notify suppliers when this segment is required. Transaction Frequency Suppliers should generate and transmit an 810 transaction to Freightliner as soon as a shipment of material has been placed in transit. Freightliner Accounting receives data from GEIS daily (M-F) at 4:00 A.M. (Pacific Time).

Transaction: 810 Page: 810-003 Description: Invoice Release Date: 02/10/97 SEGMENT: ST Transaction Set Header Header Invoice Transaction Set Tables. PURPOSE: The first segment of each transaction set containing the transaction set identifier and control number. COMMENTS: The transaction set control number (ST02) in this header must match the transaction set control number (SE02) in the transaction set trailer (SE). There is one ST for each BIG segment generated. EXAMPLE: ST*810*0001. ST Segment ID Transaction set header. 810 ST01 143 3/3 Transaction Set ID Use 810. 0001 ST02 329 4/9 Transaction Set Control Number Unique number assigned to each transaction set within a functional group; starting with 0001 and incrementing by 1 for each subsequent transaction set.

Transaction: 810 Page: 810-004 Description: Invoice Release Date: 04/29/97 SEGMENT: BIG Beginning Segment for Invoice Header None PURPOSE: To indicate the beginning of the invoice transaction set and to transmit identifying numbers and dates. COMMENTS: EXAMPLE: BIG*910313*123456**A00545. BIG Segment ID Beginning segment for invoice. 910313 BIG01 245 6/6 Invoice Date Format = YYMMDD. 123456 BIG02 76 1/22 Invoice Number BIG03 323 6/6 Purchase Order Date Not Used. BIG04 324 1/22 Purchase Order Not Used. Number BIG05 328 01/30 Release Number Not Used. BIG06 327 01/08 Change Order Not Used. Sequenced CR BIG07 640 02/02 Transaction Type Optional. CR = Credit Memo. CI or blank = Invoice.

Transaction: 810 Page: 810-005 Description: Invoice Release Date: 05/30/97 SEGMENT: CUR Currency Heading None PURPOSE: COMMENTS: To specify currency (dollars, pounds, francs, etc.) used in a transaction. If an arrangement is made between trading partners to use this segment, refer to the ANSI Data Dictionary. Monetary values are assumed to be expressed in the currency of the country of the transaction originator unless the CUR segment is used to specify a different currency. The segment also permits the transaction originator to indicate a specific exchange rate, foreign exchange location and date/time as the basis for currency conversion. EXAMPLE: CUR*SE*CAD. CUR Segment ID Currency code. SE CUR01 98 2/2 Organizational Identifier Always = SE. SE = Selling Party. CAD CUR02 100 3/3 Currency Code Multiple Codes: USD = US Dollars. CAD = Canadian Dollars.

Transaction: 810 Page: 810-006 Description: Invoice Release Date: 05/30/97 SEGMENT: REF Reference Numbers Header None 2 PURPOSE: COMMENTS: EXAMPLE: To transmit identifying numbers associated with the named party. At least one REF02 or REF03 must be present. REF*SI*70001. REF Segment Numbers Reference numbers. SI REF01 128 2/2 Reference Number Qualifier Multiple Codes: IN = Invoice Number. PK = Packing List Number. BM = Bill of Lading Number. SI = SID Number (Preferred) ON = Dealer Code. ZZ = Dealer PO for Direct Ship. 70001 REF02 127 1/30 Reference Number REF03 352 1/80 Description Not Used

Transaction: 810 Page: 810-007 Description: Invoice Release Date: 02/10/97 SEGMENT: N1 Header N1 PURPOSE: COMMENTS: EXAMPLE: To identify a party by type of organization, name and code. N1*SU*SUPPLIER NAME. N1 Segment ID. SU N101 98 2/2 Organization Identifier Multiple Codes: SU = Supplier. SE = Seller. SUPPLI... N102 93 1/35

Transaction: 810 Page: 810-008 Description: Invoice Release Date: 04/29/97 SEGMENT: N3 Address Information Header N1 MAX USAGE: 2 PURPOSE: To specify the location of the named part. COMMENTS: EXAMPLE: N3*6789 PLEASURE WAY DOOR 306. N3 Segment ID Address information. 6789 PL... N301 166 1/35 Address Supplier s address. N302 166 1/35 Address Supplier s address. (Overflow.) Optional.

Transaction: 810 Page: 810-009 Description: Invoice Release Date: 02/10/97 SEGMENT: N4 Geographic Location Header N1 PURPOSE: To specify the geographical place of the named party. COMMENTS: Used in the N1 Loop at both heading or detail level. Required segment if additional information is needed to completely specify the address. Neither N401 or N405 is required. If N401 is used, N402 is required. EXAMPLE: N4*DAYTON*OHIO*45499. N4 Segment ID Address information. Dayton N401 19 2/19 City OH N402 156 2/2 State/ Province Code 45499 N403 116 5/9 Postal Code Optional. N404 26 2/2 Country Code Optional.

Transaction: 810 Page: 810-010 Description: Invoice Release Date: 05/30/97 SEGMENT: N1 - Header N1 PURPOSE: To identify the Freightliner Ship-to location. COMMENTS: EXAMPLE: N1*ST*PORTLAND TRUCK PLANT*92*001. N1 Segment ID. ST N101 98 2/2 Entity Identifier Code Acceptable Freightliner codes: ST = Ship-to PORTLAND... N102 93 1/35 Required - Use either Abbreviation or Ship To Location. Reference Appendix C for approved locations. * 92 N103 66 2/2 ID Code Qualifier Always = 92. 92 = indicating Buyer Assigned. 001 * N104 67 3/4 ID Code Must contain Ship-to location Code. (3-4 characters.) * * Please see Appendix C (page APX_C-001) in this manual for Freightliner Ship-to location codes.

Transaction: 810 Page: 810-011 Description: Invoice Release Date: 05/30/97 SEGMENT: DTM Date/Time Reference Header None PURPOSE: To specify pertinent dates and times. COMMENTS: Date/Time is local time for sender. It is mandatory that DTM02 or DTM03 be present. EXAMPLE: DTM*011*910202. DTM Segment ID Date/time reference. 011 DTM01 374 3/3 Date/Time Qualifier 011 = Ship Date. 910202 DTM02 373 6/6 Date Format = YYMMDD.

Transaction: 810 Page: 810-012 Description: Invoice Release Date: 05/30/97 SEGMENT: IT1 Baseline Item Data Detail IT1 (Loop may occur 200000 times.) PURPOSE: COMMENTS: EXAMPLE: To specify the basic and most frequently used line item data for the invoice and related transactions. IT106 through IT125 provides for 10 different product/service ID s for each item. If additional information is to be shown, see AIAG Data Dictionary for format requirements. IT1*002*100*EA*100.00**BP*23-00012- 452*PO*A00454*PL*002*ZZ*WIDGET. IT1 Segment ID Baseline item data. 002 IT101 350 1/6 Assigned Identification Optional. Invoice line number. 100 IT102 358 1/10 Quantity Invoiced EA IT103 355 2/2 Unit of Measure Code 100.00 IT104 212 1/14 Unit Price IT105 639 2/2 Base Unit Price Code Not Used BP IT106 235 2/2 Product/Service ID Qualifier 23-00012- 452 Multiple Codes: BP = Buyer s Part No. RC = Returnable Container. IT107 234 1/30 Product/Service ID Part number. PO IT108 235 2/2 Product/Service ID Qualifier PO = PO Number. A00454 IT109 234 1/30 Product/Service ID Purchase order no. If Warranty Credit use WARRAN. PL IT110 235 2/2 Product/Service ID Qualifier PL = Purchase Order Line Number. 002 IT111 234 1/30 Product/Service ID Purchase order line no. ZZ IT112 235 2/2 Product/Service ID Qualifier ZZ = Mutually Defined. Optional. WIDGET IT113 234 1/30 Product/Service ID Line Item Description.

Optional.

Transaction: 810 Page: 810-013 Description: Invoice Release Date: 04/29/97 SEGMENT: ITA Allowance, Charge or Service Detail/Summary ITA PURPOSE: To specify allowances or charges. COMMENTS: If ITA02 is present, then at least one of ITA03 or ITA13 is required. If ITA01 = A (Allowance) or C (Charge) then at least one of ITA06, ITA07 or ITA08 must be present. If ITA08 is present, then ITA09 is required. If ITA10 is present, then ITA11 is required. EXAMPLE: ITA*C*AI*N0020*06***10000***2*EA. ITA Segment ID Other allowance indicator. C ITA01 248 1/1 Allowance/Charge Identifier Multiple Codes: A = Allowance. C = Charge. AI ITA02 559 2/2 Agency Qualifier Code AI = Automotive Industry Action Group. N0020 ITA03 560 2/10 Special Services Code Multiple Codes: PL = Palletizing. HC = Restocking. N0020 = Non-Returnable Containers. DL = Delivery. ZZ = Mutually Defined. EG = Branding Charges. 06 ITA04 331 2/2 Method of Handling Code 06 = Charge to be paid by customer. 10000 ITA07 360 1/9 Allowance/Charge Total Amount Optional. 2 ITA10 339 1/10 Allowance/Charge Quantity Optional. EA ITA11 355 2/2 Unit of Measure Code Multiple Codes Our Purchasing Unit of Measure (Conditional). Reference Appendix E

Transaction: 810 Page: 810-014 Description: Invoice Release Date: 02/10/97 SEGMENT: TDS Total Monetary Summary Summary None PURPOSE: To specify the total invoice discounts and amounts. COMMENTS: TDS02 is required if the dollar value subject to discount is not equal to the dollar value of TDS01. EXAMPLE: TDS*10000. TDS Segment ID Monetary value summary. 10000 TDS01 361 1/10 Total Invoice Amount

Transaction: 810 Page: 810-015 Description: Invoice Release Date: 04/29/97 SEGMENT: TXI Tax Information Summary None 0 PURPOSE: COMMENTS: EXAMPLE: To specify tax information. OPTIONAL. If present, at least one of TXI02 or TXI03 is required. TXI*ZZ*43.21. TXI Segment ID Tax information. ZZ TXI01 963 2/2 Tax Type Code Multiple Codes: FT = Federal Excise Tax. ST = State Sales Tax. ZZ = Canadian GST. 43.21 TXI02 782 2/15 Monetary Amount TXI03 954 1/10 Percent

Transaction: 810 Page: 810-016 Description: Invoice Release Date: 02/10/97 SEGMENT: CAD Carrier Detail Summary None PURPOSE: COMMENTS: To specify transportation details for the transaction. At least one of CAD04 or CAD05 must be present. If CAD07 is present, then CAD08 is required. The carrier detail segment is required if freight charges are billed. EXAMPLE: CAD*S***CFAF***BM*123456. CAD Segment ID Carrier detail. S CAD01 91 1/2 Transportation Method/Type Code CFAF CAD04 140 2/4 Standard Carrier Alpha Code BM CAD07 128 2/2 Reference Number Qualifier 123456 CAD08 127 1/30 Reference Number Multiple Codes: S = Ocean. A = Air. R = Rail. M = Truck. BM = Bill of Lading Number.

Transaction: 810 Page: 810-017 Description: Invoice Release Date: 04/29/97 SEGMENT: ISS Invoice Shipment Summary Summary None MAX USAGE: 5 PURPOSE: To specify details of total items shipped in terms of quantity, weight, and volume. COMMENTS: OPTIONAL. Segment is used only when freight charges are being billed and the CTT03 and CTT 04 cannot be provided. If segment is present at least one of ISS01, ISS03, or ISA05 must be present: If ISS01 is present, then ISS02 is required. If ISS03 is present, then ISS04 is required. If ISS05 is present, then ISS06 is required. EXAMPLE: ISS*10*EA. ISS Segment ID Shipment summary. 10 ISS01 382 1/10 Number of Units Shipped Optional. EA ISS02 355 2/2 Unit of Measure Code Conditional. ISS03 81 1/8 Weight Optional. ISS04 355 2/2 Unit of Measure Code Conditional. ISS05 183 1/8 Volume Optional. ISS06 355 2/2 Unit of Measure Code Conditional.

Transaction: 810 Page: 810-018 Description: Invoice Release Date: 04/29/97 SEGMENT: CTT Transaction Totals Summary None PURPOSE: To transmit a hash total for a specific element in the transaction set. COMMENTS: If CTT03 is present, then CTT04 is required. If CTT05 is present, then CTT06 is required. EXAMPLE: CTT*10. CTT Segment ID Transaction totals. 10 CTT01 354 1/6 Number of Line Items CTT02 347 1/10 Hash Total Code CTT03 81 1/8 Weight * Required for Freight Charges. CTT04 355 2/2 Unit of Measure Code Conditional. CTT05 183 1/8 Volume Not Used. CTT06 355 2/2 Unit of Measure Code Not Used. CTT07 352 1/80 Description Not Used. * Weight is required if freight charges are billed.

Transaction: 810 Page: 810-019 Description: Invoice Release Date: 02/10/97 SEGMENT: SE- Transaction Set Trailer Trailer None PURPOSE: The last segment of each transaction set containing the number of included segments and the transaction set control number. COMMENTS: The number of included segments is the total of all segments used in the transaction set including the ST and SE segments. The transaction set control number value in the trailer must match the same element value in the transaction set header ST02. EXAMPLE: SE*91*0001. SE Segment ID Transaction set trailer. 91 SE01 96 1/6 Number of Included Segments 0001 SE02 329 4/9 Transaction Set Control Number This number must equal the total number of segments between ST and SE segments, including the ST and SE segments. This number must match the transaction set control number in ST02.

Transaction: 810 Page: 810-020 Description: Invoice Release Date: 02/10/97 EXAMPLE 810 DOCUMENT WITH DATA INTERPRETATION AIAG EDI Format Interpretation ST*810*000035555. BIG*950719*7185359**BW 1 S21402. CUR*SE*USD. REF*SI*123456. REF*PK*456789. N1*SU*YOUR COMPANY NAME. Transaction start record. Invoice number, P.O. number and date. Currency in U.S. dollars. SID #. (Must Match SID number on the corresponding 856 Advance Ship Notice.) Packing slip number. Supplier. N3*1234 NE YOUR STREET. Supplier Address. N4*YOUR TOWN*OR*12345. N1*ST*PORTLAND TRUCK PLANT*92*001. DTM*011*950719 IT1*001*20*EA*30.89**BP*279351*PO*BW 1 S21402*PL*123. ITA*C*AI*DL*06***4978. TDS*66758. Supplier s City, State/Province, zip code. Ship-to Address/Receiving location code. Ship Date. Quantity, unit price, buyer part number, P.O. number. Delivery charge to be paid by customer. Total invoice amount. CAD*A***UPSE*UNITED PARCEL SERVICE**BM*123456789. Ship UPS air. Bill of lading number = 123456789 CTT*1**159*LB. SE*16*000035555. Transaction totals, 1 line item. Transaction end record.

Transaction: 810 Page: 810-021 Description: Invoice Release Date: 05/30/97 EXAMPLE 810 DOCUMENT WITH DATA INTERPRETATION AIAG EDI Format Interpretation ST*810*000035555. BIG*950719*7185359**BW 1 S21402. CUR*SE*USD. REF*SI*123456. REF*PK*456789. NTE*GEN*SHIP UPS N1*SU*YOUR COMPANY NAME. Transaction start record. Invoice number, P.O. number and date. Currency in U.S. dollars. SID #. (Must Match SID number on the corresponding 856 Advance Ship Notice.) Packing slip number. General Note, any NTE01 value accepted Supplier. N3*1234 NE YOUR STREET. Supplier Address. N4*YOUR TOWN*OR*12345. N1*ST*PORTLAND TRUCK PLANT*92*001. DTM*011*950719 IT1*001*20*EA*30.89**BP*279351*PO*BW 1 S21402*PL*123. NTE*GEN*SHIP UPS ITA*C*AI*DL*06***4978. TDS*66758. Supplier s City, State/Province, zip code. Ship-to Address/Receiving location code. Ship Date. Quantity, unit price, buyer part number, P.O. number. Line Note, any NTE01 value accepted Delivery charge to be paid by customer. Total invoice amount. CAD*A***UPSE*UNITED PARCEL SERVICE**BM*123456789. Ship UPS air. Bill of lading number = 123456789 CTT*1**159*LB. SE*16*000035555. Transaction totals, 1 line item. Transaction end record.