Lowe's
/
Invoice
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Lowe's. Contact Lowe's for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Lowe's logo

X12 810 Invoice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/lowes/invoice/01GWA5RJ33D93BCNFQPSPDDKFM
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
NTE
030
Note/Special Instruction
Max use 100
Optional
CUR
040
Currency
Max use 1
Required
N1 Loop
ITD
130
Terms of Sale/Deferred Terms of Sale
Max use 1
Required
DTM
140
Date/Time Reference
Max use 10
Required
FOB
150
F.O.B. Related Instructions
Max use 1
Required
summary
TDS
010
Total Monetary Value Summary
Max use 1
Required
TXI
020
Tax Information
Max use 10
Optional
CAD
030
Carrier Detail
Max use 1
Required
SAC Loop
CTT
070
Transaction Totals
Max use 1
Required
SE
080
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
810
Invoice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Usage notes

Example:

BIG2004070125734820040630123456789***DR\

810 TURN AROUND INFORMATION:
The Purchase Order transmitted in the BEG-03 of the 850 PO must be returned in the BIG-04 field of the 810 invoice.

Example
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG01 is the invoice issue date.
BIG-02
76
Invoice Number
Required
String (AN)
Min 1Max 22

Identifying number assigned by issuer

Usage notes

Lowe's Payables system can only handle a 10-digit invoice number. If you send more than 10 digits the invoice number will be truncated.

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG03 is the date assigned by the purchaser to purchase order.
BIG-04
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Lowe's purchase order number can be up to 9 digits.

BIG-07
640
Transaction Type Code
Optional
Identifier (ID)

Code specifying the type of transaction

  • BIG07 is used only to further define the type of invoice when needed.
Usage notes

If no value is sent, we will default to DR.

CR
Credit Memo
DR
Debit Memo
ME
Memorandum
NTE
030
Heading > NTE

Note/Special Instruction

OptionalMax use 100

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

Example:

NTEGEN1ZE445120311631005\

Example
NTE-01
363
Note Reference Code
Required
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

GEN
Entire Transaction Set
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

CUR
040
Heading > CUR

Currency

RequiredMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Usage notes

The currency code used is the three letter ISO 4217 international standard code (USD/CAD/MXN).

Example:

CURSEUSD\

810 TURN AROUND INFORMATION:
You must return the CUR segment, just as you receive it, in the 850 purchase order on the 810 invoice.

Example
CUR-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SE
Selling Party
CUR-02
100
Currency Code
Required
Identifier (ID)
Min 3Max 3

Code (Standard ISO) for country in whose currency the charges are specified

N1 Loop
RequiredMax >1
N1
070
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Example:

N1ST**92960
N1MA**92701
N1RI**9412345\

810 TURN AROUND INFORMATION:
In the first N1 segment you must return the N1-01 and N1-04 element of the 850 PO in the N1-01 and N1-04 of the 810 invoice. However, the N1-03 will have different qualifiers sent in the 810 invoice than what was received in the 850 PO.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

Usage notes

**Cross Dock Orders - Your incoming purchase order will reflect the
ship to store (ST) and the store that the goods are intended for (MA). On your 810 document to Lowe's, only send the N1 segment with the MA qualifier. If two N1 segments are transmitted (MA and ST), the N1 segment with the MA in N1-01 must be the second in the sequence of N1's.

N1ST**92960 (ship to RDC)
N1MA**92701 (ultimate store destination)

***If transmitted with the ST last, our invoice will pick up store #960 and the invoice will be kicked back for invalid store number.

MA
Party for whom Item is Ultimately Intended
RI
Remit To
ST
Ship To
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
94
Code assigned by the organization that is the ultimate destination of the transaction set
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Lowe's store number can be up to 5 digits

N3
090
Heading > N1 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Example:

N3*street address\

810 TURN AROUND INFORMATION:
You must turn around the N3 segment, as received in the 850 PO, in the N3 segment of the 810 invoice.

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
100
Heading > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

If country code specified in N404 is CAN, then the Canadian Standard Postal Format must be used. The postal code should be in upper case and expressed in the format of ANA NAN, where A = alpha and N =numeric. It should have one space between the first three and last three positions.

The country code used is the three letter ISO 3166 international standard code (USA/CAN/MEX).

