Electronic Data Interchange (EDI) Invoicing
810/824 Technical Guide
X12 Version 3040
Produced by Accounts Payable Intel Corporation
Rev 6.1 04/22/99
Rev 6.1 7/28/2006 2
Table of Contents HOW TO USE THIS GUIDE: ................................................................................................................................................................................................3
VAN INFORMATION.............................................................................................................................................................................................................3
TRANSACTION MAP ............................................................................................................................................................................................................3
SAMPLE INVOICE ..................................................................................................................................................................................................................4
810 MAPPING.........................................................................................................................................................................................................................7
HEADER INFORMATION: SEGMENT LEVEL ..........................................................................................................................................................................8 DETAIL INFORMATION: SEGMENT LEVEL............................................................................................................................................................................9 SUMMARY INFORMATION: SEGMENT LEVEL......................................................................................................................................................................9 HEADER INFORMATION: ELEMENT LEVEL........................................................................................................................................................................10 DETAIL INFORMATION: ELEMENT LEVEL ..........................................................................................................................................................................14 SUMMARY INFORMATION: ELEMENT LEVEL...................................................................................................................................................................16
824 MAPPING......................................................................................................................................................................................................................20
HEADER INFORMATION: SEGMENT LEVEL ......................................................................................................................................................................21 DETAIL INFORMATION: SEGMENT LEVEL.........................................................................................................................................................................21 SUMMARY INFORMATION: SEGMENT LEVEL..................................................................................................................................................................21 HEADER INFORMATION: ELEMENT LEVEL........................................................................................................................................................................22 DETAIL INFORMATION: ELEMENT LEVEL ..........................................................................................................................................................................23 DETAIL INFORMATION: ELEMENT LEVEL ..........................................................................................................................................................................23
Rev 6.1 7/28/2006 3
How to use this guide: This guide contains technical information and is intended to be used as a resource during the implementation of EDI invoicing. Included are Intel’s 810 and 824 mapping structures. For definitions and Intel contacts refer to the Implementation guide.
VAN Information VAN Name IBM Global Services Version used ANSI X-12, 3040 Alias Name: 047897855MAP (production mail box) 047897855MAT (Test mail box) Qualifier ID 14 IBM GS ID IMAP User ID IMAP001 (prod) IMAP002 (test) Contact Allen Amabisca E:mail [email protected] Phone 503-696-3421
Transaction map The transaction map beginning on the next page is included as an example of a typical invoice mapped to the 810 standard for AP/FA. It provides the 810 mapping segment, the ASC X12 Format, and the sample invoice content in numbered detail.
Sample Invoice Acme Company
We are Your Company!! 123 Main Street Main City, Oregon 97000 503.555.1234 Fax 503.555.9999
INVOICE NO: 1001
DATE: February 21, 1996
REFERENCE INVOICE: 999
To: Ship To: Ship From: Intel Corporation Intel Corporation Acme Company P.O. Box 1000 5300 N.E. Elam Young Parkway 987 Front Ave. Hillsboro, OR 97124-1000 Hillsboro, OR 97124 Main City, OR 97000
SALESPERSON P.O. NUMBER DATE SHIPPED SHIPPED VIA F.O.B. POINT TERMS JPM MQE00012345 1/31/96 F ABC Truck 2% 10, net 30
QUANTITY UNIT DESCRIPTION UNIT PRICE AMOUNT
A 10 Ea #X1234 Widgets $ 5.00 $ 50.00
B 5 Ea #Y9999 Wombats $ 20.00 $ 100.00
C 1 Ea Rush Order Service Charge $ 25.00 $ 25.00
$ 0.00
$ 0.00
SUBTOTAL $ 175.00
E SALES TAX $ 10.00
G SHIPPING & HANDLING $ 30.00
D TOTAL DUE $ 215.00
Make all checks payable to: Acme Company 987 Front Ave. Main City, OR 97000
If you have any questions concerning this invoice, call: Joe Acme, (503) 555-4321
THANK YOU FOR YOUR BUSINESS!
Rev 6.1 7/28/2006 4
Rev 6.1 7/28/2006 5
Intel 810 map example
Segment ASC X12 Format Sample Invoice Content HEADER Transaction Set Header, ST
ST*810*0001N/L
Beginning Segment for Invoice, BIG
BIG*960221*1001**MQE00012345 N/L 1 2 3
Invoice Date: February 21, 1996 Invoice Number: 1001 Purchase Order Number: MQE00012345 Document Type (not on invoice) DI, CR, DR
Currency, CUR CUR*SE*USD N/L Currency information (not on invoice) Name, Address, Geography, N1, N2, N3 & N4
N1*BT*Intel Corporation*92*ITL1 N/L N3*PO Box 1000 N/L N4*Hillsboro*OR*97124*USA N/L
4 Bill to: Intel Corporation ID Code Qual: 92 (not on invoice) ID Code: ITL1 (not on invoice) Address: PO Box 1000 Hillsboro, OR 97124-1000
N1*ST*Intel Corporation N/L N3*5300 NE Elam Young Parkway N/L N4*Hillsboro*OR*97124*USA N/L
5 Ship to: Intel Corporation Address: 5300 NE Elam Young Parkway Hillsboro, OR 97124
N1*SF*Acme Co. N3*987 Front Ave. N/L N4*Main City*OR*97000 N/L
5 Ship From: Acme Co. Address: 987 Front Ave. Main City, OR 97000
Admin. Comm. Contact, PER
PER*AD*Joe Acme*TE*5035554321N/L 6 Contact Name: Joe Acme Telephone: 503.555.4321
Terms of Sale, ITD ITD*01*3*2**10**30 N/L 7 Terms of Sale: 2% 10, net 30 days Reference REF*OI*999 N/L 8 Reference Invoice number 999 Ship Date DTM*O11*960131 N/L 9 Date Shipped 1/31/1996 Quantity Unit of
Measure Unit Price
Product Desc
Part #
DETAIL (Line Item) Invoice data, IT1
IT1*1*10*EA*5.00**BP*X1234 N/L A 10 EA 5.00 Widgets X1234
Product Description, PID
PID*F *Widgets N/L A “F” for free form message. Product Description: Widgets
Reference Number, REF
REF*GL*123456789*AMT5000 N/L A Reference Number: General Ledger number (not on invoice) Distribution description: Amount
Invoice data, IT1 (Line Item Detail)
IT1*1*5*EA*20.00**BP*Y9999 N/L B 5 EA 20.00 Wombats Y9999
Product Description, PID
PID*F^Wombats N/L B Product Description: Wombats
Reference Number, REF
REF*GL*123456789*AMT10000 N/L B Reference Number: General Ledger number (not on invoice) Distribution description: Amount
SUMMARY Total Invoice Amount, TDS
TDS*19000 N/L D Total Due: 190.00 (Implied 2 place decimal point)
Tax Info, TXI TXI*ST*10 00N/L E Sales Tax Due: 10.00 Carrier Detail, CAD CAD*M****ABC Truck N/L F Carrier Info: ABC Truck Special Handling/Freight
SAC*C*D240*3000*Freight G Shipping and Handling $30.00
Transaction Totals, CTT CTT*2 N/L Transaction Set Trailer SE*27*000001 N/L
Rev 6.1 7/28/2006 6
N/L = Segment Terminator Items not normally sent on an invoice, but sent on the 810 invoice transaction:
810 element Element Value Description Data Location CUR02 USD Currency code EDI code N103 92 Buyer code, used
when N101=BT EDI code
N104 ITL1 - USA
Intel ID codes, used when N101=BT
Intel provides to supplier (only for non-RAPID based PO’s)
REF02 numeric value General Ledger number
Intel provides to supplier (On RAPID based purchase orders)
IT101 numeric value INTEL PO line number (0001 Format)
Intel provides to supplier (On RAPID based purchase orders)
810 Mapping
Intel Corporation Corporate EDI Group
810 INVOICE - INBOUND TECHNICAL MAP X12 VERSION 003040
This standard provides the format and establishes the data contents of an invoice transaction set. The invoice transaction set provides for customary and established business and industry practice relative to the billing for goods and services provided. Intel Corporation Contact EC/EDI Coordinator
E-mail [email protected] Phone 503-264-7851
Rev 6.1 7/28/2006 7
HEADER INFORMATION: Segment Level ST Transaction Set Header MANDATORY BIG Beginning Segment for Invoice MANDATORY CUR Currency MANDATORY REF Other Invoice Reference OPTIONAL PER Admin. Communications Contact OPTIONAL
N1 Name Information MANDATORY N1 LOOP N3 Address Information MANDATORY N1 LOOP N4 Geographic Location Information MANDATORY N1 LOOP
ITD Terms of Sale OPTIONAL DTM Ship Date MANDATORY
Rev 6.1 7/28/2006 8
DETAIL INFORMATION: Segment Level
IT1 Invoice Baseline Item Data MANDATORY IT1 LOOP PID Product/Item Description MANDATORY IT1 LOOP REF Reference Numbers OPTIONAL IT1 LOOP
SUMMARY INFORMATION: Segment Level
TDS Total Monetary Value Summary MANDATORY TXI Tax Information OPTIONAL CAD Carrier Detail OPTIONAL SAC Freight Information OPTIONAL CTT Transaction Totals MANDATORY SE Transaction Set Trailer MANDATORY
Rev 6.1 7/28/2006 9
HEADER INFORMATION: Element Level
ST Transaction Set Header MANDATORY
Purpose: To indicate start of a transaction set and to assign a control number. Max Use: 1
ST01 Transaction Set ID Code ID 3/3 M ‘810’ ST02 Trans Set Ctrl Number AN 4/9 M Assigned by translator
BIG Beginning Segment For Invoice MANDATORY
Purpose: To indicate beginning of an invoice transaction and transmit identifying invoice number and purchase order number and date. Max Use: 1
BIG01 Invoice Date DT 6/6 M Issue Date (RAPID date) YYMMDD BIG02 Invoice Number AN 1/22 M Sender’s Invoice # BIG04 Purchase Order Number AN 1/22 M Purchase #/Contract Number BIG05 PO Release Number AN 1/30 O PO Release Number BIG07 Transaction Type Code AA 1/2 M DI - Debit Invoice CR - Credit Memo ** CI - Credit Invoice ** DR - Debit Memo BIG10 Invoice Number Credited AN 1/22 O If BIG07 is CR or CI, then BIG10 provides invoice number to be credited
Note: Intel will reject any invoices without an invoice number and a purchase order or contract number. ** For credit line Processing see IT102 or IT104 and TDS01
CUR Currency MANDATORY
Purpose: To identify the Currency of the transaction. Max Use: 1
CUR01 Entity Identifier Code AN 2/2 M ‘SE’ for Seller CUR02 Currency Code AN 3/3 M ‘USD’ For US Dollars Rev 6.1 7/28/2006 10
Rev 6.1 7/28/2006 11
Note: Intel will accept any valid CUR02 003040 standard code values.
HEADER INFORMATION: Element Level(contd.)
REF Reference OPTIONAL
Purpose: To identify another invoice for cross reference. Max Use: 1
REF01 Reference Num. Qual AN 2/2 M ‘OI’ REF02 Invoice Number AN 1/30 M Sender’s other Invoice #
Note: This is used to reference a different Intel invoice only.
PER Admin. Comm. Contact OPTIONAL
Purpose: To identify a person or office to whom admin. communications should be directed. Max Use: 1
PER01 Contact Func code AN 2/2 C ‘AD’ for Acctg Dept. ‘AF’ for Approval Contact PER02 Contact Name AN 1/35 O Literal for Contact Name and M/S # PER03 Comm# Qual AN 2/2 C ‘TE’ for Telephone PER04 Communication Number AN 1/80 C Telephone #
Note: Input the contact name here if any questions arise regarding this transaction.
N1 Name MANDATORY
Purpose: To identify a party by type of organization, name or code. Max Use: 1
N101 Entity Identifier Code ID 2/2 M ‘BT’ for Bill-To Info ‘ST’ for Ship-To Info ‘SF’ for Ship-From Info. N102 Name Text AN 1/35 M Literal for company name N103 Identification Code Qual ID 2/2 O ‘92’ for Assigned By Buyer N104 Identification Code AN 2/4 M ‘ITL1’ - for USA Only Note: Intel expects two occurrences of the N1 loop in the order specified. N1 loop is used for Bill-To and Ship-To Information N103 & N104 elements are used only for Bill-To Information.
Rev 6.1 7/28/2006 12
N2 segment is no longer requested by Intel.
HEADER INFORMATION: Element Level(contd.)
N3 Address Information MANDATORY
Purpose: To specify the location of the Bill-to, Ship-to, and Ship From addresses. Max Use: 1
N301 Address Info Line1 AN 1/35 M Address Line1 N302 Address Info Line2 AN 1/35 M Address Line2
Note: N3 segment is used for ‘BT’, and ‘ST’.
N4 Geographic Location MANDATORY
Purpose: To specify the geographic location of the Bill-to, Ship-to, and Ship From addresses. Max Use: 1
N401 City Name AN 2/30 M City Name N402 State or Province Code AN 2/2 M State Name N403 Postal Code AN 2/9 M Postal Code for Zip Code N404 Country Code AN 2/3 M Country Code
Note: N4 segment is used for ‘BT’ and ‘ST’. N404 segment description for the US is ‘USA’
ITD Terms Of Sale OPTIONAL
Purpose: To specify terms of sale. Max Use: 1
ITD01 Terms Type Code AN 2/2 M ‘01’ for Basic ‘08’ for Basic Discount Offered ITD02 Basis Date Code AN 1/2 C ‘3’ for Invoice Date ITD03 Terms Discount % R 1/6 C Discount % ITD05 Terms Disc Days Due N0 1/3 C Discount earned ITD07 Terms Net Days N0 1/3 C Net number of days
Note: If “01” is not present in ITD01, this entire element is skipped. Defaults to N30 Note: If “08” is present in ITD01, then ITD03, ITD05, and ITD07 are mandatory fields
Rev 6.1 7/28/2006 13
HEADER INFORMATION: Element Level(contd.)
DTM Invoice Date OPTIONAL
Purpose: To specify invoice date. Max Use: 1
DTM01 Number Qualifier AN 3/3 M ‘003” Invoice Date ‘011’ Shipped Date ‘173’ Week Ending Date DTM02 Invoice Date DT 6/6 M ‘YYMMDD’ DTM05 Century N0 2/2 O “CC”
Rev 6.1 7/28/2006 14
DETAIL INFORMATION: Element Level
IT1 Invoice Baseline Item Data MANDATORY
Purpose: To specify basic and most frequently used line item data for the invoice. Max Use: 200,000
IT101 Assigned Identification N 1/4 M Intel PO Line # (0001 Format) * IT102 Quantity Invoiced R 1/10 M Number Of Units Invoiced, Quantity ** IT103 Unit of Measurement AN 2/2 M Unit Of Measure IT104 Unit Price R 1/14 M Price/Unit Of Product ** IT106 Product Id Qualifier ID 2/2 M ‘BP or IN’ for Buyer’s Part Inventory IT107 Product Id AN 1/30 M Intel Inventory # IT108 Vendor Part Qualifier ID 2/2 M ‘VN or MG’ for Vendor Item # IT109 Vendor Product ID AN 1/30 M Vendor Inventory # IT110 Vendor Part Number ID 2/2 M ‘VP or VA’ for Vendor Part Number IT111 Vendor Part Number AN 1/30 M Vendor Part Number IT112 Product ID Qualifier AN 2/2 O ‘PI’ for Product ID IT113 Product ID AN 1/30 O Product ID# IT114 PO Line Qualifier ID 2/2 M ‘PL’ for PO Line # * IT115 PO Line # N 1/4 M 4 Digit PO Line # (0001) * IT116 PO Line Release Info Qual. ID 2/2 M ‘RN’ for Release Info. IT117 PO Line Release # N 1/3 M Release Number from PO IT118 Services Rendered ID 2/2 O ‘SV’ for Services Rendered IT119 Employee Name AN 1/30 O Contract Employee Name * Intel PO line number is required on either IT101 or IT114 and IT115. For NON PO 810 invoice input invoice line number on IT101 or IT114 and IT115. ** For credit line processing either IT102 or IT104 must be a credit. ** For Credit Memo processing both IT102 and IT104 must be a debit. Either the IT106 and IT107, or IT108 and IT109, or IT110 and IT111 are required. IT114 through IT117 are for AMAP PO invoicing only.
PID Product/Item Description MANDATORY
Purpose: To describe a part in free format. Max Use: 1
PID01 Item description type AN 1/1 M ‘F’ for free form message PID02 Product/Process Char. Code AN 2/3 M Product/Process Characteristic Code PID05 Product description AN 1/80 M Description Provided (Supplier part or Service Provided)
Rev 6.1 7/28/2006 15
Rev 6.1 7/28/2006 16
* Example of PID05: MMDDYY, XXXX, AAAAAAAAAA……etc.
DETAIL INFORMATION: Element Level, (cont.)
REF Reference Numbers OPTIONAL
Purpose: To identify general ledger account number & payment distribution (%, $, Qty). Max Use: 3
REF01 Reference Num. Qual AN 2/2 C ‘11’ for Account Number REF02 Reference Number NN 1/30 C Account Number 100XXXXXXXXX Capital Account Number 100XXXXXXXXXXXX REF03 Description AN 1/80 C %, $, Qty distribution description
Note: You are required to have the GL number if you receive it from Intel. This segment may be present up to 10 times depending on the user’s need. Split type = QTY, AMT or PCT Split value is numeric: QTY is 15 characters w/ 4 decimal places AMT is 15 characters w/ 2 decimal places PCT is 11 characters w/ 8 decimal places
Rev 6.1 7/28/2006 17
SUMMARY INFORMATION: Element Level
TDS Total Monetary Value Summary MANDATORY
Purpose: To specify the total invoice amount. Max Use: 1
TDS01 Total Invoice Amount N2 1/10 M Monetary Amount
Note: N2 = is an implied 2 decimals
TXI Tax Information OPTIONAL
Purpose: To specify tax information. Max Use: 1
TXI01 Tax Type Code ID 2/2 M ‘ST’ for Sales Tax TXI02 Monetary Amount R 1/15 M Monetary Amount TXI03 Tax Percentage R 1/10 C Tax Percentage TXI04 Tax Code Qualifier AN 1/2 C ‘VD” Vendor Defined TXI05 Tax Jurisdiction Code AN 1/80 C Taxing Jurisdiction
CAD Carrier Detail OPTIONAL
Purpose: To specify transportation details of the transaction. Max Use: 1
CAD01 Transportation Method AN 1/2 O ‘A’ for Air, ‘M’ for Motor; ‘R’ for Rail CAD03 Equipment # AN 1/10 O Equipment # CAD04 Std Carr Alpha Code AN 2/4 C Carrier code CAD05 Routing AN 1/35 C Carrier name
Note: If CAD01=‘R’, CAD03 is needed. CADO4 and CAD05 ARE Conditional upon CAD01
Rev 6.1 7/28/2006 18
SUMMARY INFORMATION: Element Level (cont.)
SAC Special Handling Charges & Freight OPTIONAL
Purpose: To provide freight charges at the total invoice level. Max Use: 2
SAC01 Allowance/chg Indicator AN 1/1 M ‘C’ for charges SAC02 Serv/Promo chg code AN 4/4 C Service Charge code ‘D240’ for Freight SAC05 Amount AN 1/15 C Charge Amount SAC15 Description AN 1/80 C Charge Description ‘Freight’ for actual description
Note: This segment is utilized for freight only. Trading partners are requested to discuss this matter with Intel users. The code to be used is D240 for Freight. In the SAC15 please input the description “Freight”, if SAC02 code is D240.
CTT Transaction Totals MANDATORY
Purpose: To transmit a total of number of items in the invoice transaction. Max Use: 1
CTT01 Number of Line Items N0 1/6 M Total number of items
SE Transaction Set Trailer MANDATORY
Purpose: To indicate end of a transaction set and to provide a count of transmitted segments. Max Use: 1
SE01 Number of segments N0 1/10 M Computed by translator SE02 Trans set control num. AN 4/9 M Assigned by translator
Rev 6.1 7/28/2006 19
824 Mapping
Intel Corporation Corporate EDI Group
824 Application Advice - OUTBOUND X12 VERSION 003040
This standard provides the format and establishes the data contents of an Application Advice transaction set. This transaction set provides for customary and established business and industry practice relative to the response against invoice transactions.
Rev 6.1 7/28/2006 20
HEADER INFORMATION: Segment Level
ST Transaction Set Header MANDATORY BGN Beginning Segment MANDATORY DTM Date/Time Reference MANDATORY
DETAIL INFORMATION: Segment Level
OTI Original Trans Identification MANDATORY OTI LOOP TED Tech Error Description MANDATORY TED LOOP
SUMMARY INFORMATION: Segment Level
SE Transaction Set Trailer MANDATORY
Rev 6.1 7/28/2006 21
HEADER INFORMATION: Element Level
ST Transaction Set Header MANDATORY
Purpose: To indicate start of a transaction set and to assign a control number. Max Use: 1
ST01 Transaction Set ID Code ID 3/3 M ‘824’ ST02 Trans Set Ctrl Number AN 4/9 M Assigned by translator
BGN Beginning Segment MANDATORY
Purpose: To indicate beginning of an Application Advice transaction set. Max Use: 1
BGN01 Purpose Code AN 2/2 M ‘11’ to respond; ‘15’ to resubmit BGN02 Reference Number AN 1/30 M Interchange ctrl# from transaction BGN03 Advice Date YY 6/6 M Date processed BGN04 Advice Time AN 4/4 M Time processed
Note: BGN01 indicates the type of error. ‘11’ means system reject. The incoming file could not be recognized. ‘15’ means A/P processor created 824 to record invoice error.
DTM Date/Time Reference MANDATORY
Purpose: To indicate the century. Max Use: 1
DTM01 Date/Time Qualifier NN 3/3 M ‘097’ transaction created DTM02 Invoice Date DT 6/6 M ‘YYMMDD’ DTM05 Century N0 2/2 M ‘CC’
Note: DTM01 indicates the date the transaction processed. See BGN03 segment.
Rev 6.1 7/28/2006 22
DETAIL INFORMATION: Element Level
OTI Original Trans Identification MANDATORY
Purpose: To identify the edited transaction set. Max Use: 200,000
OTI01 Appl Ack Code AN 1/2 M ‘TR’ for Trans Rejection OTI02 Ref Num. Qual AN 2/2 M ‘IK’ for Invoice number OTI03 Reference Number AN 1/30 M Invoice# from BIG02 OTI08 Group Ctrl Number N0 1/9 C GS06 from transaction OTI09 Trans Ctrl Number AN 4/9 C ST02 from transaction OTI10 Trans Identifier Code AN 3/3 M ‘810’
Note: OTI08 must be present if OTI09 is present. TED Tech Error Description MANDATORY
Purpose: To identify the error and, if feasible, the erroneous segment, element, etc. Max Use: 200,000
TED01 Appl error code AN 1/3 M Application error code TED02 Free form message AN 1/60 M Free form message TED03 Segment Id Code AN 2/3 O Segment Id Code TED05 Element position N0 1/2 O Element Position In Segment
DETAIL INFORMATION: Element Level
SE Transaction Set Trailer MANDATORY
Purpose: To indicate end of a transaction set and to provide a count of transmitted segments. Max Use: 1
SE01 Number of segments N0 1/10 M Computed by translator Rev 6.1 7/28/2006 23
Rev 6.1 7/28/2006 24
. SE02 Trans set control num AN 4/9 M Assigned by translator