Example:

N4citystate/provincepostal codecountry\

810 TURN AROUND INFORMATION:
You must turn around the N4 segment, as received in the 850 PO, in the N4 segment of the 810 invoice.

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Required
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Loop end
ITD
130
Heading > ITD

Terms of Sale/Deferred Terms of Sale

RequiredMax use >1

To specify terms of sale

Usage notes

When providing discount terms, ITD01=08, ITD02=3, ITD03 must be given with a value greater than zero, either ITD04 or ITD05 must be given, either ITD06 or ITD07 must be given, ITD08 must be given with a value greater than zero, and ITD12 must be given.

When there are no discount terms, ITD01=05, ITD02=3, either ITD06 or ITD07 must be given, and ITD12 must be given.

Example with Discount:
ITD08321516144****2% 15 NET 16\

Example with No Discount:
ITD05316No Discount Offered\

Example
ITD-01
336
Terms Type Code
Required
Identifier (ID)

Code identifying type of payment terms

  • If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
05
Discount Not Applicable
08
Basic Discount Offered
ITD-02
333
Terms Basis Date Code
Required
Identifier (ID)

Code identifying the beginning of the terms period

3
Invoice Date
ITD-03
338
Terms Discount Percent
Optional
Decimal number (R)
Min 1Max 6

Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date

Usage notes

If the discount is 2% this field should contain '2'.

ITD-04
370
Terms Discount Due Date
Optional
Date (DT)
CCYYMMDD format

Date payment is due if discount is to be earned expressed in format CCYYMMDD

Usage notes

If Lowe's receives a Terms discount, the Terms Discount Due Date(ITD04) or Terms Discount Days (ITD05) must be used. Do not use both.

ITD-05
351
Terms Discount Days Due
Optional
Numeric (N0)
Min 1Max 3

Number of days in the terms discount period by which payment is due if terms discount is earned

Usage notes

If Lowe's receives a Terms discount, use the number of days from invoice date to discount due date. Terms Discount Due Date (ITD04) can be used instead. Do not use both

ITD-06
446
Terms Net Due Date
Optional
Date (DT)
CCYYMMDD format

Date when total invoice amount becomes due expressed in format CCYYMMDD

Usage notes

Use Terms Net Due Date (ITD06) or Terms Net Days Due (ITD07), Do not use both. One of these elements MUST be present on ALL invoices.

ITD-07
386
Terms Net Days
Optional
Numeric (N0)
Min 1Max 3

Number of days until total invoice amount is due (discount not applicable)

Usage notes

Use number of days from invoice date (BIG01) to due date. Terms NetDue Date (ITD06) can be used instead. Do not use both.

ITD-08
362
Terms Discount Amount
Optional
Numeric (N2)
Min 1Max 10

Total amount of terms discount

Usage notes

Total amount of terms discount. If you offer Lowe's a terms discount, the amount of the discount must be present.

ITD-12
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
140
Heading > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Example:

DTM01120040701
DTM00820040630\

810 TURN AROUND INFORMATION:
The information received from the 850 DTM is not automatically returned in the 810 invoice. The qualifiers change from the 850 to the 810 invoice.

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

008
Purchase Order Received
011
Shipped
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

FOB
150
Heading > FOB

F.O.B. Related Instructions

RequiredMax use 1

To specify transportation instructions relating to shipment

Usage notes

Example:

FOB*PC\

810 TURN AROUND INFORMATION:
Please return the FOB segment, just as you received it, in the FOB segment of the 850 purchase order.

Example
FOB-01
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

  • FOB01 indicates which party will pay the carrier.
Usage notes

Code should match the code received on Lowe's PO. If 'PC' is used, there must be a SAC segment containing the freight charges. Freight charges CANNOT be transmitted to Lowe's as a line item. If 'CF' is used, there must be a SAC segment containing the freight allowance.

CC
Collect
CF
Collect, Freight Credited Back to Customer
PC
Prepaid but Charged to Customer
PP
Prepaid (by Seller)
Heading end

Detail

IT1 Loop
RequiredMax >1
IT1
010
Detail > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions

Usage notes

Example:

IT1120EA3.25CB40971UK*00123456789012\

810 TURN AROUND INFORMATION:
We prefer that you return the same information that you received in the PO1 segment of the 850 in the IT1 segment of the 810. However, the only fields that are mandatory in the 810 are the first seven fields,
through the Lowe's item number.

Depending on the country you are shipping the product to, remember any one item number could have multiple model numbers. Please remember to fill the order using your model number and invoice Lowe'susing Lowe's item number.
If you are not receiving any model numbers on your EDI POs, contact Lowe's EDI Analyst. If you have a model number missing or incorrect, your salesperson should contact Lowe's Merchandising to get your model number entered or corrected.

Example
If either Product/Service ID Qualifier (IT1-08) or Product/Service ID (IT1-09) is present, then the other is required
If either Product/Service ID Qualifier (IT1-10) or Product/Service ID (IT1-11) is present, then the other is required
IT1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • IT101 is the purchase order line item identification.
IT1-02
358
Quantity Invoiced
Required
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

IT1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

Unit of measure should match the unit of measure indicated on the purchase order.

IT1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

Please be sure you understand pricing for your product before you begin sending your production invoices.

IT1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
CB
Buyer's Catalog Number
IT1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Always use the Lowe's SKU that is provided on the Lowe's purchase order.

IT1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

VC
Vendor's (Seller's) Catalog Number
IT1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

IT1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

UK
U.P.C./EAN Shipping Container Code (1-2-5-5-1)
IT1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PID Loop
RequiredMax >1
PID
060
Detail > IT1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Usage notes

The EDI 850 PIDF segment includes the Item Description and must be echoed back in the EDI 810 Invoice(PID01=F).
PID
F****LIGHT BULBS\

An additional PID segment (PID01=X) is required for Environmental Protection Agency (EPA) formaldehyde compliance reporting. The following are the options and PID syntax examples.

These are the six formaldehyde compliance options:

Non-Compliant
PIDX**VIGM04COMPFE*0\

Phase 1 Compliant (California Air Resources Board (CARB) Act of 2009 - Phase 1) PIDX**VIGM04COMPFE*1\

Phase 2 Compliant (California Air Resources Board (CARB) Act of 2010 - Phase 2) PIDX**VIGM04COMPFE*2\

No Added Formaldehyde
PIDX**VIGM04COMPFE*3\

Ultra low Emission Formaldehyde Use (ULEF)
PIDX**VIGM04COMPFE*4\

TSCA (Toxic Substances Control Act) Title VI pertains to the Formaldehyde Standards for Composite Wood Products Act PIDX**VIGM04COMPTS*5\

When a product is formaldehyde compliant for both CARB Act of 2010 - Phase 2 and TSCA EPA rulings, send
PIDX**VIGM04COMPTS*5\

Example
If Product Description Code (PID-04) is present, then Agency Qualifier Code (PID-03) is required
PID-01
349
Item Description Type
Required
Identifier (ID)

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
F
Free-form
X
Semi-structured (Code and Text)
PID-03
559
Agency Qualifier Code
Optional
Identifier (ID)

Code identifying the agency assigning the code values

  • Use PID03 to indicate the organization that publishes the code list being referred to.
VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
PID-04
751
Product Description Code
Optional
String (AN)
Min 1Max 12

A code from an industry code list which provides specific data about a product characteristic

  • PID04 should be used for industry-specific product description codes.
Usage notes

PID04 Code Breakdown
Positions 1-2: GM=General Merchandise
Positions 3-4: 04=Format/Option Code
Positions 5-8: COMP=Regulatory Compliance
Positions 9-10: FE=CARB or TS=TSCA

PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Usage notes

Example:

TDS*7175\

Example
TDS-01
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Usage notes

Total invoice amount due. This total should include any allowance or charge amounts, but will not reflect any terms discounts given in the ITD (payment terms) segment.

TXI
020
Summary > TXI

Tax Information

OptionalMax use 10

To specify tax information

Usage notes

The TXI segment is used for Canada and Mexico tax.

Canada
When TXI01=CG, TXI02=Canada GST tax.
When TXI01=OH, TXI02=Quebec Canada QST tax.
When TXI01=PG, TXI02=Canada Provincial tax.
When TXI01=ZZ. TXI02=Canada HST tax.

Mexico
When TXI01=VA, TXI02=Mexico IVA (VAT tax).

The TXI-02 must be sent as no more than 18 whole number positions and up to 2 decimals.

These elements are only applicable for Canada: TXI03, TXI04, TXI05, and TXI09.

Example:
TXICG3.905*123456789 - GST
TXI
OH*7.34
.25
****
1234567890 - QST
TXIPG1.847.6VDAB*123456789012345 - PST
TXI
ZZ*9.10
12.18*****123456789 - HST
TXI
VA*8.35\ - VAT

Example
If either Tax Jurisdiction Code Qualifier (TXI-04) or Tax Jurisdiction Code (TXI-05) is present, then the other is required
TXI-01
963
Tax Type Code
Required
Identifier (ID)

Code specifying the type of tax

CG
Federal Value-added Tax (GST) on Goods
OH
Other Taxes
PG
State or Provincial Tax on Goods
VA
Value Added Tax
ZZ
Mutually Defined
TXI-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • TXI02 is the monetary amount of the tax.
TXI-03
954
Percent
Optional
Decimal number (R)
Min 1Max 10

Percentage expressed as a decimal

  • TXI03 is the tax percent expressed as a decimal.
Usage notes

XI03 is only applicable for Canada. This field should include the tax rate percent.
For example, a 5% tax should be expressed as 5 and 7.6% tax should be expressed as 7.6.

TXI-04
955
Tax Jurisdiction Code Qualifier
Optional
Identifier (ID)

Code identifying the source of the data used in tax jurisdiction code

Usage notes

TXI04 is only applicable for Canada.
When TXI01=PG, TXI04 and TXI05 must be populated (only PST).
When TXI01=CG, OH, or ZZ, TXI04 and TXI05 should not be sent.
When TXI04=VD, TXI05 must be included. Only a value of VD can be sent in TXI04.

VD
Vendor defined
TXI-05
956
Tax Jurisdiction Code
Optional
String (AN)

Code identifying the taxing jurisdiction

Usage notes

TXI05 is only applicable for Canada.
TXI05=2 character postal abbreviation for the Canadian Province:
AB=Alberta
BC=British Columbia
MB=Manitoba
NB=New Brunswick
NL=Newfoundland and Labrador
NT=Northwest Territories
NS=Nova Scotia
NU=Nunavut
ON=Ontario
PE=Prince Edward Island
SK=Saskatchewan
YT=Yukon

AB
Alberta
BC
British Columbia
MB
Manitoba
NB
New Brunswick
NL
Newfoundland and Labrador
NS
Nova Scotia
NT
Northwest Territories
NU
Nunavut
ON
Ontario
PE
Prince Edward Island
SK
Saskatchewan
YT
Yukon
TXI-09
325
Tax Identification Number
Optional
String (AN)
Min 1Max 20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number

Usage notes

TXI09 is only applicable for Canada.
If item is taxable (TXI02 is not 0), the tax registration ID is required.
The Tax Registration ID is only required for GST, HST, and QST taxes. The Tax ID is optional for PST.
When TXI01=CG (GST) or ZZ (HST), TXI09 should include a 9-digit number.
When TXI01=OH (QST), TXI09 should include a 10-digit number.
When TXI01=PG (PST), TXI09 should include a 15-digit number.

CAD
030
Summary > CAD

Carrier Detail

RequiredMax use 1

To specify transportation details for the transaction

Usage notes

Example:

CAD*ABCF
CAD
**ABC FREIGHT LINES\

810 TURN AROUND INFORMATION:
The TD5 segment of the 850 is an optional segment. If received in the 850 PO, you must return the SCAC code in the TD5-03 in the CAD-04 of the 810. If the TD5 isn't present in the 850, you must still supply the SCAC code in the CAD-04 or the carrier name in the CAD-05 of the 810 invoice because the CAD segment is mandatory on the 810 invoice.

Example
At least one of Standard Carrier Alpha Code (CAD-04) or Routing (CAD-05) is required
CAD-04
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

Usage notes

Standard Carrier Alpha Code (4 letter alpha code assigned to all freight carriers).

CAD-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

Name of carrier trucking company. Not necessary if SCAC code is given in CAD04.

SAC Loop
OptionalMax >1
SAC
040
Summary > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Usage notes

Example:
SACCD240675*06FREIGHT CHARGE\

810 TURN AROUND INFORMATION:
The information received from the 850 SAC is not automatically returned in the 810 invoice. The new store qualifier (SAC02) is just one of many codes that can be returned in the SAC of the 810 invoice.

Additional Information:
SAC02=H850 conveys Excise Tax for Hawaii and Alaska only.

SAC02=G090 conveys California Carpet Stewardship Assessment Fees.

For Special Order Sales POs, only the following SAC codes are permitted for the Invoice. If other SACcodes are submitted, the Invoice will reject.

  • C680 Environmental Protection Service
  • G090 California Carpet Stewardship Assessment Fee
  • H850 Excise Tax for Hawaii and Alaska only

The vendor’s SOS item should have all charges built into the cost of goods as approved by Lowe’sMerchandising Team. Upon receipt of a Lowe’s SOS PO, the vendor should ensure each line item on the PO encompasses all costs before submitting an order status. If an additional charge is realized, the vendor may contact the store to review the SOS PO or submit an Invalid Item data exception in the order status. When a data exception is submitted, the original PO must be canceled and a new PO released if the additional costs are approved by the store/customer.

Example
SAC-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

Code which indicates an allowance or charge for the service specified

  • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
Usage notes

An 'A' will indicate a reduction in the invoice amount. A 'C' will indicate a charge, or an increase in the invoice amount.

A
Allowance
C
Charge
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Required
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

A260
Advertising Allowance
A720
Broken Package Charge
B940
Cutting Charge
C000
Defective Allowance
C680
Environmental Protection Service
D240
Freight
D270
Fuel Surcharge
D500
Handling
D530
Hazardous Cargo Charge
E740
New Store Allowance
F180
Pallet
G090
Recovery Fee
G470
Restocking Charge
G870
Shrink-Wrap Charge
H000
Special Allowance
H850
Tax
SAC-05
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • SAC05 is the total amount for the service, promotion, allowance, or charge.
  • If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Usage notes

Amount of allowance or charge.

SAC-12
331
Allowance or Charge Method of Handling Code
Required
Identifier (ID)

Code indicating method of handling for an allowance or charge

Usage notes

If SAC 01 = 'A' the code here will be '02'.
If SAC 01 = 'C' the code here will be '06'.

02
Off Invoice
06
Charge to be Paid by Customer
SAC-15
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Description of allowance or charge.

SAC Loop end
ISS Loop
OptionalMax >1
ISS
060
Summary > ISS Loop > ISS

Invoice Shipment Summary

RequiredMax use 1

To specify summary details of total items shipped in terms of quantity, weight, and volume

Usage notes

Example:

ISS1PL
ISS2CA\

Above is an example of a shipment containing 1 pallet plus 2 cases.

Example
ISS-01
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

ISS-02
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
PL
Pallet/Unit Load
S9
Slip Sheet
ISS Loop end
CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of IT1 segments.
    If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Usage notes

Example:

CTT*1\

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
080
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

sample

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231101*0122*U*00401*000000001*0*T*>
GS*IN*SENDERGS*RECEIVERGS*20231101*012225*000000001*X*004010
ST*810*2275
BIG*20040701*257348*20040630*123456789***DR
NTE*GEN*1ZE445120311631005
CUR*SE*USD
N1*ST**92*960
N1*MA**92*701
N1*RI**94*12345
N3*street address
N4*NEY YORK*NY*11223*US
ITD*08*3*2**15**16*144****2% 15 NET 16
DTM*011*20040701
DTM*008*20040630
FOB*PC
IT1*1*20*EA*3.25**CB*40971***UK*00123456789012
PID*X**VI*GM04COMPFE*0
TDS*7175
TXI*CG*3.90*5******123456789
TXI*OH*7.34*.25******1234567890
TXI*PG*1.84*7.6*VD*AB****123456789012345
TXI*ZZ*9.10*12.18******123456789
TXI*VA*8.35
CAD****ABCF
SAC*C*D240***675*******06***FREIGHT CHARGE
ISS*1*PL
CTT*1
SE*26*2275
GE*1*000000001
IEA*1*000000001

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.